maxsimcli 4.8.0 → 4.10.0

package/dist/assets/templates/workflows/progress.md

@@ -1,5 +1,5 @@
 <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.
+Check project progress, milestone status, and offer milestone completion when all phases are done. Shows GitHub Issues-based progress alongside local ROADMAP.md progress for cross-validation. Detects phase gaps and intelligently routes to the next action.
 </purpose>
 
 <required_reading>
@@ -22,18 +22,18 @@ If `project_exists` is false (no `.planning/` directory):
 ```
 No planning structure found.
 
-Run /maxsim:new-project to start a new project.
+Run /maxsim:init to start a new project.
 ```
 
 Exit.
 
-If missing STATE.md: suggest `/maxsim:new-project`.
+If missing STATE.md: suggest `/maxsim:init`.
 
 **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 `/maxsim:new-project`.
+If missing both ROADMAP.md and PROJECT.md: suggest `/maxsim:init`.
 </step>
 
 <step name="load">
@@ -89,9 +89,12 @@ Use this instead of manually reading/parsing ROADMAP.md.
 ```bash
 # Get formatted progress bar
 PROGRESS_BAR=$(node ~/.claude/maxsim/bin/maxsim-tools.cjs progress phase-bars --raw)
+
+# Get GitHub Issues-based progress (best-effort, may fail if gh not authenticated)
+GH_PROGRESS=$(node ~/.claude/maxsim/bin/maxsim-tools.cjs mcp_get_all_progress 2>/dev/null || echo '{"error": "GitHub not available"}')
 ```
 
-Present:
+Present (include GitHub Issues progress if available for cross-validation):
 
 ```
 # [Project Name]
@@ -116,8 +119,19 @@ CONTEXT: [✓ if has_context | - if not]
 - [extract from $STATE.blockers[]]
 - [e.g. jq -r '.blockers[].text' from state-snapshot]
 
+## GitHub Issues Progress
+(If GH_PROGRESS available and not error)
+- Phase completion status from GitHub Issues
+- Cross-validate with local ROADMAP.md progress
+- Highlight any discrepancies between local and GitHub state
+
+## Issues Detected
+(Only show if gaps found during analysis)
+- Phase [N]: [issue description, e.g., "Verification failed (2 truths unmet)"]
+- Phase [M]: [issue description, e.g., "Plan exists but not executed"]
+
 ## Pending Todos
-- [count] pending — /maxsim:check-todos to review
+- [count] pending — /maxsim:quick --todo to review
 
 ## Active Debug Sessions
 - [count] active — /maxsim:debug to continue
@@ -187,7 +201,7 @@ Read its `<objective>` section.
 
 **{phase}-{plan}: [Plan Name]** — [objective summary from PLAN.md]
 
-`/maxsim:execute-phase {phase}`
+`/maxsim:execute {phase}`
 
 <sub>`/clear` first → fresh context window</sub>
 
@@ -210,7 +224,7 @@ Check if `{phase_num}-CONTEXT.md` exists in phase directory.
 **Phase {N}: {Name}** — {Goal from ROADMAP.md}
 <sub>✓ Context gathered, ready to plan</sub>
 
-`/maxsim:plan-phase {phase-number}`
+`/maxsim:plan {phase-number}`
 
 <sub>`/clear` first → fresh context window</sub>
 
@@ -225,17 +239,12 @@ Check if `{phase_num}-CONTEXT.md` exists in phase directory.
 ## ▶ Next Up
 
 **Phase {N}: {Name}** — {Goal from ROADMAP.md}
+<sub>No context yet — /maxsim:plan will start with discussion</sub>
 
-`/maxsim:discuss-phase {phase}` — gather context and clarify approach
+`/maxsim:plan {phase}`
 
 <sub>`/clear` first → fresh context window</sub>
 
----
-
-**Also available:**
-- `/maxsim:plan-phase {phase}` — skip discussion, plan directly
-- `/maxsim:list-phase-assumptions {phase}` — see Claude's assumptions
-
 ---
 ```
 
@@ -252,15 +261,14 @@ UAT.md exists with gaps (diagnosed issues). User needs to plan fixes.
 
 **{phase_num}-UAT.md** has {N} gaps requiring fixes.
 
-`/maxsim:plan-phase {phase} --gaps`
+`/maxsim:plan {phase} --gaps`
 
 <sub>`/clear` first → fresh context window</sub>
 
 ---
 
 **Also available:**
