claude-code-pilot 3.0.0 → 3.1.0

package/src/commands/{sessions.md → ccp/sessions.md}

@@ -1,10 +1,15 @@
+---
+name: ccp:sessions
+description: "Manage Claude Code session history - list, load, alias, and edit sessions"
+---
+
 # Sessions Command
 
 Manage Claude Code session history - list, load, alias, and edit sessions stored in `~/.claude/sessions/`.
 
 ## Usage
 
-`/sessions [list|load|alias|info|help] [options]`
+`/ccp:sessions [list|load|alias|info|help] [options]`
 
 ## Actions
 
@@ -13,11 +18,11 @@ Manage Claude Code session history - list, load, alias, and edit sessions stored
 Display all sessions with metadata, filtering, and pagination.
 
 ```bash
-/sessions                              # List all sessions (default)
-/sessions list                         # Same as above
-/sessions list --limit 10              # Show 10 sessions
-/sessions list --date 2026-02-01       # Filter by date
-/sessions list --search abc            # Search by session ID
+/ccp:sessions                              # List all sessions (default)
+/ccp:sessions list                         # Same as above
+/ccp:sessions list --limit 10              # Show 10 sessions
+/ccp:sessions list --date 2026-02-01       # Filter by date
+/ccp:sessions list --search abc            # Search by session ID
 ```
 
 **Script:**
