@bhargavvc/sdd-cc 1.30.0 → 1.35.0

package/sdd/workflows/help.md

@@ -9,9 +9,9 @@ Display the complete SDD command reference. Output ONLY the reference content. D
 
 ## Quick Start
 
-1. `/sdd:new-project` - Initialize project (includes research, requirements, roadmap)
-2. `/sdd:plan-phase 1` - Create detailed plan for first phase
-3. `/sdd:execute-phase 1` - Execute the phase
+1. `/sdd-new-project` - Initialize project (includes research, requirements, roadmap)
+2. `/sdd-plan-phase 1` - Create detailed plan for first phase
+3. `/sdd-execute-phase 1` - Execute the phase
 
 ## Staying Updated
 
@@ -24,12 +24,12 @@ npx @bhargavvc/sdd-cc@latest
 ## Core Workflow
 
 ```
-/sdd:new-project → /sdd:plan-phase → /sdd:execute-phase → repeat
+/sdd-new-project → /sdd-plan-phase → /sdd-execute-phase → repeat
 ```
 
 ### Project Initialization
 
-**`/sdd:new-project`**
+**`/sdd-new-project`**
 Initialize new project through unified flow.
 
 One command takes you from idea to ready-for-planning:
@@ -46,21 +46,21 @@ Creates all `.planning/` artifacts:
 - `ROADMAP.md` — phases mapped to requirements
 - `STATE.md` — project memory
 
-Usage: `/sdd:new-project`
+Usage: `/sdd-new-project`
 
-**`/sdd:map-codebase`**
+**`/sdd-map-codebase`**
 Map an existing codebase for brownfield projects.
 
 - Analyzes codebase with parallel Explore agents
 - Creates `.planning/codebase/` with 7 focused documents
 - Covers stack, architecture, structure, conventions, testing, integrations, concerns
-- Use before `/sdd:new-project` on existing codebases
+- Use before `/sdd-new-project` on existing codebases
 
-Usage: `/sdd:map-codebase`
+Usage: `/sdd-map-codebase`
 
 ### Phase Planning
 
-**`/sdd:discuss-phase <number>`**
+**`/sdd-discuss-phase <number>`**
 Help articulate your vision for a phase before planning.
 
 - Captures how you imagine this phase working
@@ -68,11 +68,11 @@ Help articulate your vision for a phase before planning.
 - Use when you have ideas about how something should look/feel
 - Optional `--batch` asks 2-5 related questions at a time instead of one-by-one
 
-Usage: `/sdd:discuss-phase 2`
-Usage: `/sdd:discuss-phase 2 --batch`
-Usage: `/sdd:discuss-phase 2 --batch=3`
+Usage: `/sdd-discuss-phase 2`
+Usage: `/sdd-discuss-phase 2 --batch`
+Usage: `/sdd-discuss-phase 2 --batch=3`
 
-**`/sdd:research-phase <number>`**
+**`/sdd-research-phase <number>`**
 Comprehensive ecosystem research for niche/complex domains.
 
 - Discovers standard stack, architecture patterns, pitfalls
@@ -80,18 +80,18 @@ Comprehensive ecosystem research for niche/complex domains.
 - Use for 3D, games, audio, shaders, ML, and other specialized domains
 - Goes beyond "which library" to ecosystem knowledge
 
-Usage: `/sdd:research-phase 3`
+Usage: `/sdd-research-phase 3`
 
-**`/sdd:list-phase-assumptions <number>`**
+**`/sdd-list-phase-assumptions <number>`**
 See what Claude is planning to do before it starts.
 
 - Shows Claude's intended approach for a phase
 - Lets you course-correct if Claude misunderstood your vision
 - No files created - conversational output only
 
-Usage: `/sdd:list-phase-assumptions 3`
+Usage: `/sdd-list-phase-assumptions 3`
 
-**`/sdd:plan-phase <number>`**
+**`/sdd-plan-phase <number>`**
 Create detailed execution plan for a specific phase.
 
 - Generates `.planning/phases/XX-phase-name/XX-YY-PLAN.md`
@@ -99,14 +99,14 @@ Create detailed execution plan for a specific phase.
 - Includes verification criteria and success measures
 - Multiple plans per phase supported (XX-01, XX-02, etc.)
 
