@bhargavvc/sdd-cc 1.30.1 → 1.35.0

package/commands/sdd/add-backlog.md

@@ -29,7 +29,7 @@ the normal phase sequence and accumulate context over time.
 
 3. **Create the phase directory:**
    ```bash
-   SLUG=$(node "$HOME/.claude/sdd/bin/sdd-tools.cjs" generate-slug "$ARGUMENTS")
+   SLUG=$(node "$HOME/.claude/sdd/bin/sdd-tools.cjs" generate-slug "$ARGUMENTS" --raw)
    mkdir -p ".planning/phases/${NEXT}-${SLUG}"
    touch ".planning/phases/${NEXT}-${SLUG}/.gitkeep"
    ```
@@ -46,7 +46,7 @@ the normal phase sequence and accumulate context over time.
    **Plans:** 0 plans
 
    Plans:
-   - [ ] TBD (promote with /sdd:review-backlog when ready)
+   - [ ] TBD (promote with /sdd-review-backlog when ready)
    ```
 
 5. **Commit:**
@@ -62,15 +62,15 @@ the normal phase sequence and accumulate context over time.
    Directory: .planning/phases/{NEXT}-{slug}/
 
    This item lives in the backlog parking lot.
-   Use /sdd:discuss-phase {NEXT} to explore it further.
-   Use /sdd:review-backlog to promote items to active milestone.
+   Use /sdd-discuss-phase {NEXT} to explore it further.
+   Use /sdd-review-backlog to promote items to active milestone.
    ```
 
 </process>
 
 <notes>
 - 999.x numbering keeps backlog items out of the active phase sequence
-- Phase directories are created immediately, so /sdd:discuss-phase and /sdd:plan-phase work on them
+- Phase directories are created immediately, so /sdd-discuss-phase and /sdd-plan-phase work on them
 - No `Depends on:` field — backlog items are unsequenced by definition
 - Sparse numbering is fine (999.1, 999.3) — always uses next-decimal
 </notes>

package/commands/sdd/add-tests.md

@@ -13,8 +13,8 @@ allowed-tools:
   - AskUserQuestion
 argument-instructions: |
   Parse the argument as a phase number (integer, decimal, or letter-suffix), plus optional free-text instructions.
-  Example: /sdd:add-tests 12
-  Example: /sdd:add-tests 12 focus on edge cases in the pricing module
+  Example: /sdd-add-tests 12
+  Example: /sdd-add-tests 12 focus on edge cases in the pricing module
 ---
 <objective>
 Generate unit and E2E tests for a completed phase, using its SUMMARY.md, CONTEXT.md, and VERIFICATION.md as specifications.

package/commands/sdd/ai-integration-phase.md

@@ -0,0 +1,36 @@
+---
+name: sdd:ai-integration-phase
+description: Generate AI design contract (AI-SPEC.md) for phases that involve building AI systems — framework selection, implementation guidance from official docs, and evaluation strategy
+argument-hint: "[phase number]"
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+  - Glob
+  - Grep
+  - Task
+  - WebFetch
+  - WebSearch
+  - AskUserQuestion
+  - mcp__context7__*
+---
+<objective>
+Create an AI design contract (AI-SPEC.md) for a phase involving AI system development.
+Orchestrates sdd-framework-selector → sdd-ai-researcher → sdd-domain-researcher → sdd-eval-planner.
+Flow: Select Framework → Research Docs → Research Domain → Design Eval Strategy → Done
+</objective>
+
+<execution_context>
+@~/.claude/sdd/workflows/ai-integration-phase.md
+@~/.claude/sdd/references/ai-frameworks.md
+@~/.claude/sdd/references/ai-evals.md
+</execution_context>
+
+<context>
+Phase number: $ARGUMENTS — optional, auto-detects next unplanned phase if omitted.
+</context>
+
+<process>
+Execute @~/.claude/sdd/workflows/ai-integration-phase.md end-to-end.
+Preserve all workflow gates.
+</process>

