claude-code-pilot 3.0.0 → 3.1.1

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

@@ -1,4 +1,5 @@
 ---
+name: ccp:cpp-test
 description: Enforce TDD workflow for C++. Write GoogleTest tests first, then implement. Verify coverage with gcov/lcov.
 ---
 
@@ -17,7 +18,7 @@ This command enforces test-driven development methodology for C++ code using Goo
 
 ## When to Use
 
-Use `/cpp-test` when:
+Use `/ccp:cpp-test` when:
 - Implementing new C++ functions or classes
 - Adding test coverage to existing code
 - Fixing bugs (write failing test first)
@@ -36,7 +37,7 @@ REPEAT  → Next test case
 ## Example Session
 
 ````
-User: /cpp-test I need a function to validate email addresses
+User: /ccp:cpp-test I need a function to validate email addresses
 
 Agent:
 # TDD Session: Email Validator
@@ -241,9 +242,9 @@ genhtml coverage.info --output-directory coverage_html
 
 ## Related Commands
 
-- `/cpp-build` - Fix build errors
-- `/cpp-review` - Review code after implementation
-- `/verify` - Run full verification loop
+- `/ccp:cpp-build` - Fix build errors
+- `/ccp:cpp-review` - Review code after implementation
+- `/ccp:verify` - Run full verification loop
 
 ## Related
 

package/src/commands/ccp/docs-update.md

@@ -0,0 +1,48 @@
+---
+name: ccp: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 ccp-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 GSD 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/pilot/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 GSD 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 ccp-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/pilot/workflows/docs-update.md end-to-end.
+Preserve all workflow gates (preservation_check, flag handling, wave execution, monorepo dispatch, commit, reporting).
+</process>

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

@@ -1,8 +1,9 @@
 ---
+name: ccp:docs
 description: Look up current documentation for a library or topic via Context7.
 ---
 
-# /docs
+# /ccp:docs
 
 ## Purpose
 
@@ -11,10 +12,10 @@ Look up up-to-date documentation for a library, framework, or API and return a s
 ## Usage
 
 ```
-/docs [library name] [question]
+/ccp:docs [library name] [question]
 ```
 
-Use quotes for multi-word arguments so they are parsed as a single token. Example: `/docs "Next.js" "How do I configure middleware?"`
+Use quotes for multi-word arguments so they are parsed as a single token. Example: `/ccp:docs "Next.js" "How do I configure middleware?"`
 
 If library or question is omitted, prompt the user for:
 1. The library or product name (e.g. Next.js, Prisma, Supabase).

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

@@ -1,4 +1,5 @@
 ---
+name: ccp:e2e
 description: Generate and run end-to-end tests with Playwright. Creates test journeys, runs tests, captures screenshots/videos/traces, and uploads artifacts.
 ---
 
@@ -16,7 +17,7 @@ This command invokes the **e2e-runner** agent to generate, maintain, and execute
 
 ## When to Use
 
-Use `/e2e` when:
+Use `/ccp:e2e` when:
 - Testing critical user journeys (login, trading, payments)
 - Verifying multi-step flows work end-to-end
 - Testing UI interactions and navigation
@@ -37,7 +38,7 @@ The e2e-runner agent will:
 ## Example Usage
 
 ```
-User: /e2e Test the market search and view flow
+User: /ccp:e2e Test the market search and view flow
 
 Agent (e2e-runner):
 # E2E Test Generation: Market Search and View Flow
@@ -330,10 +331,10 @@ For PMX, prioritize these E2E tests:
 
 ## Integration with Other Commands
 
-- Use `/plan` to identify critical journeys to test
-- Use `/tdd` for unit tests (faster, more granular)
-- Use `/e2e` for integration and user journey tests
-- Use `/code-review` to verify test quality
+- Use `/ccp:plan` to identify critical journeys to test
+- Use `/ccp:tdd` for unit tests (faster, more granular)
+- Use `/ccp:e2e` for integration and user journey tests
+- Use `/ccp:code-review` to verify test quality
 
 ## Related Agents
 

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

@@ -1,14 +1,19 @@
+---
+name: ccp:eval
+description: "Manage eval-driven development workflow"
+---
+
 # Eval Command
 
 Manage eval-driven development workflow.
 
 ## Usage
 
-`/eval [define|check|report|list] [feature-name]`
+`/ccp:eval [define|check|report|list] [feature-name]`
 
 ## Define Evals
 
-`/eval define feature-name`
+`/ccp:eval define feature-name`
 
 Create a new eval definition:
 
@@ -35,7 +40,7 @@ Created: $(date)
 
 ## Check Evals
 
-`/eval check feature-name`
+`/ccp:eval check feature-name`
 
 Run evals for a feature:
 
@@ -60,7 +65,7 @@ Status: IN PROGRESS / READY
 
 ## Report Evals
 
-`/eval report feature-name`
+`/ccp:eval report feature-name`
 
 Generate comprehensive eval report:
 
@@ -98,7 +103,7 @@ RECOMMENDATION
 
 ## List Evals
 
-`/eval list`
+`/ccp:eval list`
 
 Show all eval definitions:
 

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

@@ -1,5 +1,5 @@
 ---
-name: evolve
+name: ccp:evolve
 description: Analyze instincts and suggest or generate evolved structures
 command: true
 ---
@@ -28,8 +28,8 @@ Analyzes instincts and clusters related ones into higher-level structures:
 ## Usage
 
 ```
