@bhargavvc/sdd-cc 1.35.0 → 1.42.3

package/commands/sdd/mvp-phase.md

@@ -0,0 +1,45 @@
+---
+name: sdd:mvp-phase
+description: Plan a phase as a vertical MVP slice — user story, SPIDR splitting, then plan-phase
+argument-hint: "<phase-number>"
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+  - Glob
+  - Grep
+  - Agent
+  - AskUserQuestion
+requires: [new-project, phase, plan-phase]
+---
+<objective>
+Guide the user through MVP-mode planning for a phase. The command:
+
+1. Prompts for an "As a / I want to / So that" user story (three structured questions)
+2. Runs SPIDR splitting check — if the story is too large, walks through Spike/Paths/Interfaces/Data/Rules and offers to split into multiple phases
+3. Writes `**Mode:** mvp` and the reformatted `**Goal:**` to the phase's ROADMAP.md section
+4. Delegates to `/sdd plan-phase <N>` which auto-detects MVP mode via the roadmap field
+
+Phase 1 of the vertical-mvp-slice PRD shipped the planner-side machinery; this command is the user entry point for it.
+</objective>
+
+<execution_context>
+@~/.claude/sdd/workflows/mvp-phase.md
+@~/.claude/sdd/references/spidr-splitting.md
+@~/.claude/sdd/references/user-story-template.md
+</execution_context>
+
+<runtime_note>
+**Copilot (VS Code):** Use `vscode_askquestions` wherever this workflow calls `AskUserQuestion`. Equivalent API.
+</runtime_note>
+
+<context>
+Phase number: $ARGUMENTS (required — integer or decimal like `2.1`)
+
+The phase must already exist in ROADMAP.md (created via `/sdd new-project`, `/sdd add-phase`, or `/sdd insert-phase`). This command does not create new phases — it converts an existing phase to MVP mode.
+</context>
+
+<process>
+Execute the mvp-phase workflow from @~/.claude/sdd/workflows/mvp-phase.md end-to-end.
+Preserve all gates: phase existence, status guard (refuse in_progress/completed), user-story format validation, SPIDR splitting check, ROADMAP write confirmation, plan-phase delegation.
+</process>

package/commands/sdd/new-milestone.md

@@ -6,8 +6,9 @@ allowed-tools:
   - Read
   - Write
   - Bash
-  - Task
+  - Agent
   - AskUserQuestion
+requires: [new-project, phase, plan-phase]
 ---
 <objective>
 Start a new milestone: questioning → research (optional) → requirements → roadmap.
@@ -21,7 +22,7 @@ Brownfield equivalent of new-project. Project exists, PROJECT.md has history. Ga
 - `.planning/ROADMAP.md` — phase structure (continues numbering)
 - `.planning/STATE.md` — reset for new milestone
 
-**After:** `/sdd-plan-phase [N]` to start execution.
+**After:** `/sdd:plan-phase [N]` to start execution.
 </objective>
 
 <execution_context>
