claude-code-pilot 3.0.0 → 3.1.0

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

@@ -1,4 +1,5 @@
 ---
+name: ccp:kotlin-test
 description: Enforce TDD workflow for Kotlin. Write Kotest tests first, then implement. Verify 80%+ coverage with Kover.
 ---
 
@@ -17,7 +18,7 @@ This command enforces test-driven development methodology for Kotlin code using
 
 ## When to Use
 
-Use `/kotlin-test` when:
+Use `/ccp:kotlin-test` when:
 - Implementing new Kotlin functions or classes
 - Adding test coverage to existing Kotlin code
 - Fixing bugs (write failing test first)
@@ -36,7 +37,7 @@ REPEAT  -> Next test case
 ## Example Session
 
 ````text
-User: /kotlin-test I need a function to validate user registration requests
+User: /ccp:kotlin-test I need a function to validate user registration requests
 
 Agent:
 # TDD Session: Registration Validator
@@ -302,9 +303,9 @@ open build/reports/kover/html/index.html
 
 ## Related Commands
 
-- `/kotlin-build` - Fix build errors
-- `/kotlin-review` - Review code after implementation
-- `/verify` - Run full verification loop
+- `/ccp:kotlin-build` - Fix build errors
+- `/ccp:kotlin-review` - Review code after implementation
+- `/ccp:verify` - Run full verification loop
 
 ## Related
 

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

@@ -1,10 +1,15 @@
-# /learn - Extract Reusable Patterns
+---
+name: ccp:learn
+description: "Extract reusable patterns from the current session into skills"
+---
+
+# /ccp:learn - Extract Reusable Patterns
 
 Analyze the current session and extract any patterns worth saving as skills.
 
 ## Trigger
 
-Run `/learn` at any point during a session when you've solved a non-trivial problem.
+Run `/ccp:learn` at any point during a session when you've solved a non-trivial problem.
 
 ## What to Extract
 

package/src/commands/{model-route.md → ccp/model-route.md}

@@ -1,10 +1,15 @@
+---
+name: ccp:model-route
+description: "Recommend the best model tier for the current task by complexity and budget"
+---
+
 # Model Route Command
 
 Recommend the best model tier for the current task by complexity and budget.
 
 ## Usage
 
-`/model-route [task-description] [--budget low|med|high]`
+`/ccp:model-route [task-description] [--budget low|med|high]`
 
 ## Routing Heuristic
 

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

@@ -1,4 +1,5 @@
 ---
+name: ccp:orchestrate
 description: Sequential and tmux/worktree orchestration guidance for multi-agent workflows.
 ---
 
@@ -8,7 +9,7 @@ Sequential agent workflow for complex tasks.
 
 ## Usage
 
-`/orchestrate [workflow-type] [task-description]`
+`/ccp:orchestrate [workflow-type] [task-description]`
 
 ## Workflow Types
 
@@ -71,7 +72,7 @@ Between agents, create handoff document:
 ## Example: Feature Workflow
 
 ```
-/orchestrate feature "Add user authentication"
+/ccp:orchestrate feature "Add user authentication"
 ```
 
 Executes:
@@ -219,7 +220,7 @@ $ARGUMENTS:
 ## Custom Workflow Example
 
 ```
-/orchestrate custom "architect,tdd-guide,code-reviewer" "Redesign caching layer"
+/ccp:orchestrate custom "architect,tdd-guide,code-reviewer" "Redesign caching layer"
 ```
 
 ## Tips

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

@@ -1,4 +1,5 @@
 ---
+name: ccp:plan
 description: Restate requirements, assess risks, and create step-by-step implementation plan. WAIT for user CONFIRM before touching any code.
 ---
 
@@ -15,7 +16,7 @@ This command invokes the **planner** agent to create a comprehensive implementat
 
 ## When to Use
 
-Use `/plan` when:
+Use `/ccp:plan` when:
 - Starting a new feature
 - Making significant architectural changes
 - Working on complex refactoring