-- `/maxsim:execute-phase {phase}` — execute phase plans
-- `/maxsim:verify-work {phase}` — run more UAT testing
+- `/maxsim:execute {phase}` — execute phase plans (includes verification)
 
 ---
 ```
@@ -299,16 +307,10 @@ Read ROADMAP.md to get the next phase's name and goal.
 
 **Phase {Z+1}: {Name}** — {Goal from ROADMAP.md}
 
-`/maxsim:discuss-phase {Z+1}` — gather context and clarify approach
+`/maxsim:plan {Z+1}` — starts with discussion, then plans
 
 <sub>`/clear` first → fresh context window</sub>
 
----
-
-**Also available:**
-- `/maxsim:plan-phase {Z+1}` — skip discussion, plan directly
-- `/maxsim:verify-work {Z}` — user acceptance test before continuing
-
 ---
 ```
 
@@ -316,29 +318,27 @@ Read ROADMAP.md to get the next phase's name and goal.
 
 **Route D: Milestone complete**
 
+All phases are done. Offer milestone completion interactively:
+
 ```
 ---
 
-## 🎉 Milestone Complete
-
-All {N} phases finished!
-
-## ▶ Next Up
+## Milestone Complete!
 
-**Complete Milestone** — archive and prepare for next
+All {N} phases are complete. Ready to wrap up?
 
-`/maxsim:complete-milestone`
+1. Complete milestone (archive, create release notes) → `/maxsim:init` (detects milestone completion)
+2. Start new milestone → `/maxsim:init` (starts new milestone flow)
+3. Just show me the progress (stay on this screen)
 
 <sub>`/clear` first → fresh context window</sub>
 
----
-
-**Also available:**
-- `/maxsim:verify-work` — user acceptance test before completing milestone
-
 ---
 ```
 
+If user chooses option 1 or 2: route to `/maxsim:init` which handles milestone lifecycle interactively.
+If user chooses option 3: display progress report only, no routing.
+
 ---
 
 **Route F: Between milestones (ROADMAP.md missing, PROJECT.md exists)**
@@ -358,7 +358,7 @@ Ready to plan the next milestone.
 
 **Start Next Milestone** — questioning → research → requirements → roadmap
 
-`/maxsim:new-milestone`
+`/maxsim:init`
 
 <sub>`/clear` first → fresh context window</sub>
 
@@ -370,10 +370,11 @@ Ready to plan the next milestone.
 <step name="edge_cases">
 **Handle edge cases:**
 
-- Phase complete but next phase not planned → offer `/maxsim:plan-phase [next]`
-- All work complete → offer milestone completion
+- Phase complete but next phase not planned → offer `/maxsim:plan [next]`
+- All work complete → offer milestone completion via `/maxsim:init`
 - Blockers present → highlight before offering to continue
-- Handoff file exists → mention it, offer `/maxsim:resume-work`
+- Phase gaps detected → surface in Issues Detected section
+- Handoff file exists → mention it, offer `/maxsim:go`
   </step>
 
 </process>
@@ -381,9 +382,12 @@ Ready to plan the next milestone.
 <success_criteria>
 
 - [ ] Rich context provided (recent work, decisions, issues)
+- [ ] GitHub Issues progress shown (cross-validated with local ROADMAP)
+- [ ] Phase gaps detected and surfaced in Issues Detected section
 - [ ] Current position clear with visual progress
 - [ ] What's next clearly explained
-- [ ] Smart routing: /maxsim:execute-phase if plans exist, /maxsim:plan-phase if not
+- [ ] Smart routing: /maxsim:execute if plans exist, /maxsim:plan if not
+- [ ] Milestone completion offered when all phases done
 - [ ] User confirms before any action
 - [ ] Seamless handoff to appropriate maxsim command
       </success_criteria>

package/dist/assets/templates/workflows/quick.md

@@ -1,13 +1,17 @@
 <sanity_check>
 Before executing any step in this workflow, verify:
-1. The current directory contains a `.planning/` folder — if not, stop and tell the user to run `/maxsim:new-project` first.
+1. The current directory contains a `.planning/` folder — if not, stop and tell the user to run `/maxsim:init` first.
 2. `.planning/ROADMAP.md` exists — if not, stop and tell the user to initialize the project.
 </sanity_check>
 
 <purpose>