package/commands/sdd/analyze-dependencies.md

@@ -0,0 +1,34 @@
+---
+name: sdd:analyze-dependencies
+description: Analyze phase dependencies and suggest Depends on entries for ROADMAP.md
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+  - Glob
+  - Grep
+  - AskUserQuestion
+---
+<objective>
+Analyze the phase dependency graph for the current milestone. For each phase pair, determine if there is a dependency relationship based on:
+- File overlap (phases that modify the same files must be ordered)
+- Semantic dependencies (a phase that uses an API built by another phase)
+- Data flow (a phase that consumes output from another phase)
+
+Then suggest `Depends on` updates to ROADMAP.md.
+</objective>
+
+<execution_context>
+@~/.claude/sdd/workflows/analyze-dependencies.md
+</execution_context>
+
+<context>
+No arguments required. Requires an active milestone with ROADMAP.md.
+
+Run this command BEFORE `/sdd-manager` to fill in missing `Depends on` fields and prevent merge conflicts from unordered parallel execution.
+</context>
+
+<process>
+Execute the analyze-dependencies workflow from @~/.claude/sdd/workflows/analyze-dependencies.md end-to-end.
+Present dependency suggestions clearly and apply confirmed updates to ROADMAP.md.
+</process>

package/commands/sdd/audit-fix.md

@@ -0,0 +1,33 @@
+---
+type: prompt
+name: sdd:audit-fix
+description: Autonomous audit-to-fix pipeline — find issues, classify, fix, test, commit
+argument-hint: "--source <audit-uat> [--severity <medium|high|all>] [--max N] [--dry-run]"
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Grep
+  - Glob
+  - Agent
+  - AskUserQuestion
+---
+<objective>
+Run an audit, classify findings as auto-fixable vs manual-only, then autonomously fix
+auto-fixable issues with test verification and atomic commits.
+
+Flags:
+- `--max N` — maximum findings to fix (default: 5)
+- `--severity high|medium|all` — minimum severity to process (default: medium)
+- `--dry-run` — classify findings without fixing (shows classification table)
+- `--source <audit>` — which audit to run (default: audit-uat)
+</objective>
+
+<execution_context>
+@~/.claude/sdd/workflows/audit-fix.md
+</execution_context>
+
+<process>
+Execute the audit-fix workflow from @~/.claude/sdd/workflows/audit-fix.md end-to-end.
+</process>

package/commands/sdd/autonomous.md

@@ -1,7 +1,7 @@
 ---
 name: sdd:autonomous
 description: Run all remaining phases autonomously — discuss→plan→execute per phase
-argument-hint: "[--from N]"
+argument-hint: "[--from N] [--to N] [--only N] [--interactive]"
 allowed-tools:
   - Read
   - Write
@@ -10,6 +10,7 @@ allowed-tools:
   - Grep
   - AskUserQuestion
   - Task
+  - Agent
 ---
 <objective>
 Execute all remaining milestone phases autonomously. For each phase: discuss → plan → execute. Pauses only for user decisions (grey area acceptance, blockers, validation requests).
@@ -30,7 +31,11 @@ Uses ROADMAP.md phase discovery and Skill() flat invocations for each phase comm
 </execution_context>
 
 <context>
-Optional flag: `--from N` — start from phase N instead of the first incomplete phase.
+Optional flags:
+- `--from N` — start from phase N instead of the first incomplete phase.
+- `--to N` — stop after phase N completes (halt instead of advancing to next phase).
+- `--only N` — execute only phase N (single-phase mode).
+- `--interactive` — run discuss inline with questions (not auto-answered), then dispatch plan→execute as background agents. Keeps the main context lean while preserving user input on decisions.
 
 Project context, phase list, and state are resolved inside the workflow using init commands (`sdd-tools.cjs init milestone-op`, `sdd-tools.cjs roadmap analyze`). No upfront context loading needed.
 </context>

package/commands/sdd/cleanup.md

