Check project progress, summarize recent work and what's ahead, then intelligently route to the next action — either executing an existing plan or creating the next one. Provides situational awareness before continuing work. Read all files referenced by the invoking prompt's execution_context before starting. **Load progress context (paths only):** ```bash INIT=$(node ~/.claude/pan-wizard-core/bin/pan-tools.cjs init progress) ``` Extract from init JSON: `project_exists`, `roadmap_exists`, `state_exists`, `phases`, `current_phase`, `next_phase`, `milestone_version`, `completed_count`, `phase_count`, `paused_at`, `state_path`, `roadmap_path`, `project_path`, `config_path`. If `project_exists` is false (no `.planning/` directory): ``` No planning structure found. Run /pan:new-project to start a new project. ``` Exit. If missing state.md: suggest `/pan:new-project`. **If roadmap.md missing but project.md exists:** This means a milestone was completed and archived. Go to **Route F** (between milestones). If missing both roadmap.md and project.md: suggest `/pan:new-project`. **Use structured extraction from pan-tools:** Instead of reading full files, use targeted tools to get only the data needed for the report: - `ROADMAP=$(node ~/.claude/pan-wizard-core/bin/pan-tools.cjs roadmap analyze)` - `STATE=$(node ~/.claude/pan-wizard-core/bin/pan-tools.cjs state-snapshot)` This minimizes orchestrator context usage. **Get comprehensive roadmap analysis (replaces manual parsing):** ```bash ROADMAP=$(node ~/.claude/pan-wizard-core/bin/pan-tools.cjs roadmap analyze) ``` This returns structured JSON with: - All phases with disk status (complete/partial/planned/empty/no_directory) - Goal and dependencies per phase - Plan and summary counts per phase - Aggregated stats: total plans, summaries, progress percent - Current and next phase identification Use this instead of manually reading/parsing roadmap.md. **Gather recent work context:** - Find the 2-3 most recent summary.md files - Use `summary-extract` for efficient parsing: ```bash node ~/.claude/pan-wizard-core/bin/pan-tools.cjs summary-extract --fields one_liner ``` - This shows "what we've been working on" **Parse current position from init context and roadmap analysis:** - Use `current_phase` and `next_phase` from `$ROADMAP` - Note `paused_at` if work was paused (from `$STATE`) - Count pending todos: use `init todos` or `list-todos` - Check for active debug sessions: `ls .planning/debug/*.md 2>/dev/null | grep -v resolved | wc -l` **Generate progress bar from pan-tools, then present rich status report:** ```bash # Get formatted progress bar PROGRESS_BAR=$(node ~/.claude/pan-wizard-core/bin/pan-tools.cjs progress bar --raw) ``` Present: ``` # [Project Name] **Progress:** {PROGRESS_BAR} **Profile:** [quality/balanced/budget] ## Recent Work - [Phase X, Plan Y]: [what was accomplished - 1 line from summary-extract] - [Phase X, Plan Z]: [what was accomplished - 1 line from summary-extract] ## Current Position Phase [N] of [total]: [phase-name] Plan [M] of [phase-total]: [status] CONTEXT: [✓ if has_context | - if not] ## Key Decisions Made - [extract from $STATE.decisions[]] - [e.g. jq -r '.decisions[].decision' from state-snapshot] ## Blockers/Concerns - [extract from $STATE.blockers[]] - [e.g. jq -r '.blockers[].text' from state-snapshot] ## Pending Todos - [count] pending — /pan:todo-check to review ## Active Debug Sessions - [count] active — /pan:debug to continue (Only show this section if count > 0) ## What's Next [Next phase/plan objective from roadmap analyze] ``` **Determine next action based on verified counts.** **Step 1: Count plans, summaries, and issues in current phase** List files in the current phase directory: ```bash ls -1 .planning/phases/[current-phase-dir]/*-plan.md 2>/dev/null | wc -l ls -1 .planning/phases/[current-phase-dir]/*-summary.md 2>/dev/null | wc -l ls -1 .planning/phases/[current-phase-dir]/*-uat.md 2>/dev/null | wc -l ``` State: "This phase has {X} plans, {Y} summaries." **Step 1.5: Check for unaddressed UAT gaps** Check for uat.md files with status "diagnosed" (has gaps needing fixes). ```bash # Check for diagnosed UAT with gaps grep -l "status: diagnosed" .planning/phases/[current-phase-dir]/*-uat.md 2>/dev/null ``` Track: - `uat_with_gaps`: uat.md files with status "diagnosed" (gaps need fixing) **Step 2: Route based on counts** | Condition | Meaning | Action | |-----------|---------|--------| | uat_with_gaps > 0 | UAT gaps need fix plans | Go to **Route E** | | summaries < plans | Unexecuted plans exist | Go to **Route A** | | summaries = plans AND plans > 0 | Phase complete | Go to Step 3 | | plans = 0 | Phase not yet planned | Go to **Route B** | --- **Route A: Unexecuted plan exists** Find the first plan.md without matching summary.md. Read its `` section. ``` --- ## ▶ Next Up **{phase}-{plan}: [Plan Name]** — [objective summary from plan.md] `/pan:exec-phase {phase}` <sub>`/clear` first → fresh context window</sub> --- ``` --- **Route B: Phase needs planning** Check if `{phase_num}-context.md` exists in phase directory. **If context.md exists:** ``` --- ## ▶ Next Up **Phase {N}: {Name}** — {Goal from roadmap.md} <sub>✓ Context gathered, ready to plan</sub> `/pan:plan-phase {phase-number}` <sub>`/clear` first → fresh context window</sub> --- ``` **If context.md does NOT exist:** ``` --- ## ▶ Next Up **Phase {N}: {Name}** — {Goal from roadmap.md} `/pan:discuss-phase {phase}` — gather context and clarify approach <sub>`/clear` first → fresh context window</sub> --- **Also available:** - `/pan:plan-phase {phase}` — skip discussion, plan directly - `/pan:assumptions {phase}` — see Claude's assumptions --- ``` --- **Route E: UAT gaps need fix plans** uat.md exists with gaps (diagnosed issues). User needs to plan fixes. ``` --- ## ⚠ UAT Gaps Found **{phase_num}-uat.md** has {N} gaps requiring fixes. `/pan:plan-phase {phase} --gaps` <sub>`/clear` first → fresh context window</sub> --- **Also available:** - `/pan:exec-phase {phase}` — execute phase plans - `/pan:verify-phase {phase}` — run more UAT testing --- ``` --- **Step 3: Check milestone status (only when phase complete)** Read roadmap.md and identify: 1. Current phase number 2. All phase numbers in the current milestone section Count total phases and identify the highest phase number. State: "Current phase is {X}. Milestone has {N} phases (highest: {Y})." **Route based on milestone status:** | Condition | Meaning | Action | |-----------|---------|--------| | current phase < highest phase | More phases remain | Go to **Route C** | | current phase = highest phase | Milestone complete | Go to **Route D** | --- **Route C: Phase complete, more phases remain** Read roadmap.md to get the next phase's name and goal. ``` --- ## ✓ Phase {Z} Complete ## ▶ Next Up **Phase {Z+1}: {Name}** — {Goal from roadmap.md} `/pan:discuss-phase {Z+1}` — gather context and clarify approach <sub>`/clear` first → fresh context window</sub> --- **Also available:** - `/pan:plan-phase {Z+1}` — skip discussion, plan directly - `/pan:verify-phase {Z}` — user acceptance test before continuing --- ``` --- **Route D: Milestone complete** ``` --- ## 🎉 Milestone Complete All {N} phases finished! ## ▶ Next Up **Complete Milestone** — archive and prepare for next `/pan:milestone-done` <sub>`/clear` first → fresh context window</sub> --- **Also available:** - `/pan:verify-phase` — user acceptance test before completing milestone --- ``` --- **Route F: Between milestones (roadmap.md missing, project.md exists)** A milestone was completed and archived. Ready to start the next milestone cycle. Read milestones.md to find the last completed milestone version. ``` --- ## ✓ Milestone v{X.Y} Complete Ready to plan the next milestone. ## ▶ Next Up **Start Next Milestone** — questioning → research → requirements → roadmap `/pan:milestone-new` <sub>`/clear` first → fresh context window</sub> --- ``` **Handle edge cases:** - Phase complete but next phase not planned → offer `/pan:plan-phase [next]` - All work complete → offer milestone completion - Blockers present → highlight before offering to continue - Handoff file exists → mention it, offer `/pan:resume` - [ ] Rich context provided (recent work, decisions, issues) - [ ] Current position clear with visual progress - [ ] What's next clearly explained - [ ] Smart routing: /pan:exec-phase if plans exist, /pan:plan-phase if not - [ ] User confirms before any action - [ ] Seamless handoff to appropriate pan command