@@ -39,6 +40,6 @@ Project and milestone context files are resolved inside the workflow (`init new-
 </context>
 
 <process>
-Execute the new-milestone workflow from @~/.claude/sdd/workflows/new-milestone.md end-to-end.
+Execute end-to-end.
 Preserve all workflow gates (validation, questioning, research, requirements, roadmap approval, commits).
 </process>

package/commands/sdd/new-project.md

@@ -6,8 +6,9 @@ allowed-tools:
   - Read
   - Bash
   - Write
-  - Task
+  - Agent
   - AskUserQuestion
+requires: [config, phase, plan-phase]
 ---
 <runtime_note>
 **Copilot (VS Code):** Use `vscode_askquestions` wherever this workflow calls `AskUserQuestion`. They are equivalent — `vscode_askquestions` is the VS Code Copilot implementation of the same interactive question API.
@@ -29,7 +30,7 @@ Initialize a new project through unified flow: questioning → research (optiona
 - `.planning/ROADMAP.md` — phase structure
 - `.planning/STATE.md` — project memory
 
-**After this command:** Run `/sdd-plan-phase 1` to start execution.
+**After this command:** Run `/sdd:plan-phase 1` to start execution.
 </objective>
 
 <execution_context>
@@ -41,6 +42,6 @@ Initialize a new project through unified flow: questioning → research (optiona
 </execution_context>
 
 <process>
-Execute the new-project workflow from @~/.claude/sdd/workflows/new-project.md end-to-end.
+Execute end-to-end.
 Preserve all workflow gates (validation, approvals, commits, routing).
 </process>

package/commands/sdd/ns-context.md

@@ -0,0 +1,23 @@
+---
+name: sdd-context
+description: "codebase intelligence | map graphify docs learnings"
+argument-hint: ""
+allowed-tools:
+  - Read
+  - Skill
+requires: [map-codebase, graphify, docs-update, extract-learnings]
+---
+
+Route to the appropriate codebase-intelligence skill based on the user's intent.
+`sdd-scan` and `sdd-intel` were folded into `sdd-map-codebase` flags by #2790.
+
+| User wants | Invoke |
+|---|---|
+| Map the full codebase structure | sdd-map-codebase |
+| Quick lightweight codebase scan | sdd-map-codebase --fast |
+| Query mapped intelligence files | sdd-map-codebase --query |
+| Generate a knowledge graph | sdd-graphify |
+| Update project documentation | sdd-docs-update |
+| Extract learnings from a completed phase | sdd-extract-learnings |
+
+Invoke the matched skill directly using the Skill tool.

package/commands/sdd/ns-ideate.md

@@ -0,0 +1,24 @@
+---
+name: sdd-ideate
+description: "exploration capture | explore sketch spike spec capture"
+argument-hint: ""
+allowed-tools:
+  - Read
+  - Skill
+requires: [capture, explore, sketch, spike, spec-phase]
+---
+
+Route to the appropriate exploration / capture skill based on the user's intent.
+`sdd-note`, `sdd-add-todo`, `sdd-add-backlog`, and `sdd-plant-seed` were folded
+into `sdd-capture` (with `--note`, default, `--backlog`, `--seed` modes) by
+#2790. The capture target lists pending todos via `--list`.
+
+| User wants | Invoke |
+|---|---|
+| Explore an idea or opportunity | sdd-explore |
+| Sketch out a rough design or plan | sdd-sketch |
+| Time-boxed technical spike | sdd-spike |
+| Write a spec for a phase | sdd-spec-phase |
+| Capture a thought (todo / note / backlog / seed) | sdd-capture |
+
+Invoke the matched skill directly using the Skill tool.

package/commands/sdd/ns-manage.md

@@ -0,0 +1,29 @@
+---
+name: sdd-manage
+description: "config workspace | workstreams thread update ship inbox"
+argument-hint: ""
+allowed-tools:
+  - Read
+  - Skill
+requires: [config, workspace, workstreams, thread, pause-work, resume-work, update, ship, inbox, pr-branch, undo]
+---
+
+Route to the appropriate management skill based on the user's intent.
+`sdd-config` (settings + advanced + integrations + profile) and `sdd-workspace`
+(new + list + remove) are post-#2790 consolidated entries.
+
+| User wants | Invoke |
+|---|---|
+| Configure SDD settings (basic / advanced / integrations / profile) | sdd-config |
+| Manage workspaces (create / list / remove) | sdd-workspace |
+| Manage parallel workstreams | sdd-workstreams |
+| Continue work in a fresh context thread | sdd-thread |
+| Pause current work | sdd-pause-work |
+| Resume paused work | sdd-resume-work |
+| Update the SDD installation | sdd-update |
+| Ship completed work | sdd-ship |
+| Process inbox items | sdd-inbox |
+| Create a clean PR branch | sdd-pr-branch |
+| Undo the last SDD action | sdd-undo |
+
+Invoke the matched skill directly using the Skill tool.

package/commands/sdd/ns-project.md

@@ -0,0 +1,22 @@
+---
+name: sdd-project
+description: "project lifecycle | milestones audits summary"
+argument-hint: ""
+allowed-tools:
+  - Read
+  - Skill
+---
+
+Route to the appropriate project / milestone skill based on the user's intent.
+`sdd-plan-milestone-gaps` was deleted by #2790 — gap planning now happens
+inline as part of `sdd-audit-milestone`'s output.
+
+| User wants | Invoke |
+|---|---|
+| Start a new project | sdd-new-project |
+| Create a new milestone | sdd-new-milestone |
+| Complete the current milestone | sdd-complete-milestone |
+| Audit a milestone for issues | sdd-audit-milestone |
+| Summarize milestone status | sdd-milestone-summary |
+
+Invoke the matched skill directly using the Skill tool.

package/commands/sdd/ns-review.md

@@ -0,0 +1,26 @@
+---
+name: sdd-quality
+description: "quality gates | code review debug audit security eval ui"
+argument-hint: ""
+allowed-tools:
+  - Read
+  - Skill
+requires: [code-review, audit-uat, secure-phase, eval-review, ui-review, validate-phase, debug, forensics]
+---
+
+Route to the appropriate quality / review skill based on the user's intent.
+`sdd-code-review-fix` was absorbed by `sdd-code-review --fix` in #2790.
+
+| User wants | Invoke |
+|---|---|
+| Review code for quality and correctness | sdd-code-review |
+| Auto-fix code review findings | sdd-code-review --fix |
+| Audit UAT / acceptance testing | sdd-audit-uat |
+| Security review of a phase | sdd-secure-phase |
+| Evaluate AI response quality | sdd-eval-review |
+| Review UI for design and accessibility | sdd-ui-review |
+| Validate phase outputs | sdd-validate-phase |
+| Debug a failing feature or error | sdd-debug |
+| Forensic investigation of a broken system | sdd-forensics |
+
+Invoke the matched skill directly using the Skill tool.

package/commands/sdd/ns-workflow.md

@@ -0,0 +1,28 @@
+---
+name: sdd-workflow
+description: "workflow | discuss plan execute verify phase progress"
+argument-hint: ""
+allowed-tools:
+  - Read
+  - Skill
+requires: [discuss-phase, spec-phase, plan-phase, execute-phase, verify-work, phase, progress, ultraplan-phase, plan-review-convergence]
+---
+
+Route to the appropriate phase-pipeline skill based on the user's intent.
+Sub-skill names below are post-#2790 consolidated targets — `sdd-phase`
+absorbs the former add/insert/remove/edit-phase commands and `sdd-progress`
+absorbs the former next/do commands.
+
+| User wants | Invoke |
+|---|---|
+| Gather context before planning | sdd-discuss-phase |
+| Clarify what a phase delivers | sdd-spec-phase |
+| Create a PLAN.md | sdd-plan-phase |
+| Execute plans in a phase | sdd-execute-phase |
+| Verify built features through UAT | sdd-verify-work |
+| Add / insert / remove / edit a phase | sdd-phase |
+| Advance to the next logical step | sdd-progress |
+| Offload planning to the ultraplan cloud | sdd-ultraplan-phase |
+| Cross-AI plan review convergence loop | sdd-plan-review-convergence |
+
+Invoke the matched skill directly using the Skill tool.

package/commands/sdd/pause-work.md

@@ -1,10 +1,12 @@
 ---
 name: sdd:pause-work
 description: Create context handoff when pausing work mid-phase
+argument-hint: "[--report]"
 allowed-tools:
   - Read
   - Write
   - Bash
+requires: [phase, progress]
 ---
 
 <objective>
@@ -27,7 +29,10 @@ State and phase progress are gathered in-workflow with targeted reads.
 </context>
 
 <process>
-**Follow the pause-work workflow** from `@~/.claude/sdd/workflows/pause-work.md`.
+If `--report` is in $ARGUMENTS:
+Read and execute `~/.claude/sdd/workflows/session-report.md` end-to-end.
+
+**Follow the pause-work workflow**.
 
 The workflow handles all logic including:
 1. Phase directory detection

package/commands/sdd/phase.md

@@ -0,0 +1,56 @@
+---
+name: sdd:phase
+description: CRUD for phases in ROADMAP.md — add, insert, remove, or edit phases
+argument-hint: "[--insert | --remove | --edit] <phase-name-or-number>"
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+  - Glob
+---
+
+<objective>
+Manage phases in ROADMAP.md with a single consolidated command.
+
+Mode routing:
+- **default** (no flag): Add a new integer phase to the end of the current milestone → add-phase workflow
+- **--insert**: Insert urgent work as a decimal phase (e.g., 72.1) between existing phases → insert-phase workflow
+- **--remove**: Remove a future phase and renumber subsequent phases → remove-phase workflow
+- **--edit**: Edit any field of an existing phase in place → edit-phase workflow
+</objective>
+
+<routing>
+
+| Flag | Action | Workflow |
+|------|--------|----------|
+| (none) | Add new integer phase at end of milestone | add-phase |
+| --insert | Insert decimal phase (e.g., 72.1) after specified phase | insert-phase |
+| --remove | Remove future phase, renumber subsequent | remove-phase |
+| --edit | Edit fields of existing phase in place | edit-phase |
+
+</routing>
+
+<execution_context>
+@~/.claude/sdd/workflows/add-phase.md
+@~/.claude/sdd/workflows/insert-phase.md
+@~/.claude/sdd/workflows/remove-phase.md
+@~/.claude/sdd/workflows/edit-phase.md
+</execution_context>
+
+<context>
+Arguments: $ARGUMENTS
+
+Parse the first token of $ARGUMENTS:
+- If it is `--insert`: strip the flag, pass remainder (format: <after-phase-number> <description>) to insert-phase workflow
+- If it is `--remove`: strip the flag, pass remainder (phase number) to remove-phase workflow
+- If it is `--edit`: strip the flag, pass remainder (phase-number [--force]) to edit-phase workflow
+- Otherwise: pass all of $ARGUMENTS (phase description) to add-phase workflow
+
+Roadmap and state are resolved in-workflow via `init phase-op` and targeted reads.
+</context>
+
+<process>
+1. Parse the leading flag (if any) from $ARGUMENTS.
+2. Load and execute the appropriate workflow end-to-end based on the routing table above.
+3. Preserve all validation gates from the target workflow.
+</process>

package/commands/sdd/plan-phase.md

@@ -1,24 +1,31 @@
 ---
 name: sdd:plan-phase
 description: Create detailed phase plan (PLAN.md) with verification loop
-argument-hint: "[phase] [--auto] [--research] [--skip-research] [--gaps] [--skip-verify] [--prd <file>] [--reviews] [--text]"
-agent: sdd-planner
+argument-hint: "[phase] [--auto] [--research] [--skip-research] [--research-phase <N>] [--view] [--gaps] [--skip-verify] [--prd <file>] [--ingest <path-or-glob>] [--ingest-format <auto|nygard|madr|narrative>] [--reviews] [--text] [--tdd] [--mvp]"
 allowed-tools:
   - Read
   - Write
   - Bash
   - Glob
   - Grep
-  - Task
+  - Agent
   - AskUserQuestion
   - WebFetch
   - mcp__context7__*
+requires: [discuss-phase, phase, review, update]
 ---
 <objective>
 Create executable phase prompts (PLAN.md files) for a roadmap phase with integrated research and verification.
 
 **Default flow:** Research (if needed) → Plan → Verify → Done
 
+**Research-only mode (`--research-phase <N>`):** Spawn `sdd-phase-researcher` for phase `N`, write `RESEARCH.md`, then exit before the planner runs. Useful for cross-phase research, doc review before committing to a planning approach, and correction-without-replanning loops where iterating on research alone is dramatically cheaper than re-spawning the planner. Replaces the deleted `/sdd-research-phase` command (#3042).
+
+**Research-only modifiers:**
+- **No flag** — when `RESEARCH.md` already exists, prompt the user to choose `update / view / skip`.
+- **`--research`** — force-refresh: re-spawn the researcher unconditionally, no prompt. Skips the existing-RESEARCH.md menu.
+- **`--view`** — view-only: print existing `RESEARCH.md` to stdout. Does not spawn the researcher. Cheapest mode for the correction-without-replanning loop. If no `RESEARCH.md` exists yet, errors with a hint to drop `--view`.
+
 **Orchestrator role:** Parse arguments, validate phase, research domain (unless skipped), spawn sdd-planner, verify with sdd-plan-checker, iterate until pass or max iterations, present results.
 </objective>
 
@@ -40,13 +47,16 @@ Phase number: $ARGUMENTS (optional — auto-detects next unplanned phase if omit
 - `--gaps` — Gap closure mode (reads VERIFICATION.md, skips research)
 - `--skip-verify` — Skip verification loop
 - `--prd <file>` — Use a PRD/acceptance criteria file instead of discuss-phase. Parses requirements into CONTEXT.md automatically. Skips discuss-phase entirely.
-- `--reviews` — Replan incorporating cross-AI review feedback from REVIEWS.md (produced by `/sdd-review`)
+- `--ingest <path-or-glob>` — Use one or more ADR files instead of discuss-phase. Parses locked decisions + scope fences into CONTEXT.md automatically. Skips discuss-phase entirely.
+- `--ingest-format <auto|nygard|madr|narrative>` — Optional ADR parser format override (`auto` default).
+- `--reviews` — Replan incorporating cross-AI review feedback from REVIEWS.md (produced by `/sdd:review`)
 - `--text` — Use plain-text numbered lists instead of TUI menus (required for `/rc` remote sessions)
+- `--mvp` — Vertical MVP mode. Planner organizes tasks as feature slices (UI→API→DB) instead of horizontal layers. On Phase 1 of a new project, also emits `SKELETON.md` (Walking Skeleton). Can be persisted on a phase via `**Mode:** mvp` in ROADMAP.md.
 
 Normalize phase input in step 2 before any directory lookups.
 </context>
 
 <process>
-Execute the plan-phase workflow from @~/.claude/sdd/workflows/plan-phase.md end-to-end.
+Execute end-to-end.
 Preserve all workflow gates (validation, research, planning, verification loop, routing).
 </process>

package/commands/sdd/plan-review-convergence.md

@@ -0,0 +1,59 @@
+---
+name: sdd:plan-review-convergence
+description: "Cross-AI plan convergence loop — replan with review feedback until no HIGH concerns remain."
+argument-hint: "<phase> [--codex] [--gemini] [--claude] [--opencode] [--ollama] [--lm-studio] [--llama-cpp] [--text] [--ws <name>] [--all] [--max-cycles N]"
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+  - Glob
+  - Grep
+  - Agent
+  - AskUserQuestion
+requires: [phase, review]
+---
+
+<objective>
+Cross-AI plan convergence loop — an outer revision gate around sdd-review and sdd-planner.
+Repeatedly: review plans with external AI CLIs → if HIGH concerns found → replan with --reviews feedback → re-review. Stops when no HIGH concerns remain or max cycles reached.
+
+**Flow:** Agent→Skill("sdd-plan-phase") → Agent→Skill("sdd-review") → check HIGHs → Agent→Skill("sdd-plan-phase --reviews") → Agent→Skill("sdd-review") → ... → Converge or escalate
+
+Replaces sdd-plan-phase's internal sdd-plan-checker with external AI reviewers (codex, gemini, etc.). Each step runs inside an isolated Agent that calls the corresponding existing Skill — orchestrator only does loop control.
+
+**Orchestrator role:** Parse arguments, validate phase, spawn Agents for existing Skills, check HIGHs, stall detection, escalation gate.
+</objective>
+
+<execution_context>
+@$HOME/.claude/sdd/workflows/plan-review-convergence.md
+@$HOME/.claude/sdd/references/revision-loop.md
+@$HOME/.claude/sdd/references/gates.md
+@$HOME/.claude/sdd/references/agent-contracts.md
+</execution_context>
+
+<runtime_note>
+**Copilot (VS Code):** Use `vscode_askquestions` wherever this workflow calls `AskUserQuestion`. They are equivalent — `vscode_askquestions` is the VS Code Copilot implementation of the same interactive question API. Do not skip questioning steps because `AskUserQuestion` appears unavailable; use `vscode_askquestions` instead.
+</runtime_note>
+
+<context>
+Phase number: extracted from $ARGUMENTS (required)
+
+**Flags:**
+- `--codex` — Use Codex CLI as reviewer (default if no reviewer specified)
+- `--gemini` — Use Gemini CLI as reviewer
+- `--claude` — Use Claude CLI as reviewer (separate session)
+- `--opencode` — Use OpenCode as reviewer
+- `--ollama` — Use local Ollama server as reviewer (OpenAI-compatible, default host `http://localhost:11434`; configure model via `review.models.ollama`)
+- `--lm-studio` — Use local LM Studio server as reviewer (OpenAI-compatible, default host `http://localhost:1234`; configure model via `review.models.lm_studio`)
+- `--llama-cpp` — Use local llama.cpp server as reviewer (OpenAI-compatible, default host `http://localhost:8080`; configure model via `review.models.llama_cpp`)
+- `--all` — Use all available CLIs and running local model servers
+- `--max-cycles N` — Maximum replan→review cycles (default: 3)
+
+**Feature gate:** This command requires `workflow.plan_review_convergence=true`. Enable with:
+`sdd config-set workflow.plan_review_convergence true`
+</context>
+
+<process>
+Execute end-to-end.
+Preserve all workflow gates (pre-flight, revision loop, stall detection, escalation).
+</process>

package/commands/sdd/pr-branch.md

@@ -6,6 +6,7 @@ allowed-tools:
   - Bash
   - Read
   - AskUserQuestion
+requires: [review]
 ---
 
 <objective>
@@ -21,5 +22,5 @@ changes that are irrelevant to code review.
 </execution_context>
 
 <process>
-Execute the pr-branch workflow from @~/.claude/sdd/workflows/pr-branch.md end-to-end.
+Execute end-to-end.
 </process>

package/commands/sdd/profile-user.md

@@ -9,7 +9,7 @@ allowed-tools:
   - Glob
   - Grep
   - AskUserQuestion
-  - Task
+  - Agent
 ---
 
 <objective>

package/commands/sdd/progress.md

@@ -1,24 +1,46 @@
 ---
 name: sdd:progress
-description: Check project progress, show context, and route to next action (execute or plan)
+description: Check progress, advance workflow, or dispatch freeform intent — the unified SDD situational command
+argument-hint: "[--forensic | --next | --do \"task description\"]"
 allowed-tools:
   - Read
   - Bash
   - Grep
   - Glob
   - SlashCommand
+  - AskUserQuestion
+requires: [phase]
 ---
 <objective>
-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.
+Check project progress, summarize recent work and what's ahead, then intelligently route to the next action.
 
-Provides situational awareness before continuing work.
+Three modes:
+- **default**: Show progress report + intelligently route to the next action (execute or plan). Provides situational awareness before continuing work.
+- **--next**: Automatically advance to the next logical step without manual route selection. Reads STATE.md, ROADMAP.md, and phase directories. Supports `--force` to bypass safety gates.
+- **--do "task description"**: Analyze freeform natural language and dispatch to the most appropriate SDD command. Never does the work itself — matches intent, confirms, hands off.
+- **--forensic**: Append a 6-check integrity audit after the standard progress report.
 </objective>
 
+<flags>
+- **--next**: Detect current project state and automatically invoke the next logical SDD workflow step. Scans all prior phases for incomplete work before routing. `--next --force` bypasses safety gates.
+- **--do "..."**: Smart dispatcher — match freeform intent to the best SDD command using routing rules, confirm the match, then hand off.
+- **--forensic**: Run 6-check integrity audit after the standard progress report.
+- **(no flag)**: Standard progress check + intelligent routing (Routes A through F).
+</flags>
+
 <execution_context>
 @~/.claude/sdd/workflows/progress.md
+@~/.claude/sdd/workflows/next.md
+@~/.claude/sdd/workflows/do.md
+@~/.claude/sdd/references/ui-brand.md
 </execution_context>
 
 <process>
-Execute the progress workflow from @~/.claude/sdd/workflows/progress.md end-to-end.
-Preserve all routing logic (Routes A through F) and edge case handling.
+Arguments provided: "$ARGUMENTS"
+Parse the first token from the provided arguments:
+- If it is `--next`: strip the flag, execute the next workflow (passing remaining args e.g. --force).
+- If it is `--do`: strip the flag, pass remainder as freeform intent to the do workflow.
+- Otherwise: execute the progress workflow end-to-end (pass --forensic through if present).
+
+Preserve all routing logic from the target workflow.
 </process>