@@ -1,6 +1,11 @@
 ---
 name: sdd:cleanup
 description: Archive accumulated phase directories from completed milestones
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+  - AskUserQuestion
 ---
 <objective>
 Archive phase directories from completed milestones into `.planning/milestones/v{X.Y}-phases/`.

package/commands/sdd/code-review-fix.md

@@ -0,0 +1,52 @@
+---
+name: sdd:code-review-fix
+description: Auto-fix issues found by code review in REVIEW.md. Spawns fixer agent, commits each fix atomically, produces REVIEW-FIX.md summary.
+argument-hint: "<phase-number> [--all] [--auto]"
+allowed-tools:
+  - Read
+  - Bash
+  - Glob
+  - Grep
+  - Write
+  - Edit
+  - Task
+---
+<objective>
+Auto-fix issues found by code review. Reads REVIEW.md from the specified phase, spawns sdd-code-fixer agent to apply fixes, and produces REVIEW-FIX.md summary.
+
+Arguments:
+- Phase number (required) — which phase's REVIEW.md to fix (e.g., "2" or "02")
+- `--all` (optional) — include Info findings in fix scope (default: Critical + Warning only)
+- `--auto` (optional) — enable fix + re-review iteration loop, capped at 3 iterations
+
+Output: {padded_phase}-REVIEW-FIX.md in phase directory + inline summary of fixes applied
+</objective>
+
+<execution_context>
+@~/.claude/sdd/workflows/code-review-fix.md
+</execution_context>
+
+<context>
+Phase: $ARGUMENTS (first positional argument is phase number)
+
+Optional flags parsed from $ARGUMENTS:
+- `--all` — Include Info findings in fix scope. Default behavior fixes Critical + Warning only.
+- `--auto` — Enable fix + re-review iteration loop. After applying fixes, re-run code-review at same depth. If new issues found, iterate. Cap at 3 iterations total. Without this flag, single fix pass only.
+
+Context files (CLAUDE.md, REVIEW.md, phase state) are resolved inside the workflow via `sdd-tools init phase-op` and delegated to agent via config blocks.
+</context>
+
+<process>
+This command is a thin dispatch layer. It parses arguments and delegates to the workflow.
+
+Execute the code-review-fix workflow from @~/.claude/sdd/workflows/code-review-fix.md end-to-end.
+
+The workflow (not this command) enforces these gates:
+- Phase validation (before config gate)
+- Config gate check (workflow.code_review)
+- REVIEW.md existence check (error if missing)
+- REVIEW.md status check (skip if clean/skipped)
+- Agent spawning (sdd-code-fixer)
+- Iteration loop (if --auto, capped at 3 iterations)
+- Result presentation (inline summary + next steps)
+</process>

package/commands/sdd/code-review.md

@@ -0,0 +1,55 @@
+---
+name: sdd:code-review
+description: Review source files changed during a phase for bugs, security issues, and code quality problems
+argument-hint: "<phase-number> [--depth=quick|standard|deep] [--files file1,file2,...]"
+allowed-tools:
+  - Read
+  - Bash
+  - Glob
+  - Grep
+  - Write
+  - Task
+---
+<objective>
+Review source files changed during a phase for bugs, security vulnerabilities, and code quality problems.
+
+Spawns the sdd-code-reviewer agent to analyze code at the specified depth level. Produces REVIEW.md artifact in the phase directory with severity-classified findings.
+
+Arguments:
+- Phase number (required) — which phase's changes to review (e.g., "2" or "02")
+- `--depth=quick|standard|deep` (optional) — review depth level, overrides workflow.code_review_depth config
+  - quick: Pattern-matching only (~2 min)
+  - standard: Per-file analysis with language-specific checks (~5-15 min, default)
+  - deep: Cross-file analysis including import graphs and call chains (~15-30 min)
+- `--files file1,file2,...` (optional) — explicit comma-separated file list, skips SUMMARY/git scoping (highest precedence for scoping)
+
+Output: {padded_phase}-REVIEW.md in phase directory + inline summary of findings
+</objective>
+
+<execution_context>
+@~/.claude/sdd/workflows/code-review.md
+</execution_context>
+
+<context>
+Phase: $ARGUMENTS (first positional argument is phase number)
+
+Optional flags parsed from $ARGUMENTS:
+- `--depth=VALUE` — Depth override (quick|standard|deep). If provided, overrides workflow.code_review_depth config.
+- `--files=file1,file2,...` — Explicit file list override. Has highest precedence for file scoping per D-08. When provided, workflow skips SUMMARY.md extraction and git diff fallback entirely.
+
+Context files (CLAUDE.md, SUMMARY.md, phase state) are resolved inside the workflow via `sdd-tools init phase-op` and delegated to agent via `<files_to_read>` blocks.
+</context>
+
+<process>
+This command is a thin dispatch layer. It parses arguments and delegates to the workflow.
+
+Execute the code-review workflow from @~/.claude/sdd/workflows/code-review.md end-to-end.
+
+The workflow (not this command) enforces these gates:
+- Phase validation (before config gate)
+- Config gate check (workflow.code_review)
+- File scoping (--files override > SUMMARY.md > git diff fallback)
+- Empty scope check (skip if no files)
+- Agent spawning (sdd-code-reviewer)
+- Result presentation (inline summary + next steps)
+</process>

