Plan Phase Skill
Research and create an executable plan for a quest phase.
Usage
code
/plan-phase Plan the current (next pending) phase /plan-phase 2 Plan a specific phase by number
Behavior
- •Read
.planning/QUEST.mdandPHASES.mdfor context - •Identify the target phase (next pending, or specified by number)
- •Optionally spawn a research subagent to explore the codebase or search the web for the phase domain
- •Spawn
quest-planneragent in phase planning mode with:- •Phase goal from PHASES.md
- •Quest context from QUEST.md
- •Relevant codebase patterns
- •Write the plan to
phases/NN-name/PLAN.mdusing structured XML task format - •Update PHASES.md phase status to
planned - •Update STATE.md with planning decisions
- •Emit
phase_plannedevent:bashcurl -s -X POST http://localhost:4011/event \ -H "Content-Type: application/json" \ -d '{"type":"phase_planned","questId":"<id>","phaseId":"<id>","phaseName":"<name>","taskCount":<n>}'
Plan Format
Plans use structured XML tasks targeting 2-3 tasks (50% context budget):
xml
<plan>
<goal>Phase goal statement</goal>
<context>Relevant codebase context</context>
<task id="1">
<name>Task name</name>
<files>file1.ts, file2.ts</files>
<action>Detailed implementation instructions</action>
<verify>Concrete verification commands</verify>
<done>Completion criteria</done>
</task>
</plan>
Prerequisites
- •Active quest (
.planning/directory exists) - •Phase must be in
pendingstatus
Quick Reference
- •Runbook:
runbook/quest-workflow.md - •Planner agent:
claude-config/agents/quest-planner.md