mindforge-cc 9.0.0 → 10.0.1

package/.agent/workflows/mindforge-progress.md

@@ -1,507 +0,0 @@
-<purpose>
-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.
-</purpose>
-
-<required_reading>
-Read all files referenced by the invoking prompt's execution_context before starting.
-</required_reading>
-
-<process>
-
-<step name="init_context">
-**Load progress context (paths only):**
-
-```bash
-INIT=$(node ".agent/bin/mindforge-tools.cjs" init progress)
-if [[ "$INIT" == @file:* ]]; then INIT=$(cat "${INIT#@file:}"); fi
-```
-
-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`.
-
-```bash
-DISCUSS_MODE=$(node ".agent/bin/mindforge-tools.cjs" config-get workflow.discuss_mode 2>/dev/null || echo "discuss")
-```
-
-If `project_exists` is false (no `.planning/` directory):
-
-```
-No planning structure found.
-
-Run /mindforge-new-project to start a new project.
-```
-
-Exit.
-
-If missing STATE.md: suggest `/mindforge-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 `/mindforge-new-project`.
-</step>
-
-<step name="load">
-**Use structured extraction from mindforge-tools:**
-
-Instead of reading full files, use targeted tools to get only the data needed for the report:
-- `ROADMAP=$(node ".agent/bin/mindforge-tools.cjs" roadmap analyze)`
-- `STATE=$(node ".agent/bin/mindforge-tools.cjs" state-snapshot)`
-
-This minimizes orchestrator context usage.
-</step>
-
-<step name="analyze_roadmap">
-**Get comprehensive roadmap analysis (replaces manual parsing):**
-
-```bash
-ROADMAP=$(node ".agent/bin/mindforge-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.
-</step>
-
-<step name="recent">
-**Gather recent work context:**
-
-- Find the 2-3 most recent SUMMARY.md files
-- Use `summary-extract` for efficient parsing:
-  ```bash
-  node ".agent/bin/mindforge-tools.cjs" summary-extract <path> --fields one_liner
-  ```
-- This shows "what we've been working on"
-  </step>
-
-<step name="position">
-**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`
-  </step>
-
-<step name="report">
-**Generate progress bar from mindforge-tools, then present rich status report:**
-
-```bash
-# Get formatted progress bar
-PROGRESS_BAR=$(node ".agent/bin/mindforge-tools.cjs" progress bar --raw)
-```
-
-Present:
-
-```
-# [Project Name]
-
-**Progress:** {PROGRESS_BAR}
-**Profile:** [quality/balanced/budget/inherit]
-**Discuss mode:** {DISCUSS_MODE}
-
-## 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 — /mindforge-check-todos to review
-
-## Active Debug Sessions
-- [count] active — /mindforge-debug to continue
-(Only show this section if count > 0)
-
-## What's Next
-[Next phase/plan objective from roadmap analyze]
-```
-
-</step>
-
-<step name="route">
-**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 or partial (incomplete) testing
-grep -l "status: diagnosed\|status: partial" .planning/phases/[current-phase-dir]/*-UAT.md 2>/dev/null
-```
-
-Track:
-- `uat_with_gaps`: UAT.md files with status "diagnosed" (gaps need fixing)
-- `uat_partial`: UAT.md files with status "partial" (incomplete testing)
-
-**Step 1.6: Cross-phase health check**
-
-Scan ALL phases in the current milestone for outstanding verification debt using the CLI (which respects milestone boundaries via `getMilestonePhaseFilter`):
-
-```bash
-DEBT=$(node ".agent/bin/mindforge-tools.cjs" audit-uat --raw 2>/dev/null)
-```
-
-Parse JSON for `summary.total_items` and `summary.total_files`.
-
-Track: `outstanding_debt` — `summary.total_items` from the audit.
-
-**If outstanding_debt > 0:** Add a warning section to the progress report output (in the `report` step), placed between "## What's Next" and the route suggestion:
-
-```markdown
-## Verification Debt ({N} files across prior phases)
-
-| Phase | File | Issue |
-|-------|------|-------|
-| {phase} | {filename} | {pending_count} pending, {skipped_count} skipped, {blocked_count} blocked |
-| {phase} | {filename} | human_needed — {count} items |
-
-Review: `/mindforge-audit-uat ${MindForge_WS}` — full cross-phase audit
-Resume testing: `/mindforge-verify-work {phase} ${MindForge_WS}` — retest specific phase
-```
-
-This is a WARNING, not a blocker — routing proceeds normally. The debt is visible so the user can make an informed choice.
-
-**Step 2: Route based on counts**
-
-| Condition | Meaning | Action |
-|-----------|---------|--------|
-| uat_partial > 0 | UAT testing incomplete | Go to **Route E.2** |
-| 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 `<objective>` section.
-
-```
----
-
-## ▶ Next Up
-
-**{phase}-{plan}: [Plan Name]** — [objective summary from PLAN.md]
-
-`/mindforge-execute-phase {phase} ${MindForge_WS}`
-
-<sub>`/clear` first → fresh context window</sub>
-
----
-```
-
----
-
-**Route B: Phase needs planning**
-
-Check if `{phase_num}-CONTEXT.md` exists in phase directory.
-
-Check if current phase has UI indicators:
-
-```bash
-PHASE_SECTION=$(node ".agent/bin/mindforge-tools.cjs" roadmap get-phase "${CURRENT_PHASE}" 2>/dev/null)
-PHASE_HAS_UI=$(echo "$PHASE_SECTION" | grep -qi "UI hint.*yes" && echo "true" || echo "false")
-```
-
-**If CONTEXT.md exists:**
-
-```
----
-
-## ▶ Next Up
-
-**Phase {N}: {Name}** — {Goal from ROADMAP.md}
-<sub>✓ Context gathered, ready to plan</sub>
-
-`/mindforge-plan-phase {phase-number} ${MindForge_WS}`
-
-<sub>`/clear` first → fresh context window</sub>
-
----
-```
-
-**If CONTEXT.md does NOT exist AND phase has UI (`PHASE_HAS_UI` is `true`):**
-
-```
----
-
-## ▶ Next Up
-
-**Phase {N}: {Name}** — {Goal from ROADMAP.md}
-
-`/mindforge-discuss-phase {phase}` — gather context and clarify approach
-
-<sub>`/clear` first → fresh context window</sub>
-
----
-
-**Also available:**
-- `/mindforge-ui-phase {phase}` — generate UI design contract (recommended for frontend phases)
-- `/mindforge-plan-phase {phase}` — skip discussion, plan directly
-- `/mindforge-list-phase-assumptions {phase}` — see the agent's assumptions
-
----
-```
-
-**If CONTEXT.md does NOT exist AND phase has no UI:**
-
-```
----
-
-## ▶ Next Up
-
-**Phase {N}: {Name}** — {Goal from ROADMAP.md}
-
-`/mindforge-discuss-phase {phase} ${MindForge_WS}` — gather context and clarify approach
-
-<sub>`/clear` first → fresh context window</sub>
-
----
-
-**Also available:**
-- `/mindforge-plan-phase {phase} ${MindForge_WS}` — skip discussion, plan directly
-- `/mindforge-list-phase-assumptions {phase} ${MindForge_WS}` — see the agent'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.
-
-`/mindforge-plan-phase {phase} --gaps ${MindForge_WS}`
-
-<sub>`/clear` first → fresh context window</sub>
-
----
-
-**Also available:**
-- `/mindforge-execute-phase {phase} ${MindForge_WS}` — execute phase plans
-- `/mindforge-verify-work {phase} ${MindForge_WS}` — run more UAT testing
-
----
-```
-
----
-
-**Route E.2: UAT testing incomplete (partial)**
-
-UAT.md exists with `status: partial` — testing session ended before all items resolved.
-
-```
----
-
-## Incomplete UAT Testing
-
-**{phase_num}-UAT.md** has {N} unresolved tests (pending, blocked, or skipped).
-
-`/mindforge-verify-work {phase} ${MindForge_WS}` — resume testing from where you left off
-
-<sub>`/clear` first → fresh context window</sub>
-
----
-
-**Also available:**
-- `/mindforge-audit-uat ${MindForge_WS}` — full cross-phase UAT audit
-- `/mindforge-execute-phase {phase} ${MindForge_WS}` — execute phase plans
-
----
-```
-
----
-
-**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.
-
-Check if next phase has UI indicators:
-
-```bash
-NEXT_PHASE_SECTION=$(node ".agent/bin/mindforge-tools.cjs" roadmap get-phase "$((Z+1))" 2>/dev/null)
-NEXT_HAS_UI=$(echo "$NEXT_PHASE_SECTION" | grep -qi "UI hint.*yes" && echo "true" || echo "false")
-```
-
-**If next phase has UI (`NEXT_HAS_UI` is `true`):**
-
-```
----
-
-## ✓ Phase {Z} Complete
-
-## ▶ Next Up
-
-**Phase {Z+1}: {Name}** — {Goal from ROADMAP.md}
-
-`/mindforge-discuss-phase {Z+1}` — gather context and clarify approach
-
-<sub>`/clear` first → fresh context window</sub>
-
----
-
-**Also available:**
-- `/mindforge-ui-phase {Z+1}` — generate UI design contract (recommended for frontend phases)
-- `/mindforge-plan-phase {Z+1}` — skip discussion, plan directly
-- `/mindforge-verify-work {Z}` — user acceptance test before continuing
-
----
-```
-
-**If next phase has no UI:**
-
-```
----
-
-## ✓ Phase {Z} Complete
-
-## ▶ Next Up
-
-**Phase {Z+1}: {Name}** — {Goal from ROADMAP.md}
-
-`/mindforge-discuss-phase {Z+1} ${MindForge_WS}` — gather context and clarify approach
-
-<sub>`/clear` first → fresh context window</sub>
-
----
-
-**Also available:**
-- `/mindforge-plan-phase {Z+1} ${MindForge_WS}` — skip discussion, plan directly
-- `/mindforge-verify-work {Z} ${MindForge_WS}` — user acceptance test before continuing
-
----
-```
-
----
-
-**Route D: Milestone complete**
-
-```
----
-
-## 🎉 Milestone Complete
-
-All {N} phases finished!
-
-## ▶ Next Up
-
-**Complete Milestone** — archive and prepare for next
-
-`/mindforge-complete-milestone ${MindForge_WS}`
-
-<sub>`/clear` first → fresh context window</sub>
-
----
-
-**Also available:**
-- `/mindforge-verify-work ${MindForge_WS}` — 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
-
-`/mindforge-new-milestone ${MindForge_WS}`
-
-<sub>`/clear` first → fresh context window</sub>
-
----
-```
-
-</step>
-
-<step name="edge_cases">
-**Handle edge cases:**
-
-- Phase complete but next phase not planned → offer `/mindforge-plan-phase [next] ${MindForge_WS}`
-- All work complete → offer milestone completion
-- Blockers present → highlight before offering to continue
-- Handoff file exists → mention it, offer `/mindforge-resume-work ${MindForge_WS}`
-  </step>
-
-</process>
-
-<success_criteria>
-
-- [ ] Rich context provided (recent work, decisions, issues)
-- [ ] Current position clear with visual progress
-- [ ] What's next clearly explained
-- [ ] Smart routing: /mindforge-execute-phase if plans exist, /mindforge-plan-phase if not
-- [ ] User confirms before any action
-- [ ] Seamless handoff to appropriate mindforge command
-      </success_criteria>