-/evolve                    # Analyze all instincts and suggest evolutions
-/evolve --generate         # Also generate files under evolved/{skills,commands,agents}
+/ccp:evolve                    # Analyze all instincts and suggest evolutions
+/ccp:evolve --generate         # Also generate files under evolved/{skills,commands,agents}
 ```
 
 ## Evolution Rules

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

@@ -1,4 +1,5 @@
 ---
+name: ccp:go-build
 description: Fix Go build errors, go vet warnings, and linter issues incrementally. Invokes the go-build-resolver agent for minimal, surgical fixes.
 ---
 
@@ -16,7 +17,7 @@ This command invokes the **go-build-resolver** agent to incrementally fix Go bui
 
 ## When to Use
 
-Use `/go-build` when:
+Use `/ccp:go-build` when:
 - `go build ./...` fails with errors
 - `go vet ./...` reports issues
 - `golangci-lint run` shows warnings
@@ -44,7 +45,7 @@ go mod tidy -v
 ## Example Session
 
 ```text
-User: /go-build
+User: /ccp:go-build
 
 Agent:
 # Go Build Resolution
@@ -173,9 +174,9 @@ The agent will stop and report if:
 
 ## Related Commands
 
-- `/go-test` - Run tests after build succeeds
-- `/go-review` - Review code quality
-- `/verify` - Full verification loop
+- `/ccp:go-test` - Run tests after build succeeds
+- `/ccp:go-review` - Review code quality
+- `/ccp:verify` - Full verification loop
 
 ## Related
 

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

@@ -1,4 +1,5 @@
 ---
+name: ccp:go-review
 description: Comprehensive Go code review for idiomatic patterns, concurrency safety, error handling, and security. Invokes the go-reviewer agent.
 ---
 
@@ -17,7 +18,7 @@ This command invokes the **go-reviewer** agent for comprehensive Go-specific cod
 
 ## When to Use
 
-Use `/go-review` when:
+Use `/ccp:go-review` when:
 - After writing or modifying Go code
 - Before committing Go changes
 - Reviewing pull requests with Go code