-Usage: `/sdd:plan-phase 1`
+Usage: `/sdd-plan-phase 1`
 Result: Creates `.planning/phases/01-foundation/01-01-PLAN.md`
 
 **PRD Express Path:** Pass `--prd path/to/requirements.md` to skip discuss-phase entirely. Your PRD becomes locked decisions in CONTEXT.md. Useful when you already have clear acceptance criteria.
 
 ### Execution
 
-**`/sdd:execute-phase <phase-number>`**
+**`/sdd-execute-phase <phase-number>`**
 Execute all plans in a phase, or run a specific wave.
 
 - Groups plans by wave (from frontmatter), executes waves sequentially
@@ -115,26 +115,26 @@ Execute all plans in a phase, or run a specific wave.
 - Verifies phase goal after all plans complete
 - Updates REQUIREMENTS.md, ROADMAP.md, STATE.md
 
-Usage: `/sdd:execute-phase 5`
-Usage: `/sdd:execute-phase 5 --wave 2`
+Usage: `/sdd-execute-phase 5`
+Usage: `/sdd-execute-phase 5 --wave 2`
 
 ### Smart Router
 
-**`/sdd:do <description>`**
+**`/sdd-do <description>`**
 Route freeform text to the right SDD command automatically.
 
 - Analyzes natural language input to find the best matching SDD command
 - Acts as a dispatcher — never does the work itself
 - Resolves ambiguity by asking you to pick between top matches
-- Use when you know what you want but don't know which `/sdd:*` command to run
+- Use when you know what you want but don't know which `/sdd-*` command to run
 
-Usage: `/sdd:do fix the login button`
-Usage: `/sdd:do refactor the auth system`
-Usage: `/sdd:do I want to start a new milestone`
+Usage: `/sdd-do fix the login button`
+Usage: `/sdd-do refactor the auth system`
+Usage: `/sdd-do I want to start a new milestone`
 
 ### Quick Mode
 
-**`/sdd:quick [--full] [--discuss] [--research]`**
+**`/sdd-quick [--full] [--validate] [--discuss] [--research]`**
 Execute small, ad-hoc tasks with SDD guarantees but skip optional agents.
 
 Quick mode uses the same system with a shorter path:
@@ -143,53 +143,55 @@ Quick mode uses the same system with a shorter path:
 - Updates STATE.md tracking (not ROADMAP.md)
 
 Flags enable additional quality steps:
+- `--full` — Complete quality pipeline: discussion + research + plan-checking + verification
+- `--validate` — Plan-checking (max 2 iterations) and post-execution verification only
 - `--discuss` — Lightweight discussion to surface gray areas before planning
 - `--research` — Focused research agent investigates approaches before planning
-- `--full` — Adds plan-checking (max 2 iterations) and post-execution verification
 
-Flags are composable: `--discuss --research --full` gives the complete quality pipeline for a single task.
+Granular flags are composable: `--discuss --research --validate` gives the same as `--full`.
 
-Usage: `/sdd:quick`
-Usage: `/sdd:quick --research --full`
+Usage: `/sdd-quick`
+Usage: `/sdd-quick --full`
+Usage: `/sdd-quick --research --validate`
 Result: Creates `.planning/quick/NNN-slug/PLAN.md`, `.planning/quick/NNN-slug/SUMMARY.md`
 
 ---
 
-**`/sdd:fast [description]`**
+**`/sdd-fast [description]`**
 Execute a trivial task inline — no subagents, no planning files, no overhead.
 
 For tasks too small to justify planning: typo fixes, config changes, forgotten commits, simple additions. Runs in the current context, makes the change, commits, and logs to STATE.md.
 
 - No PLAN.md or SUMMARY.md created
 - No subagent spawned (runs inline)
-- ≤ 3 file edits — redirects to `/sdd:quick` if task is non-trivial
+- ≤ 3 file edits — redirects to `/sdd-quick` if task is non-trivial
 - Atomic commit with conventional message
 
-Usage: `/sdd:fast "fix the typo in README"`
-Usage: `/sdd:fast "add .env to gitignore"`
+Usage: `/sdd-fast "fix the typo in README"`
+Usage: `/sdd-fast "add .env to gitignore"`
 
 ### Roadmap Management
 
-**`/sdd:add-phase <description>`**
+**`/sdd-add-phase <description>`**
 Add new phase to end of current milestone.
 
 - Appends to ROADMAP.md
 - Uses next sequential number
 - Updates phase directory structure
 