@@ -36,7 +37,7 @@ The planner agent will:
 ## Example Usage
 
 ```
-User: /plan I need to add real-time notifications when markets resolve
+User: /ccp:plan I need to add real-time notifications when markets resolve
 
 Agent (planner):
 # Implementation Plan: Real-Time Market Resolution Notifications
@@ -103,9 +104,9 @@ If you want changes, respond with:
 ## Integration with Other Commands
 
 After planning:
-- Use `/tdd` to implement with test-driven development
-- Use `/build-fix` if build errors occur
-- Use `/code-review` to review completed implementation
+- Use `/ccp:tdd` to implement with test-driven development
+- Use `/ccp:build-fix` if build errors occur
+- Use `/ccp:code-review` to review completed implementation
 
 ## Related Agents
 

package/src/commands/ccp/profile-user.md

@@ -0,0 +1,46 @@
+---
+name: ccp:profile-user
+description: Generate developer behavioral profile and create Claude-discoverable artifacts
+argument-hint: "[--questionnaire] [--refresh]"
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+  - Glob
+  - Grep
+  - AskUserQuestion
+  - Task
+---
+
+<objective>
+Generate a developer behavioral profile from session analysis (or questionnaire) and produce artifacts (USER-PROFILE.md, /ccp:dev-preferences, CLAUDE.md section) that personalize Claude's responses.
+
+Routes to the profile-user workflow which orchestrates the full flow: consent gate, session analysis or questionnaire fallback, profile generation, result display, and artifact selection.
+</objective>
+
+<execution_context>
+@~/.claude/pilot/workflows/profile-user.md
+@~/.claude/pilot/references/ui-brand.md
+</execution_context>
+
+<context>
+Flags from $ARGUMENTS:
+- `--questionnaire` -- Skip session analysis entirely, use questionnaire-only path
+- `--refresh` -- Rebuild profile even when one exists, backup old profile, show dimension diff
+</context>
+
+<process>
+Execute the profile-user workflow end-to-end.
+
+The workflow handles all logic including:
+1. Initialization and existing profile detection
+2. Consent gate before session analysis
+3. Session scanning and data sufficiency checks
+4. Session analysis (profiler agent) or questionnaire fallback
+5. Cross-project split resolution
+6. Profile writing to USER-PROFILE.md
+7. Result display with report card and highlights
+8. Artifact selection (dev-preferences, CLAUDE.md sections)
+9. Sequential artifact generation
+10. Summary with refresh diff (if applicable)
+</process>

package/src/commands/{prompt-optimize.md → ccp/prompt-optimize.md}

@@ -1,8 +1,9 @@
 ---
+name: ccp:prompt-optimize
 description: Analyze a draft prompt and output an optimized version ready to paste and run. Does NOT execute the task — outputs advisory analysis only.
 ---
 
-# /prompt-optimize
+# /ccp:prompt-optimize
 
 Analyze and optimize the following prompt for maximum effectiveness.
 
@@ -28,7 +29,7 @@ Apply the **prompt-optimizer** skill to the user's input below. Follow the 6-pha
 ## CRITICAL
 
 Do NOT execute the user's task. Output ONLY the analysis and optimized prompt.
-If the user asks for direct execution, explain that `/prompt-optimize` only produces advisory output and tell them to start a normal task request instead.
+If the user asks for direct execution, explain that `/ccp:prompt-optimize` only produces advisory output and tell them to start a normal task request instead.
 
 Note: `blueprint` is a **skill**, not a slash command. Write "Use the blueprint skill"
 instead of presenting it as a `/...` command.

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

@@ -1,5 +1,5 @@
 ---
-name: prune
+name: ccp:prune
 description: Delete pending instincts older than 30 days that were never promoted
 command: true
 ---
@@ -19,7 +19,7 @@ python3 ~/.claude/skills/continuous-learning-v2/scripts/instinct-cli.py prune
 ## Usage
 
 ```