-Execute small, ad-hoc tasks with MAXSIM guarantees (atomic commits, STATE.md tracking). Quick mode spawns maxsim-planner (quick mode) + maxsim-executor(s), tracks tasks in `.planning/quick/`, and updates STATE.md's "Quick Tasks Completed" table.
+Execute small, ad-hoc tasks with MAXSIM guarantees (atomic commits, STATE.md tracking). Also supports "save for later" todo capture -- managing ideas as local todos with best-effort GitHub Issue creation.
+
+Quick mode spawns planner (quick mode) + executor(s), tracks tasks in `.planning/quick/`, and updates STATE.md's "Quick Tasks Completed" table.
 
 With `--full` flag: enables plan-checking (max 2 iterations) and post-execution verification for quality guarantees without full milestone ceremony.
+
+With `--todo` flag (or trigger words): enters Todo Mode for listing, capturing, completing, and triaging todos.
 </purpose>
 
 <required_reading>
@@ -16,12 +20,21 @@ Read all files referenced by the invoking prompt's execution_context before star
 </required_reading>
 
 <process>
-**Step 1: Parse arguments and get task description**
+**Step 1: Parse arguments and detect mode**
 
 Parse `$ARGUMENTS` for:
+- `--todo` flag → store as `$TODO_MODE` (true/false)
 - `--full` flag → store as `$FULL_MODE` (true/false)
 - Remaining text → use as `$DESCRIPTION` if non-empty
 
+**Mode detection:** Enter Todo Mode if ANY of these are true:
+1. `--todo` flag is present
+2. `$DESCRIPTION` starts with "todo", "save", "remember", "later" (case-insensitive)
+
+**If Todo Mode → skip to Step T1 (Todo Mode section below)**
+
+If not Todo Mode, continue with Quick Task Mode:
+
 If `$DESCRIPTION` is empty after parsing, prompt user interactively:
 
 ```
@@ -55,7 +68,7 @@ INIT=$(node ~/.claude/maxsim/bin/maxsim-tools.cjs init quick "$DESCRIPTION")
 
 Parse JSON for: `planner_model`, `executor_model`, `checker_model`, `verifier_model`, `commit_docs`, `next_num`, `slug`, `date`, `timestamp`, `quick_dir`, `task_dir`, `roadmap_exists`, `planning_exists`.
 
-**If `roadmap_exists` is false:** Error — Quick mode requires an active project with ROADMAP.md. Run `/maxsim:new-project` first.
+**If `roadmap_exists` is false:** Error — Quick mode requires an active project with ROADMAP.md. Run `/maxsim:init` first.
 
 Quick tasks can run mid-phase - validation only checks ROADMAP.md exists, not phase status.
 
@@ -126,7 +139,7 @@ Write plan to: ${QUICK_DIR}/${next_num}-PLAN.md
 Return: ## PLANNING COMPLETE with plan path
 </output>
 ",
-  subagent_type="maxsim-planner",
+  subagent_type="planner",
   model="{planner_model}",
   description="Quick plan: ${DESCRIPTION}"
 )
@@ -186,8 +199,8 @@ Skip: context compliance (no CONTEXT.md), cross-plan deps (single plan), ROADMAP
 
 ```
 Task(
-  prompt=checker_prompt,
-  subagent_type="maxsim-plan-checker",
+  prompt="## Task: Verify plans achieve phase goal\n\n## Suggested Skills: verification-gates\n\n" + checker_prompt,
+  subagent_type="planner",
   model="{checker_model}",
   description="Check quick plan: ${DESCRIPTION}"
 )
@@ -229,8 +242,8 @@ Return what changed.
 
 ```
 Task(
-  prompt="First, read ~/.claude/agents/maxsim-planner.md for your role and instructions.\n\n" + revision_prompt,
-  subagent_type="general-purpose",
+  prompt=revision_prompt,
+  subagent_type="planner",
   model="{planner_model}",
   description="Revise quick plan: ${DESCRIPTION}"
 )
@@ -248,7 +261,7 @@ Offer: 1) Force proceed, 2) Abort
 
 **Step 6: Spawn executor**
 
-Spawn maxsim-executor with plan reference:
+Spawn executor with plan reference:
 
 ```
 Task(
@@ -269,7 +282,7 @@ Execute quick task ${next_num}.
 - Do NOT update ROADMAP.md (quick tasks are separate from planned phases)
 </constraints>
 ",
-  subagent_type="maxsim-executor",
+  subagent_type="executor",
   model="{executor_model}",
   description="Execute: ${DESCRIPTION}"
 )
