@bhargavvc/sdd-cc 1.35.0 → 1.42.4

package/sdd/workflows/profile-user.md

@@ -1,7 +1,7 @@
 <purpose>
 Orchestrate the full developer profiling flow: consent, session analysis (or questionnaire fallback), profile generation, result display, and artifact creation.
 
-This workflow wires Phase 1 (session pipeline) and Phase 2 (profiling engine) into a cohesive user-facing experience. All heavy lifting is done by existing sdd-tools.cjs subcommands and the sdd-user-profiler agent -- this workflow orchestrates the sequence, handles branching, and provides the UX.
+This workflow wires Phase 1 (session pipeline) and Phase 2 (profiling engine) into a cohesive user-facing experience. All heavy lifting is done by existing `sdd-sdk query` handlers (with legacy `sdd-tools.cjs` parity where needed) and the sdd-user-profiler agent -- this workflow orchestrates the sequence, handles branching, and provides the UX.
 </purpose>
 
 <required_reading>
@@ -9,7 +9,7 @@ Read all files referenced by the invoking prompt's execution_context before star
 
 Key references:
 - @$HOME/.claude/sdd/references/ui-brand.md (display patterns)
-- @$HOME/.claude/sdd/agents/sdd-user-profiler.md (profiler agent definition)
+- @$HOME/.claude/agents/sdd-user-profiler.md (profiler agent definition)
 - @$HOME/.claude/sdd/references/user-profiling.md (profiling reference doc)
 </required_reading>
 
@@ -120,7 +120,7 @@ Use AskUserQuestion:
 - options:
   - "Let's go" -- Proceed to step 3 (session analysis)
   - "Use questionnaire instead" -- Jump to step 4b (questionnaire path)
-  - "Not now" -- Display "No worries. Run /sdd-profile-user when ready." and exit
+  - "Not now" -- Display "No worries. Run /sdd:profile-user when ready." and exit
 
 ---
 
@@ -130,7 +130,7 @@ Display: "◆ Scanning sessions..."
 
 Run session scan:
 ```bash
-SCAN_RESULT=$(node $HOME/.claude/sdd/bin/sdd-tools.cjs scan-sessions --json 2>/dev/null)
+SCAN_RESULT=$(sdd-sdk query scan-sessions --json 2>/dev/null)
 ```
 
 Parse the JSON output to get session count and project count.
@@ -150,7 +150,7 @@ Display: "◆ Sampling messages..."
 
 Run profile sampling:
 ```bash
-SAMPLE_RESULT=$(node $HOME/.claude/sdd/bin/sdd-tools.cjs profile-sample --json 2>/dev/null)
+SAMPLE_RESULT=$(sdd-sdk query profile-sample --json 2>/dev/null)
 ```
 
 Parse the JSON output to get the temp directory path and message count.
@@ -201,7 +201,7 @@ Display: "Using questionnaire to build your profile."
 
 **Get questions:**
 ```bash
-QUESTIONS=$(node $HOME/.claude/sdd/bin/sdd-tools.cjs profile-questionnaire --json 2>/dev/null)
+QUESTIONS=$(sdd-sdk query profile-questionnaire --json 2>/dev/null)
 ```
 
 Parse the questions JSON. It contains 8 questions, one per dimension.
@@ -224,7 +224,7 @@ Write the answers JSON to `$ANSWERS_PATH`.
 
 **Convert answers to analysis:**
 ```bash
-ANALYSIS_RESULT=$(node $HOME/.claude/sdd/bin/sdd-tools.cjs profile-questionnaire --answers "$ANSWERS_PATH" --json 2>/dev/null)
+ANALYSIS_RESULT=$(sdd-sdk query profile-questionnaire --answers "$ANSWERS_PATH" --json 2>/dev/null)
 ```
 
 Parse the analysis JSON from the result.