-/prune                    # Delete instincts older than 30 days
-/prune --max-age 60      # Custom age threshold (days)
-/prune --dry-run         # Preview without deleting
+/ccp:prune                    # Delete instincts older than 30 days
+/ccp:prune --max-age 60      # Custom age threshold (days)
+/ccp:prune --dry-run         # Preview without deleting
 ```

package/src/commands/{python-review.md → ccp/python-review.md}

@@ -1,4 +1,5 @@
 ---
+name: ccp:python-review
 description: Comprehensive Python code review for PEP 8 compliance, type hints, security, and Pythonic idioms. Invokes the python-reviewer agent.
 ---
 
@@ -17,7 +18,7 @@ This command invokes the **python-reviewer** agent for comprehensive Python-spec
 
 ## When to Use
 
-Use `/python-review` when:
+Use `/ccp:python-review` when:
 - After writing or modifying Python code
 - Before committing Python changes
 - Reviewing pull requests with Python code
@@ -77,7 +78,7 @@ pytest --cov=app --cov-report=term-missing
 ## Example Usage
 
 ```text
-User: /python-review
+User: /ccp:python-review
 
 Agent:
 # Python Code Review Report
@@ -171,10 +172,10 @@ Run: `black app/routes/user.py app/services/auth.py`
 
 ## Integration with Other Commands
 
-- Use `/tdd` first to ensure tests pass
-- Use `/code-review` for non-Python specific concerns
-- Use `/python-review` before committing
-- Use `/build-fix` if static analysis tools fail
+- Use `/ccp:tdd` first to ensure tests pass
+- Use `/ccp:code-review` for non-Python specific concerns
+- Use `/ccp:python-review` before committing
+- Use `/ccp:build-fix` if static analysis tools fail
 
 ## Framework-Specific Reviews
 

package/src/commands/{quality-gate.md → ccp/quality-gate.md}

@@ -1,10 +1,15 @@
+---
+name: ccp:quality-gate
+description: "Run the CCP quality pipeline on demand for a file or project scope"
+---
+
 # Quality Gate Command
 
 Run the CCP quality pipeline on demand for a file or project scope.
 
 ## Usage
 
-`/quality-gate [path|.] [--fix] [--strict]`
+`/ccp:quality-gate [path|.] [--fix] [--strict]`
 
 - default target: current directory (`.`)
 - `--fix`: allow auto-format/fix where configured

package/src/commands/{refactor-clean.md → ccp/refactor-clean.md}

@@ -1,3 +1,8 @@
+---
+name: ccp:refactor-clean
+description: "Safely identify and remove dead code with test verification"
+---
+
 # Refactor Clean
 
 Safely identify and remove dead code with test verification at every step.

package/src/commands/{resume-session.md → ccp/resume-session.md}

@@ -1,11 +1,12 @@
 ---
+name: ccp:resume-session
 description: Load the most recent session file from ~/.claude/sessions/ and resume work with full context from where the last session ended.
 ---
 
 # Resume Session Command
 
 Load the last saved session state and orient fully before doing any work.
-This command is the counterpart to `/save-session`.
+This command is the counterpart to `/ccp:save-session`.
 
 ## When to Use
 
@@ -17,10 +18,10 @@ This command is the counterpart to `/save-session`.
 ## Usage
 
 ```
-/resume-session                                                      # loads most recent file in ~/.claude/sessions/
-/resume-session 2024-01-15                                           # loads most recent session for that date
-/resume-session ~/.claude/sessions/2024-01-15-session.tmp           # loads a specific legacy-format file
-/resume-session ~/.claude/sessions/2024-01-15-abc123de-session.tmp  # loads a current short-id session file
+/ccp:resume-session                                                      # loads most recent file in ~/.claude/sessions/
+/ccp:resume-session 2024-01-15                                           # loads most recent session for that date
+/ccp:resume-session ~/.claude/sessions/2024-01-15-session.tmp           # loads a specific legacy-format file
+/ccp:resume-session ~/.claude/sessions/2024-01-15-abc123de-session.tmp  # loads a current short-id session file
 ```
 
 ## Process
@@ -34,7 +35,7 @@ If no argument provided:
 3. If the folder does not exist or has no matching files, tell the user:
    ```
    No session files found in ~/.claude/sessions/
-   Run /save-session at the end of a session to create one.
+   Run /ccp:save-session at the end of a session to create one.
    ```
    Then stop.
 
@@ -107,7 +108,7 @@ Note the gap — "⚠️ This session is from N days ago (threshold: 7 days). Th
 Read it and follow the same briefing process — the format is the same regardless of source.
 
 **Session file is empty or malformed:**