-Usage: `/sdd:add-phase "Add admin dashboard"`
+Usage: `/sdd-add-phase "Add admin dashboard"`
 
-**`/sdd:insert-phase <after> <description>`**
+**`/sdd-insert-phase <after> <description>`**
 Insert urgent work as decimal phase between existing phases.
 
 - Creates intermediate phase (e.g., 7.1 between 7 and 8)
 - Useful for discovered work that must happen mid-milestone
 - Maintains phase ordering
 
-Usage: `/sdd:insert-phase 7 "Fix critical auth bug"`
+Usage: `/sdd-insert-phase 7 "Fix critical auth bug"`
 Result: Creates Phase 7.1
 
-**`/sdd:remove-phase <number>`**
+**`/sdd-remove-phase <number>`**
 Remove a future phase and renumber subsequent phases.
 
 - Deletes phase directory and all references
@@ -197,12 +199,12 @@ Remove a future phase and renumber subsequent phases.
 - Only works on future (unstarted) phases
 - Git commit preserves historical record
 
-Usage: `/sdd:remove-phase 17`
+Usage: `/sdd-remove-phase 17`
 Result: Phase 17 deleted, phases 18-20 become 17-19
 
 ### Milestone Management
 
-**`/sdd:new-milestone <name>`**
+**`/sdd-new-milestone <name>`**
 Start a new milestone through unified flow.
 
 - Deep questioning to understand what you're building next
@@ -211,12 +213,12 @@ Start a new milestone through unified flow.
 - Roadmap creation with phase breakdown
 - Optional `--reset-phase-numbers` flag restarts numbering at Phase 1 and archives old phase dirs first for safety
 
-Mirrors `/sdd:new-project` flow for brownfield projects (existing PROJECT.md).
+Mirrors `/sdd-new-project` flow for brownfield projects (existing PROJECT.md).
 
-Usage: `/sdd:new-milestone "v2.0 Features"`
-Usage: `/sdd:new-milestone --reset-phase-numbers "v2.0 Features"`
+Usage: `/sdd-new-milestone "v2.0 Features"`
+Usage: `/sdd-new-milestone --reset-phase-numbers "v2.0 Features"`
 
-**`/sdd:complete-milestone <version>`**
+**`/sdd-complete-milestone <version>`**
 Archive completed milestone and prepare for next version.
 
 - Creates MILESTONES.md entry with stats
@@ -224,11 +226,11 @@ Archive completed milestone and prepare for next version.
 - Creates git tag for the release
 - Prepares workspace for next version
 
-Usage: `/sdd:complete-milestone 1.0.0`
+Usage: `/sdd-complete-milestone 1.0.0`
 
 ### Progress Tracking
 
-**`/sdd:progress`**
+**`/sdd-progress`**
 Check project status and intelligently route to next action.
 
 - Shows visual progress bar and completion percentage
@@ -238,45 +240,45 @@ Check project status and intelligently route to next action.
 - Offers to execute next plan or create it if missing
 - Detects 100% milestone completion
 
-Usage: `/sdd:progress`
+Usage: `/sdd-progress`
 
 ### Session Management
 
-**`/sdd:resume-work`**
+**`/sdd-resume-work`**
 Resume work from previous session with full context restoration.
 
 - Reads STATE.md for project context
 - Shows current position and recent progress
 - Offers next actions based on project state
 
-Usage: `/sdd:resume-work`
+Usage: `/sdd-resume-work`
 
-**`/sdd:pause-work`**
+**`/sdd-pause-work`**
 Create context handoff when pausing work mid-phase.
 
 - Creates .continue-here file with current state
 - Updates STATE.md session continuity section
 - Captures in-progress work context
 
-Usage: `/sdd:pause-work`
+Usage: `/sdd-pause-work`
 
 ### Debugging
 
-**`/sdd:debug [issue description]`**
+**`/sdd-debug [issue description]`**
 Systematic debugging with persistent state across context resets.
 
 - Gathers symptoms through adaptive questioning
 - Creates `.planning/debug/[slug].md` to track investigation
 - Investigates using scientific method (evidence → hypothesis → test)
-- Survives `/clear` — run `/sdd:debug` with no args to resume
+- Survives `/clear` — run `/sdd-debug` with no args to resume
 - Archives resolved issues to `.planning/debug/resolved/`
 