@@ -69,7 +70,7 @@ govulncheck ./...
 ## Example Usage
 
 ```text
-User: /go-review
+User: /ccp:go-review
 
 Agent:
 # Go Code Review Report
@@ -137,10 +138,10 @@ Recommendation: ❌ Block merge until CRITICAL issue is fixed
 
 ## Integration with Other Commands
 
-- Use `/go-test` first to ensure tests pass
-- Use `/go-build` if build errors occur
-- Use `/go-review` before committing
-- Use `/code-review` for non-Go specific concerns
+- Use `/ccp:go-test` first to ensure tests pass
+- Use `/ccp:go-build` if build errors occur
+- Use `/ccp:go-review` before committing
+- Use `/ccp:code-review` for non-Go specific concerns
 
 ## Related
 

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

@@ -1,4 +1,5 @@
 ---
+name: ccp:go-test
 description: Enforce TDD workflow for Go. Write table-driven tests first, then implement. Verify 80%+ coverage with go test -cover.
 ---
 
@@ -17,7 +18,7 @@ This command enforces test-driven development methodology for Go code using idio
 
 ## When to Use
 
-Use `/go-test` when:
+Use `/ccp:go-test` when:
 - Implementing new Go functions
 - Adding test coverage to existing code
 - Fixing bugs (write failing test first)
@@ -36,7 +37,7 @@ REPEAT  → Next test case
 ## Example Session
 
 ````
-User: /go-test I need a function to validate email addresses
+User: /ccp:go-test I need a function to validate email addresses
 
 Agent:
 # TDD Session: Email Validator
@@ -258,9 +259,9 @@ go test -race -cover ./...
 
 ## Related Commands
 
-- `/go-build` - Fix build errors
-- `/go-review` - Review code after implementation
-- `/verify` - Run full verification loop
+- `/ccp:go-build` - Fix build errors
+- `/ccp:go-review` - Review code after implementation
+- `/ccp:verify` - Run full verification loop
 
 ## Related
 

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

@@ -1,4 +1,5 @@
 ---
+name: ccp:gradle-build
 description: Fix Gradle build errors for Android and KMP projects
 ---
 

package/src/commands/{harness-audit.md → ccp/harness-audit.md}

@@ -1,10 +1,15 @@
+---
+name: ccp:harness-audit
+description: "Run deterministic repository harness audit and return prioritized scorecard"
+---
+
 # Harness Audit Command
 
 Run a deterministic repository harness audit and return a prioritized scorecard.
 
 ## Usage
 
-`/harness-audit [scope] [--format text|json]`
+`/ccp:harness-audit [scope] [--format text|json]`
 
 - `scope` (optional): `repo` (default), `hooks`, `skills`, `commands`, `agents`
 - `--format`: output style (`text` default, `json` for automation)

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

@@ -1,4 +1,5 @@
 ---
+name: ccp:kotlin-build
 description: Fix Kotlin/Gradle build errors, compiler warnings, and dependency issues incrementally. Invokes the kotlin-build-resolver agent for minimal, surgical fixes.
 ---
 
@@ -16,7 +17,7 @@ This command invokes the **kotlin-build-resolver** agent to incrementally fix Ko
 
 ## When to Use
 
-Use `/kotlin-build` when:
+Use `/ccp:kotlin-build` when:
 - `./gradlew build` fails with errors
 - Kotlin compiler reports errors
 - `./gradlew detekt` reports violations
@@ -43,7 +44,7 @@ Use `/kotlin-build` when:
 ## Example Session
 
 ````text
-User: /kotlin-build
+User: /ccp:kotlin-build
 
 Agent:
 # Kotlin Build Resolution
@@ -164,9 +165,9 @@ The agent will stop and report if:
 
 ## Related Commands
 
-- `/kotlin-test` - Run tests after build succeeds
-- `/kotlin-review` - Review code quality
-- `/verify` - Full verification loop
+- `/ccp:kotlin-test` - Run tests after build succeeds
+- `/ccp:kotlin-review` - Review code quality
+- `/ccp:verify` - Full verification loop
 
 ## Related
 

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

@@ -1,4 +1,5 @@
 ---
+name: ccp:kotlin-review
 description: Comprehensive Kotlin code review for idiomatic patterns, null safety, coroutine safety, and security. Invokes the kotlin-reviewer agent.
 ---
 
@@ -17,7 +18,7 @@ This command invokes the **kotlin-reviewer** agent for comprehensive Kotlin-spec
 
 ## When to Use
 
-Use `/kotlin-review` when:
+Use `/ccp:kotlin-review` when:
 - After writing or modifying Kotlin code
 - Before committing Kotlin changes
 - Reviewing pull requests with Kotlin code
@@ -68,7 +69,7 @@ Use `/kotlin-review` when:
 ## Example Usage
 
 ````text
-User: /kotlin-review
+User: /ccp:kotlin-review
 
 Agent:
 # Kotlin Code Review Report
@@ -129,10 +130,10 @@ Recommendation: ❌ Block merge until CRITICAL issue is fixed
 
 ## Integration with Other Commands
 
-- Use `/kotlin-test` first to ensure tests pass
-- Use `/kotlin-build` if build errors occur
-- Use `/kotlin-review` before committing
-- Use `/code-review` for non-Kotlin-specific concerns
+- Use `/ccp:kotlin-test` first to ensure tests pass
+- Use `/ccp:kotlin-build` if build errors occur
+- Use `/ccp:kotlin-review` before committing
+- Use `/ccp:code-review` for non-Kotlin-specific concerns
 
 ## Related
 

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
 ```