-Report: "Session file found but appears empty or unreadable. You may need to create a new one with /save-session."
+Report: "Session file found but appears empty or unreadable. You may need to create a new one with /ccp:save-session."
 
 ---
 
@@ -152,4 +153,4 @@ Ready to continue. What would you like to do?
 - Never modify the session file when loading it — it's a read-only historical record
 - The briefing format is fixed — do not skip sections even if they are empty
 - "What Not To Retry" must always be shown, even if it just says "None" — it's too important to miss
-- After resuming, the user may want to run `/save-session` again at the end of the new session to create a new dated file
+- After resuming, the user may want to run `/ccp:save-session` again at the end of the new session to create a new dated file

package/src/commands/ccp/review.md

@@ -0,0 +1,37 @@
+---
+name: ccp:review
+description: Request cross-AI peer review of phase plans from external AI CLIs
+argument-hint: "--phase N [--gemini] [--claude] [--codex] [--all]"
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+  - Glob
+  - Grep
+---
+
+<objective>
+Invoke external AI CLIs (Gemini, Claude, Codex) to independently review phase plans.
+Produces a structured REVIEWS.md with per-reviewer feedback that can be fed back into
+planning via /ccp:plan-phase --reviews.
+
+**Flow:** Detect CLIs → Build review prompt → Invoke each CLI → Collect responses → Write REVIEWS.md
+</objective>
+
+<execution_context>
+@~/.claude/pilot/workflows/review.md
+</execution_context>
+
+<context>
+Phase number: extracted from $ARGUMENTS (required)
+
+**Flags:**
+- `--gemini` — Include Gemini CLI review
+- `--claude` — Include Claude CLI review (uses separate session)
+- `--codex` — Include Codex CLI review
+- `--all` — Include all available CLIs
+</context>
+
+<process>
+Execute the review workflow from @~/.claude/pilot/workflows/review.md end-to-end.
+</process>

package/src/commands/{rules-distill.md → ccp/rules-distill.md}

@@ -1,8 +1,9 @@
 ---
+name: ccp:rules-distill
 description: "Scan skills to extract cross-cutting principles and distill them into rules"
 ---
 
-# /rules-distill — Distill Principles from Skills into Rules
+# /ccp:rules-distill — Distill Principles from Skills into Rules
 
 Scan installed skills, extract cross-cutting principles, and distill them into rules.
 

package/src/commands/{rust-build.md → ccp/rust-build.md}

@@ -1,4 +1,5 @@
 ---
+name: ccp:rust-build
 description: Fix Rust build errors, borrow checker issues, and dependency problems incrementally. Invokes the rust-build-resolver agent for minimal, surgical fixes.
 ---
 
@@ -16,7 +17,7 @@ This command invokes the **rust-build-resolver** agent to incrementally fix Rust
 
 ## When to Use
 
-Use `/rust-build` when:
+Use `/ccp:rust-build` when:
 - `cargo build` or `cargo check` fails with errors
 - `cargo clippy` reports warnings
 - Borrow checker or lifetime errors block compilation
@@ -45,7 +46,7 @@ if command -v cargo-audit >/dev/null; then cargo audit; else echo "cargo-audit n
 ## Example Session
 
 ````text
-User: /rust-build
+User: /ccp:rust-build
 
 Agent:
 # Rust Build Resolution
@@ -177,9 +178,9 @@ The agent will stop and report if:
 
 ## Related Commands
 
-- `/rust-test` - Run tests after build succeeds
-- `/rust-review` - Review code quality
-- `/verify` - Full verification loop
+- `/ccp:rust-test` - Run tests after build succeeds
+- `/ccp:rust-review` - Review code quality
+- `/ccp:verify` - Full verification loop
 
 ## Related
 

package/src/commands/{rust-review.md → ccp/rust-review.md}

@@ -1,4 +1,5 @@
 ---
+name: ccp:rust-review
 description: Comprehensive Rust code review for ownership, lifetimes, error handling, unsafe usage, and idiomatic patterns. Invokes the rust-reviewer agent.
 ---
 
@@ -17,7 +18,7 @@ This command invokes the **rust-reviewer** agent for comprehensive Rust-specific
 
 ## When to Use
 