-Usage: `/sdd:debug "login button doesn't work"`
-Usage: `/sdd:debug` (resume active session)
+Usage: `/sdd-debug "login button doesn't work"`
+Usage: `/sdd-debug` (resume active session)
 
 ### Quick Notes
 
-**`/sdd:note <text>`**
+**`/sdd-note <text>`**
 Zero-friction idea capture — one command, instant save, no questions.
 
 - Saves timestamped note to `.planning/notes/` (or `~/.claude/notes/` globally)
@@ -284,14 +286,14 @@ Zero-friction idea capture — one command, instant save, no questions.
 - Promote converts a note into a structured todo
 - Works without a project (falls back to global scope)
 
-Usage: `/sdd:note refactor the hook system`
-Usage: `/sdd:note list`
-Usage: `/sdd:note promote 3`
-Usage: `/sdd:note --global cross-project idea`
+Usage: `/sdd-note refactor the hook system`
+Usage: `/sdd-note list`
+Usage: `/sdd-note promote 3`
+Usage: `/sdd-note --global cross-project idea`
 
 ### Todo Management
 
-**`/sdd:add-todo [description]`**
+**`/sdd-add-todo [description]`**
 Capture idea or task as todo from current conversation.
 
 - Extracts context from conversation (or uses provided description)
@@ -300,24 +302,24 @@ Capture idea or task as todo from current conversation.
 - Checks for duplicates before creating
 - Updates STATE.md todo count
 
-Usage: `/sdd:add-todo` (infers from conversation)
-Usage: `/sdd:add-todo Add auth token refresh`
+Usage: `/sdd-add-todo` (infers from conversation)
+Usage: `/sdd-add-todo Add auth token refresh`
 
-**`/sdd:check-todos [area]`**
+**`/sdd-check-todos [area]`**
 List pending todos and select one to work on.
 
 - Lists all pending todos with title, area, age
-- Optional area filter (e.g., `/sdd:check-todos api`)
+- Optional area filter (e.g., `/sdd-check-todos api`)
 - Loads full context for selected todo
 - Routes to appropriate action (work now, add to phase, brainstorm)
 - Moves todo to done/ when work begins
 
-Usage: `/sdd:check-todos`
-Usage: `/sdd:check-todos api`
+Usage: `/sdd-check-todos`
+Usage: `/sdd-check-todos api`
 
 ### User Acceptance Testing
 
-**`/sdd:verify-work [phase]`**
+**`/sdd-verify-work [phase]`**
 Validate built features through conversational UAT.
 
 - Extracts testable deliverables from SUMMARY.md files
@@ -325,11 +327,11 @@ Validate built features through conversational UAT.
 - Automatically diagnoses failures and creates fix plans
 - Ready for re-execution if issues found
 
-Usage: `/sdd:verify-work 3`
+Usage: `/sdd-verify-work 3`
 
 ### Ship Work
 
-**`/sdd:ship [phase]`**
+**`/sdd-ship [phase]`**
 Create a PR from completed phase work with an auto-generated body.
 
 - Pushes branch to remote
@@ -339,56 +341,57 @@ Create a PR from completed phase work with an auto-generated body.
 
 Prerequisites: Phase verified, `gh` CLI installed and authenticated.
 
-Usage: `/sdd:ship 4` or `/sdd:ship 4 --draft`
+Usage: `/sdd-ship 4` or `/sdd-ship 4 --draft`
 
 ---
 
-**`/sdd:review --phase N [--gemini] [--claude] [--codex] [--all]`**
+**`/sdd-review --phase N [--gemini] [--claude] [--codex] [--coderabbit] [--opencode] [--qwen] [--cursor] [--all]`**
 Cross-AI peer review — invoke external AI CLIs to independently review phase plans.
 
-- Detects available CLIs (gemini, claude, codex)
+- Detects available CLIs (gemini, claude, codex, coderabbit)
 - Each CLI reviews plans independently with the same structured prompt
+- CodeRabbit reviews the current git diff (not a prompt) — may take up to 5 minutes
 - Produces REVIEWS.md with per-reviewer feedback and consensus summary
-- Feed reviews back into planning: `/sdd:plan-phase N --reviews`
+- Feed reviews back into planning: `/sdd-plan-phase N --reviews`
 