@@ -310,6 +323,10 @@ Display banner:
 ```
 Task(
   prompt="
+    ## Task: Review for spec compliance
+
+    ## Suggested Skills: verification-gates, evidence-collection
+
     <review_context>
     **Plan:** quick-${next_num}
     **Description:** ${DESCRIPTION}
@@ -327,7 +344,7 @@ Task(
     </plan_frontmatter>
     </review_context>
   ",
-  subagent_type="maxsim-spec-reviewer",
+  subagent_type="verifier",
   model="{executor_model}",
   description="Spec review: ${DESCRIPTION}"
 )
@@ -359,6 +376,10 @@ STOP and wait for user decision.
 ```
 Task(
   prompt="
+    ## Task: Review for code quality
+
+    ## Suggested Skills: code-review
+
     <review_context>
     **Plan:** quick-${next_num}
 
@@ -375,7 +396,7 @@ Task(
     </test_results>
     </review_context>
   ",
-  subagent_type="maxsim-code-reviewer",
+  subagent_type="verifier",
   model="{executor_model}",
   description="Code review: ${DESCRIPTION}"
 )
@@ -422,7 +443,7 @@ Task goal: ${DESCRIPTION}
 </files_to_read>
 
 Check must_haves against actual codebase. Create VERIFICATION.md at ${QUICK_DIR}/${next_num}-VERIFICATION.md.",
-  subagent_type="maxsim-verifier",
+  subagent_type="verifier",
   model="{verifier_model}",
   description="Verify: ${DESCRIPTION}"
 )
@@ -552,9 +573,161 @@ Commit: ${commit_hash}
 Ready for next task: /maxsim:quick
 ```
 
+---
+
+## Todo Mode
+
+**Entered when `--todo` flag is set or description starts with "todo", "save", "remember", "later".**
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ MAXSIM ► TODO MODE
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+```
+
+**Step T1: Initialize todo context**
+
+```bash
+INIT=$(node ~/.claude/maxsim/bin/maxsim-tools.cjs init todos)
+mkdir -p .planning/todos/pending .planning/todos/done
+```
+
+Extract from init JSON: `todo_count`, `todos`, `pending_dir`, `date`, `timestamp`.
+
+---
+
+**Step T2: Determine todo action**
+
+Parse `$DESCRIPTION` (text after `--todo` flag or trigger word) for intent:
+
+| Intent | Trigger | Action |
+|--------|---------|--------|
+| List | No description, or "list", "show" | Go to **T3: List** |
+| Capture | Has a description (not a trigger word) | Go to **T4: Capture** |
+| Complete | "done", "complete", "finish" + identifier | Go to **T5: Complete** |
+| Triage | "triage", "what next", "what should I work on" | Go to **T6: Triage** |
+
+If intent is ambiguous, default to **T3: List** (shows todos, then offers options).
+
+---
+
+**Step T3: List Existing Todos**
+
+```bash
+node ~/.claude/maxsim/bin/maxsim-tools.cjs todos list
+```
+
+Display current todos in a clean table:
+
+```
+Pending Todos:
+
+| # | Title | Area | Priority | Age |
+|---|-------|------|----------|-----|
+| 1 | [title] | [area] | [priority] | [relative time] |
+
+---
+
+Options:
+1. Add a new todo: /maxsim:quick --todo [description]
+2. Complete a todo: /maxsim:quick --todo done [number]
+3. Triage: /maxsim:quick --todo triage
+4. Back to quick tasks: /maxsim:quick [description]
+```
+
+If no pending todos: "No pending todos. Use `/maxsim:quick --todo [description]` to capture one."
+
+Exit after display.
+
+---
+
+**Step T4: Capture New Todo**
+
+If user provided a description:
+
+1. Parse priority from description (look for HIGH/MEDIUM/LOW keywords, default MEDIUM)
+2. Infer area from file paths mentioned or conversation context (default "general")
+3. Generate slug: `slug=$(node ~/.claude/maxsim/bin/maxsim-tools.cjs generate-slug "$TITLE" --raw)`
+4. Create todo file at `.planning/todos/pending/${date}-${slug}.md`:
+
+```markdown
+---
+created: [timestamp]
+title: [title]
+area: [area]
+priority: [HIGH/MEDIUM/LOW]
+mode: quick
+files: []
+---
+
+## Problem
+
+[description - enough context for future Claude to understand]
+
+## Solution
+
+TBD
+```
+
+5. Best-effort GitHub Issue with 'todo' label: `node ~/.claude/maxsim/bin/maxsim-tools.cjs todos add "$TITLE" "$PRIORITY" 2>/dev/null || true`
+6. Commit: `node ~/.claude/maxsim/bin/maxsim-tools.cjs commit "docs: capture todo - ${TITLE}" --files .planning/todos/pending/${date}-${slug}.md`
+7. Confirm: "Saved: ${TITLE} (priority: ${PRIORITY})"
+
+Exit after confirm.
+
+---
+
+**Step T5: Complete Todo**
+
+If user references an existing todo to complete:
+
+1. Parse identifier (number from list, or title fragment)
+2. Find matching todo in `.planning/todos/pending/`
+3. Move to done: `mv ".planning/todos/pending/[filename]" ".planning/todos/done/"`
+4. Best-effort: close corresponding GitHub Issue
+5. Commit: `node ~/.claude/maxsim/bin/maxsim-tools.cjs commit "docs: complete todo - ${TITLE}" --files .planning/todos/done/${filename}`
+6. Confirm: "Completed: ${TITLE}"
+
+Exit after confirm.
+
+---
+
+**Step T6: Triage**
+
+Help user decide what to work on next:
+
+1. List all pending todos sorted by priority (HIGH first)
+2. Check if any todos relate to the current phase (cross-reference with ROADMAP.md):
+
+```bash
+ROADMAP=$(node ~/.claude/maxsim/bin/maxsim-tools.cjs roadmap analyze)
+```
+
+3. Present prioritized view:
+
+```
+What should I work on?
+
+## Phase-Related Todos
+- [todo title] -- relates to Phase [N]: [phase name]
+
+## Standalone Todos
+- [HIGH] [todo title] (created [age] ago)
+- [MEDIUM] [todo title] (created [age] ago)
+
+---
+
+Pick a todo to work on, or:
+- /maxsim:quick [description] -- start a new task
+- /maxsim:quick --todo [description] -- save something for later
+```
+
+Exit after display.
+
 </process>
 
 <success_criteria>