-Use `/rust-review` when:
+Use `/ccp:rust-review` when:
 - After writing or modifying Rust code
 - Before committing Rust changes
 - Reviewing pull requests with Rust code
@@ -71,7 +72,7 @@ if command -v cargo-audit >/dev/null; then cargo audit; else echo "cargo-audit n
 ## Example Usage
 
 ````text
-User: /rust-review
+User: /ccp:rust-review
 
 Agent:
 # Rust Code Review Report
@@ -131,10 +132,10 @@ Recommendation: Block merge until CRITICAL issue is fixed
 
 ## Integration with Other Commands
 
-- Use `/rust-test` first to ensure tests pass
-- Use `/rust-build` if build errors occur
-- Use `/rust-review` before committing
-- Use `/code-review` for non-Rust-specific concerns
+- Use `/ccp:rust-test` first to ensure tests pass
+- Use `/ccp:rust-build` if build errors occur
+- Use `/ccp:rust-review` before committing
+- Use `/ccp:code-review` for non-Rust-specific concerns
 
 ## Related
 

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

@@ -1,4 +1,5 @@
 ---
+name: ccp:rust-test
 description: Enforce TDD workflow for Rust. Write tests first, then implement. Verify 80%+ coverage with cargo-llvm-cov.
 ---
 
@@ -17,7 +18,7 @@ This command enforces test-driven development methodology for Rust code using `#
 
 ## When to Use
 
-Use `/rust-test` when:
+Use `/ccp:rust-test` when:
 - Implementing new Rust functions, methods, or traits
 - Adding test coverage to existing Rust code
 - Fixing bugs (write failing test first)
@@ -36,7 +37,7 @@ REPEAT  -> Next test case
 ## Example Session
 
 ````text
-User: /rust-test I need a function to validate user registration
+User: /ccp:rust-test I need a function to validate user registration
 
 Agent:
 # TDD Session: Registration Validator
@@ -298,9 +299,9 @@ cargo test --no-fail-fast
 
 ## Related Commands
 
-- `/rust-build` - Fix build errors
-- `/rust-review` - Review code after implementation
-- `/verify` - Run full verification loop
+- `/ccp:rust-build` - Fix build errors
+- `/ccp:rust-review` - Review code after implementation
+- `/ccp:verify` - Run full verification loop
 
 ## Related
 

package/src/commands/{save-session.md → ccp/save-session.md}

@@ -1,4 +1,5 @@
 ---
+name: ccp:save-session
 description: Save current session state to a dated file in ~/.claude/sessions/ so work can be resumed in a future session with full context.
 ---
 
@@ -270,6 +271,6 @@ Then test with Postman — the response should include a `Set-Cookie` header.
 - Each session gets its own file — never append to a previous session's file
 - The "What Did NOT Work" section is the most critical — future sessions will blindly retry failed approaches without it
 - If the user asks to save mid-session (not just at the end), save what's known so far and mark in-progress items clearly
-- The file is meant to be read by Claude at the start of the next session via `/resume-session`
+- The file is meant to be read by Claude at the start of the next session via `/ccp:resume-session`
 - Use the canonical global session store: `~/.claude/sessions/`
 - Prefer the short-id filename form (`YYYY-MM-DD-<short-id>-session.tmp`) for any new session file

package/src/commands/ccp/secure-phase.md

@@ -0,0 +1,35 @@
+---
+name: ccp:secure-phase
+description: Retroactively verify threat mitigations for a completed phase
+argument-hint: "[phase number]"
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Glob
+  - Grep
+  - Task
+  - AskUserQuestion
+---
+<objective>
+Verify threat mitigations for a completed phase. Three states:
+- (A) SECURITY.md exists — audit and verify mitigations
+- (B) No SECURITY.md, PLAN.md with threat model exists — run from artifacts
+- (C) Phase not executed — exit with guidance
+
+Output: updated SECURITY.md.
+</objective>
+
+<execution_context>
+@~/.claude/pilot/workflows/secure-phase.md
+</execution_context>
+
+<context>
+Phase: $ARGUMENTS — optional, defaults to last completed phase.
+</context>
+
+<process>
+Execute @~/.claude/pilot/workflows/secure-phase.md.
+Preserve all workflow gates.
+</process>