-Usage: `/sdd:review --phase 3 --all`
+Usage: `/sdd-review --phase 3 --all`
 
 ---
 
-**`/sdd:pr-branch [target]`**
+**`/sdd-pr-branch [target]`**
 Create a clean branch for pull requests by filtering out .planning/ commits.
 
 - Classifies commits: code-only (include), planning-only (exclude), mixed (include sans .planning/)
 - Cherry-picks code commits onto a clean branch
 - Reviewers see only code changes, no SDD artifacts
 
-Usage: `/sdd:pr-branch` or `/sdd:pr-branch main`
+Usage: `/sdd-pr-branch` or `/sdd-pr-branch main`
 
 ---
 
-**`/sdd:plant-seed [idea]`**
+**`/sdd-plant-seed [idea]`**
 Capture a forward-looking idea with trigger conditions for automatic surfacing.
 
 - Seeds preserve WHY, WHEN to surface, and breadcrumbs to related code
-- Auto-surfaces during `/sdd:new-milestone` when trigger conditions match
+- Auto-surfaces during `/sdd-new-milestone` when trigger conditions match
 - Better than deferred items — triggers are checked, not forgotten
 
-Usage: `/sdd:plant-seed "add real-time notifications when we build the events system"`
+Usage: `/sdd-plant-seed "add real-time notifications when we build the events system"`
 
 ---
 
-**`/sdd:audit-uat`**
+**`/sdd-audit-uat`**
 Cross-phase audit of all outstanding UAT and verification items.
 - Scans every phase for pending, skipped, blocked, and human_needed items
 - Cross-references against codebase to detect stale documentation
 - Produces prioritized human test plan grouped by testability
 - Use before starting a new milestone to clear verification debt
 
-Usage: `/sdd:audit-uat`
+Usage: `/sdd-audit-uat`
 
 ### Milestone Auditing
 
-**`/sdd:audit-milestone [version]`**
+**`/sdd-audit-milestone [version]`**
 Audit milestone completion against original intent.
 
 - Reads all phase VERIFICATION.md files
@@ -396,30 +399,30 @@ Audit milestone completion against original intent.
 - Spawns integration checker for cross-phase wiring
 - Creates MILESTONE-AUDIT.md with gaps and tech debt
 
-Usage: `/sdd:audit-milestone`
+Usage: `/sdd-audit-milestone`
 
-**`/sdd:plan-milestone-gaps`**
+**`/sdd-plan-milestone-gaps`**
 Create phases to close gaps identified by audit.
 
 - Reads MILESTONE-AUDIT.md and groups gaps into phases
 - Prioritizes by requirement priority (must/should/nice)
 - Adds gap closure phases to ROADMAP.md
-- Ready for `/sdd:plan-phase` on new phases
+- Ready for `/sdd-plan-phase` on new phases
 
-Usage: `/sdd:plan-milestone-gaps`
+Usage: `/sdd-plan-milestone-gaps`
 
 ### Configuration
 
-**`/sdd:settings`**
+**`/sdd-settings`**
 Configure workflow toggles and model profile interactively.
 
 - Toggle researcher, plan checker, verifier agents
 - Select model profile (quality/balanced/budget/inherit)
 - Updates `.planning/config.json`
 
-Usage: `/sdd:settings`
+Usage: `/sdd-settings`
 
-**`/sdd:set-profile <profile>`**
+**`/sdd-set-profile <profile>`**
 Quick switch model profile for SDD agents.
 
 - `quality` — Opus everywhere except verification
@@ -427,11 +430,11 @@ Quick switch model profile for SDD agents.
 - `budget` — Sonnet for writing, Haiku for research/verification
 - `inherit` — Use current session model for all agents (OpenCode `/model`)
 
-Usage: `/sdd:set-profile budget`
+Usage: `/sdd-set-profile budget`
 
 ### Utility Commands
 
-**`/sdd:cleanup`**
+**`/sdd-cleanup`**
 Archive accumulated phase directories from completed milestones.
 
 - Identifies phases from completed milestones still in `.planning/phases/`
@@ -439,12 +442,12 @@ Archive accumulated phase directories from completed milestones.
 - Moves phase dirs to `.planning/milestones/v{X.Y}-phases/`
 - Use after multiple milestones to reduce `.planning/phases/` clutter
 
-Usage: `/sdd:cleanup`
+Usage: `/sdd-cleanup`
 
