@bhargavvc/sdd-cc 1.30.0 → 1.35.0

package/README.md

@@ -1,20 +1,20 @@
 <div align="center">
 
-# GET SHIT DONE
+# SPEC-DRIVEN DEVELOPMENT
 
 **English** · [Português](README.pt-BR.md) · [简体中文](README.zh-CN.md) · [日本語](README.ja-JP.md) · [한국어](README.ko-KR.md)
 
-**A light-weight and powerful meta-prompting, context engineering and spec-driven development system for Claude Code, OpenCode, Gemini CLI, Codex, Copilot, Cursor, Windsurf, and Antigravity.**
+**A light-weight and powerful meta-prompting, context engineering and spec-driven development system for Claude Code, OpenCode, Gemini CLI, Kilo, Codex, Copilot, Cursor, Windsurf, Antigravity, Augment, Trae, Qwen Code, Cline, and CodeBuddy.**
 
 **Solves context rot — the quality degradation that happens as Claude fills its context window.**
 
 [![npm version](https://img.shields.io/npm/v/@bhargavvc/sdd-cc?style=for-the-badge&logo=npm&logoColor=white&color=CB3837)](https://www.npmjs.com/package/@bhargavvc/sdd-cc)
 [![npm downloads](https://img.shields.io/npm/dm/@bhargavvc/sdd-cc?style=for-the-badge&logo=npm&logoColor=white&color=CB3837)](https://www.npmjs.com/package/@bhargavvc/sdd-cc)
-[![Tests](https://img.shields.io/github/actions/workflow/status/gsd-build/sdd/test.yml?branch=main&style=for-the-badge&logo=github&label=Tests)](https://github.com/gsd-build/sdd/actions/workflows/test.yml)
-[![Discord](https://img.shields.io/badge/Discord-Join-5865F2?style=for-the-badge&logo=discord&logoColor=white)](https://discord.gg/sdd)
+[![Tests](https://img.shields.io/github/actions/workflow/status/bhargavvc/sdd-cc/test.yml?branch=main&style=for-the-badge&logo=github&label=Tests)](https://github.com/bhargavvc/sdd-cc/actions/workflows/test.yml)
+[![Discord](https://img.shields.io/badge/Discord-Join-5865F2?style=for-the-badge&logo=discord&logoColor=white)](https://discord.gg/mYgfVNfA2r)
 [![X (Twitter)](https://img.shields.io/badge/X-@sdd__foundation-000000?style=for-the-badge&logo=x&logoColor=white)](https://x.com/sdd_foundation)
 [![$SDD Token](https://img.shields.io/badge/$SDD-Dexscreener-1C1C1C?style=for-the-badge&logo=data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMjQiIGhlaWdodD0iMjQiIHZpZXdCb3g9IjAgMCAyNCAyNCIgZmlsbD0ibm9uZSIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIj48Y2lyY2xlIGN4PSIxMiIgY3k9IjEyIiByPSIxMCIgZmlsbD0iIzAwRkYwMCIvPjwvc3ZnPg==&logoColor=00FF00)](https://dexscreener.com/solana/dwudwjvan7bzkw9zwlbyv6kspdlvhwzrqy6ebk8xzxkv)
-[![GitHub stars](https://img.shields.io/github/stars/gsd-build/sdd?style=for-the-badge&logo=github&color=181717)](https://github.com/gsd-build/sdd)
+[![GitHub stars](https://img.shields.io/github/stars/bhargavvc/sdd-cc?style=for-the-badge&logo=github&color=181717)](https://github.com/bhargavvc/sdd-cc)
 [![License](https://img.shields.io/badge/license-MIT-blue?style=for-the-badge)](LICENSE)
 
 <br>
@@ -47,6 +47,20 @@ npx @bhargavvc/sdd-cc@latest
 
 ---
 
+> [!IMPORTANT]
+> ### Welcome Back to SDD
+>
+> If you're returning to SDD after the recent Anthropic Terms of Service changes — welcome back. We kept building while you were gone.
+>
+> **To re-import an existing project into SDD:**
+> 1. Run `/sdd-map-codebase` to scan and index your current codebase state
+> 2. Run `/sdd-new-project` to initialize a fresh SDD planning structure using the codebase map as context
+> 3. Review [docs/USER-GUIDE.md](docs/USER-GUIDE.md) and the [CHANGELOG](CHANGELOG.md) for updates — a lot has changed since you were last here
+>
+> Your code is fine. SDD just needs its planning context rebuilt. The two commands above handle that.
+
+---
+
 ## Why I Built This
 
 I'm a solo developer. I don't write code — Claude Code does.
@@ -73,6 +87,16 @@ SDD fixes that. It's the context engineering layer that makes Claude Code reliab
 
 People who want to describe what they want and have it built correctly — without pretending they're running a 50-person engineering org.
 
+Built-in quality gates catch real problems: schema drift detection flags ORM changes missing migrations, security enforcement anchors verification to threat models, and scope reduction detection prevents the planner from silently dropping your requirements.
+
+### v1.34.0 Highlights
+
+- **Gates taxonomy** — 4 canonical gate types (pre-flight, revision, escalation, abort) wired into plan-checker and verifier agents
+- **Shell hooks fix** — `hooks/*.sh` files are now correctly included in the npm package, eliminating startup hook errors on fresh installs
+- **Post-merge hunk verification** — `reapply-patches` detects silently dropped hunks after three-way merge
+- **detectConfigDir fix** — Claude Code users no longer see false "update available" warnings when multiple runtimes are installed
+- **3 bug fixes** — Milestone backlog preservation, detectConfigDir priority, and npm package manifest
+
 ---
 
 ## Getting Started
@@ -82,18 +106,20 @@ npx @bhargavvc/sdd-cc@latest
 ```
 
 The installer prompts you to choose:
-1. **Runtime** — Claude Code, OpenCode, Gemini, Codex, Copilot, Cursor, Windsurf, Antigravity, or all (interactive multi-select — pick multiple runtimes in a single install session)
+1. **Runtime** — Claude Code, OpenCode, Gemini, Kilo, Codex, Copilot, Cursor, Windsurf, Antigravity, Augment, Trae, Qwen Code, CodeBuddy, Cline, or all (interactive multi-select — pick multiple runtimes in a single install session)
 2. **Location** — Global (all projects) or local (current project only)
 
 Verify with:
-- Claude Code / Gemini: `/sdd:help`
-- OpenCode: `/sdd-help`
+- Claude Code / Gemini / Copilot / Antigravity / Qwen Code: `/sdd-help`
+- OpenCode / Kilo / Augment / Trae / CodeBuddy: `/sdd-help`
 - Codex: `$sdd-help`
-- Copilot: `/sdd:help`
-- Antigravity: `/sdd:help`
+- Cline: SDD installs via `.clinerules` — verify by checking `.clinerules` exists
 
 > [!NOTE]
-> Codex installation uses skills (`skills/sdd-*/SKILL.md`) rather than custom prompts.
+> Claude Code 2.1.88+, Qwen Code, and Codex install as skills (`skills/sdd-*/SKILL.md`). Older Claude Code versions use `commands/sdd/`. Cline uses `.clinerules` for configuration. The installer handles all formats automatically.
+
+> [!TIP]
+> For source-based installs or environments where npm is unavailable, see **[docs/manual-update.md](docs/manual-update.md)**.
 
 ### Staying Updated
 
@@ -111,17 +137,21 @@ npx @bhargavvc/sdd-cc@latest
 npx @bhargavvc/sdd-cc --claude --global   # Install to ~/.claude/
 npx @bhargavvc/sdd-cc --claude --local    # Install to ./.claude/
 
-# OpenCode (open source, free models)
+# OpenCode
 npx @bhargavvc/sdd-cc --opencode --global # Install to ~/.config/opencode/
 
 # Gemini CLI
 npx @bhargavvc/sdd-cc --gemini --global   # Install to ~/.gemini/
 
-# Codex (skills-first)
+# Kilo
+npx @bhargavvc/sdd-cc --kilo --global     # Install to ~/.config/kilo/
+npx @bhargavvc/sdd-cc --kilo --local      # Install to ./.kilo/
+
+# Codex
 npx @bhargavvc/sdd-cc --codex --global    # Install to ~/.codex/
 npx @bhargavvc/sdd-cc --codex --local     # Install to ./.codex/
 
-# Copilot (GitHub Copilot CLI)
+# Copilot
 npx @bhargavvc/sdd-cc --copilot --global  # Install to ~/.github/
 npx @bhargavvc/sdd-cc --copilot --local   # Install to ./.github/
 
@@ -129,20 +159,40 @@ npx @bhargavvc/sdd-cc --copilot --local   # Install to ./.github/
 npx @bhargavvc/sdd-cc --cursor --global      # Install to ~/.cursor/
 npx @bhargavvc/sdd-cc --cursor --local       # Install to ./.cursor/
 
-# Windsurf (Codeium, VS Code-based)
-npx @bhargavvc/sdd-cc --windsurf --global    # Install to ~/.windsurf/
+# Windsurf
+npx @bhargavvc/sdd-cc --windsurf --global    # Install to ~/.codeium/windsurf/
 npx @bhargavvc/sdd-cc --windsurf --local     # Install to ./.windsurf/
 
-# Antigravity (Google, skills-first, Gemini-based)
+# Antigravity
 npx @bhargavvc/sdd-cc --antigravity --global # Install to ~/.gemini/antigravity/
 npx @bhargavvc/sdd-cc --antigravity --local  # Install to ./.agent/
 
+# Augment
+npx @bhargavvc/sdd-cc --augment --global     # Install to ~/.augment/
+npx @bhargavvc/sdd-cc --augment --local      # Install to ./.augment/
+
+# Trae
+npx @bhargavvc/sdd-cc --trae --global        # Install to ~/.trae/
+npx @bhargavvc/sdd-cc --trae --local         # Install to ./.trae/
+
+# Qwen Code
+npx @bhargavvc/sdd-cc --qwen --global        # Install to ~/.qwen/
+npx @bhargavvc/sdd-cc --qwen --local         # Install to ./.qwen/
+
+# CodeBuddy
+npx @bhargavvc/sdd-cc --codebuddy --global   # Install to ~/.codebuddy/
+npx @bhargavvc/sdd-cc --codebuddy --local    # Install to ./.codebuddy/
+
+# Cline
+npx @bhargavvc/sdd-cc --cline --global       # Install to ~/.cline/
+npx @bhargavvc/sdd-cc --cline --local        # Install to ./.clinerules
+
 # All runtimes
 npx @bhargavvc/sdd-cc --all --global      # Install to all directories
 ```
 
 Use `--global` (`-g`) or `--local` (`-l`) to skip the location prompt.
-Use `--claude`, `--opencode`, `--gemini`, `--codex`, `--copilot`, `--cursor`, `--windsurf`, `--antigravity`, or `--all` to skip the runtime prompt.
+Use `--claude`, `--opencode`, `--gemini`, `--kilo`, `--codex`, `--copilot`, `--cursor`, `--windsurf`, `--antigravity`, `--augment`, `--trae`, `--qwen`, `--codebuddy`, `--cline`, or `--all` to skip the runtime prompt.
 Use `--sdk` to also install the SDD SDK CLI (`sdd-sdk`) for headless autonomous execution.
 
 </details>
@@ -150,14 +200,17 @@ Use `--sdk` to also install the SDD SDK CLI (`sdd-sdk`) for headless autonomous
 <details>
 <summary><strong>Development Installation</strong></summary>
 
-Clone the repository and run the installer locally:
+Clone the repository, build hooks, and run the installer locally:
 
 ```bash
-git clone https://github.com/gsd-build/sdd.git
+git clone https://github.com/bhargavvc/sdd-cc.git
 cd sdd
+npm run build:hooks
 node bin/install.js --claude --local
 ```
 
+The `build:hooks` step is required — it compiles hook sources into `hooks/dist/` which the installer copies from. Without it, hooks won't be installed and you'll get hook errors in Claude Code. (The npm release handles this automatically via `prepublishOnly`.)
+
 Installs to `./.claude/` for testing modifications before contributing.
 
 </details>
@@ -210,12 +263,12 @@ If you prefer not to use that flag, add this to your project's `.claude/settings
 
 ## How It Works
 
-> **Already have code?** Run `/sdd:map-codebase` first. It spawns parallel agents to analyze your stack, architecture, conventions, and concerns. Then `/sdd:new-project` knows your codebase — questions focus on what you're adding, and planning automatically loads your patterns.
+> **Already have code?** Run `/sdd-map-codebase` first. It spawns parallel agents to analyze your stack, architecture, conventions, and concerns. Then `/sdd-new-project` knows your codebase — questions focus on what you're adding, and planning automatically loads your patterns.
 
 ### 1. Initialize Project
 
 ```
-/sdd:new-project
+/sdd-new-project
 ```
 
 One command, one flow. The system:
@@ -234,7 +287,7 @@ You approve the roadmap. Now you're ready to build.
 ### 2. Discuss Phase
 
 ```
-/sdd:discuss-phase 1
+/sdd-discuss-phase 1
 ```
 
 **This is where you shape the implementation.**
@@ -257,14 +310,14 @@ The deeper you go here, the more the system builds what you actually want. Skip
 
 **Creates:** `{phase_num}-CONTEXT.md`
 
-> **Assumptions Mode:** Prefer codebase analysis over questions? Set `workflow.discuss_mode` to `assumptions` in `/sdd:settings`. The system reads your code, surfaces what it would do and why, and only asks you to correct what's wrong. See [Discuss Mode](docs/workflow-discuss-mode.md).
+> **Assumptions Mode:** Prefer codebase analysis over questions? Set `workflow.discuss_mode` to `assumptions` in `/sdd-settings`. The system reads your code, surfaces what it would do and why, and only asks you to correct what's wrong. See [Discuss Mode](docs/workflow-discuss-mode.md).
 
 ---
 
 ### 3. Plan Phase
 
 ```
-/sdd:plan-phase 1
+/sdd-plan-phase 1
 ```
 
 The system:
@@ -282,7 +335,7 @@ Each plan is small enough to execute in a fresh context window. No degradation,
 ### 4. Execute Phase
 
 ```
-/sdd:execute-phase 1
+/sdd-execute-phase 1
 ```
 
 The system:
@@ -333,7 +386,7 @@ This is why "vertical slices" (Plan 01: User feature end-to-end) parallelize bet
 ### 5. Verify Work
 
 ```
-/sdd:verify-work 1
+/sdd-verify-work 1
 ```
 
 **This is where you confirm it actually works.**
@@ -347,7 +400,7 @@ The system:
 3. **Diagnoses failures automatically** — Spawns debug agents to find root causes
 4. **Creates verified fix plans** — Ready for immediate re-execution
 
-If everything passes, you move on. If something's broken, you don't manually debug — you just run `/sdd:execute-phase` again with the fix plans it created.
+If everything passes, you move on. If something's broken, you don't manually debug — you just run `/sdd-execute-phase` again with the fix plans it created.
 
 **Creates:** `{phase_num}-UAT.md`, fix plans if issues found
 
@@ -356,38 +409,38 @@ If everything passes, you move on. If something's broken, you don't manually deb
 ### 6. Repeat → Ship → Complete → Next Milestone
 
 ```
-/sdd:discuss-phase 2
-/sdd:plan-phase 2
-/sdd:execute-phase 2
-/sdd:verify-work 2
-/sdd:ship 2                  # Create PR from verified work
+/sdd-discuss-phase 2
+/sdd-plan-phase 2
+/sdd-execute-phase 2
+/sdd-verify-work 2
+/sdd-ship 2                  # Create PR from verified work
 ...
-/sdd:complete-milestone
-/sdd:new-milestone
+/sdd-complete-milestone
+/sdd-new-milestone
 ```
 
 Or let SDD figure out the next step automatically:
 
 ```
-/sdd:next                    # Auto-detect and run next step
+/sdd-next                    # Auto-detect and run next step
 ```
 
 Loop **discuss → plan → execute → verify → ship** until milestone complete.
 
-If you want faster intake during discussion, use `/sdd:discuss-phase <n> --batch` to answer a small grouped set of questions at once instead of one-by-one.
+If you want faster intake during discussion, use `/sdd-discuss-phase <n> --batch` to answer a small grouped set of questions at once instead of one-by-one. Use `--chain` to auto-chain discuss into plan+execute without stopping between steps.
 
 Each phase gets your input (discuss), proper research (plan), clean execution (execute), and human verification (verify). Context stays fresh. Quality stays high.
 
-When all phases are done, `/sdd:complete-milestone` archives the milestone and tags the release.
+When all phases are done, `/sdd-complete-milestone` archives the milestone and tags the release.
 
-Then `/sdd:new-milestone` starts the next version — same flow as `new-project` but for your existing codebase. You describe what you want to build next, the system researches the domain, you scope requirements, and it creates a fresh roadmap. Each milestone is a clean cycle: define → build → ship.
+Then `/sdd-new-milestone` starts the next version — same flow as `new-project` but for your existing codebase. You describe what you want to build next, the system researches the domain, you scope requirements, and it creates a fresh roadmap. Each milestone is a clean cycle: define → build → ship.
 
 ---
 
 ### Quick Mode
 
 ```
-/sdd:quick
+/sdd-quick
 ```
 
 **For ad-hoc tasks that don't need full planning.**
@@ -402,12 +455,14 @@ Quick mode gives you SDD guarantees (atomic commits, state tracking) with a fast
 
 **`--research` flag:** Spawns a focused researcher before planning. Investigates implementation approaches, library options, and pitfalls. Use when you're unsure how to approach a task.
 
-**`--full` flag:** Enables plan-checking (max 2 iterations) and post-execution verification.
+**`--full` flag:** Enables all phases — discussion + research + plan-checking + verification. The full SDD pipeline in quick-task form.
+
+**`--validate` flag:** Enables plan-checking + post-execution verification only (the previous `--full` behavior).
 
-Flags are composable: `--discuss --research --full` gives discussion + research + plan-checking + verification.
+Flags are composable: `--discuss --research --validate` gives discussion + research + plan-checking + verification.
 
 ```
-/sdd:quick
+/sdd-quick
 > What do you want to do? "Add dark mode toggle to settings"
 ```
 
@@ -506,117 +561,119 @@ You're never locked in. The system adapts.
 
 | Command | What it does |
 |---------|--------------|
-| `/sdd:new-project [--auto]` | Full initialization: questions → research → requirements → roadmap |
-| `/sdd:discuss-phase [N] [--auto] [--analyze]` | Capture implementation decisions before planning (`--analyze` adds trade-off analysis) |
-| `/sdd:plan-phase [N] [--auto] [--reviews]` | Research + plan + verify for a phase (`--reviews` loads codebase review findings) |
-| `/sdd:execute-phase <N>` | Execute all plans in parallel waves, verify when complete |
-| `/sdd:verify-work [N]` | Manual user acceptance testing ¹ |
-| `/sdd:ship [N] [--draft]` | Create PR from verified phase work with auto-generated body |
-| `/sdd:next` | Automatically advance to the next logical workflow step |
-| `/sdd:fast <text>` | Inline trivial tasks — skips planning entirely, executes immediately |
-| `/sdd:audit-milestone` | Verify milestone achieved its definition of done |
-| `/sdd:complete-milestone` | Archive milestone, tag release |
-| `/sdd:new-milestone [name]` | Start next version: questions → research → requirements → roadmap |
-| `/sdd:forensics [desc]` | Post-mortem investigation of failed workflow runs (diagnoses stuck loops, missing artifacts, git anomalies) |
-| `/sdd:milestone-summary [version]` | Generate comprehensive project summary for team onboarding and review |
+| `/sdd-new-project [--auto]` | Full initialization: questions → research → requirements → roadmap |
+| `/sdd-discuss-phase [N] [--auto] [--analyze] [--chain]` | Capture implementation decisions before planning (`--analyze` adds trade-off analysis, `--chain` auto-chains into plan+execute) |
+| `/sdd-plan-phase [N] [--auto] [--reviews]` | Research + plan + verify for a phase (`--reviews` loads codebase review findings) |
+| `/sdd-execute-phase <N>` | Execute all plans in parallel waves, verify when complete |
+| `/sdd-verify-work [N]` | Manual user acceptance testing ¹ |
+| `/sdd-ship [N] [--draft]` | Create PR from verified phase work with auto-generated body |
+| `/sdd-next` | Automatically advance to the next logical workflow step |
+| `/sdd-fast <text>` | Inline trivial tasks — skips planning entirely, executes immediately |
+| `/sdd-audit-milestone` | Verify milestone achieved its definition of done |
+| `/sdd-complete-milestone` | Archive milestone, tag release |
+| `/sdd-new-milestone [name]` | Start next version: questions → research → requirements → roadmap |
+| `/sdd-forensics [desc]` | Post-mortem investigation of failed workflow runs (diagnoses stuck loops, missing artifacts, git anomalies) |
+| `/sdd-milestone-summary [version]` | Generate comprehensive project summary for team onboarding and review |
 
 ### Workstreams
 
 | Command | What it does |
 |---------|--------------|
-| `/sdd:workstreams list` | Show all workstreams and their status |
-| `/sdd:workstreams create <name>` | Create a namespaced workstream for parallel milestone work |
-| `/sdd:workstreams switch <name>` | Switch active workstream |
-| `/sdd:workstreams complete <name>` | Complete and merge a workstream |
+| `/sdd-workstreams list` | Show all workstreams and their status |
+| `/sdd-workstreams create <name>` | Create a namespaced workstream for parallel milestone work |
+| `/sdd-workstreams switch <name>` | Switch active workstream |
+| `/sdd-workstreams complete <name>` | Complete and merge a workstream |
 
 ### Multi-Project Workspaces
 
 | Command | What it does |
 |---------|--------------|
-| `/sdd:new-workspace` | Create isolated workspace with repo copies (worktrees or clones) |
-| `/sdd:list-workspaces` | Show all SDD workspaces and their status |
-| `/sdd:remove-workspace` | Remove workspace and clean up worktrees |
+| `/sdd-new-workspace` | Create isolated workspace with repo copies (worktrees or clones) |
+| `/sdd-list-workspaces` | Show all SDD workspaces and their status |
+| `/sdd-remove-workspace` | Remove workspace and clean up worktrees |
 
 ### UI Design
 
 | Command | What it does |
 |---------|--------------|
-| `/sdd:ui-phase [N]` | Generate UI design contract (UI-SPEC.md) for frontend phases |
-| `/sdd:ui-review [N]` | Retroactive 6-pillar visual audit of implemented frontend code |
+| `/sdd-ui-phase [N]` | Generate UI design contract (UI-SPEC.md) for frontend phases |
+| `/sdd-ui-review [N]` | Retroactive 6-pillar visual audit of implemented frontend code |
 
 ### Navigation
 
 | Command | What it does |
 |---------|--------------|
-| `/sdd:progress` | Where am I? What's next? |
-| `/sdd:next` | Auto-detect state and run the next step |
-| `/sdd:help` | Show all commands and usage guide |
-| `/sdd:update` | Update SDD with changelog preview |
-| `/sdd:join-discord` | Join the SDD Discord community |
-| `/sdd:manager` | Interactive command center for managing multiple phases |
+| `/sdd-progress` | Where am I? What's next? |
+| `/sdd-next` | Auto-detect state and run the next step |
+| `/sdd-help` | Show all commands and usage guide |
+| `/sdd-update` | Update SDD with changelog preview |
+| `/sdd-join-discord` | Join the SDD Discord community |
+| `/sdd-manager` | Interactive command center for managing multiple phases |
 
 ### Brownfield
 
 | Command | What it does |
 |---------|--------------|
-| `/sdd:map-codebase [area]` | Analyze existing codebase before new-project |
+| `/sdd-map-codebase [area]` | Analyze existing codebase before new-project |
 
 ### Phase Management
 
 | Command | What it does |
 |---------|--------------|
-| `/sdd:add-phase` | Append phase to roadmap |
-| `/sdd:insert-phase [N]` | Insert urgent work between phases |
-| `/sdd:remove-phase [N]` | Remove future phase, renumber |
-| `/sdd:list-phase-assumptions [N]` | See Claude's intended approach before planning |
-| `/sdd:plan-milestone-gaps` | Create phases to close gaps from audit |
+| `/sdd-add-phase` | Append phase to roadmap |
+| `/sdd-insert-phase [N]` | Insert urgent work between phases |
+| `/sdd-remove-phase [N]` | Remove future phase, renumber |
+| `/sdd-list-phase-assumptions [N]` | See Claude's intended approach before planning |
+| `/sdd-plan-milestone-gaps` | Create phases to close gaps from audit |
 
 ### Session
 
 | Command | What it does |
 |---------|--------------|
-| `/sdd:pause-work` | Create handoff when stopping mid-phase (writes HANDOFF.json) |
-| `/sdd:resume-work` | Restore from last session |
-| `/sdd:session-report` | Generate session summary with work performed and outcomes |
+| `/sdd-pause-work` | Create handoff when stopping mid-phase (writes HANDOFF.json) |
+| `/sdd-resume-work` | Restore from last session |
+| `/sdd-session-report` | Generate session summary with work performed and outcomes |
 
 ### Workstreams
 
 | Command | What it does |
 |---------|--------------|
-| `/sdd:workstreams` | Manage parallel workstreams (list, create, switch, status, progress, complete) |
+| `/sdd-workstreams` | Manage parallel workstreams (list, create, switch, status, progress, complete) |
 
 ### Code Quality
 
 | Command | What it does |
 |---------|--------------|
-| `/sdd:review` | Cross-AI peer review of current phase or branch |
-| `/sdd:pr-branch` | Create clean PR branch filtering `.planning/` commits |
-| `/sdd:audit-uat` | Audit verification debt — find phases missing UAT |
+| `/sdd-review` | Cross-AI peer review of current phase or branch |
+| `/sdd-secure-phase [N]` | Security enforcement with threat-model-anchored verification |
+| `/sdd-pr-branch` | Create clean PR branch filtering `.planning/` commits |
+| `/sdd-audit-uat` | Audit verification debt — find phases missing UAT |
+| `/sdd-docs-update` | Verified documentation generation with doc-writer and doc-verifier agents |
 
 ### Backlog & Threads
 
 | Command | What it does |
 |---------|--------------|
-| `/sdd:plant-seed <idea>` | Capture forward-looking ideas with trigger conditions — surfaces at the right milestone |
-| `/sdd:add-backlog <desc>` | Add idea to backlog parking lot (999.x numbering, outside active sequence) |
-| `/sdd:review-backlog` | Review and promote backlog items to active milestone or remove stale entries |
-| `/sdd:thread [name]` | Persistent context threads — lightweight cross-session knowledge for work spanning multiple sessions |
+| `/sdd-plant-seed <idea>` | Capture forward-looking ideas with trigger conditions — surfaces at the right milestone |
+| `/sdd-add-backlog <desc>` | Add idea to backlog parking lot (999.x numbering, outside active sequence) |
+| `/sdd-review-backlog` | Review and promote backlog items to active milestone or remove stale entries |
+| `/sdd-thread [name]` | Persistent context threads — lightweight cross-session knowledge for work spanning multiple sessions |
 
 ### Utilities
 
 | Command | What it does |
 |---------|--------------|
-| `/sdd:settings` | Configure model profile and workflow agents |
-| `/sdd:set-profile <profile>` | Switch model profile (quality/balanced/budget/inherit) |
-| `/sdd:add-todo [desc]` | Capture idea for later |
-| `/sdd:check-todos` | List pending todos |
-| `/sdd:debug [desc]` | Systematic debugging with persistent state |
-| `/sdd:do <text>` | Route freeform text to the right SDD command automatically |
-| `/sdd:note <text>` | Zero-friction idea capture — append, list, or promote notes to todos |
-| `/sdd:quick [--full] [--discuss] [--research]` | Execute ad-hoc task with SDD guarantees (`--full` adds plan-checking and verification, `--discuss` gathers context first, `--research` investigates approaches before planning) |
-| `/sdd:health [--repair]` | Validate `.planning/` directory integrity, auto-repair with `--repair` |
-| `/sdd:stats` | Display project statistics — phases, plans, requirements, git metrics |
-| `/sdd:profile-user [--questionnaire] [--refresh]` | Generate developer behavioral profile from session analysis for personalized responses |
+| `/sdd-settings` | Configure model profile and workflow agents |
+| `/sdd-set-profile <profile>` | Switch model profile (quality/balanced/budget/inherit) |
+| `/sdd-add-todo [desc]` | Capture idea for later |
+| `/sdd-check-todos` | List pending todos |
+| `/sdd-debug [desc]` | Systematic debugging with persistent state |
+| `/sdd-do <text>` | Route freeform text to the right SDD command automatically |
+| `/sdd-note <text>` | Zero-friction idea capture — append, list, or promote notes to todos |
+| `/sdd-quick [--full] [--validate] [--discuss] [--research]` | Execute ad-hoc task with SDD guarantees (`--full` enables all phases, `--validate` adds plan-checking and verification, `--discuss` gathers context first, `--research` investigates approaches before planning) |
+| `/sdd-health [--repair]` | Validate `.planning/` directory integrity, auto-repair with `--repair` |
+| `/sdd-stats` | Display project statistics — phases, plans, requirements, git metrics |
+| `/sdd-profile-user [--questionnaire] [--refresh]` | Generate developer behavioral profile from session analysis for personalized responses |
 
 <sup>¹ Contributed by reddit user OracleGreyBeard</sup>
 
@@ -624,7 +681,7 @@ You're never locked in. The system adapts.
 
 ## Configuration
 
-SDD stores project settings in `.planning/config.json`. Configure during `/sdd:new-project` or update later with `/sdd:settings`. For the full config schema, workflow toggles, git branching options, and per-agent model breakdown, see the [User Guide](docs/USER-GUIDE.md#configuration-reference).
+SDD stores project settings in `.planning/config.json`. Configure during `/sdd-new-project` or update later with `/sdd-settings`. For the full config schema, workflow toggles, git branching options, and per-agent model breakdown, see the [User Guide](docs/USER-GUIDE.md#configuration-reference).
 
 ### Core Settings
 
@@ -632,6 +689,7 @@ SDD stores project settings in `.planning/config.json`. Configure during `/sdd:n
 |---------|---------|---------|------------------|
 | `mode` | `yolo`, `interactive` | `interactive` | Auto-approve vs confirm at each step |
 | `granularity` | `coarse`, `standard`, `fine` | `standard` | Phase granularity — how finely scope is sliced (phases × plans) |
+| `project_code` | string | `""` | Prefix phase directories with a project code |
 
 ### Model Profiles
 
@@ -646,12 +704,12 @@ Control which Claude model each agent uses. Balance quality vs token spend.
 
 Switch profiles:
 ```
-/sdd:set-profile budget
+/sdd-set-profile budget
 ```
 
 Use `inherit` when using non-Anthropic providers (OpenRouter, local models) or to follow the current runtime model selection (e.g. OpenCode `/model`).
 
-Or configure via `/sdd:settings`.
+Or configure via `/sdd-settings`.
 
 ### Workflow Agents
 
@@ -667,10 +725,11 @@ These spawn additional agents during planning/execution. They improve quality bu
 | `workflow.discuss_mode` | `'discuss'` | Discussion mode: `discuss` (interview), `assumptions` (codebase-first) |
 | `workflow.skip_discuss` | `false` | Skip discuss-phase in autonomous mode |
 | `workflow.text_mode` | `false` | Text-only mode for remote sessions (no TUI menus) |
+| `workflow.use_worktrees` | `true` | Toggle worktree isolation for execution |
 
-Use `/sdd:settings` to toggle these, or override per-invocation:
-- `/sdd:plan-phase --skip-research`
-- `/sdd:plan-phase --skip-verify`
+Use `/sdd-settings` to toggle these, or override per-invocation:
+- `/sdd-plan-phase --skip-research`
+- `/sdd-plan-phase --skip-verify`
 
 ### Execution
 
@@ -758,11 +817,11 @@ This prevents Claude from reading these files entirely, regardless of what comma
 
 **Commands not found after install?**
 - Restart your runtime to reload commands/skills
-- Verify files exist in `~/.claude/commands/sdd/` (global) or `./.claude/commands/sdd/` (local)
+- Verify files exist in `~/.claude/skills/sdd-*/SKILL.md` (Claude Code 2.1.88+) or `~/.claude/commands/sdd/` (legacy)
 - For Codex, verify skills exist in `~/.codex/skills/sdd-*/SKILL.md` (global) or `./.codex/skills/sdd-*/SKILL.md` (local)
 
 **Commands not working as expected?**
-- Run `/sdd:help` to verify installation
+- Run `/sdd-help` to verify installation
 - Re-run `npx @bhargavvc/sdd-cc` to reinstall
 
 **Updating to the latest version?**
@@ -787,21 +846,33 @@ To remove SDD completely:
 npx @bhargavvc/sdd-cc --claude --global --uninstall
 npx @bhargavvc/sdd-cc --opencode --global --uninstall
 npx @bhargavvc/sdd-cc --gemini --global --uninstall
+npx @bhargavvc/sdd-cc --kilo --global --uninstall
 npx @bhargavvc/sdd-cc --codex --global --uninstall
 npx @bhargavvc/sdd-cc --copilot --global --uninstall
 npx @bhargavvc/sdd-cc --cursor --global --uninstall
 npx @bhargavvc/sdd-cc --windsurf --global --uninstall
 npx @bhargavvc/sdd-cc --antigravity --global --uninstall
+npx @bhargavvc/sdd-cc --augment --global --uninstall
+npx @bhargavvc/sdd-cc --trae --global --uninstall
+npx @bhargavvc/sdd-cc --qwen --global --uninstall
+npx @bhargavvc/sdd-cc --codebuddy --global --uninstall
+npx @bhargavvc/sdd-cc --cline --global --uninstall
 
 # Local installs (current project)
 npx @bhargavvc/sdd-cc --claude --local --uninstall
 npx @bhargavvc/sdd-cc --opencode --local --uninstall
 npx @bhargavvc/sdd-cc --gemini --local --uninstall
+npx @bhargavvc/sdd-cc --kilo --local --uninstall
 npx @bhargavvc/sdd-cc --codex --local --uninstall
 npx @bhargavvc/sdd-cc --copilot --local --uninstall
 npx @bhargavvc/sdd-cc --cursor --local --uninstall
 npx @bhargavvc/sdd-cc --windsurf --local --uninstall
 npx @bhargavvc/sdd-cc --antigravity --local --uninstall
+npx @bhargavvc/sdd-cc --augment --local --uninstall
+npx @bhargavvc/sdd-cc --trae --local --uninstall
+npx @bhargavvc/sdd-cc --qwen --local --uninstall
+npx @bhargavvc/sdd-cc --codebuddy --local --uninstall
+npx @bhargavvc/sdd-cc --cline --local --uninstall
 ```
 
 This removes all SDD commands, agents, hooks, and settings while preserving your other configurations.
@@ -810,7 +881,7 @@ This removes all SDD commands, agents, hooks, and settings while preserving your
 
 ## Community Ports
 
-OpenCode, Gemini CLI, and Codex are now natively supported via `npx @bhargavvc/sdd-cc`.
+OpenCode, Gemini CLI, Kilo, and Codex are now natively supported via `npx @bhargavvc/sdd-cc`.
 
 These community ports pioneered multi-runtime support:
 
@@ -823,11 +894,11 @@ These community ports pioneered multi-runtime support:
 
 ## Star History
 
-<a href="https://star-history.com/#gsd-build/sdd&Date">
+<a href="https://star-history.com/#bhargavvc/sdd-cc&Date">
  <picture>
-   <source media="(prefers-color-scheme: dark)" srcset="https://api.star-history.com/svg?repos=gsd-build/sdd&type=Date&theme=dark" />
-   <source media="(prefers-color-scheme: light)" srcset="https://api.star-history.com/svg?repos=gsd-build/sdd&type=Date" />
-   <img alt="Star History Chart" src="https://api.star-history.com/svg?repos=gsd-build/sdd&type=Date" />
+   <source media="(prefers-color-scheme: dark)" srcset="https://api.star-history.com/svg?repos=bhargavvc/sdd-cc&type=Date&theme=dark" />
+   <source media="(prefers-color-scheme: light)" srcset="https://api.star-history.com/svg?repos=bhargavvc/sdd-cc&type=Date" />
+   <img alt="Star History Chart" src="https://api.star-history.com/svg?repos=bhargavvc/sdd-cc&type=Date" />
  </picture>
 </a>