quest-complete

Validate completed phases, update quest records, emit completion events, and archive quests.

2|5|Updated Jan 2, 2026
One-click install
npx skills add https://github.com/whoabuddy/claude-knowledge --skill quest-complete
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: quest-complete
Source: https://github.com/whoabuddy/claude-knowledge/tree/main/claude-config/skills/quest-complete
Command: npx skills add https://github.com/whoabuddy/claude-knowledge --skill quest-complete

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill offers a reliable end-to-end way to transition an active quest to completed by validating all phases, updating status and state logs, emitting a completion event, and archiving the quest for future reference.

Core Features & Use Cases

  • Validate that all phases are completed by reading PHASES.md and ensuring each phase status is completed.
  • Update QUEST.md to mark Status as completed and record the completion timestamp.
  • Update STATE.md by adding the completion entry to the decisions log and recording final stats.
  • Emit quest_completed events via the provided script, enabling downstream automations and dashboards.
  • Archive the completed quest under .planning/archive/<quest-name>/ and preserve history for auditing.

Quick Start

Execute the /quest-complete command to finish the active quest, updating its status, logging results, emitting a completion event, and archiving it for future reference.

Frequently Asked Questions about quest-complete

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I mark a project workflow as complete and archive it?▼

To mark a workflow complete, the process validates all phases, updates status logs, emits a completion event, and archives the records under a designated directory for future reference.

What happens if not all phases are completed when I try to finish a quest?▼

If phases are incomplete, the completion process fails because the system enforces explicit checks by reading phase records to ensure every phase status is marked completed.

How do I emit completion events for downstream automations after a workflow finishes?▼

You emit completion events by executing the provided completion script, which deterministically triggers a completed event to enable downstream automations and dashboards.

Does quest completion require specific state and planning files?▼

Yes, quest completion requires specific files including phase records for validation, quest files for status updates, and state files for logging decisions and recording final stats.

Can I preserve the history and final stats of a completed project phase for auditing?▼

Yes, you can preserve history for auditing by archiving the completed quest under the planning archive directory, which updates state logs with the completion entry and final stats.