+**Quick Task Mode:**
 - [ ] ROADMAP.md validation passes
 - [ ] User provides task description
 - [ ] `--full` flag parsed from arguments when present
@@ -567,4 +740,12 @@ Ready for next task: /maxsim:quick
 - [ ] (--full) `${next_num}-VERIFICATION.md` created by verifier
 - [ ] STATE.md updated with quick task row (Status column when --full)
 - [ ] Artifacts committed
+
+**Todo Mode:**
+- [ ] `--todo` flag or trigger words detected
+- [ ] Todo action determined (list/capture/complete/triage)
+- [ ] (capture) Todo file created with valid frontmatter
+- [ ] (capture) Best-effort GitHub Issue creation attempted
+- [ ] (complete) Todo moved from pending to done
+- [ ] (triage) Prioritized view with phase context shown
 </success_criteria>

package/dist/assets/templates/workflows/research-phase.md

@@ -1,7 +1,7 @@
 <purpose>
-Research how to implement a phase. Spawns maxsim-phase-researcher with phase context.
+Research how to implement a phase. Spawns researcher with phase context.
 
-Standalone research command. For most workflows, use `/maxsim:plan-phase` which integrates research automatically.
+Standalone research command. For most workflows, use `/maxsim:plan` which integrates research automatically.
 </purpose>
 
 <process>
@@ -11,7 +11,7 @@ Standalone research command. For most workflows, use `/maxsim:plan-phase` which
 @./references/model-profile-resolution.md
 
 Resolve model for:
-- `maxsim-phase-researcher`
+- `researcher`
 
 ## Step 1: Normalize and Validate Phase
 
@@ -47,7 +47,7 @@ Research implementation approach for Phase {phase}: {name}
 </objective>
 
 <files_to_read>
-- {context_path} (USER DECISIONS from /maxsim:discuss-phase)
+- {context_path} (USER DECISIONS from /maxsim:plan discussion stage)
 - {requirements_path} (Project requirements)
 - {state_path} (Project decisions and history)
 </files_to_read>
@@ -59,7 +59,7 @@ Phase description: {description}
 <output>
 Write to: .planning/phases/${PHASE}-{slug}/${PHASE}-RESEARCH.md
 </output>",