@@ -271,7 +271,7 @@ Write updated analysis JSON back to `$ANALYSIS_PATH`.
 Display: "◆ Writing profile..."
 
 ```bash
-node $HOME/.claude/sdd/bin/sdd-tools.cjs write-profile --input "$ANALYSIS_PATH" --json 2>/dev/null
+sdd-sdk query write-profile --input "$ANALYSIS_PATH" --json
 ```
 
 Display: "✓ Profile written to $HOME/.claude/sdd/USER-PROFILE.md"
@@ -350,15 +350,15 @@ Generate selected artifacts sequentially (file I/O is fast, no benefit from para
 **For /sdd-dev-preferences (if selected):**
 
 ```bash
-node $HOME/.claude/sdd/bin/sdd-tools.cjs generate-dev-preferences --analysis "$ANALYSIS_PATH" --json 2>/dev/null
+sdd-sdk query generate-dev-preferences --analysis "$ANALYSIS_PATH" --json
 ```
 
-Display: "✓ Generated /sdd-dev-preferences at $HOME/.claude/commands/sdd/dev-preferences.md"
+Display: "✓ Generated /sdd-dev-preferences at $HOME/.claude/skills/sdd-dev-preferences/SKILL.md"
 
 **For CLAUDE.md profile section (if selected):**
 
 ```bash
-node $HOME/.claude/sdd/bin/sdd-tools.cjs generate-claude-profile --analysis "$ANALYSIS_PATH" --json 2>/dev/null
+sdd-sdk query generate-claude-profile --analysis "$ANALYSIS_PATH" --json
 ```
 
 Display: "✓ Added profile section to CLAUDE.md"
@@ -366,12 +366,12 @@ Display: "✓ Added profile section to CLAUDE.md"
 **For Global CLAUDE.md (if selected):**
 
 ```bash
-node $HOME/.claude/sdd/bin/sdd-tools.cjs generate-claude-profile --analysis "$ANALYSIS_PATH" --global --json 2>/dev/null
+sdd-sdk query generate-claude-profile --analysis "$ANALYSIS_PATH" --global --json
 ```
 
 Display: "✓ Added profile section to $HOME/.claude/CLAUDE.md"
 
-**Error handling:** If any sdd-tools.cjs call fails, display the error message and use AskUserQuestion to offer "Retry" or "Skip this artifact". On retry, re-run the command. On skip, continue to next artifact.
+**Error handling:** If any `sdd-sdk query` or sdd-tools.cjs call fails, display the error message and use AskUserQuestion to offer "Retry" or "Skip this artifact". On retry, re-run the command. On skip, continue to next artifact.
 
 ---
 
@@ -412,7 +412,7 @@ Your profile:    $HOME/.claude/sdd/USER-PROFILE.md
 Then list paths for each generated artifact:
 ```
 Artifacts:
-  ✓ /sdd-dev-preferences   $HOME/.claude/commands/sdd/dev-preferences.md
+  ✓ /sdd-dev-preferences   $HOME/.claude/skills/sdd-dev-preferences/SKILL.md
   ✓ CLAUDE.md section       ./CLAUDE.md
   ✓ Global CLAUDE.md        $HOME/.claude/CLAUDE.md
 ```
@@ -446,7 +446,7 @@ rm -f "$ANALYSIS_PATH" 2>/dev/null
 - [ ] Profile written to USER-PROFILE.md via write-profile subcommand
 - [ ] Result display shows report card table and highlight reel with evidence
 - [ ] Artifact selection uses multiSelect with all options pre-selected
-- [ ] Artifacts generated sequentially via sdd-tools.cjs subcommands
+- [ ] Artifacts generated sequentially via sdd-sdk query (or sdd-tools.cjs) subcommands
 - [ ] Refresh diff shows changed dimensions when --refresh was used
 - [ ] Temp files cleaned up on completion
 </success_criteria>

package/sdd/workflows/progress.md

@@ -12,14 +12,14 @@ Read all files referenced by the invoking prompt's execution_context before star
 **Load progress context (paths only):**
 
 ```bash
-INIT=$(node "$HOME/.claude/sdd/bin/sdd-tools.cjs" init progress)
+INIT=$(sdd-sdk query 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 "$HOME/.claude/sdd/bin/sdd-tools.cjs" config-get workflow.discuss_mode 2>/dev/null || echo "discuss")
+DISCUSS_MODE=$(sdd-sdk query config-get workflow.discuss_mode 2>/dev/null || echo "discuss")
 ```
 
 If `project_exists` is false (no `.planning/` directory):
@@ -27,26 +27,26 @@ If `project_exists` is false (no `.planning/` directory):
 ```
 No planning structure found.
 
-Run /sdd-new-project to start a new project.
+Run /sdd:new-project to start a new project.
 ```
 
 Exit.
 
-If missing STATE.md: suggest `/sdd-new-project`.
+If missing STATE.md: suggest `/sdd: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 `/sdd-new-project`.
+If missing both ROADMAP.md and PROJECT.md: suggest `/sdd:new-project`.
 </step>
 
 <step name="load">
-**Use structured extraction from sdd-tools:**
+**Use structured extraction from `sdd-sdk query` (or legacy sdd-tools.cjs):**
 
 Instead of reading full files, use targeted tools to get only the data needed for the report:
-- `ROADMAP=$(node "$HOME/.claude/sdd/bin/sdd-tools.cjs" roadmap analyze)`
-- `STATE=$(node "$HOME/.claude/sdd/bin/sdd-tools.cjs" state-snapshot)`
+- `ROADMAP=$(sdd-sdk query roadmap.analyze)`
+- `STATE=$(sdd-sdk query state-snapshot)`
 
 This minimizes orchestrator context usage.
 </step>
@@ -55,7 +55,7 @@ This minimizes orchestrator context usage.
 **Get comprehensive roadmap analysis (replaces manual parsing):**
 
 ```bash
-ROADMAP=$(node "$HOME/.claude/sdd/bin/sdd-tools.cjs" roadmap analyze)
+ROADMAP=$(sdd-sdk query roadmap.analyze)
 ```
 
 This returns structured JSON with:
@@ -74,7 +74,7 @@ Use this instead of manually reading/parsing ROADMAP.md.
 - Find the 2-3 most recent SUMMARY.md files
 - Use `summary-extract` for efficient parsing:
   ```bash
-  node "$HOME/.claude/sdd/bin/sdd-tools.cjs" summary-extract <path> --fields one_liner
+  sdd-sdk query summary-extract <path> --fields one_liner
   ```
 - This shows "what we've been working on"
   </step>
@@ -89,11 +89,16 @@ Use this instead of manually reading/parsing ROADMAP.md.
   </step>
 
 <step name="report">
-**Generate progress bar from sdd-tools, then present rich status report:**
+> ⚠️ Context authority: PROJECT.md, STATE.md, and ROADMAP.md are the authoritative sources
+> for project name, milestone, current phase, and next-step routing. CLAUDE.md ## Project
+> blocks are a secondary config aid that may be significantly stale — do NOT use the
+> CLAUDE.md project description as a source for any progress report field.
+
+**Generate progress bar from `sdd-sdk query progress` / `progress.json`, then present rich status report:**
 
 ```bash
 # Get formatted progress bar
-PROGRESS_BAR=$(node "$HOME/.claude/sdd/bin/sdd-tools.cjs" progress bar --raw)
+PROGRESS_BAR=$(sdd-sdk query progress.bar --raw)
 ```
 
 Present:
@@ -123,10 +128,10 @@ CONTEXT: [✓ if has_context | - if not]
 - [e.g. jq -r '.blockers[].text' from state-snapshot]
 
 ## Pending Todos
-- [count] pending — /sdd-check-todos to review
+- [count] pending — /sdd:capture --list to review
 
 ## Active Debug Sessions
-- [count] active — /sdd-debug to continue
+- [count] active — /sdd:debug to continue
 (Only show this section if count > 0)
 
 ## What's Next
@@ -135,6 +140,31 @@ CONTEXT: [✓ if has_context | - if not]
 
 </step>
 
+<step name="mvp_display">
+**MVP-mode display (when phase has `**Mode:** mvp` in ROADMAP.md).**
+
+Resolve `MVP_MODE` per phase via the centralized resolver. progress has no `--mvp` CLI flag (mode is inherited from the planned phase), so we omit `--cli-flag`:
+
+```bash
+MVP_MODE=$(sdd-sdk query phase.mvp-mode "${PHASE_NUMBER}" --pick active)
+```
+
+When `MVP_MODE=true`, the per-phase progress block adds a **user-flow status** sub-block sourced from the phase's PLAN.md task names. Each task whose name reads like a user-visible capability (e.g., "Register flow", "Login flow", "Password reset") is rendered as a status line:
+
+```
+Phase 1 — User Auth MVP
+  ✅ Walking Skeleton complete           ← from SKELETON.md existence
+  ✅ Register flow working               ← from PLAN.md task with summary
+  ✅ Login flow working                  ← from PLAN.md task with summary
+  🔄 Password reset (in progress)        ← from PLAN.md task without summary
+  ⬜ Email verification                  ← from PLAN.md task not yet started
+```
+
+**User-flow filter:** Tasks whose names are technical-sounding ("Wire DB schema", "Create migration", "Bump deps") are NOT rendered as user-flow status lines. Heuristic: a task name is user-flow-shaped if it ends in "flow", "page", "screen", or starts with a verb the user would recognize ("Register", "Login", "Upload", "View"). Tasks that fail the heuristic still count toward the standard task progress total but don't appear in the user-flow sub-block.
+
+When `MVP_MODE=false` (mode is null, absent, or the phase has no `**Mode:**` line), fall back to the standard display path — no behavioral change.
+</step>
+
 <step name="route">
 **Determine next action based on verified counts.**
 
@@ -168,7 +198,7 @@ Track:
 Scan ALL phases in the current milestone for outstanding verification debt using the CLI (which respects milestone boundaries via `getMilestonePhaseFilter`):
 
 ```bash
-DEBT=$(node "$HOME/.claude/sdd/bin/sdd-tools.cjs" audit-uat --raw 2>/dev/null)
+DEBT=$(sdd-sdk query audit-uat --raw 2>/dev/null)
 ```
 
 Parse JSON for `summary.total_items` and `summary.total_files`.
@@ -185,8 +215,8 @@ Track: `outstanding_debt` — `summary.total_items` from the audit.
 | {phase} | {filename} | {pending_count} pending, {skipped_count} skipped, {blocked_count} blocked |
 | {phase} | {filename} | human_needed — {count} items |
 
-Review: `/sdd-audit-uat ${SDD_WS}` — full cross-phase audit
-Resume testing: `/sdd-verify-work {phase} ${SDD_WS}` — retest specific phase
+Review: `/sdd:audit-uat ${SDD_WS}` — full cross-phase audit
+Resume testing: `/sdd:verify-work {phase} ${SDD_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.
@@ -211,13 +241,13 @@ Read its `<objective>` section.
 ```
 ---
 
-## ▶ Next Up
+## ▶ Next Up — [${PROJECT_CODE}] ${PROJECT_TITLE}
 
 **{phase}-{plan}: [Plan Name]** — [objective summary from PLAN.md]
 
 `/clear` then:
 
-`/sdd-execute-phase {phase} ${SDD_WS}`
+`/sdd:execute-phase {phase} ${SDD_WS}`
 
 ---
 ```
@@ -231,7 +261,7 @@ Check if `{phase_num}-CONTEXT.md` exists in phase directory.
 Check if current phase has UI indicators:
 
 ```bash
-PHASE_SECTION=$(node "$HOME/.claude/sdd/bin/sdd-tools.cjs" roadmap get-phase "${CURRENT_PHASE}" 2>/dev/null)
+PHASE_SECTION=$(sdd-sdk query roadmap.get-phase "${CURRENT_PHASE}" 2>/dev/null)
 PHASE_HAS_UI=$(echo "$PHASE_SECTION" | grep -qi "UI hint.*yes" && echo "true" || echo "false")
 ```
 
@@ -240,14 +270,14 @@ PHASE_HAS_UI=$(echo "$PHASE_SECTION" | grep -qi "UI hint.*yes" && echo "true" ||
 ```
 ---
 
-## ▶ Next Up
+## ▶ Next Up — [${PROJECT_CODE}] ${PROJECT_TITLE}
 
 **Phase {N}: {Name}** — {Goal from ROADMAP.md}
 <sub>✓ Context gathered, ready to plan</sub>
 
 `/clear` then:
 
-`/sdd-plan-phase {phase-number} ${SDD_WS}`
+`/sdd:plan-phase {phase-number} ${SDD_WS}`
 
 ---
 ```
@@ -257,20 +287,20 @@ PHASE_HAS_UI=$(echo "$PHASE_SECTION" | grep -qi "UI hint.*yes" && echo "true" ||
 ```
 ---
 
-## ▶ Next Up
+## ▶ Next Up — [${PROJECT_CODE}] ${PROJECT_TITLE}
 
 **Phase {N}: {Name}** — {Goal from ROADMAP.md}
 
 `/clear` then:
 
-`/sdd-discuss-phase {phase}` — gather context and clarify approach
+`/sdd:discuss-phase {phase}` — gather context and clarify approach
 
 ---
 
 **Also available:**
-- `/sdd-ui-phase {phase}` — generate UI design contract (recommended for frontend phases)
-- `/sdd-plan-phase {phase}` — skip discussion, plan directly
-- `/sdd-list-phase-assumptions {phase}` — see Claude's assumptions
+- `/sdd:ui-phase {phase}` — generate UI design contract (recommended for frontend phases)
+- `/sdd:plan-phase {phase}` — skip discussion, plan directly
+- `/sdd:discuss-phase {phase}` — include assumptions check before planning
 
 ---
 ```
@@ -280,19 +310,19 @@ PHASE_HAS_UI=$(echo "$PHASE_SECTION" | grep -qi "UI hint.*yes" && echo "true" ||
 ```
 ---
 
-## ▶ Next Up
+## ▶ Next Up — [${PROJECT_CODE}] ${PROJECT_TITLE}
 
 **Phase {N}: {Name}** — {Goal from ROADMAP.md}
 
 `/clear` then:
 
-`/sdd-discuss-phase {phase} ${SDD_WS}` — gather context and clarify approach
+`/sdd:discuss-phase {phase} ${SDD_WS}` — gather context and clarify approach
 
 ---
 
 **Also available:**
-- `/sdd-plan-phase {phase} ${SDD_WS}` — skip discussion, plan directly
-- `/sdd-list-phase-assumptions {phase} ${SDD_WS}` — see Claude's assumptions
+- `/sdd:plan-phase {phase} ${SDD_WS}` — skip discussion, plan directly
+- `/sdd:discuss-phase {phase} ${SDD_WS}` — include assumptions check before planning
 
 ---
 ```
@@ -312,13 +342,13 @@ UAT.md exists with gaps (diagnosed issues). User needs to plan fixes.
 
 `/clear` then:
 
-`/sdd-plan-phase {phase} --gaps ${SDD_WS}`
+`/sdd:plan-phase {phase} --gaps ${SDD_WS}`
 
 ---
 
 **Also available:**
-- `/sdd-execute-phase {phase} ${SDD_WS}` — execute phase plans
-- `/sdd-verify-work {phase} ${SDD_WS}` — run more UAT testing
+- `/sdd:execute-phase {phase} ${SDD_WS}` — execute phase plans
+- `/sdd:verify-work {phase} ${SDD_WS}` — run more UAT testing
 
 ---
 ```
@@ -338,13 +368,13 @@ UAT.md exists with `status: partial` — testing session ended before all items
 
 `/clear` then:
 
-`/sdd-verify-work {phase} ${SDD_WS}` — resume testing from where you left off
+`/sdd:verify-work {phase} ${SDD_WS}` — resume testing from where you left off
 
 ---
 
 **Also available:**
-- `/sdd-audit-uat ${SDD_WS}` — full cross-phase UAT audit
-- `/sdd-execute-phase {phase} ${SDD_WS}` — execute phase plans
+- `/sdd:audit-uat ${SDD_WS}` — full cross-phase UAT audit
+- `/sdd:execute-phase {phase} ${SDD_WS}` — execute phase plans
 
 ---
 ```
@@ -377,7 +407,7 @@ Read ROADMAP.md to get the next phase's name and goal.
 Check if next phase has UI indicators:
 
 ```bash
-NEXT_PHASE_SECTION=$(node "$HOME/.claude/sdd/bin/sdd-tools.cjs" roadmap get-phase "$((Z+1))" 2>/dev/null)
+NEXT_PHASE_SECTION=$(sdd-sdk query roadmap.get-phase "$((Z+1))" 2>/dev/null)
 NEXT_HAS_UI=$(echo "$NEXT_PHASE_SECTION" | grep -qi "UI hint.*yes" && echo "true" || echo "false")
 ```
 
@@ -388,20 +418,20 @@ NEXT_HAS_UI=$(echo "$NEXT_PHASE_SECTION" | grep -qi "UI hint.*yes" && echo "true
 
 ## ✓ Phase {Z} Complete
 
-## ▶ Next Up
+## ▶ Next Up — [${PROJECT_CODE}] ${PROJECT_TITLE}
 
 **Phase {Z+1}: {Name}** — {Goal from ROADMAP.md}
 
 `/clear` then:
 
-`/sdd-discuss-phase {Z+1}` — gather context and clarify approach
+`/sdd:discuss-phase {Z+1}` — gather context and clarify approach
 
 ---
 
 **Also available:**
-- `/sdd-ui-phase {Z+1}` — generate UI design contract (recommended for frontend phases)
-- `/sdd-plan-phase {Z+1}` — skip discussion, plan directly
-- `/sdd-verify-work {Z}` — user acceptance test before continuing
+- `/sdd:ui-phase {Z+1}` — generate UI design contract (recommended for frontend phases)
+- `/sdd:plan-phase {Z+1}` — skip discussion, plan directly
+- `/sdd:verify-work {Z}` — user acceptance test before continuing
 
 ---
 ```
@@ -413,19 +443,19 @@ NEXT_HAS_UI=$(echo "$NEXT_PHASE_SECTION" | grep -qi "UI hint.*yes" && echo "true
 
 ## ✓ Phase {Z} Complete
 
-## ▶ Next Up
+## ▶ Next Up — [${PROJECT_CODE}] ${PROJECT_TITLE}
 
 **Phase {Z+1}: {Name}** — {Goal from ROADMAP.md}
 
 `/clear` then:
 
-`/sdd-discuss-phase {Z+1} ${SDD_WS}` — gather context and clarify approach
+`/sdd:discuss-phase {Z+1} ${SDD_WS}` — gather context and clarify approach
 
 ---
 
 **Also available:**
-- `/sdd-plan-phase {Z+1} ${SDD_WS}` — skip discussion, plan directly
-- `/sdd-verify-work {Z} ${SDD_WS}` — user acceptance test before continuing
+- `/sdd:plan-phase {Z+1} ${SDD_WS}` — skip discussion, plan directly
+- `/sdd:verify-work {Z} ${SDD_WS}` — user acceptance test before continuing
 
 ---
 ```
@@ -441,18 +471,18 @@ NEXT_HAS_UI=$(echo "$NEXT_PHASE_SECTION" | grep -qi "UI hint.*yes" && echo "true
 
 All {N} phases finished!
 
-## ▶ Next Up
+## ▶ Next Up — [${PROJECT_CODE}] ${PROJECT_TITLE}
 
 **Complete Milestone** — archive and prepare for next
 
 `/clear` then:
 
-`/sdd-complete-milestone ${SDD_WS}`
+`/sdd:complete-milestone ${SDD_WS}`
 
 ---
 
 **Also available:**
-- `/sdd-verify-work ${SDD_WS}` — user acceptance test before completing milestone
+- `/sdd:verify-work ${SDD_WS}` — user acceptance test before completing milestone
 
 ---
 ```
@@ -472,13 +502,13 @@ Read MILESTONES.md to find the last completed milestone version.
 
 Ready to plan the next milestone.
 
-## ▶ Next Up
+## ▶ Next Up — [${PROJECT_CODE}] ${PROJECT_TITLE}
 
 **Start Next Milestone** — questioning → research → requirements → roadmap
 
 `/clear` then:
 
-`/sdd-new-milestone ${SDD_WS}`
+`/sdd:new-milestone ${SDD_WS}`
 
 ---
 ```
@@ -488,11 +518,123 @@ Ready to plan the next milestone.
 <step name="edge_cases">
 **Handle edge cases:**
 
-- Phase complete but next phase not planned → offer `/sdd-plan-phase [next] ${SDD_WS}`
+- Phase complete but next phase not planned → offer `/sdd:plan-phase [next] ${SDD_WS}`
 - All work complete → offer milestone completion
 - Blockers present → highlight before offering to continue
-- Handoff file exists → mention it, offer `/sdd-resume-work ${SDD_WS}`
-  </step>
+- Handoff file exists → mention it, offer `/sdd:resume-work ${SDD_WS}`
+</step>
+
+<step name="forensic_audit">
+**Forensic Integrity Audit** — only runs when `--forensic` is present in ARGUMENTS.
+
+If `--forensic` is NOT present in ARGUMENTS: skip this step entirely. Default progress behavior (standard report + routing) is unchanged.
+
+If `--forensic` IS present: after the standard report and routing suggestion have been displayed, append the following audit section.
+
+---
+
+## Forensic Integrity Audit
+
+Running 6 deep checks against project state...
+
+Run each check in order. For each check, emit ✓ (pass) or ⚠ (warning) with concrete evidence when a problem is found.
+
+**Check 1 — STATE vs artifact consistency**
+
+Read STATE.md `status` / `stopped_at` fields (from the STATE snapshot already loaded). Compare against the artifact count from the roadmap analysis. If STATE.md claims the current phase is pending/mid-flight but the artifact count shows it as complete (all PLAN.md files have matching SUMMARY.md files), flag inconsistency. Emit:
+- ✓ `STATE.md consistent with artifact count` — if both agree
+- ⚠ `STATE.md claims [status] but artifact count shows phase complete` — with the specific values
+
+**Check 2 — Orphaned handoff files**
+
+Check for existence of:
+```bash
+ls .planning/HANDOFF.json .planning/phases/*/.continue-here.md .planning/phases/*/*HANDOFF*.md 2>/dev/null || true
+```
+Also check `.planning/continue-here.md`.
+
+Emit:
+- ✓ `No orphaned handoff files` — if none found
+- ⚠ `Orphaned handoff files found` — list each file path, add: `→ Work was paused mid-flight. Read the handoff before continuing.`
+
+**Check 3 — Deferred scope drift**
+
+Search phase artifacts (CONTEXT.md, DISCUSSION-LOG.md, BUG-BRIEF.md, VERIFICATION.md, SUMMARY.md, HANDOFF.md files under `.planning/phases/`) for patterns:
+```bash
+grep -rl "defer to Phase\|future phase\|out of scope Phase\|deferred to Phase" .planning/phases/ 2>/dev/null || true
+```
+
+For each match, extract the referenced phase number. Cross-reference against ROADMAP.md phase list. If the referenced phase number is NOT in ROADMAP.md, flag as deferred scope not captured.
+
+Emit:
+- ✓ `All deferred scope captured in ROADMAP` — if no mismatches
+- ⚠ `Deferred scope references phase(s) not in ROADMAP` — list: file, reference text, missing phase number
+
+**Check 4 — Memory-flagged pending work**
+
+Check if `.planning/MEMORY.md` or `.planning/memory/` exists:
+```bash
+ls .planning/MEMORY.md .planning/memory/*.md 2>/dev/null || true
+```
+
+If found, grep for entries containing: `pending`, `status`, `deferred`, `not yet run`, `backfill`, `blocking`.
+
+Emit:
+- ✓ `No memory entries flagging pending work` — if none found or no MEMORY.md
+- ⚠ `Memory entries flag pending/deferred work` — list the matching lines (max 5, truncated at 80 chars)
+
+**Check 5 — Blocking operational todos**
+
+Check for pending todos:
+```bash
+ls .planning/todos/pending/*.md 2>/dev/null || true
+```
+
+For files found, scan for keywords indicating operational blockers: `script`, `credential`, `API key`, `manual`, `verification`, `setup`, `configure`, `run `.
+
+Emit:
+- ✓ `No blocking operational todos` — if no pending todos or none match operational keywords
+- ⚠ `Blocking operational todos found` — list the file names and matching keywords (max 5)
+
+**Check 6 — Uncommitted code**
+
+```bash
+git status --porcelain 2>/dev/null | grep -v "^??" | grep -v "^.planning\/" | grep -v "^\.\." | head -10
+```
+
+If output is non-empty (modified/staged files outside `.planning/`), flag as uncommitted code.
+
+Emit:
+- ✓ `Working tree clean` — if no modified files outside `.planning/`
+- ⚠ `Uncommitted changes in source files` — list up to 10 file paths
+
+---
+
+After all 6 checks, display the verdict:
+
+**If all 6 checks passed:**
+```
+### Verdict: CLEAN
+
+The standard progress report is trustworthy — proceed with the routing suggestion above.
+```
+
+**If 1 or more checks failed:**
+```
+### Verdict: N INTEGRITY ISSUE(S) FOUND
+
+The standard progress report may not reflect true project state.
+Review the flagged items above before acting on the routing suggestion.
+```
+
+Then for each failed check, add a concrete next action:
+- Check 2 (orphaned handoff): `Read the handoff file(s) and resume from where work was paused: /sdd:resume-work ${SDD_WS}`
+- Check 3 (deferred scope): `Add the missing phases to ROADMAP.md or update the deferred references`
+- Check 4 (memory pending): `Review the flagged memory entries and resolve or clear them`
+- Check 5 (blocking todos): `Complete the operational steps in .planning/todos/pending/ before continuing`
+- Check 6 (uncommitted code): `Commit or stash the uncommitted changes before advancing`
+- Check 1 (STATE inconsistency): `Run /sdd:verify-work ${PHASE} ${SDD_WS} to reconcile state`
+</step>
 
 </process>
 
@@ -501,7 +643,7 @@ Ready to plan the next milestone.
 - [ ] Rich context provided (recent work, decisions, issues)
 - [ ] Current position clear with visual progress
 - [ ] What's next clearly explained
-- [ ] Smart routing: /sdd-execute-phase if plans exist, /sdd-plan-phase if not
+- [ ] Smart routing: /sdd:execute-phase if plans exist, /sdd:plan-phase if not
 - [ ] User confirms before any action
 - [ ] Seamless handoff to appropriate sdd command
       </success_criteria>