@@ -53,10 +58,10 @@ for (const s of result.sessions) {
 Load and display a session's content (by ID or alias).
 
 ```bash
-/sessions load <id|alias>             # Load session
-/sessions load 2026-02-01             # By date (for no-id sessions)
-/sessions load a1b2c3d4               # By short ID
-/sessions load my-alias               # By alias name
+/ccp:sessions load <id|alias>             # Load session
+/ccp:sessions load 2026-02-01             # By date (for no-id sessions)
+/ccp:sessions load a1b2c3d4               # By short ID
+/ccp:sessions load my-alias               # By alias name
 ```
 
 **Script:**
@@ -116,8 +121,8 @@ if (session.metadata.lastUpdated) {
 Create a memorable alias for a session.
 
 ```bash
-/sessions alias <id> <name>           # Create alias
-/sessions alias 2026-02-01 today-work # Create alias named "today-work"
+/ccp:sessions alias <id> <name>           # Create alias
+/ccp:sessions alias 2026-02-01 today-work # Create alias named "today-work"
 ```
 
 **Script:**
@@ -130,7 +135,7 @@ const sessionId = process.argv[1];
 const aliasName = process.argv[2];
 
 if (!sessionId || !aliasName) {
-  console.log('Usage: /sessions alias <id> <name>');
+  console.log('Usage: /ccp:sessions alias <id> <name>');
   process.exit(1);
 }
 
@@ -156,8 +161,8 @@ if (result.success) {
 Delete an existing alias.
 
 ```bash
-/sessions alias --remove <name>        # Remove alias
-/sessions unalias <name>               # Same as above
+/ccp:sessions alias --remove <name>        # Remove alias
+/ccp:sessions unalias <name>               # Same as above
 ```
 
 **Script:**
@@ -167,7 +172,7 @@ const aa = require((process.env.CCP_CLAUDE_DIR||require('path').join(require('os
 
 const aliasName = process.argv[1];
 if (!aliasName) {
-  console.log('Usage: /sessions alias --remove <name>');
+  console.log('Usage: /ccp:sessions alias --remove <name>');
   process.exit(1);
 }
 
@@ -186,7 +191,7 @@ if (result.success) {
 Show detailed information about a session.
 
 ```bash
-/sessions info <id|alias>              # Show session details
+/ccp:sessions info <id|alias>              # Show session details
 ```
 
 **Script:**
@@ -233,7 +238,7 @@ if (aliases.length > 0) {
 Show all session aliases.
 
 ```bash
-/sessions aliases                      # List all aliases
+/ccp:sessions aliases                      # List all aliases
 ```
 
 **Script:**
@@ -279,22 +284,22 @@ $ARGUMENTS:
 
 ```bash
 # List all sessions
-/sessions list
+/ccp:sessions list
 
 # Create an alias for today's session
-/sessions alias 2026-02-01 today
+/ccp:sessions alias 2026-02-01 today
 
 # Load session by alias
-/sessions load today
+/ccp:sessions load today
 
 # Show session info
-/sessions info today
+/ccp:sessions info today
 
 # Remove alias
-/sessions alias --remove today
+/ccp:sessions alias --remove today
 
 # List all aliases
-/sessions aliases
+/ccp:sessions aliases
 ```
 
 ## Notes

package/src/commands/{setup-pm.md → ccp/setup-pm.md}

@@ -1,4 +1,5 @@
 ---
+name: ccp:setup-pm
 description: Configure your preferred package manager (npm/pnpm/yarn/bun)
 disable-model-invocation: true
 ---

package/src/commands/{setup-refresh.md → ccp/setup-refresh.md}

@@ -1,4 +1,5 @@
 ---
+name: ccp:setup-refresh
 description: "Re-scan codebase and update CLAUDE.md, rules, directory CLAUDE.md files, and architecture docs after major changes"
 ---
 
@@ -23,10 +24,10 @@ Present differences.
    - Scan for recognized directories: `src/`, `test/`, `tests/`, `lib/`, `app/`, `api/`, `scripts/`, `docs/`
    - For each existing recognized directory with a CLAUDE.md file:
      - Read the file's first line
-     - If it contains `<!-- Generated by /setup -- customize freely, /setup:refresh will regenerate if this comment is present -->`: regenerate using the same stack-aware templates from /setup Stage 4
+     - If it contains `<!-- Generated by /ccp:setup -- customize freely, /ccp:setup:refresh will regenerate if this comment is present -->`: regenerate using the same stack-aware templates from /ccp:setup Stage 4
      - If the marker is absent: skip (print: "Skipping {dir}/CLAUDE.md -- customized by user")
    - For each recognized directory WITHOUT a CLAUDE.md file:
-     - Generate a new one using the same stack-aware templates from /setup Stage 4
+     - Generate a new one using the same stack-aware templates from /ccp:setup Stage 4
    - Show summary of changes:
      ```
      Directory CLAUDE.md refresh:
@@ -40,7 +41,7 @@ Present differences.
 
 Show diff before writing.
 
-Note: MCP detection is NOT re-run during refresh. Binaries rarely change. Re-run `/setup` to re-detect MCP tools.
+Note: MCP detection is NOT re-run during refresh. Binaries rarely change. Re-run `/ccp:setup` to re-detect MCP tools.
 
 ## Step 3 — Commit
 

package/src/commands/{setup.md → ccp/setup.md}

@@ -1,4 +1,5 @@
 ---
+name: ccp:setup
 description: "First-time project setup — scans codebase, generates CLAUDE.md, installs language rules, discovers skills"
 ---
 
@@ -12,7 +13,7 @@ Verify that all 4 source directories from the Claude Code Pilot are properly ins
 
 Check the following paths relative to the project root:
 
-1. **Kit commands** — check if `.claude/commands/setup.md` exists (this file is a kit-specific marker)
+1. **Kit commands** — check if `.claude/commands/ccp/setup.md` exists (this file is a kit-specific marker)
 2. **CCP commands** — check if `.claude/commands/ccp/` directory exists and is non-empty (contains the 32 CCP commands)
 3. **CCP toolbox** — check if `.claude/hooks/` directory exists (contains hooks, lib, detection scripts)
 4. **CCP SDLC workflows** — check if `.claude/pilot/` directory exists and contains `workflows/` subdirectory
@@ -75,7 +76,7 @@ Codebase Intelligence:
 
 4. If NO (key not in .mcp.json): skip graph queries entirely, proceed with standard subagent exploration below.
 
-**Important:** This is a best-effort enhancement. The standard subagent exploration (grep/find) must ALWAYS run as the baseline. Graph results supplement, they don't replace. If codebase-memory-mcp adds value, great. If not, /setup works exactly as before.
+**Important:** This is a best-effort enhancement. The standard subagent exploration (grep/find) must ALWAYS run as the baseline. Graph results supplement, they don't replace. If codebase-memory-mcp adds value, great. If not, /ccp:setup works exactly as before.
 
 ---
 
@@ -185,7 +186,7 @@ Skip any directory that does not exist.
 
 For each existing recognized directory:
 - If no `CLAUDE.md` exists in the directory: mark for generation
-- If `CLAUDE.md` exists and its **first line** contains `<!-- Generated by /setup -- customize freely, /setup:refresh will regenerate if this comment is present -->`: mark for regeneration (overwrite)
+- If `CLAUDE.md` exists and its **first line** contains `<!-- Generated by /ccp:setup -- customize freely, /ccp:setup:refresh will regenerate if this comment is present -->`: mark for regeneration (overwrite)
 - If `CLAUDE.md` exists **without** that marker on line 1: skip (user customized it)
 
 **Step 3: Confirm with user**
@@ -197,7 +198,7 @@ Directory-scoped CLAUDE.md files will be generated for:
   test/    -- Test files (Jest + React Testing Library)
   docs/    -- Documentation
 
-Proceed? (These can be customized later -- /setup:refresh will skip files you edit)
+Proceed? (These can be customized later -- /ccp:setup:refresh will skip files you edit)
 ```
 
 **Step 4: Generate files**
@@ -210,7 +211,7 @@ Use these templates based on the detected stack (from Stage 1):
 
 **Next.js project:**
 ```markdown
-<!-- Generated by /setup -- customize freely, /setup:refresh will regenerate if this comment is present -->
+<!-- Generated by /ccp:setup -- customize freely, /ccp:setup:refresh will regenerate if this comment is present -->
 # Source Code (src/)
 
 This directory contains the application source code for a **Next.js** project.
@@ -226,7 +227,7 @@ This directory contains the application source code for a **Next.js** project.
 
 **Express + TypeScript project:**
 ```markdown
-<!-- Generated by /setup -- customize freely, /setup:refresh will regenerate if this comment is present -->
+<!-- Generated by /ccp:setup -- customize freely, /ccp:setup:refresh will regenerate if this comment is present -->
 # Source Code (src/)
 
 This directory contains the application source code for an **Express + TypeScript** project.
@@ -242,7 +243,7 @@ This directory contains the application source code for an **Express + TypeScrip
 
 **Python + Django project:**
 ```markdown
-<!-- Generated by /setup -- customize freely, /setup:refresh will regenerate if this comment is present -->
+<!-- Generated by /ccp:setup -- customize freely, /ccp:setup:refresh will regenerate if this comment is present -->
 # Source Code (src/)
 
 This directory contains the application source code for a **Django** project.
@@ -258,7 +259,7 @@ This directory contains the application source code for a **Django** project.
 
 **Go project:**
 ```markdown
-<!-- Generated by /setup -- customize freely, /setup:refresh will regenerate if this comment is present -->
+<!-- Generated by /ccp:setup -- customize freely, /ccp:setup:refresh will regenerate if this comment is present -->
 # Source Code (src/)
 
 This directory contains the application source code for a **Go** project.
@@ -274,7 +275,7 @@ This directory contains the application source code for a **Go** project.
 
 **Generic project (unknown framework):**
 ```markdown
-<!-- Generated by /setup -- customize freely, /setup:refresh will regenerate if this comment is present -->
+<!-- Generated by /ccp:setup -- customize freely, /ccp:setup:refresh will regenerate if this comment is present -->
 # Source Code (src/)
 
 This directory contains the application source code.
@@ -292,7 +293,7 @@ This directory contains the application source code.
 
 **Next.js / React project:**
 ```markdown
-<!-- Generated by /setup -- customize freely, /setup:refresh will regenerate if this comment is present -->
+<!-- Generated by /ccp:setup -- customize freely, /ccp:setup:refresh will regenerate if this comment is present -->
 # Tests (test/)
 
 This directory contains automated tests.
@@ -308,7 +309,7 @@ This directory contains automated tests.
 
 **Python + Django project:**
 ```markdown
-<!-- Generated by /setup -- customize freely, /setup:refresh will regenerate if this comment is present -->
+<!-- Generated by /ccp:setup -- customize freely, /ccp:setup:refresh will regenerate if this comment is present -->
 # Tests (tests/)
 
 This directory contains automated tests.
@@ -324,7 +325,7 @@ This directory contains automated tests.
 
 **Go project:**
 ```markdown
-<!-- Generated by /setup -- customize freely, /setup:refresh will regenerate if this comment is present -->
+<!-- Generated by /ccp:setup -- customize freely, /ccp:setup:refresh will regenerate if this comment is present -->
 # Tests (test/)
 
 This directory contains automated tests.
@@ -340,7 +341,7 @@ This directory contains automated tests.
 
 **Generic project:**
 ```markdown
-<!-- Generated by /setup -- customize freely, /setup:refresh will regenerate if this comment is present -->
+<!-- Generated by /ccp:setup -- customize freely, /ccp:setup:refresh will regenerate if this comment is present -->
 # Tests (test/)
 
 This directory contains automated tests.
@@ -357,7 +358,7 @@ This directory contains automated tests.
 ### lib/ template (all stacks)
 
 ```markdown
-<!-- Generated by /setup -- customize freely, /setup:refresh will regenerate if this comment is present -->
+<!-- Generated by /ccp:setup -- customize freely, /ccp:setup:refresh will regenerate if this comment is present -->
 # Shared Libraries (lib/)
 
 This directory contains shared utility functions and libraries.
@@ -375,7 +376,7 @@ This directory contains shared utility functions and libraries.
 
 **Next.js App Router:**
 ```markdown
-<!-- Generated by /setup -- customize freely, /setup:refresh will regenerate if this comment is present -->
+<!-- Generated by /ccp:setup -- customize freely, /ccp:setup:refresh will regenerate if this comment is present -->
 # App Directory (app/)
 
 This directory contains Next.js App Router pages and layouts.
@@ -391,7 +392,7 @@ This directory contains Next.js App Router pages and layouts.
 
 **Rails project:**
 ```markdown
-<!-- Generated by /setup -- customize freely, /setup:refresh will regenerate if this comment is present -->
+<!-- Generated by /ccp:setup -- customize freely, /ccp:setup:refresh will regenerate if this comment is present -->
 # App Directory (app/)
 
 This directory contains the Rails application code.
@@ -407,7 +408,7 @@ This directory contains the Rails application code.
 
 **Generic app/ directory:**
 ```markdown
-<!-- Generated by /setup -- customize freely, /setup:refresh will regenerate if this comment is present -->
+<!-- Generated by /ccp:setup -- customize freely, /ccp:setup:refresh will regenerate if this comment is present -->
 # Application (app/)
 
 This directory contains the main application code.
@@ -424,7 +425,7 @@ This directory contains the main application code.
 ### api/ template (all stacks)
 
 ```markdown
-<!-- Generated by /setup -- customize freely, /setup:refresh will regenerate if this comment is present -->
+<!-- Generated by /ccp:setup -- customize freely, /ccp:setup:refresh will regenerate if this comment is present -->
 # API Layer (api/)
 
 This directory contains API endpoints and route handlers.
@@ -441,7 +442,7 @@ This directory contains API endpoints and route handlers.
 ### scripts/ template (all stacks)
 
 ```markdown
-<!-- Generated by /setup -- customize freely, /setup:refresh will regenerate if this comment is present -->
+<!-- Generated by /ccp:setup -- customize freely, /ccp:setup:refresh will regenerate if this comment is present -->
 # Scripts (scripts/)
 
 This directory contains build, development, and maintenance scripts.
@@ -458,7 +459,7 @@ This directory contains build, development, and maintenance scripts.
 ### docs/ template (all stacks)
 
 ```markdown
-<!-- Generated by /setup -- customize freely, /setup:refresh will regenerate if this comment is present -->
+<!-- Generated by /ccp:setup -- customize freely, /ccp:setup:refresh will regenerate if this comment is present -->
 # Documentation (docs/)
 
 This directory contains project documentation.
@@ -485,7 +486,7 @@ Write CLAUDE.md under 100 lines. Sections:
 - **Universal Rules** (5-7 lines): project-specific patterns
 - **Forbidden** (4-6 lines): things that break this project
 - **Methodology — CCP** (6-8 lines): reference /ccp: commands
-- **Toolbox — CCP** (6-8 lines): reference /verify, /checkpoint, /save-session, /learn
+- **Toolbox — CCP** (6-8 lines): reference /ccp:verify, /ccp:checkpoint, /ccp:save-session, /ccp:learn
 - **Before ANY work** (2 lines): `npx skills find <keywords>`
 - **Reference Docs & MCP** (3-4 lines): point to docs/, contexts/, registries
 - **Gotchas** (3-5 lines): non-obvious things from scan
@@ -599,7 +600,7 @@ Configured:
 - Safety hooks + desktop notifications
 
 Methodology:  /ccp:discuss → /ccp:plan → /ccp:execute → /ccp:verify
-Quality:      /verify → /checkpoint → /quality-gate
-Persistence:  /save-session → /resume-session → /learn → /evolve
+Quality:      /ccp:verify → /ccp:checkpoint → /ccp:quality-gate
+Persistence:  /ccp:save-session → /ccp:resume-session → /ccp:learn → /ccp:evolve
 Update:       /ccp:update
 ```

package/src/commands/{skill-create.md → ccp/skill-create.md}

@@ -1,20 +1,20 @@
 ---
-name: skill-create
+name: ccp:skill-create
 description: Analyze local git history to extract coding patterns and generate SKILL.md files. Local version of the Skill Creator GitHub App.
 allowed_tools: ["Bash", "Read", "Write", "Grep", "Glob"]
 ---
 
-# /skill-create - Local Skill Generation
+# /ccp:skill-create - Local Skill Generation
 
 Analyze your repository's git history to extract coding patterns and generate SKILL.md files that teach Claude your team's practices.
 
 ## Usage
 
 ```bash
-/skill-create                    # Analyze current repo
-/skill-create --commits 100      # Analyze last 100 commits
-/skill-create --output ./skills  # Custom output directory
-/skill-create --instincts        # Also generate instincts for continuous-learning-v2
+/ccp:skill-create                    # Analyze current repo
+/ccp:skill-create --commits 100      # Analyze last 100 commits
+/ccp:skill-create --output ./skills  # Custom output directory
+/ccp:skill-create --instincts        # Also generate instincts for continuous-learning-v2
 ```
 
 ## What It Does
@@ -104,7 +104,7 @@ Prefix commits with: feat:, fix:, chore:, docs:, test:, refactor:
 
 ## Example Output
 
-Running `/skill-create` on a TypeScript project might produce:
+Running `/ccp:skill-create` on a TypeScript project might produce:
 
 ```markdown
 ---
@@ -167,6 +167,6 @@ For advanced features (10k+ commits, team sharing, auto-PRs), use the [Skill Cre
 
 - `/instinct-import` - Import generated instincts
 - `/instinct-status` - View learned instincts
-- `/evolve` - Cluster instincts into skills/agents
+- `/ccp:evolve` - Cluster instincts into skills/agents
 
 ---

package/src/commands/{skill-health.md → ccp/skill-health.md}

@@ -1,5 +1,5 @@
 ---
-name: skill-health
+name: ccp:skill-health
 description: Show skill portfolio health dashboard with charts and analytics
 command: true
 ---
@@ -31,16 +31,16 @@ node ~/.claude/scripts/skills-health.js --dashboard --json
 ## Usage
 
 ```
-/skill-health                    # Full dashboard view
-/skill-health --panel failures   # Only failure clustering panel
-/skill-health --json             # Machine-readable JSON output
+/ccp:skill-health                    # Full dashboard view
+/ccp:skill-health --panel failures   # Only failure clustering panel
+/ccp:skill-health --json             # Machine-readable JSON output
 ```
 
 ## What to Do
 
 1. Run the skills-health.js script with --dashboard flag
 2. Display the output to the user
-3. If any skills are declining, highlight them and suggest running /evolve
+3. If any skills are declining, highlight them and suggest running /ccp:evolve
 4. If there are pending amendments, suggest reviewing them
 
 ## Panels

package/src/commands/{tdd.md → ccp/tdd.md}

@@ -1,4 +1,5 @@
 ---
+name: ccp:tdd
 description: Enforce test-driven development workflow. Scaffold interfaces, generate tests FIRST, then implement minimal code to pass. Ensure 80%+ coverage.
 ---
 
@@ -16,7 +17,7 @@ This command invokes the **tdd-guide** agent to enforce test-driven development
 
 ## When to Use
 
-Use `/tdd` when:
+Use `/ccp:tdd` when:
 - Implementing new features
 - Adding new functions/components
 - Fixing bugs (write test that reproduces bug first)
@@ -49,7 +50,7 @@ REPEAT:   Next feature/scenario
 ## Example Usage
 
 ```
-User: /tdd I need a function to calculate market liquidity score
+User: /ccp:tdd I need a function to calculate market liquidity score
 
 Agent (tdd-guide):
 # TDD Session: Market Liquidity Score Calculator
@@ -285,7 +286,7 @@ Coverage: 100% ✅ (Target: 80%)
 - External service calls
 - React components with hooks
 
-**E2E Tests** (use `/e2e` command):
+**E2E Tests** (use `/ccp:e2e` command):
 - Critical user flows
 - Multi-step processes
 - Full stack integration
@@ -311,11 +312,11 @@ Never skip the RED phase. Never write code before tests.
 
 ## Integration with Other Commands
 
-- Use `/plan` first to understand what to build
-- Use `/tdd` to implement with tests
-- Use `/build-fix` if build errors occur
-- Use `/code-review` to review implementation
-- Use `/test-coverage` to verify coverage
+- Use `/ccp:plan` first to understand what to build
+- Use `/ccp:tdd` to implement with tests
+- Use `/ccp:build-fix` if build errors occur
+- Use `/ccp:code-review` to review implementation
+- Use `/ccp:test-coverage` to verify coverage
 
 ## Related Agents
 

package/src/commands/{test-coverage.md → ccp/test-coverage.md}

@@ -1,3 +1,8 @@
+---
+name: ccp:test-coverage
+description: "Analyze test coverage, identify gaps, and generate missing tests for 80%+ coverage"
+---
+
 # Test Coverage
 
 Analyze test coverage, identify gaps, and generate missing tests to reach 80%+ coverage.

package/src/commands/{tool-guide.md → ccp/tool-guide.md}

@@ -1,4 +1,5 @@
 ---
+name: ccp:tool-guide
 description: "MCP tool recommendations per task type -- which tools to use when"
 ---
 
@@ -32,7 +33,7 @@ The kit configures or recommends these MCP tools:
 ## Usage Tips
 
 - If a tool is not installed, Claude will skip it automatically -- no errors.
-- Use `/setup` to auto-detect and configure available MCP tools.
+- Use `/ccp:setup` to auto-detect and configure available MCP tools.
 - Context7 is the highest-value tool -- it prevents the #1 cause of agent errors (outdated API usage).
 - codebase-memory-mcp and cocoindex-code serve similar purposes -- you don't need both.
 - For large codebases (100+ files), codebase-memory-mcp significantly reduces context waste from file exploration.

package/src/commands/{update-codemaps.md → ccp/update-codemaps.md}

@@ -1,3 +1,8 @@
+---
+name: ccp:update-codemaps
+description: "Analyze codebase structure and generate token-lean architecture documentation"
+---
+
 # Update Codemaps
 
 Analyze the codebase structure and generate token-lean architecture documentation.

package/src/commands/{update-docs.md → ccp/update-docs.md}

@@ -1,3 +1,8 @@
+---
+name: ccp:update-docs
+description: "Sync documentation with the codebase from source-of-truth files"
+---
+
 # Update Documentation
 
 Sync documentation with the codebase, generating from source-of-truth files.

package/src/commands/{verify.md → ccp/verify.md}

@@ -1,3 +1,8 @@
+---
+name: ccp:verify
+description: "Run comprehensive verification on current codebase state"
+---
+
 # Verification Command
 
 Run comprehensive verification on current codebase state.

package/src/commands/ccp/workstreams.md

@@ -0,0 +1,68 @@
+---
+name: ccp:workstreams
+description: Manage parallel workstreams — list, create, switch, status, progress, complete, and resume
+---
+
+# /ccp:workstreams
+
+Manage parallel workstreams for concurrent milestone work.
+
+## Usage
+
+`/ccp:workstreams [subcommand] [args]`
+
+### Subcommands
+
+| Command | Description |
+|---------|-------------|
+| `list` | List all workstreams with status |
+| `create <name>` | Create a new workstream |
+| `status <name>` | Detailed status for one workstream |
+| `switch <name>` | Set active workstream |
+| `progress` | Progress summary across all workstreams |
+| `complete <name>` | Archive a completed workstream |
+| `resume <name>` | Resume work in a workstream |
+
+## Step 1: Parse Subcommand
+
+Parse the user's input to determine which workstream operation to perform.
+If no subcommand given, default to `list`.
+
+## Step 2: Execute Operation
+
+### list
+Scan `.planning/` directory structure for workstream directories. For each workstream found:
+- Read its STATE.md to get status, current phase, and progress
+- Display results in a table format showing name, status, current phase, and progress
+
+If no workstreams exist (only default `.planning/` directory), display:
+"No workstreams found. Use `/ccp:workstreams create <name>` to create one."
+
+### create
+Create a new workstream directory at `.planning/workstreams/<name>/`:
+- Create the directory with `mkdir -p`
+- Create a STATE.md from the standard template (copy structure from `.planning/STATE.md` with fresh values)
+- Display the new workstream path and suggest: `/ccp:new-milestone --ws <name>` to set up the milestone
+
+### status
+Read `.planning/workstreams/<name>/STATE.md` and display detailed phase breakdown and state information.
+If the workstream does not exist, display: "Workstream '<name>' not found."
+
+### switch
+Verify `.planning/workstreams/<name>/` exists, then set `CCP_WORKSTREAM=<name>` environment variable for the current session.
+Display: "Switched to workstream '<name>'."
+
+### progress
+Scan all workstream directories under `.planning/workstreams/`. For each, read its STATE.md and extract progress percentage. Display a progress overview table across all workstreams.
+
+### complete
+Move `.planning/workstreams/<name>/` to `.planning/milestones/<name>/` to archive the completed workstream.
+Display: "Workstream '<name>' archived to milestones/."
+
+### resume
+Set the workstream as active and suggest `/ccp:resume-work --ws <name>`.
+
+## Step 3: Display Results
+
+Format the results into a human-readable display.
+Include the `${CCP_WS}` flag in any routing suggestions.

package/src/examples/CLAUDE.md

@@ -87,10 +87,10 @@ DEBUG=false
 
 ## Available Commands
 
-- `/tdd` - Test-driven development workflow
-- `/plan` - Create implementation plan
-- `/code-review` - Review code quality
-- `/build-fix` - Fix build errors
+- `/ccp:tdd` - Test-driven development workflow
+- `/ccp:plan` - Create implementation plan
+- `/ccp:code-review` - Review code quality
+- `/ccp:build-fix` - Fix build errors
 
 ## Git Workflow
 

package/src/examples/django-api-CLAUDE.md

@@ -286,18 +286,18 @@ pytest --lf
 
 ```bash
 # Planning
-/plan "Add order refund system with Stripe integration"
+/ccp:plan "Add order refund system with Stripe integration"
 
 # Development with TDD
-/tdd                    # pytest-based TDD workflow
+/ccp:tdd                # pytest-based TDD workflow
 
 # Review
-/python-review          # Python-specific code review
+/ccp:python-review      # Python-specific code review
 /security-scan          # Django security audit
-/code-review            # General quality check
+/ccp:code-review        # General quality check
 
 # Verification
-/verify                 # Build, lint, test, security scan
+/ccp:verify             # Build, lint, test, security scan
 ```
 
 ## Git Workflow