-**`/sdd:help`**
+**`/sdd-help`**
 Show this command reference.
 
-**`/sdd:update`**
+**`/sdd-update`**
 Update SDD to latest version with changelog preview.
 
 - Shows installed vs latest version comparison
@@ -453,15 +456,15 @@ Update SDD to latest version with changelog preview.
 - Confirms before running install
 - Better than raw `npx @bhargavvc/sdd-cc`
 
-Usage: `/sdd:update`
+Usage: `/sdd-update`
 
-**`/sdd:join-discord`**
+**`/sdd-join-discord`**
 Join the SDD Discord community.
 
 - Get help, share what you're building, stay updated
 - Connect with other SDD users
 
-Usage: `/sdd:join-discord`
+Usage: `/sdd-join-discord`
 
 ## Files & Structure
 
@@ -480,7 +483,7 @@ Usage: `/sdd:join-discord`
 ├── milestones/
 │   ├── v1.0-ROADMAP.md       # Archived roadmap snapshot
 │   ├── v1.0-REQUIREMENTS.md  # Archived requirements
-│   └── v1.0-phases/          # Archived phase dirs (via /sdd:cleanup or --archive-phases)
+│   └── v1.0-phases/          # Archived phase dirs (via /sdd-cleanup or --archive-phases)
 │       ├── 01-foundation/
 │       └── 02-core-features/
 ├── codebase/             # Codebase map (brownfield projects)
@@ -502,7 +505,7 @@ Usage: `/sdd:join-discord`
 
 ## Workflow Modes
 
-Set during `/sdd:new-project`:
+Set during `/sdd-new-project`:
 
 **Interactive Mode**
 
@@ -550,51 +553,51 @@ Example config:
 **Starting a new project:**
 
 ```
-/sdd:new-project        # Unified flow: questioning → research → requirements → roadmap
+/sdd-new-project        # Unified flow: questioning → research → requirements → roadmap
 /clear
-/sdd:plan-phase 1       # Create plans for first phase
+/sdd-plan-phase 1       # Create plans for first phase
 /clear
-/sdd:execute-phase 1    # Execute all plans in phase
+/sdd-execute-phase 1    # Execute all plans in phase
 ```
 
 **Resuming work after a break:**
 
 ```
-/sdd:progress  # See where you left off and continue
+/sdd-progress  # See where you left off and continue
 ```
 
 **Adding urgent mid-milestone work:**
 
 ```
-/sdd:insert-phase 5 "Critical security fix"
-/sdd:plan-phase 5.1
-/sdd:execute-phase 5.1
+/sdd-insert-phase 5 "Critical security fix"
+/sdd-plan-phase 5.1
+/sdd-execute-phase 5.1
 ```
 
 **Completing a milestone:**
 
 ```
-/sdd:complete-milestone 1.0.0
+/sdd-complete-milestone 1.0.0
 /clear
-/sdd:new-milestone  # Start next milestone (questioning → research → requirements → roadmap)
+/sdd-new-milestone  # Start next milestone (questioning → research → requirements → roadmap)
 ```
 
 **Capturing ideas during work:**
 
 ```
-/sdd:add-todo                    # Capture from conversation context
-/sdd:add-todo Fix modal z-index  # Capture with explicit description
-/sdd:check-todos                 # Review and work on todos
-/sdd:check-todos api             # Filter by area
+/sdd-add-todo                    # Capture from conversation context
+/sdd-add-todo Fix modal z-index  # Capture with explicit description
+/sdd-check-todos                 # Review and work on todos
+/sdd-check-todos api             # Filter by area
 ```
 
 **Debugging an issue:**
 
 ```
-/sdd:debug "form submission fails silently"  # Start debug session
+/sdd-debug "form submission fails silently"  # Start debug session
 # ... investigation happens, context fills up ...
 /clear
-/sdd:debug                                    # Resume from where you left off
+/sdd-debug                                    # Resume from where you left off
 ```
 
 ## Getting Help
@@ -602,5 +605,5 @@ Example config:
 - Read `.planning/PROJECT.md` for project vision
 - Read `.planning/STATE.md` for current context
 - Check `.planning/ROADMAP.md` for phase status
-- Run `/sdd:progress` to check where you're up to
+- Run `/sdd-progress` to check where you're up to
 </reference>