-  subagent_type="maxsim-phase-researcher",
+  subagent_type="researcher",
   model="{researcher_model}"
 )
 ```

package/dist/assets/templates/workflows/sdd.md

@@ -1,6 +1,6 @@
 <sanity_check>
 Before executing any step in this workflow, verify:
-1. The current directory contains a `.planning/` folder — if not, stop and tell the user to run `/maxsim:new-project` first.
+1. The current directory contains a `.planning/` folder — if not, stop and tell the user to run `/maxsim:init` first.
 2. `.planning/ROADMAP.md` exists — if not, stop and tell the user to initialize the project.
 </sanity_check>
 
@@ -102,11 +102,11 @@ Context table (SDD principle):
 
 **4b — Spawn Executor**
 
-Fresh `maxsim-executor` agent with minimal context:
+Fresh executor agent with minimal context:
 
 ```
 Task(
-  subagent_type="maxsim-executor",
+  subagent_type="executor",
   model="{executor_model}",
   prompt="
     <objective>
@@ -155,13 +155,17 @@ Record the commit hash from the executor's output.
 
 **4c — Review Stage 1: Spec Compliance**
 
-Spawn `maxsim-spec-reviewer` to verify implementation matches task spec:
+Spawn verifier to check implementation matches task spec:
 
 ```
 Task(
-  subagent_type="maxsim-spec-reviewer",
+  subagent_type="verifier",
   model="{executor_model}",
   prompt="
+    ## Task: Review for spec compliance
+
+    ## Suggested Skills: verification-gates, evidence-collection
+
     <objective>
     Review task {task_number} of plan {plan_id} for spec compliance.
     </objective>
@@ -192,13 +196,17 @@ Task(
 
 **4d — Review Stage 2: Code Quality**
 
-Spawn `maxsim-code-reviewer` to check for bugs, edge cases, and conventions:
+Spawn verifier to check for bugs, edge cases, and conventions:
 
 ```
 Task(
-  subagent_type="maxsim-code-reviewer",
+  subagent_type="verifier",
   model="{executor_model}",
   prompt="
+    ## Task: Review for code quality
+
+    ## Suggested Skills: code-review
+
     <objective>
     Review task {task_number} of plan {plan_id} for code quality.
     Spec compliance already verified.
@@ -232,7 +240,7 @@ If EITHER review stage returns FAIL:
 
 ```
 Task(
-  subagent_type="maxsim-executor",
+  subagent_type="executor",
   model="{executor_model}",
   prompt="
     <objective>
@@ -404,9 +412,9 @@ ls -1 .planning/phases/${PHASE_DIR_NAME}/*-SUMMARY.md 2>/dev/null | wc -l
 
 | Condition | Route | Action |
 |-----------|-------|--------|
-| summaries < plans | **A: More plans** | Find next incomplete plan. Show next plan, suggest `/maxsim:sdd {phase}` to continue. |
-| summaries = plans, more phases exist | **B: Phase done** | Show completion, suggest `/maxsim:verify-work {phase}` then `/maxsim:plan-phase {next}`. |
-| summaries = plans, last phase | **C: Milestone done** | Show banner, suggest `/maxsim:complete-milestone` + `/maxsim:verify-work`. |
+| summaries < plans | **A: More plans** | Find next incomplete plan. Show next plan, suggest `/maxsim:execute {phase}` (SDD mode) to continue. |
+| summaries = plans, more phases exist | **B: Phase done** | Show completion, suggest `/maxsim:execute {phase}` (verification) then `/maxsim:plan {next}`. |
+| summaries = plans, last phase | **C: Milestone done** | Show banner, suggest `/maxsim:progress` (milestone completion) + `/maxsim:execute` (verification). |
 
 All routes: recommend `/clear` first for fresh context.
 </step>
@@ -422,5 +430,5 @@ All routes: recommend `/clear` first for fresh context.
 </failure_handling>
 
 <resumption>
-Re-run `/maxsim:sdd {phase}` — discover_plans finds completed SUMMARYs, skips them, resumes from first incomplete plan. Within a plan, completed tasks (those with commits matching the plan pattern) can be detected and skipped.
+Re-run `/maxsim:execute {phase}` (SDD mode) — discover_plans finds completed SUMMARYs, skips them, resumes from first incomplete plan. Within a plan, completed tasks (those with commits matching the plan pattern) can be detected and skipped.
 </resumption>