package/commands/sdd/complete-milestone.md

@@ -42,19 +42,19 @@ Output: Milestone archived (roadmap + requirements), PROJECT.md evolved, git tag
 0. **Check for audit:**
 
    - Look for `.planning/v{{version}}-MILESTONE-AUDIT.md`
-   - If missing or stale: recommend `/sdd:audit-milestone` first
-   - If audit status is `gaps_found`: recommend `/sdd:plan-milestone-gaps` first
+   - If missing or stale: recommend `/sdd-audit-milestone` first
+   - If audit status is `gaps_found`: recommend `/sdd-plan-milestone-gaps` first
    - If audit status is `passed`: proceed to step 1
 
    ```markdown
    ## Pre-flight Check
 
    {If no v{{version}}-MILESTONE-AUDIT.md:}
-   ⚠ No milestone audit found. Run `/sdd:audit-milestone` first to verify
+   ⚠ No milestone audit found. Run `/sdd-audit-milestone` first to verify
    requirements coverage, cross-phase integration, and E2E flows.
 
    {If audit has gaps:}
-   ⚠ Milestone audit found gaps. Run `/sdd:plan-milestone-gaps` to create
+   ⚠ Milestone audit found gaps. Run `/sdd-plan-milestone-gaps` to create
    phases that close the gaps, or proceed anyway to accept as tech debt.
 
    {If audit passed:}
@@ -108,7 +108,7 @@ Output: Milestone archived (roadmap + requirements), PROJECT.md evolved, git tag
    - Ask about pushing tag
 
 8. **Offer next steps:**
-   - `/sdd:new-milestone` — start next milestone (questioning → research → requirements → roadmap)
+   - `/sdd-new-milestone` — start next milestone (questioning → research → requirements → roadmap)
 
 </process>
 
@@ -132,5 +132,5 @@ Output: Milestone archived (roadmap + requirements), PROJECT.md evolved, git tag
 - **Archive before deleting:** Always create archive files before updating/deleting originals
 - **One-line summary:** Collapsed milestone in ROADMAP.md should be single line with link
 - **Context efficiency:** Archive keeps ROADMAP.md and REQUIREMENTS.md constant size per milestone
-- **Fresh requirements:** Next milestone starts with `/sdd:new-milestone` which includes requirements definition
+- **Fresh requirements:** Next milestone starts with `/sdd-new-milestone` which includes requirements definition
   </critical_rules>

package/commands/sdd/debug.md

@@ -1,7 +1,7 @@
 ---
 name: sdd:debug
 description: Systematic debugging with persistent state across context resets
-argument-hint: [issue description]
+argument-hint: [--diagnose] [issue description]
 allowed-tools:
   - Read
   - Bash
@@ -15,6 +15,9 @@ Debug issues using scientific method with subagent isolation.
 **Orchestrator role:** Gather symptoms, spawn sdd-debugger agent, handle checkpoints, spawn continuations.
 
 **Why subagent:** Investigation burns context fast (reading files, forming hypotheses, testing). Fresh 200k context per investigation. Main context stays lean for user interaction.
+
+**Flags:**
+- `--diagnose` — Diagnose only. Find root cause without applying a fix. Returns a structured Root Cause Report. Use when you want to validate the diagnosis before committing to a fix.
 </objective>
 
 <available_agent_types>
@@ -25,6 +28,10 @@ Valid SDD subagent types (use exact names — do not fall back to 'general-purpo
 <context>
 User's issue: $ARGUMENTS
 
+Parse flags from $ARGUMENTS:
+- If `--diagnose` is present, set `diagnose_only=true` and remove the flag from the issue description.
+- Otherwise, `diagnose_only=false`.
+
 Check for active sessions:
 ```bash
 ls .planning/debug/*.md 2>/dev/null | grep -v resolved | head -5
@@ -87,7 +94,7 @@ timeline: {timeline}
 
 <mode>
 symptoms_prefilled: true
-goal: find_and_fix
+goal: {if diagnose_only: "find_root_cause_only", else: "find_and_fix"}
 </mode>
 
 <debug_file>
@@ -106,12 +113,18 @@ Task(
 
 ## 4. Handle Agent Return
 
-**If `## ROOT CAUSE FOUND`:**
-- Display root cause and evidence summary
+**If `## ROOT CAUSE FOUND` (diagnose-only mode):**
+- Display root cause, confidence level, files involved, and suggested fix strategies
+- Offer options:
+  - "Fix now" — spawn a continuation agent with `goal: find_and_fix` to apply the fix (see step 5)
+  - "Plan fix" — suggest `/sdd-plan-phase --gaps`
+  - "Manual fix" — done
+
+**If `## DEBUG COMPLETE` (find_and_fix mode):**
+- Display root cause and fix summary
 - Offer options:
-  - "Fix now" - spawn fix subagent
-  - "Plan fix" - suggest /sdd:plan-phase --gaps
-  - "Manual fix" - done
+  - "Plan fix" — suggest `/sdd-plan-phase --gaps` if further work needed
+  - "Done" — mark resolved
 
 **If `## CHECKPOINT REACHED`:**
 - Present checkpoint details to user
@@ -128,9 +141,9 @@ Task(
   - "Manual investigation" - done
   - "Add more context" - gather more symptoms, spawn again
 
-## 5. Spawn Continuation Agent (After Checkpoint)
+## 5. Spawn Continuation Agent (After Checkpoint or "Fix now")
 
-When user responds to checkpoint, spawn fresh agent:
+When user responds to checkpoint OR selects "Fix now" from diagnose-only results, spawn fresh agent:
 
 ```markdown
 <objective>

package/commands/sdd/discuss-phase.md

@@ -1,7 +1,7 @@
 ---
 name: sdd:discuss-phase
-description: Gather phase context through adaptive questioning before planning. Use --auto to skip interactive questions (Claude picks recommended defaults).
-argument-hint: "<phase> [--auto] [--batch] [--analyze] [--text]"
+description: Gather phase context through adaptive questioning before planning. Use --auto to skip interactive questions (Claude picks recommended defaults). Use --chain for interactive discuss followed by automatic plan+execute. Use --power for bulk question generation into a file-based UI (answer at your own pace).
+argument-hint: "<phase> [--auto] [--chain] [--batch] [--analyze] [--text] [--power]"
 allowed-tools:
   - Read
   - Write
@@ -31,9 +31,14 @@ Extract implementation decisions that downstream agents need — researcher and
 <execution_context>
 @~/.claude/sdd/workflows/discuss-phase.md
 @~/.claude/sdd/workflows/discuss-phase-assumptions.md
+@~/.claude/sdd/workflows/discuss-phase-power.md
 @~/.claude/sdd/templates/context.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.
+</runtime_note>
+
 <context>
 Phase number: $ARGUMENTS (required)
 

package/commands/sdd/do.md

@@ -12,7 +12,7 @@ Analyze freeform natural language input and dispatch to the most appropriate SDD
 
 Acts as a smart dispatcher — never does the work itself. Matches intent to the best SDD command using routing rules, confirms the match, then hands off.
 
-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.
 </objective>
 
 <execution_context>

package/commands/sdd/docs-update.md

@@ -0,0 +1,48 @@
+---
+name: sdd:docs-update
+description: Generate or update project documentation verified against the codebase
+argument-hint: "[--force] [--verify-only]"
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Glob
+  - Grep
+  - Task
+  - AskUserQuestion
+---
+<objective>
+Generate and update up to 9 documentation files for the current project. Each doc type is written by a sdd-doc-writer subagent that explores the codebase directly — no hallucinated paths, phantom endpoints, or stale signatures.
+
+Flag handling rule:
+- The optional flags documented below are available behaviors, not implied active behaviors
+- A flag is active only when its literal token appears in `$ARGUMENTS`
+- If a documented flag is absent from `$ARGUMENTS`, treat it as inactive
+- `--force`: skip preservation prompts, regenerate all docs regardless of existing content or SDD markers
+- `--verify-only`: check existing docs for accuracy against codebase, no generation (full verification requires Phase 4 verifier)
+- If `--force` and `--verify-only` both appear in `$ARGUMENTS`, `--force` takes precedence
+</objective>
+
+<execution_context>
+@~/.claude/sdd/workflows/docs-update.md
+</execution_context>
+
+<context>
+Arguments: $ARGUMENTS
+
+**Available optional flags (documentation only — not automatically active):**
+- `--force` — Regenerate all docs. Overwrites hand-written and SDD docs alike. No preservation prompts.
+- `--verify-only` — Check existing docs for accuracy against the codebase. No files are written. Reports VERIFY marker count. Full codebase fact-checking requires the sdd-doc-verifier agent (Phase 4).
+
+**Active flags must be derived from `$ARGUMENTS`:**
+- `--force` is active only if the literal `--force` token is present in `$ARGUMENTS`
+- `--verify-only` is active only if the literal `--verify-only` token is present in `$ARGUMENTS`
+- If neither token appears, run the standard full-phase generation flow
+- Do not infer that a flag is active just because it is documented in this prompt
+</context>
+
+<process>
+Execute the docs-update workflow from @~/.claude/sdd/workflows/docs-update.md end-to-end.
+Preserve all workflow gates (preservation_check, flag handling, wave execution, monorepo dispatch, commit, reporting).
+</process>

package/commands/sdd/eval-review.md

@@ -0,0 +1,32 @@
+---
+name: sdd:eval-review
+description: Retroactively audit an executed AI phase's evaluation coverage — scores each eval dimension as COVERED/PARTIAL/MISSING and produces an actionable EVAL-REVIEW.md with remediation plan
+argument-hint: "[phase number]"
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+  - Glob
+  - Grep
+  - Task
+  - AskUserQuestion
+---
+<objective>
+Conduct a retroactive evaluation coverage audit of a completed AI phase.
+Checks whether the evaluation strategy from AI-SPEC.md was implemented.
+Produces EVAL-REVIEW.md with score, verdict, gaps, and remediation plan.
+</objective>
+
+<execution_context>
+@~/.claude/sdd/workflows/eval-review.md
+@~/.claude/sdd/references/ai-evals.md
+</execution_context>
+
+<context>
+Phase: $ARGUMENTS — optional, defaults to last completed phase.
+</context>
+
+<process>
+Execute @~/.claude/sdd/workflows/eval-review.md end-to-end.
+Preserve all workflow gates.
+</process>

package/commands/sdd/execute-phase.md

@@ -35,6 +35,10 @@ Context budget: ~15% orchestrator, 100% fresh per subagent.
 @~/.claude/sdd/references/ui-brand.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.
+</runtime_note>
+
 <context>
 Phase: $ARGUMENTS
 

package/commands/sdd/explore.md

@@ -0,0 +1,27 @@
+---
+name: sdd:explore
+description: Socratic ideation and idea routing — think through ideas before committing to plans
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+  - Grep
+  - Glob
+  - Task
+  - AskUserQuestion
+---
+<objective>
+Open-ended Socratic ideation session. Guides the developer through exploring an idea via
+probing questions, optionally spawns research, then routes outputs to the appropriate SDD
+artifacts (notes, todos, seeds, research questions, requirements, or new phases).
+
+Accepts an optional topic argument: `/sdd-explore authentication strategy`
+</objective>
+
+<execution_context>
+@~/.claude/sdd/workflows/explore.md
+</execution_context>
+
+<process>
+Execute the explore workflow from @~/.claude/sdd/workflows/explore.md end-to-end.
+</process>

package/commands/sdd/fast.md

@@ -16,8 +16,8 @@ Execute a trivial task directly in the current context without spawning subagent
 or generating PLAN.md files. For tasks too small to justify planning overhead:
 typo fixes, config changes, small refactors, forgotten commits, simple additions.
 
-This is NOT a replacement for /sdd:quick — use /sdd:quick for anything that
-needs research, multi-step planning, or verification. /sdd:fast is for tasks
+This is NOT a replacement for /sdd-quick — use /sdd-quick for anything that
+needs research, multi-step planning, or verification. /sdd-fast is for tasks
 you could describe in one sentence and execute in under 2 minutes.
 </objective>
 

package/commands/sdd/from-sdd2.md

@@ -0,0 +1,45 @@
+---
+name: sdd:from-sdd2
+description: Import a SDD-2 (.sdd/) project back to SDD v1 (.planning/) format
+argument-hint: "[--path <dir>] [--force]"
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+type: prompt
+---
+
+<objective>
+Reverse-migrate a SDD-2 project (`.sdd/` directory) back to SDD v1 (`.planning/`) format.
+
+Maps the SDD-2 hierarchy (Milestone → Slice → Task) to the SDD v1 hierarchy (Milestone sections in ROADMAP.md → Phase → Plan), preserving completion state, research files, and summaries.
+</objective>
+
+<process>
+
+1. **Locate the .sdd/ directory** — check the current working directory (or `--path` argument):
+   ```bash
+   node "$HOME/.claude/sdd/bin/sdd-tools.cjs" from-sdd2 --dry-run
+   ```
+   If no `.sdd/` is found, report the error and stop.
+
+2. **Show the dry-run preview** — present the full file list and migration statistics to the user. Ask for confirmation before writing anything.
+
+3. **Run the migration** after confirmation:
+   ```bash
+   node "$HOME/.claude/sdd/bin/sdd-tools.cjs" from-sdd2
+   ```
+   Use `--force` if `.planning/` already exists and the user has confirmed overwrite.
+
+4. **Report the result** — show the `filesWritten` count, `planningDir` path, and the preview summary.
+
+</process>
+
+<notes>
+- The migration is non-destructive: `.sdd/` is never modified or removed.
+- Pass `--path <dir>` to migrate a project at a different path than the current directory.
+- Slices are numbered sequentially across all milestones (M001/S01 → phase 01, M001/S02 → phase 02, M002/S01 → phase 03, etc.).
+- Tasks within each slice become plans (T01 → plan 01, T02 → plan 02, etc.).
+- Completed slices and tasks carry their done state into ROADMAP.md checkboxes and SUMMARY.md files.
+- SDD-2 cost/token ledger, database state, and VS Code extension state cannot be migrated.
+</notes>

package/commands/sdd/help.md

@@ -1,6 +1,8 @@
 ---
 name: sdd:help
 description: Show available SDD commands and usage guide
+allowed-tools:
+  - Read
 ---
 <objective>
 Display the complete SDD command reference.