From 4254eeeaa7877fd2150d780ae40b42fe89ffe64c Mon Sep 17 00:00:00 2001 From: catlog22 Date: Sun, 8 Mar 2026 17:09:23 +0800 Subject: [PATCH] docs: update CCW Commands & Skills reference with 8-field format - Add CCW-COMMANDS-SKILLS-REFERENCE.md with comprehensive documentation - Update docs/reference/commands-skills.md (English) - Update docs/zh/reference/commands-skills.md (Chinese) - Include 55 Slash Commands and 41 Skills - Each entry follows 8-field format: Who, When, What, How, Output, Done, Failure & Recovery, Impact & Boundary - Exclude academic skills (scholar-*, journal-paper-writing, software-manual) --- docs/CCW-COMMANDS-SKILLS-REFERENCE.md | 1321 +++++++++++++++++ docs/reference/commands-skills.md | 1955 ++++++++++++++++--------- docs/zh/reference/commands-skills.md | 1955 ++++++++++++++++--------- 3 files changed, 3861 insertions(+), 1370 deletions(-) create mode 100644 docs/CCW-COMMANDS-SKILLS-REFERENCE.md diff --git a/docs/CCW-COMMANDS-SKILLS-REFERENCE.md b/docs/CCW-COMMANDS-SKILLS-REFERENCE.md new file mode 100644 index 00000000..4bb9b11c --- /dev/null +++ b/docs/CCW-COMMANDS-SKILLS-REFERENCE.md @@ -0,0 +1,1321 @@ +# CCW Commands & Skills Reference Manual + +> Generated: 2026-03-08 | Project: Claude Code Workspace (CCW) + +This reference manual provides quick lookup for all slash commands and skills in the CCW system. + +--- + +## Table of Contents + +- [Section 1: Slash Commands](#section-1-slash-commands) + - [Core](#core) + - [DDD (Document-Driven Development)](#ddd-document-driven-development) + - [Issue](#issue) + - [IDAW (Iterative Development Automation Workflow)](#idaw-iterative-development-automation-workflow) + - [Workflow](#workflow) + - [Memory](#memory) + - [CLI](#cli) +- [Section 2: Skills](#section-2-skills) + - [Workflow Skills](#workflow-skills) + - [Team Skills](#team-skills) + - [Utility Skills](#utility-skills) +- [Appendix A: Quick Reference Table](#appendix-a-quick-reference-table) +- [Appendix B: Command Chain Examples](#appendix-b-command-chain-examples) + +--- + +## Section 1: Slash Commands + +### Core + +#### `/ccw` + +| Field | Description | +|-------|-------------| +| **Who** | Developer starting any task | +| **When** | Entry point for workflow orchestration | +| **What** | Main workflow orchestrator that analyzes intent, dispatches to appropriate skill chain. Example: `/ccw "implement user authentication"` | +| **How** | Parses intent -> Selects skill chain -> Executes orchestrator | +| **Output** | Delegates to workflow-plan, issue-manage, or other skills | +| **Done** | Appropriate skill completes execution | +| **Failure & Recovery** | Fallback to manual skill selection if intent unclear | +| **Impact & Boundary** | Project-wide orchestration entry point | + +#### `/ccw-coordinator` + +| Field | Description | +|-------|-------------| +| **Who** | System needing command orchestration | +| **When** | Multi-command coordination required | +| **What** | Command orchestration tool that analyzes requirements and dispatches commands. Example: `/ccw-coordinator "review and fix auth module"` | +| **How** | Requirement analysis -> Command selection -> Sequential execution | +| **Output** | Coordinated command execution results | +| **Done** | All dispatched commands complete | +| **Failure & Recovery** | Partial results preserved, user notified of failures | +| **Impact & Boundary** | Cross-command coordination | + +#### `/flow-create` + +| Field | Description | +|-------|-------------| +| **Who** | Developer creating reusable workflow templates | +| **When** | Need to document and share workflow patterns | +| **What** | Flow template generator for creating reusable command chains. Example: `/flow-create "auth-feature-flow"` | +| **How** | Template definition -> Parameter extraction -> Flow file generation | +| **Output** | Flow template file in `.claude/flows/` | +| **Done** | Template file created and validated | +| **Failure & Recovery** | Validation errors show specific issues | +| **Impact & Boundary** | Workflow template creation only | + +--- + +### DDD (Document-Driven Development) + +#### `/ddd:scan` + +| Field | Description | +|-------|-------------| +| **Who** | Developer onboarding to existing project without specs | +| **When** | Starting doc-driven workflow on legacy codebase | +| **What** | Scans codebase to build doc-index by reverse-engineering structure. Example: `/ddd:scan -y "existing project"` | +| **How** | Framework detection -> Component discovery -> Feature inference -> Requirement extraction -> doc-index.json | +| **Output** | `.workflow/.doc-index/doc-index.json` + feature-maps/ + tech-registry/ | +| **Done** | doc-index.json created with components, features, IREQ entries | +| **Failure & Recovery** | Graceful degradation if DeepWiki unavailable | +| **Impact & Boundary** | Code-first entry point, can upgrade to spec-first later | + +#### `/ddd:index-build` + +| Field | Description | +|-------|-------------| +| **Who** | Developer with existing spec-generator outputs | +| **When** | Building index from REQ, ADR, EPIC documents | +| **What** | Builds doc-index from spec outputs and maps entities to code. Example: `/ddd:index-build --spec SPEC-auth-2026-03-08` | +| **How** | Parse specs -> Codebase mapping via CLI -> Feature grouping -> doc-index.json | +| **Output** | `.workflow/.doc-index/doc-index.json` with spec-first traceability | +| **Done** | All spec entities linked to code components | +| **Failure & Recovery** | Orphan components flagged for review | +| **Impact & Boundary** | Spec-first entry point, merges with existing code-first index | + +#### `/ddd:plan` + +| Field | Description | +|-------|-------------| +| **Who** | Developer planning document-driven task | +| **When** | Before any development task in DDD workflow | +| **What** | Queries doc-index, explores codebase with doc-aware angles, produces plan.json. Example: `/ddd:plan -y "add rate limiting"` | +| **How** | Doc-index query -> Guided exploration -> Clarification -> Task planning -> Handoff | +| **Output** | `.workflow/.doc-index/planning/{session}/plan.json` + TASK-*.json | +| **Done** | Plan with doc_context traceability generated | +| **Failure & Recovery** | Schema version mismatch warns but continues | +| **Impact & Boundary** | Requires existing doc-index.json | + +#### `/ddd:execute` + +| Field | Description | +|-------|-------------| +| **Who** | Developer executing document-aware tasks | +| **When** | After /ddd:plan produces plan.json | +| **What** | Document-aware execution engine with doc-context loading. Example: `/ddd:execute --in-memory` | +| **How** | Load plan -> Read doc-context -> Execute task -> Update doc-index | +| **Output** | Code changes + updated doc-index traceability | +| **Done** | All tasks executed, doc-index updated | +| **Failure & Recovery** | Task failures logged, recovery options presented | +| **Impact & Boundary** | Requires plan.json from /ddd:plan | + +#### `/ddd:doc-generate` + +| Field | Description | +|-------|-------------| +| **Who** | Developer regenerating documentation | +| **When** | After doc-index built or needs refresh | +| **What** | Generates full document tree from doc-index.json. Example: `/ddd:doc-generate --force --layer all` | +| **How** | Layer 3 (components) -> Layer 2 (features) -> Layer 1 (indexes) | +| **Output** | tech-registry/*.md, feature-maps/*.md, README.md, ARCHITECTURE.md | +| **Done** | All layers generated, SCHEMA.md created | +| **Failure & Recovery** | Existing docs warning, --force to overwrite | +| **Impact & Boundary** | Read-only from doc-index, generates MD files | + +#### `/ddd:doc-refresh` + +| Field | Description | +|-------|-------------| +| **Who** | Developer after incremental code changes | +| **When** | Code changed, need targeted doc updates | +| **What** | Incrementally updates affected documents after code changes. Example: `/ddd:doc-refresh -y` | +| **How** | Detect changed files -> Find affected docs -> Regenerate only affected | +| **Output** | Updated subset of documentation files | +| **Done** | Affected docs updated, unchanged docs preserved | +| **Failure & Recovery** | Falls back to full regeneration if detection fails | +| **Impact & Boundary** | Incremental update, more efficient than full regenerate | + +#### `/ddd:sync` + +| Field | Description | +|-------|-------------| +| **Who** | Developer after task completion | +| **When** | Post-task synchronization to update index | +| **What** | Post-task synchronization updates doc-index with completed work. Example: `/ddd:sync -y "auth feature complete"` | +| **How** | Detect changes -> Update components -> Update requirements status -> Add action log | +| **Output** | Updated doc-index.json with action entries | +| **Done** | Index reflects current codebase state | +| **Failure & Recovery** | Merge conflicts resolved automatically | +| **Impact & Boundary** | Post-execution sync only | + +#### `/ddd:update` + +| Field | Description | +|-------|-------------| +| **Who** | Developer maintaining doc-index | +| **When** | Detecting drift between code and docs | +| **What** | Incremental index update detecting code changes. Example: `/ddd:update --scope src/auth` | +| **How** | File hash comparison -> Detect changes -> Update affected entries | +| **Output** | Updated doc-index.json entries | +| **Done** | Index entries match current code | +| **Failure & Recovery** | Unchanged files skipped | +| **Impact & Boundary** | Lightweight incremental update | + +#### `/ddd:auto` + +| Field | Description | +|-------|-------------| +| **Who** | Developer wanting full automation | +| **When** | Quick feature implementation with docs | +| **What** | Chain command for automated DDD workflow. Example: `/ddd:auto -y "implement search feature"` | +| **How** | plan -> execute -> sync in single command | +| **Output** | Complete implementation + updated docs | +| **Done** | Feature implemented and documented | +| **Failure & Recovery** | Stops at first failing phase | +| **Impact & Boundary** | Full automation, less control | + +--- + +### Issue + +#### `/issue:new` + +| Field | Description | +|-------|-------------| +| **Who** | Developer creating structured issue | +| **When** | Starting issue tracking for a task | +| **What** | Creates structured issue from GitHub URL or description. Example: `/issue:new "Fix login timeout bug"` | +| **How** | Parse input -> Structure issue -> Create in issues.jsonl | +| **Output** | Issue entry in `.workflow/issues/issues.jsonl` | +| **Done** | Issue created with status "registered" | +| **Failure & Recovery** | Duplicate detection warns user | +| **Impact & Boundary** | Issue creation only, no planning | + +#### `/issue:discover` + +| Field | Description | +|-------|-------------| +| **Who** | Developer finding potential issues | +| **When** | Starting issue management workflow | +| **What** | Discovers potential issues from multiple sources. Example: `/issue:discover --scope src/auth` | +| **How** | Scan codebase -> Detect patterns -> Generate issue candidates | +| **Output** | List of discovered issue candidates | +| **Done** | Candidates presented for user selection | +| **Failure & Recovery** | Empty results suggest manual creation | +| **Impact & Boundary** | Discovery only, no automatic creation | + +#### `/issue:discover-by-prompt` + +| Field | Description | +|-------|-------------| +| **Who** | Developer with natural language query | +| **When** | Finding issues via description | +| **What** | Discovers issues from user prompt with Gemini analysis. Example: `/issue:discover-by-prompt "authentication problems"` | +| **How** | Gemini analysis -> Pattern matching -> Issue suggestions | +| **Output** | Issue candidates matching prompt | +| **Done** | Candidates presented for confirmation | +| **Failure & Recovery** | Falls back to keyword search | +| **Impact & Boundary** | Natural language discovery | + +#### `/issue:from-brainstorm` + +| Field | Description | +|-------|-------------| +| **Who** | Developer converting ideas to issues | +| **When** | After brainstorm session | +| **What** | Converts brainstorm session ideas into issues. Example: `/issue:from-brainstorm BRAIN-2026-03-08` | +| **How** | Parse brainstorm -> Extract actionables -> Create issues | +| **Output** | Multiple issues from brainstorm artifacts | +| **Done** | All actionables converted to issues | +| **Failure & Recovery** | Partial conversion on parse errors | +| **Impact & Boundary** | Requires completed brainstorm session | + +#### `/issue:plan` + +| Field | Description | +|-------|-------------| +| **Who** | Developer planning issue resolution | +| **When** | Issue registered, needs solution | +| **What** | Batch plans issue resolution using issue-planning-agent. Example: `/issue:plan ISS-001 ISS-002` | +| **How** | Load issues -> Generate solutions -> Bind to issues | +| **Output** | Solution files in `.workflow/issues/solutions/` | +| **Done** | Issues have bound solutions | +| **Failure & Recovery** | Partial planning on complex issues | +| **Impact & Boundary** | Planning only, no execution | + +#### `/issue:queue` + +| Field | Description | +|-------|-------------| +| **Who** | Developer forming execution queue | +| **When** | Solutions planned, ready to execute | +| **What** | Forms execution queue from bound solutions. Example: `/issue:queue ISS-001 ISS-002` | +| **How** | Build DAG -> Resolve dependencies -> Create queue | +| **Output** | Queue file in `.workflow/issues/queues/` | +| **Done** | Queue ready for execution | +| **Failure & Recovery** | Circular dependency detection | +| **Impact & Boundary** | Queue formation only | + +#### `/issue:execute` + +| Field | Description | +|-------|-------------| +| **Who** | Developer executing queued issues | +| **When** | Queue formed, ready to run | +| **What** | Executes queue with DAG-based parallel orchestration. Example: `/issue:execute -y` | +| **How** | DAG traversal -> Parallel execution -> Progress tracking | +| **Output** | Task execution results, code changes | +| **Done** | All queued tasks completed | +| **Failure & Recovery** | Failed tasks skipped, dependents notified | +| **Impact & Boundary** | Execution engine for issue workflow | + +#### `/issue:convert-to-plan` + +| Field | Description | +|-------|-------------| +| **Who** | Developer with existing planning artifacts | +| **When** | Converting lite-plan or brainstorm to issue | +| **What** | Converts planning artifacts to issue format. Example: `/issue:convert-to-plan plan.json` | +| **How** | Parse artifact -> Extract tasks -> Create issue + solution | +| **Output** | Issue and solution from plan | +| **Done** | Plan converted to trackable issue | +| **Failure & Recovery** | Partial conversion preserved | +| **Impact & Boundary** | Artifact conversion only | + +--- + +### IDAW (Iterative Development Automation Workflow) + +#### `/idaw:status` + +| Field | Description | +|-------|-------------| +| **Who** | Developer checking IDAW progress | +| **When** | During IDAW session | +| **What** | Views IDAW task and session progress. Example: `/idaw:status` | +| **How** | Read session state -> Display progress | +| **Output** | Status summary of active IDAW session | +| **Done** | Status displayed | +| **Failure & Recovery** | No active session message | +| **Impact & Boundary** | Read-only status check | + +#### `/idaw:add` + +| Field | Description | +|-------|-------------| +| **Who** | Developer adding IDAW tasks | +| **When** | Building IDAW task list | +| **What** | Adds IDAW tasks via manual creation or import. Example: `/idaw:add "Implement caching layer"` | +| **How** | Parse input -> Create task entry -> Add to session | +| **Output** | Task added to IDAW session | +| **Done** | Task registered in session | +| **Failure & Recovery** | Duplicate task warning | +| **Impact & Boundary** | Task creation only | + +#### `/idaw:run` + +| Field | Description | +|-------|-------------| +| **Who** | Developer starting IDAW execution | +| **When** | Tasks added, ready to run | +| **What** | IDAW orchestrator executing task skill chain. Example: `/idaw:run -y` | +| **How** | Task dispatch -> Skill execution -> Progress tracking | +| **Output** | Task execution results | +| **Done** | All tasks processed | +| **Failure & Recovery** | Failed tasks logged, continue others | +| **Impact & Boundary** | Main IDAW execution engine | + +#### `/idaw:run-coordinate` + +| Field | Description | +|-------|-------------| +| **Who** | Developer needing coordinated execution | +| **When** | Complex multi-task IDAW session | +| **What** | IDAW coordinator executing task skill chain. Example: `/idaw:run-coordinate` | +| **How** | Coordinate multiple task executions -> Handle dependencies | +| **Output** | Coordinated execution results | +| **Done** | All coordinated tasks complete | +| **Failure & Recovery** | Dependency failures handled | +| **Impact & Boundary** | Coordinated execution mode | + +#### `/idaw:resume` + +| Field | Description | +|-------|-------------| +| **Who** | Developer resuming interrupted IDAW | +| **When** | IDAW session interrupted | +| **What** | Resumes interrupted IDAW session from last checkpoint. Example: `/idaw:resume` | +| **How** | Load state -> Resume from checkpoint -> Continue execution | +| **Output** | Continued execution from interruption point | +| **Done** | Session completes | +| **Failure & Recovery** | Checkpoint validation on load | +| **Impact & Boundary** | Resume capability for IDAW | + +--- + +### Workflow + +#### `/workflow:session:start` + +| Field | Description | +|-------|-------------| +| **Who** | Developer starting workflow session | +| **When** | Beginning any workflow work | +| **What** | Discovers or starts workflow session with conflict detection. Example: `/workflow:session:start --auto "implement OAuth2"` | +| **How** | Check active -> Detect conflicts -> Create/reuse session | +| **Output** | `SESSION_ID: WFS-{slug}` | +| **Done** | Session ready for work | +| **Failure & Recovery** | Multiple sessions warning | +| **Impact & Boundary** | Session initialization, calls /workflow:spec:setup if needed | + +#### `/workflow:session:list` + +| Field | Description | +|-------|-------------| +| **Who** | Developer reviewing sessions | +| **When** | Checking available sessions | +| **What** | Lists all workflow sessions with status filtering. Example: `/workflow:session:list --status active` | +| **How** | Scan .workflow/active -> Parse session metadata -> Display | +| **Output** | Session list with status, dates | +| **Done** | List displayed | +| **Failure & Recovery** | Empty list if no sessions | +| **Impact & Boundary** | Read-only listing | + +#### `/workflow:session:sync` + +| Field | Description | +|-------|-------------| +| **Who** | Developer syncing session work | +| **When** | After completing work in session | +| **What** | Quick-sync session work to specs/*.md and project-tech. Example: `/workflow:session:sync -y "auth complete"` | +| **How** | Gather context -> Extract updates -> Write specs + project-tech | +| **Output** | Updated specs/*.md and project-tech.json | +| **Done** | Sync complete message | +| **Failure & Recovery** | Duplicate rules skipped silently | +| **Impact & Boundary** | Updates project guidelines | + +#### `/workflow:session:resume` + +| Field | Description | +|-------|-------------| +| **Who** | Developer resuming paused session | +| **When** | Returning to paused work | +| **What** | Resumes most recently paused workflow session. Example: `/workflow:session:resume` | +| **How** | Find paused session -> Load state -> Continue | +| **Output** | Session context restored | +| **Done** | Ready to continue work | +| **Failure & Recovery** | No paused session error | +| **Impact & Boundary** | Session resumption | + +#### `/workflow:session:complete` + +| Field | Description | +|-------|-------------| +| **Who** | Developer finishing session | +| **When** | Session work complete | +| **What** | Archives completed session and removes from active. Example: `/workflow:session:complete -y` | +| **How** | Finalize state -> Archive -> Remove from active | +| **Output** | Archived session in .workflow/archived/ | +| **Done** | Session archived, specs updated | +| **Failure & Recovery** | Pending tasks warning | +| **Impact & Boundary** | Session finalization | + +#### `/workflow:spec:setup` + +| Field | Description | +|-------|-------------| +| **Who** | Developer initializing project specs | +| **When** | First time setup or regenerating | +| **What** | Initializes project-level state via cli-explore-agent analysis. Example: `/workflow:spec:setup --regenerate` | +| **How** | cli-explore-agent -> Generate project-tech.json -> Interactive questionnaire -> Write specs | +| **Output** | `.workflow/project-tech.json` + `.ccw/specs/*.md` | +| **Done** | Project specs configured | +| **Failure & Recovery** | Agent failure falls back to basic init | +| **Impact & Boundary** | Project-level initialization | + +#### `/workflow:spec:add` + +| Field | Description | +|-------|-------------| +| **Who** | Developer adding project rules | +| **When** | Adding conventions, constraints, or learnings | +| **What** | Adds specs, conventions, constraints to project guidelines. Example: `/workflow:spec:add -y "Use functional components"` | +| **How** | Parse input -> Auto-detect type -> Append to spec file | +| **Output** | Updated spec file in .ccw/specs/ | +| **Done** | Rule added confirmation | +| **Failure & Recovery** | Duplicate detection | +| **Impact & Boundary** | Single rule addition | + +#### `/workflow:clean` + +| Field | Description | +|-------|-------------| +| **Who** | Developer cleaning code | +| **When** | Before commits or after refactoring | +| **What** | Intelligent code cleanup with mainline detection. Example: `/workflow:clean -y` | +| **How** | Detect unused -> Remove dead code -> Format | +| **Output** | Cleaned code files | +| **Done** | Cleanup report displayed | +| **Failure & Recovery** | Preserves files with unclear usage | +| **Impact & Boundary** | Code cleanup only | + +#### `/workflow:debug-with-file` + +| Field | Description | +|-------|-------------| +| **Who** | Developer debugging issues | +| **When** | Encountering bugs or errors | +| **What** | Interactive hypothesis-driven debugging with file output. Example: `/workflow:debug-with-file "login fails on timeout"` | +| **How** | Hypothesis generation -> Evidence collection -> Validation -> Fix | +| **Output** | Debug report + potential fixes | +| **Done** | Root cause identified or fix applied | +| **Failure & Recovery** | Multiple hypothesis iteration | +| **Impact & Boundary** | Debugging workflow | + +#### `/workflow:analyze-with-file` + +| Field | Description | +|-------|-------------| +| **Who** | Developer analyzing code | +| **When** | Understanding codebase or issues | +| **What** | Interactive collaborative analysis with multi-CLI support. Example: `/workflow:analyze-with-file "analyze auth flow"` | +| **How** | Discovery -> Analysis -> Synthesis -> Report | +| **Output** | Analysis report in session folder | +| **Done** | Analysis complete with insights | +| **Failure & Recovery** | Partial analysis on errors | +| **Impact & Boundary** | Analysis workflow | + +#### `/workflow:brainstorm-with-file` + +| Field | Description | +|-------|-------------| +| **Who** | Developer exploring solutions | +| **When** | Starting new feature or solving complex problem | +| **What** | Interactive brainstorming with multi-CLI support. Example: `/workflow:brainstorm-with-file "caching strategy"` | +| **How** | Multi-perspective analysis -> Idea synthesis -> Recommendations | +| **Output** | Brainstorm report with actionables | +| **Done** | Ideas documented and prioritized | +| **Failure & Recovery** | Partial results preserved | +| **Impact & Boundary** | Ideation workflow | + +#### `/workflow:collaborative-plan-with-file` + +| Field | Description | +|-------|-------------| +| **Who** | Developer planning collaboratively | +| **When** | Complex feature planning | +| **What** | Collaborative planning with Plan Note output. Example: `/workflow:collaborative-plan-with-file "user dashboard redesign"` | +| **How** | Context gathering -> Planning -> Plan Note generation | +| **Output** | Plan with structured notes | +| **Done** | Plan ready for execution | +| **Failure & Recovery** | Iterative refinement | +| **Impact & Boundary** | Planning workflow | + +#### `/workflow:integration-test-cycle` + +| Field | Description | +|-------|-------------| +| **Who** | Developer running integration tests | +| **When** | After implementation, before merge | +| **What** | Self-iterating integration test workflow with reflection log. Example: `/workflow:integration-test-cycle -y "test auth flow"` | +| **How** | Generate tests -> Execute -> Reflect -> Iterate until pass | +| **Output** | Passing tests + reflection-log.md | +| **Done** | All tests passing | +| **Failure & Recovery** | Reflection-driven adjustment loop | +| **Impact & Boundary** | Integration testing workflow | + +#### `/workflow:refactor-cycle` + +| Field | Description | +|-------|-------------| +| **Who** | Developer addressing tech debt | +| **When** | Systematic code improvement | +| **What** | Tech debt discovery and self-iterating refactoring. Example: `/workflow:refactor-cycle -y "src/auth module"` | +| **How** | Debt discovery -> Prioritization -> Refactor -> Validate -> Reflect | +| **Output** | reflection-log.md + state.json + code changes | +| **Done** | All queued debt items processed | +| **Failure & Recovery** | Per-item validation with rollback | +| **Impact & Boundary** | Tech debt lifecycle management | + +#### `/workflow:roadmap-with-file` + +| Field | Description | +|-------|-------------| +| **Who** | Developer planning strategic requirements | +| **When** | Large feature or project planning | +| **What** | Strategic requirement roadmap with iterative decomposition. Example: `/workflow:roadmap-with-file -y "implement auth system"` | +| **How** | Understand -> Decompose -> Iterate -> Validate -> Handoff | +| **Output** | roadmap.md + issues.jsonl | +| **Done** | Roadmap approved, issues ready | +| **Failure & Recovery** | Max iteration rounds force proceed | +| **Impact & Boundary** | Strategic planning workflow | + +#### `/workflow:unified-execute-with-file` + +| Field | Description | +|-------|-------------| +| **Who** | Developer executing plans | +| **When** | After planning, ready to implement | +| **What** | Universal execution engine for any planning output. Example: `/workflow:unified-execute-with-file -y plan.json` | +| **How** | Load plan -> Validate -> Wave execution -> Track progress | +| **Output** | Code changes + execution-events.md | +| **Done** | All tasks executed | +| **Failure & Recovery** | Per-task retry with rollback | +| **Impact & Boundary** | Universal execution engine | + +#### UI Design Commands + +| Command | Who | When | What | Output | +|---------|-----|------|------|--------| +| `/workflow:ui-design:explore-auto` | Designer/Developer | Starting UI design | Interactive exploratory workflow | Style variants + layout templates + prototypes | +| `/workflow:ui-design:imitate-auto` | Designer/Developer | Imitating reference | UI design imitation workflow | Prototypes matching reference style | +| `/workflow:ui-design:generate` | Designer/Developer | Assembling prototypes | Pure assembler combining layouts + tokens | HTML/CSS prototypes | +| `/workflow:ui-design:style-extract` | Designer/Developer | Extracting styles | Extract design tokens from images | design-tokens.json + style-guide.md | +| `/workflow:ui-design:layout-extract` | Designer/Developer | Extracting layouts | Extract layout templates | layout-*.json files | +| `/workflow:ui-design:animation-extract` | Designer/Developer | Extracting animations | Extract animation patterns | animation-tokens.json | +| `/workflow:ui-design:codify-style` | Developer | From code to design | Extract styles from code files | Design tokens from CSS/SCSS | +| `/workflow:ui-design:import-from-code` | Developer | Code-based design | Import design from existing code | Design system from codebase | +| `/workflow:ui-design:design-sync` | Designer | Syncing design | Synchronize design references | Updated design system docs | +| `/workflow:ui-design:reference-page-generator` | Developer | Reference docs | Generate component reference pages | Multi-component reference pages | + +--- + +### Memory + +#### `/memory:prepare` + +| Field | Description | +|-------|-------------| +| **Who** | Developer preparing memory capture | +| **When** | Before capturing session knowledge | +| **What** | Delegates to universal-executor agent to prepare memory. Example: `/memory:prepare "auth session"` | +| **How** | Context gathering -> Memory structure preparation | +| **Output** | Prepared memory structure | +| **Done** | Ready for memory capture | +| **Failure & Recovery** | Agent failure handled | +| **Impact & Boundary** | Memory preparation only | + +#### `/memory:style-skill-memory` + +| Field | Description | +|-------|-------------| +| **Who** | Developer documenting style knowledge | +| **When** | After learning project patterns | +| **What** | Generates SKILL memory package from style patterns. Example: `/memory:style-skill-memory "React patterns"` | +| **How** | Pattern extraction -> Skill memory generation | +| **Output** | SKILL memory package | +| **Done** | Skill memory documented | +| **Failure & Recovery** | Partial patterns preserved | +| **Impact & Boundary** | Style-specific memory | + +--- + +### CLI + +#### `/cli:codex-review` + +| Field | Description | +|-------|-------------| +| **Who** | Developer reviewing code | +| **When** | Code review needed | +| **What** | Interactive code review using Codex CLI. Example: `/cli:codex-review --uncommitted` | +| **How** | Codex CLI -> Review analysis -> Interactive feedback | +| **Output** | Code review report | +| **Done** | Review complete with recommendations | +| **Failure & Recovery** | Codex unavailability fallback | +| **Impact & Boundary** | Git-aware code review | + +#### `/cli:cli-init` + +| Field | Description | +|-------|-------------| +| **Who** | Developer setting up CLI config | +| **When** | First time setup | +| **What** | Generates .gemini/ and .qwen/ config directories. Example: `/cli:cli-init` | +| **How** | Create directories -> Generate default configs | +| **Output** | CLI configuration directories | +| **Done** | Configs ready for customization | +| **Failure & Recovery** | Existing configs preserved | +| **Impact & Boundary** | CLI configuration setup | + +--- + +## Section 2: Skills + +### Workflow Skills + +#### `workflow-plan` + +| Field | Description | +|-------|-------------| +| **Who** | Developer planning tasks | +| **When** | Starting any planned work | +| **What** | Unified 4-phase planning: session discovery -> context gathering -> conflict resolution -> task generation | +| **How** | Phase 0: Session -> Phase 1: Context -> Phase 2: Conflicts -> Phase 3: Tasks | +| **Output** | plan.json + TASK-*.json in session folder | +| **Done** | Plan with TodoWrite tracking complete | +| **Failure & Recovery** | Conflict resolution prompts user | +| **Impact & Boundary** | Core planning skill | + +#### `workflow-execute` + +| Field | Description | +|-------|-------------| +| **Who** | Developer executing planned tasks | +| **When** | After workflow-plan | +| **What** | Agent execution orchestration with lazy task loading, auto-commit | +| **How** | Load plan -> Spawn agents -> Execute -> Commit | +| **Output** | Code changes + task completion status | +| **Done** | All tasks executed or user-stopped | +| **Failure & Recovery** | Per-task retry, auto-rollback | +| **Impact & Boundary** | Core execution skill | + +#### `workflow-lite-plan` + +| Field | Description | +|-------|-------------| +| **Who** | Developer needing quick planning | +| **When** | Simple tasks without full session | +| **What** | Lightweight planning - task analysis + breakdown | +| **How** | Analyze -> Break down -> Generate tasks | +| **Output** | Simplified plan.json | +| **Done** | Quick plan ready | +| **Failure & Recovery** | Falls back to workflow-plan for complex cases | +| **Impact & Boundary** | Lightweight alternative | + +#### `workflow-lite-execute` + +| Field | Description | +|-------|-------------| +| **Who** | Developer executing simple plans | +| **When** | After lite-plan or standalone | +| **What** | Lightweight execution engine - multi-model collaboration | +| **How** | Load tasks -> Execute -> Verify | +| **Output** | Code changes | +| **Done** | Tasks completed | +| **Failure & Recovery** | Simple retry mechanism | +| **Impact & Boundary** | Lightweight alternative | + +#### `workflow-tdd-plan` + +| Field | Description | +|-------|-------------| +| **Who** | Developer using TDD approach | +| **When** | Test-driven development | +| **What** | TDD workflow combining 6-phase planning with test-first | +| **How** | Plan tests -> Write tests -> Implement -> Verify | +| **Output** | Tests + implementation | +| **Done** | All tests passing | +| **Failure & Recovery** | Test failure iteration | +| **Impact & Boundary** | TDD-specific workflow | + +#### `workflow-test-fix` + +| Field | Description | +|-------|-------------| +| **Who** | Developer fixing test failures | +| **When** | Tests failing | +| **What** | Test-fix pipeline combining test runner with fix agent | +| **How** | Run tests -> Identify failures -> Fix -> Re-run | +| **Output** | Passing tests | +| **Done** | All tests pass | +| **Failure & Recovery** | Iterative fix loop | +| **Impact & Boundary** | Test fixing workflow | + +#### `workflow-multi-cli-plan` + +| Field | Description | +|-------|-------------| +| **Who** | Developer using multiple CLIs | +| **When** | Complex multi-perspective planning | +| **What** | Multi-CLI collaborative planning with ACE integration | +| **How** | Parallel CLI analysis -> Merge perspectives -> Generate plan | +| **Output** | Comprehensive plan from multiple models | +| **Done** | Merged plan complete | +| **Failure & Recovery** | Partial results merged | +| **Impact & Boundary** | Multi-model planning | + +#### `workflow-skill-designer` + +| Field | Description | +|-------|-------------| +| **Who** | Developer creating skills | +| **When** | Building new workflow skills | +| **What** | Meta-skill for designing orchestrator+phase skills | +| **How** | Design -> Template -> Generate skill files | +| **Output** | New skill SKILL.md + phases | +| **Done** | Skill ready for use | +| **Failure & Recovery** | Validation errors guide fixes | +| **Impact & Boundary** | Skill meta-creation | + +--- + +### Team Skills + +#### `team-coordinate` + +| Field | Description | +|-------|-------------| +| **Who** | Developer coordinating multi-agent work | +| **When** | Complex multi-role tasks | +| **What** | Universal team coordination with dynamic role generation | +| **How** | Analyze task -> Generate role-specs -> Dispatch workers -> Execute -> Deliver | +| **Output** | Coordinated multi-agent results | +| **Done** | Pipeline complete, artifacts delivered | +| **Failure & Recovery** | Role regeneration on capability gaps | +| **Impact & Boundary** | Universal team orchestrator | + +#### `team-edict` + +| Field | Description | +|-------|-------------| +| **Who** | Developer using Edict architecture | +| **When** | Large-scale multi-agent coordination | +| **What** | Three-Six Ministry multi-agent framework replicating Edict architecture | +| **How** | Ministry-based role assignment -> Task dispatch -> Report aggregation | +| **Output** | Comprehensive multi-role deliverables | +| **Done** | All ministries report complete | +| **Failure & Recovery** | Ministry-level retry | +| **Impact & Boundary** | Large-scale coordination | + +#### `team-planex` + +| Field | Description | +|-------|-------------| +| **Who** | Developer planning and executing | +| **When** | Plan-and-execute workflow | +| **What** | Unified team skill for plan-and-execute team | +| **How** | Plan -> Execute -> Verify | +| **Output** | Planned and executed work | +| **Done** | Plan executed completely | +| **Failure & Recovery** | Plan adjustment on failures | +| **Impact & Boundary** | Plan-execute team | + +#### `team-frontend` + +| Field | Description | +|-------|-------------| +| **Who** | Frontend developer | +| **When** | Frontend development work | +| **What** | Unified team skill for frontend development | +| **How** | Component design -> Implementation -> Testing | +| **Output** | Frontend components and features | +| **Done** | Frontend work complete | +| **Failure & Recovery** | Component-level retry | +| **Impact & Boundary** | Frontend-specific team | + +#### `team-frontend-debug` + +| Field | Description | +|-------|-------------| +| **Who** | Frontend developer debugging | +| **When** | Frontend issues | +| **What** | Frontend debugging team using Chrome DevTools MCP | +| **How** | Inspect -> Diagnose -> Fix -> Verify | +| **Output** | Fixed frontend issues | +| **Done** | Issues resolved | +| **Failure & Recovery** | Iterative debugging | +| **Impact & Boundary** | Frontend debugging specific | + +#### `team-testing` + +| Field | Description | +|-------|-------------| +| **Who** | Developer writing tests | +| **When** | Test generation needed | +| **What** | Unified team skill for testing team | +| **How** | Test planning -> Generation -> Execution | +| **Output** | Test suites | +| **Done** | Tests passing | +| **Failure & Recovery** | Test iteration | +| **Impact & Boundary** | Testing-specific team | + +#### `team-review` + +| Field | Description | +|-------|-------------| +| **Who** | Developer reviewing code | +| **When** | Code review needed | +| **What** | Unified team skill for code review | +| **How** | Multi-perspective review -> Feedback aggregation | +| **Output** | Review reports | +| **Done** | Review complete | +| **Failure & Recovery** | Partial review preserved | +| **Impact & Boundary** | Review-specific team | + +#### `team-quality-assurance` + +| Field | Description | +|-------|-------------| +| **Who** | QA engineer | +| **When** | Quality verification | +| **What** | Unified team skill for quality assurance | +| **How** | Quality checks -> Issue identification -> Remediation | +| **Output** | QA reports and fixes | +| **Done** | Quality verified | +| **Failure & Recovery** | Issue-driven iteration | +| **Impact & Boundary** | QA-specific team | + +#### `team-arch-opt` + +| Field | Description | +|-------|-------------| +| **Who** | Developer optimizing architecture | +| **When** | Architecture improvement | +| **What** | Unified team skill for architecture optimization | +| **How** | Analysis -> Optimization plan -> Implementation | +| **Output** | Improved architecture | +| **Done** | Optimization complete | +| **Failure & Recovery** | Gradual optimization | +| **Impact & Boundary** | Architecture-specific team | + +#### `team-perf-opt` + +| Field | Description | +|-------|-------------| +| **Who** | Developer optimizing performance | +| **When** | Performance issues | +| **What** | Unified team skill for performance optimization | +| **How** | Profiling -> Bottleneck identification -> Optimization | +| **Output** | Performance improvements | +| **Done** | Performance targets met | +| **Failure & Recovery** | Iterative optimization | +| **Impact & Boundary** | Performance-specific team | + +#### `team-tech-debt` + +| Field | Description | +|-------|-------------| +| **Who** | Developer addressing tech debt | +| **When** | Tech debt cleanup | +| **What** | Unified team skill for tech debt identification | +| **How** | Detection -> Prioritization -> Resolution | +| **Output** | Tech debt reduction | +| **Done** | Debt items resolved | +| **Failure & Recovery** | Prioritized resolution | +| **Impact & Boundary** | Tech debt specific | + +#### `team-ux-improve` + +| Field | Description | +|-------|-------------| +| **Who** | UX designer/developer | +| **When** | UX improvements | +| **What** | Unified team skill for UX improvement | +| **How** | UX audit -> Improvement plan -> Implementation | +| **Output** | UX improvements | +| **Done** | UX enhanced | +| **Failure & Recovery** | User feedback iteration | +| **Impact & Boundary** | UX-specific team | + +#### `team-uidesign` + +| Field | Description | +|-------|-------------| +| **Who** | UI designer | +| **When** | UI design work | +| **What** | Unified team skill for UI design team | +| **How** | Design system -> Components -> Prototypes | +| **Output** | UI designs and prototypes | +| **Done** | Design complete | +| **Failure & Recovery** | Design iteration | +| **Impact & Boundary** | UI design specific | + +#### `team-brainstorm` + +| Field | Description | +|-------|-------------| +| **Who** | Team brainstorming | +| **When** | Ideation sessions | +| **What** | Unified team skill for brainstorming team | +| **How** | Multi-perspective ideation -> Synthesis | +| **Output** | Brainstorm results | +| **Done** | Ideas documented | +| **Failure & Recovery** | Partial synthesis | +| **Impact & Boundary** | Brainstorming specific | + +#### `team-issue` + +| Field | Description | +|-------|-------------| +| **Who** | Developer managing issues | +| **When** | Issue resolution workflow | +| **What** | Unified team skill for issue resolution | +| **How** | Issue analysis -> Resolution -> Verification | +| **Output** | Resolved issues | +| **Done** | Issues closed | +| **Failure & Recovery** | Issue-specific handling | +| **Impact & Boundary** | Issue-specific team | + +#### `team-iterdev` + +| Field | Description | +|-------|-------------| +| **Who** | Developer in iterative mode | +| **When** | Iterative development | +| **What** | Unified team skill for iterative development | +| **How** | Iteration -> Feedback -> Refinement | +| **Output** | Iteratively improved code | +| **Done** | Iteration goals met | +| **Failure & Recovery** | Iteration adjustment | +| **Impact & Boundary** | Iterative development team | + +#### `team-roadmap-dev` + +| Field | Description | +|-------|-------------| +| **Who** | Developer on roadmap features | +| **When** | Roadmap-driven development | +| **What** | Unified team skill for roadmap-driven development | +| **How** | Roadmap parsing -> Feature development -> Tracking | +| **Output** | Roadmap feature completions | +| **Done** | Roadmap items complete | +| **Failure & Recovery** | Roadmap adjustment | +| **Impact & Boundary** | Roadmap-specific team | + +#### `team-ultra-analyze` + +| Field | Description | +|-------|-------------| +| **Who** | Developer needing deep analysis | +| **When** | Complex analysis required | +| **What** | Deep collaborative analysis team skill | +| **How** | Multi-angle analysis -> Deep dive -> Synthesis | +| **Output** | Comprehensive analysis reports | +| **Done** | Analysis complete | +| **Failure & Recovery** | Partial analysis preserved | +| **Impact & Boundary** | Deep analysis team | + +#### `team-executor` + +| Field | Description | +|-------|-------------| +| **Who** | Developer executing tasks | +| **When** | Task execution needed | +| **What** | Lightweight session execution skill | +| **How** | Load session -> Execute tasks -> Report | +| **Output** | Task execution results | +| **Done** | Session tasks complete | +| **Failure & Recovery** | Task-level retry | +| **Impact & Boundary** | Lightweight execution | + +#### `team-lifecycle-v4` + +| Field | Description | +|-------|-------------| +| **Who** | Developer managing full lifecycle | +| **When** | Complete feature lifecycle | +| **What** | Full lifecycle team skill with clean architecture | +| **How** | Plan -> Develop -> Test -> Deploy -> Monitor | +| **Output** | Complete feature lifecycle | +| **Done** | Feature fully delivered | +| **Failure & Recovery** | Lifecycle stage retry | +| **Impact & Boundary** | Full lifecycle management | + +#### `team-designer` + +| Field | Description | +|-------|-------------| +| **Who** | Developer designing teams | +| **When** | Creating new team skills | +| **What** | Meta-skill for generating team skills for different domains | +| **How** | Domain analysis -> Role definition -> Skill generation | +| **Output** | New team skill files | +| **Done** | Team skill ready | +| **Failure & Recovery** | Template validation | +| **Impact & Boundary** | Team skill meta-creation | + +--- + +### Utility Skills + +#### `brainstorm` + +| Field | Description | +|-------|-------------| +| **Who** | Developer exploring ideas | +| **When** | Starting new work, exploring solutions | +| **What** | Unified brainstorming with dual-mode (auto/single-role) and 9 available roles | +| **How** | Role selection -> Perspective analysis -> Idea synthesis | +| **Output** | Brainstorm report with actionables | +| **Done** | Ideas documented | +| **Failure & Recovery** | Partial analysis preserved | +| **Impact & Boundary** | Ideation support | + +#### `spec-generator` + +| Field | Description | +|-------|-------------| +| **Who** | Developer creating specifications | +| **When** | Starting new project or feature | +| **What** | 6-phase specification chain producing product brief, PRD, architecture, epics | +| **How** | Phase 1-6 chain: Brief -> PRD -> Architecture -> Epics -> Docs | +| **Output** | Complete specification documents | +| **Done** | All spec documents generated | +| **Failure & Recovery** | Phase-level retry | +| **Impact & Boundary** | Specification generation | + +#### `issue-manage` + +| Field | Description | +|-------|-------------| +| **Who** | Developer managing issues | +| **When** | Issue CRUD operations | +| **What** | Interactive menu-driven interface for issue CRUD via ccw issue CLI | +| **How** | Menu selection -> CLI execution -> Result display | +| **Output** | Issue management operations | +| **Done** | Operation complete | +| **Failure & Recovery** | CLI error handling | +| **Impact & Boundary** | Issue CRUD only | + +#### `review-code` + +| Field | Description | +|-------|-------------| +| **Who** | Developer reviewing code | +| **When** | Code review needed | +| **What** | Multi-dimensional code review with 6 dimensions: correctness, readability, performance, security, testing, architecture | +| **How** | Collect context -> Quick scan -> Deep review -> Generate report | +| **Output** | Structured review report | +| **Done** | Review complete | +| **Failure & Recovery** | Partial review preserved | +| **Impact & Boundary** | Code review only | + +#### `review-cycle` + +| Field | Description | +|-------|-------------| +| **Who** | Developer in review cycle | +| **When** | Iterative code review | +| **What** | Unified multi-dimensional code review with iterative cycle | +| **How** | Review -> Feedback -> Fix -> Re-review | +| **Output** | Iteratively improved code | +| **Done** | All issues addressed | +| **Failure & Recovery** | Cycle iteration | +| **Impact & Boundary** | Iterative review | + +#### `memory-capture` + +| Field | Description | +|-------|-------------| +| **Who** | Developer capturing knowledge | +| **When** | After important learnings | +| **What** | Unified memory capture with routing - session/tech/module context | +| **How** | Context detection -> Memory extraction -> Storage | +| **Output** | Captured memory entries | +| **Done** | Memory captured | +| **Failure & Recovery** | Partial capture preserved | +| **Impact & Boundary** | Memory capture only | + +#### `memory-manage` + +| Field | Description | +|-------|-------------| +| **Who** | Developer managing memory | +| **When** | Memory maintenance | +| **What** | Unified memory management - CLAUDE.md updates and memory cleanup | +| **How** | Load memory -> Organize -> Update CLAUDE.md | +| **Output** | Updated memory files | +| **Done** | Memory organized | +| **Failure & Recovery** | Backup before changes | +| **Impact & Boundary** | Memory management | + +#### `skill-tuning` + +| Field | Description | +|-------|-------------| +| **Who** | Developer improving skills | +| **When** | Skill optimization needed | +| **What** | Universal skill diagnosis and optimization | +| **How** | Diagnose -> Optimize -> Validate | +| **Output** | Improved skill files | +| **Done** | Skill optimized | +| **Failure & Recovery** | Incremental improvement | +| **Impact & Boundary** | Skill optimization | + +#### `skill-simplify` + +| Field | Description | +|-------|-------------| +| **Who** | Developer simplifying skills | +| **When** | Skill too complex | +| **What** | SKILL.md simplification with functional preservation | +| **How** | Analyze -> Simplify -> Verify functionality | +| **Output** | Simplified skill file | +| **Done** | Skill simplified | +| **Failure & Recovery** | Functional verification | +| **Impact & Boundary** | Skill simplification | + +#### `skill-generator` + +| Field | Description | +|-------|-------------| +| **Who** | Developer creating skills | +| **When** | New skill needed | +| **What** | Meta-skill for creating new Claude Code skills | +| **How** | Requirements -> Template -> Skill generation | +| **Output** | New skill SKILL.md + supporting files | +| **Done** | Skill ready for use | +| **Failure & Recovery** | Template validation | +| **Impact & Boundary** | Skill creation | + +#### `command-generator` + +| Field | Description | +|-------|-------------| +| **Who** | Developer creating commands | +| **When** | New slash command needed | +| **What** | Command file generator - 5 phase workflow | +| **How** | Requirements -> Template -> Command generation | +| **Output** | New command .md file | +| **Done** | Command ready for use | +| **Failure & Recovery** | Schema validation | +| **Impact & Boundary** | Command creation | + +#### `ccw-help` + +| Field | Description | +|-------|-------------| +| **Who** | Developer seeking help | +| **When** | Learning CCW system | +| **What** | CCW command help system - search, browse, documentation | +| **How** | Query -> Search -> Display help | +| **Output** | Help information | +| **Done** | Help displayed | +| **Failure & Recovery** | Fuzzy matching | +| **Impact & Boundary** | Help system only | + +--- + +## Appendix A: Quick Reference Table + +### Commands by Category + +| Category | Commands | Count | +|----------|----------|-------| +| Core | ccw, ccw-coordinator, flow-create | 3 | +| DDD | scan, index-build, plan, execute, doc-generate, doc-refresh, sync, update, auto | 9 | +| Issue | new, discover, discover-by-prompt, from-brainstorm, plan, queue, execute, convert-to-plan | 8 | +| IDAW | status, add, run, run-coordinate, resume | 5 | +| Workflow Session | start, list, sync, resume, complete | 5 | +| Workflow Spec | setup, add | 2 | +| Workflow Core | clean, debug-with-file, analyze-with-file, brainstorm-with-file, collaborative-plan-with-file | 5 | +| Workflow Cycle | integration-test-cycle, refactor-cycle, roadmap-with-file, unified-execute-with-file | 4 | +| Workflow UI Design | explore-auto, imitate-auto, generate, style-extract, layout-extract, animation-extract, codify-style, import-from-code, design-sync, reference-page-generator | 10 | +| Memory | prepare, style-skill-memory | 2 | +| CLI | codex-review, cli-init | 2 | +| **Total Commands** | | **55** | + +### Skills by Category + +| Category | Skills | Count | +|----------|--------|-------| +| Workflow | workflow-plan, workflow-execute, workflow-lite-plan, workflow-lite-execute, workflow-tdd-plan, workflow-test-fix, workflow-multi-cli-plan, workflow-skill-designer | 8 | +| Team | team-coordinate, team-edict, team-planex, team-frontend, team-frontend-debug, team-testing, team-review, team-quality-assurance, team-arch-opt, team-perf-opt, team-tech-debt, team-ux-improve, team-uidesign, team-brainstorm, team-issue, team-iterdev, team-roadmap-dev, team-ultra-analyze, team-executor, team-lifecycle-v4, team-designer | 21 | +| Utility | brainstorm, spec-generator, issue-manage, review-code, review-cycle, memory-capture, memory-manage, skill-tuning, skill-simplify, skill-generator, command-generator, ccw-help | 12 | +| **Total Skills** | | **41** | + +--- + +## Appendix B: Command Chain Examples + +### Document-Driven Development Flow + +``` +/ddd:scan # Code-first: scan existing codebase + -> /ddd:plan "add feature" # Plan with doc context + -> /ddd:execute # Execute with doc awareness + -> /ddd:sync # Sync changes to docs +``` + +### Spec-First Development Flow + +``` +Skill: spec-generator # Generate specifications + -> /ddd:index-build # Build index from specs + -> /ddd:plan # Plan with spec context + -> /ddd:execute # Execute + -> /ddd:doc-refresh # Refresh affected docs +``` + +### Issue Resolution Flow + +``` +/issue:new "bug description" # Create issue + -> /issue:plan ISS-001 # Generate solution + -> /issue:queue ISS-001 # Add to queue + -> /issue:execute # Execute queue +``` + +### Team Coordination Flow + +``` +Skill: team-coordinate "implement auth" + -> Dynamic role generation + -> Parallel worker execution + -> Result aggregation + -> Completion action +``` + +### UI Design Flow + +``` +/workflow:ui-design:explore-auto --input "modern dashboard" + -> /workflow:ui-design:style-extract # Extract styles + -> /workflow:ui-design:layout-extract # Extract layouts + -> /workflow:ui-design:generate # Assemble prototypes +``` + +### Integration Test Flow + +``` +/workflow:integration-test-cycle "test auth flow" + -> Generate tests + -> Execute tests + -> Reflect on failures + -> Iterate until pass + -> Reflection log +``` + +### Refactoring Flow + +``` +/workflow:refactor-cycle "src/auth" + -> Debt discovery + -> Prioritization + -> Per-item refactor + -> Validation + -> Reflection +``` + +--- + +## Summary + +| Metric | Count | +|--------|-------| +| **Total Commands** | 55 | +| **Total Skills** | 41 | +| **DDD Commands** | 9 | +| **Issue Commands** | 8 | +| **Team Skills** | 21 | +| **Workflow Skills** | 8 | + +--- + +*End of Reference Manual* diff --git a/docs/reference/commands-skills.md b/docs/reference/commands-skills.md index 9b5be5a3..4bb9b11c 100644 --- a/docs/reference/commands-skills.md +++ b/docs/reference/commands-skills.md @@ -1,736 +1,1321 @@ -# Commands & Skills Reference +# CCW Commands & Skills Reference Manual -> **Quick Reference**: Complete catalog of Claude commands, skills, and Codex capabilities +> Generated: 2026-03-08 | Project: Claude Code Workspace (CCW) + +This reference manual provides quick lookup for all slash commands and skills in the CCW system. --- -## Quick Reference Table +## Table of Contents -### Commands Quick Reference - -| Category | Command | Description | Arguments | -|----------|---------|-------------|-----------| -| **Orchestrator** | `/ccw` | Main workflow orchestrator | `"task description"` | -| **Orchestrator** | `/ccw-coordinator` | Command orchestration tool | `[task description]` | -| **Session** | `/workflow:session:start` | Start workflow session | `[--type] [--auto|--new] [task]` | -| **Session** | `/workflow:session:resume` | Resume paused session | - | -| **Session** | `/workflow:session:complete` | Complete active session | `[-y] [--detailed]` | -| **Session** | `/workflow:session:list` | List all sessions | - | -| **Session** | `/workflow:session:sync` | Sync session to specs | `[-y] ["what was done"]` | -| **Session** | `/workflow:session:solidify` | Crystallize learnings | `[--type] [--category] "rule"` | -| **Issue** | `/issue:new` | Create structured issue | ` [--priority 1-5]` | -| **Issue** | `/issue:discover` | Discover potential issues | ` [--perspectives=...]` | -| **Issue** | `/issue:plan` | Plan issue resolution | `--all-pending ` | -| **Issue** | `/issue:queue` | Form execution queue | `[--queues ] [--issue ]` | -| **Issue** | `/issue:execute` | Execute queue | `--queue [--worktree]` | -| **IDAW** | `/idaw:run` | IDAW orchestrator | `[--task ] [--dry-run]` | -| **IDAW** | `/idaw:add` | Add task to queue | - | -| **IDAW** | `/idaw:resume` | Resume IDAW session | - | -| **IDAW** | `/idaw:status` | Show queue status | - | -| **With-File** | `/workflow:brainstorm-with-file` | Interactive brainstorming | `[-c] [-m creative|structured] "topic"` | -| **With-File** | `/workflow:analyze-with-file` | Collaborative analysis | `[-c] "topic"` | -| **With-File** | `/workflow:debug-with-file` | Hypothesis-driven debugging | `"bug description"` | -| **With-File** | `/workflow:collaborative-plan-with-file` | Multi-agent planning | - | -| **With-File** | `/workflow:roadmap-with-file` | Strategic roadmap | - | -| **Cycle** | `/workflow:integration-test-cycle` | Integration test cycle | - | -| **Cycle** | `/workflow:refactor-cycle` | Refactor cycle | - | -| **CLI** | `/cli:codex-review` | Codex code review | `[--uncommitted|--base|--commit]` | -| **CLI** | `/cli:cli-init` | Initialize CLI config | - | -| **Memory** | `/memory:prepare` | Prepare memory context | - | -| **Memory** | `/memory:style-skill-memory` | Style/skill memory | - | - -### Skills Quick Reference - -| Category | Skill | Internal Pipeline | Use Case | -|----------|-------|-------------------|----------| -| **Workflow** | workflow-lite-plan | explore → plan → confirm → execute | Quick features, bug fixes | -| **Workflow** | workflow-plan | session → context → convention → gen → verify/replan | Complex feature planning | -| **Workflow** | workflow-execute | session discovery → task processing → commit | Execute pre-generated plans | -| **Workflow** | workflow-tdd-plan | 6-phase TDD plan → verify | TDD development | -| **Workflow** | workflow-test-fix | session → context → analysis → gen → cycle | Test generation and fixes | -| **Workflow** | workflow-multi-cli-plan | ACE context → CLI discussion → plan → execute | Multi-perspective planning | -| **Workflow** | workflow-skill-designer | - | Create new skills | -| **Team** | team-lifecycle | spec pipeline → impl pipeline | Full lifecycle | -| **Team** | team-planex | planner wave → executor wave | Issue batch execution | -| **Team** | team-arch-opt | architecture analysis → optimization | Architecture optimization | -| **Utility** | brainstorm | framework → parallel analysis → synthesis | Multi-perspective ideation | -| **Utility** | review-cycle | discovery → analysis → aggregation → deep-dive | Code review | -| **Utility** | spec-generator | study → brief → PRD → architecture → epics | Specification packages | +- [Section 1: Slash Commands](#section-1-slash-commands) + - [Core](#core) + - [DDD (Document-Driven Development)](#ddd-document-driven-development) + - [Issue](#issue) + - [IDAW (Iterative Development Automation Workflow)](#idaw-iterative-development-automation-workflow) + - [Workflow](#workflow) + - [Memory](#memory) + - [CLI](#cli) +- [Section 2: Skills](#section-2-skills) + - [Workflow Skills](#workflow-skills) + - [Team Skills](#team-skills) + - [Utility Skills](#utility-skills) +- [Appendix A: Quick Reference Table](#appendix-a-quick-reference-table) +- [Appendix B: Command Chain Examples](#appendix-b-command-chain-examples) --- -## 1. Main Orchestrator Commands +## Section 1: Slash Commands -### /ccw +### Core -**Description**: Main workflow orchestrator - analyze intent, select workflow, execute command chain in main process +#### `/ccw` -**Arguments**: `"task description"` - -**Category**: orchestrator - -**5-Phase Workflow**: -1. Phase 1: Analyze Intent (detect task type, complexity, clarity) -2. Phase 1.5: Requirement Clarification (if clarity < 2) -3. Phase 2: Select Workflow & Build Command Chain -4. Phase 3: User Confirmation -5. Phase 4: Setup TODO Tracking & Status File -6. Phase 5: Execute Command Chain - -**Skill Mapping**: - -| Skill | Internal Pipeline | -|-------|-------------------| -| workflow-lite-plan | explore → plan → confirm → execute | -| workflow-plan | session → context → convention → gen → verify/replan | -| workflow-execute | session discovery → task processing → commit | -| workflow-tdd-plan | 6-phase TDD plan → verify | -| workflow-test-fix | session → context → analysis → gen → cycle | -| workflow-multi-cli-plan | ACE context → CLI discussion → plan → execute | -| review-cycle | session/module review → fix orchestration | -| brainstorm | auto/single-role → artifacts → analysis → synthesis | -| spec-generator | product-brief → PRD → architecture → epics | - -**Auto Mode**: `-y` or `--yes` flag skips confirmations, propagates to all skills - ---- - -### /ccw-coordinator - -**Description**: Command orchestration tool - analyze requirements, recommend chain, execute sequentially with state persistence - -**Arguments**: `[task description]` - -**Category**: orchestrator - -**3-Phase Workflow**: -1. Phase 1: Analyze Requirements -2. Phase 2: Discover Commands & Recommend Chain -3. Phase 3: Execute Sequential Command Chain - -**Minimum Execution Units**: - -| Unit | Commands | Purpose | -|------|----------|---------| -| Quick Implementation | lite-plan (plan → execute) | Lightweight plan and execution | -| Multi-CLI Planning | multi-cli-plan | Multi-perspective planning | -| Bug Fix | lite-plan --bugfix | Bug diagnosis and fix | -| Full Planning + Execution | plan → execute | Detailed planning | -| Verified Planning + Execution | plan → plan-verify → execute | Planning with verification | -| TDD Planning + Execution | tdd-plan → execute | TDD workflow | -| Issue Workflow | discover → plan → queue → execute | Complete issue lifecycle | - ---- - -### /flow-create - -**Description**: Flow template generator for meta-skill/flow-coordinator - -**Arguments**: `[template-name] [--output ]` - -**Category**: utility - -**Execution Flow**: -1. Phase 1: Template Design (name + description + level) -2. Phase 2: Step Definition (command category → specific command → execution unit → mode) -3. Phase 3: Generate JSON - ---- - -## 2. Workflow Session Commands - -### /workflow:session:start - -**Description**: Discover existing sessions or start new workflow session with intelligent session management and conflict detection - -**Arguments**: `[--type ] [--auto|--new] [task description]` - -**Category**: session-management - -**Session Types**: - -| Type | Description | Default For | -|------|-------------|-------------| -| workflow | Standard implementation | workflow-plan skill | -| review | Code review sessions | review-cycle skill | -| tdd | TDD-based development | workflow-tdd-plan skill | -| test | Test generation/fix | workflow-test-fix skill | -| docs | Documentation sessions | memory-manage skill | - -**Modes**: -- **Discovery Mode** (default): List active sessions, prompt user -- **Auto Mode** (`--auto`): Intelligent session selection -- **Force New Mode** (`--new`): Create new session - ---- - -### /workflow:session:resume - -**Description**: Resume the most recently paused workflow session with automatic session discovery and status update - -**Category**: session-management - ---- - -### /workflow:session:complete - -**Description**: Mark active workflow session as complete, archive with lessons learned, update manifest, remove active flag - -**Arguments**: `[-y|--yes] [--detailed]` - -**Category**: session-management - -**Execution Phases**: -1. Find Session -2. Generate Manifest Entry -3. Atomic Commit (mv to archives) -4. Auto-Sync Project State - ---- - -### /workflow:session:list - -**Description**: List all workflow sessions with status filtering, shows session metadata and progress information - -**Category**: session-management - ---- - -### /workflow:session:sync - -**Description**: Quick-sync session work to specs/*.md and project-tech - -**Arguments**: `[-y|--yes] ["what was done"]` - -**Category**: session-management - -**Process**: -1. Gather Context (git diff, session, summary) -2. Extract Updates (guidelines, tech) -3. Preview & Confirm -4. Write both files - ---- - -### /workflow:session:solidify - -**Description**: Crystallize session learnings and user-defined constraints into permanent project guidelines, or compress recent memories - -**Arguments**: `[-y|--yes] [--type ] [--category ] [--limit ] "rule or insight"` - -**Category**: session-management - -**Type Categories**: - -| Type | Subcategories | -|------|---------------| -| convention | coding_style, naming_patterns, file_structure, documentation | -| constraint | architecture, tech_stack, performance, security | -| learning | architecture, performance, security, testing, process, other | -| compress | (operates on core memories) | - ---- - -## 3. Issue Workflow Commands - -### /issue:new - -**Description**: Create structured issue from GitHub URL or text description - -**Arguments**: `[-y|--yes] [--priority 1-5]` - -**Category**: issue - -**Execution Flow**: -1. Input Analysis & Clarity Detection -2. Data Extraction (GitHub or Text) -3. Lightweight Context Hint (ACE for medium clarity) -4. Conditional Clarification -5. GitHub Publishing Decision -6. Create Issue - ---- - -### /issue:discover - -**Description**: Discover potential issues from multiple perspectives using CLI explore. Supports Exa external research for security and best-practices perspectives. - -**Arguments**: `[-y|--yes] [--perspectives=bug,ux,...] [--external]` - -**Category**: issue - -**Available Perspectives**: - -| Perspective | Focus | Categories | -|-------------|-------|------------| -| bug | Potential Bugs | edge-case, null-check, resource-leak, race-condition | -| ux | User Experience | error-message, loading-state, feedback, accessibility | -| test | Test Coverage | missing-test, edge-case-test, integration-gap | -| quality | Code Quality | complexity, duplication, naming, documentation | -| security | Security Issues | injection, auth, encryption, input-validation | -| performance | Performance | n-plus-one, memory-usage, caching, algorithm | -| maintainability | Maintainability | coupling, cohesion, tech-debt, extensibility | -| best-practices | Best Practices | convention, pattern, framework-usage, anti-pattern | - ---- - -### /issue:plan - -**Description**: Batch plan issue resolution using issue-plan-agent (explore + plan closed-loop) - -**Arguments**: `[-y|--yes] --all-pending [,,...] [--batch-size 3]` - -**Category**: issue - -**Execution Process**: -1. Issue Loading & Intelligent Grouping -2. Unified Explore + Plan (issue-plan-agent) -3. Solution Registration & Binding -4. Summary - ---- - -### /issue:queue - -**Description**: Form execution queue from bound solutions using issue-queue-agent (solution-level) - -**Arguments**: `[-y|--yes] [--queues ] [--issue ]` - -**Category**: issue - -**Core Capabilities**: -- Agent-driven ordering logic -- Solution-level granularity -- Conflict clarification -- Parallel/Sequential group assignment - ---- - -### /issue:execute - -**Description**: Execute queue with DAG-based parallel orchestration (one commit per solution) - -**Arguments**: `[-y|--yes] --queue [--worktree []]` - -**Category**: issue - -**Execution Flow**: -1. Validate Queue ID (REQUIRED) -2. Get DAG & User Selection -3. Dispatch Parallel Batch (DAG-driven) -4. Next Batch (repeat) -5. Worktree Completion - -**Recommended Executor**: Codex (2hr timeout, full write access) - ---- - -### /issue:from-brainstorm - -**Description**: Convert brainstorm session ideas into issue with executable solution for parallel-dev-cycle - -**Arguments**: `SESSION="" [--idea=] [--auto] [-y|--yes]` - -**Category**: issue - -**Execution Flow**: -1. Session Loading -2. Idea Selection -3. Enrich Issue Context -4. Create Issue -5. Generate Solution Tasks -6. Bind Solution - ---- - -## 4. IDAW Commands - -### /idaw:run - -**Description**: IDAW orchestrator - execute task skill chains serially with git checkpoints - -**Arguments**: `[-y|--yes] [--task [,,...]] [--dry-run]` - -**Category**: idaw - -**Skill Chain Mapping**: - -| Task Type | Skill Chain | -|-----------|-------------| -| bugfix | workflow-lite-plan → workflow-test-fix | -| bugfix-hotfix | workflow-lite-plan | -| feature | workflow-lite-plan → workflow-test-fix | -| feature-complex | workflow-plan → workflow-execute → workflow-test-fix | -| refactor | workflow:refactor-cycle | -| tdd | workflow-tdd-plan → workflow-execute | -| test | workflow-test-fix | -| test-fix | workflow-test-fix | -| review | review-cycle | -| docs | workflow-lite-plan | - -**6-Phase Execution**: -1. Load Tasks -2. Session Setup -3. Startup Protocol -4. Main Loop (serial, one task at a time) -5. Checkpoint (per task) -6. Report - ---- - -### /idaw:add - -**Description**: Add task to IDAW queue with auto-inferred task type and skill chain - -**Category**: idaw - ---- - -### /idaw:resume - -**Description**: Resume IDAW session with crash recovery - -**Category**: idaw - ---- - -### /idaw:status - -**Description**: Show IDAW queue status - -**Category**: idaw - ---- - -### /idaw:run-coordinate - -**Description**: Multi-agent IDAW execution with parallel task coordination - -**Category**: idaw - ---- - -## 5. With-File Workflows - -### /workflow:brainstorm-with-file - -**Description**: Interactive brainstorming with multi-CLI collaboration, idea expansion, and documented thought evolution - -**Arguments**: `[-y|--yes] [-c|--continue] [-m|--mode creative|structured] "idea or topic"` - -**Category**: with-file - -**Output Directory**: `.workflow/.brainstorm/{session-id}/` - -**4-Phase Workflow**: -1. Phase 1: Seed Understanding (parse topic, select roles, expand vectors) -2. Phase 2: Divergent Exploration (cli-explore-agent + Multi-CLI perspectives) -3. Phase 3: Interactive Refinement (multi-round) -4. Phase 4: Convergence & Crystallization - -**Output Artifacts**: -- `brainstorm.md` - Complete thought evolution timeline -- `exploration-codebase.json` - Codebase context -- `perspectives.json` - Multi-CLI findings -- `synthesis.json` - Final synthesis - ---- - -### /workflow:analyze-with-file - -**Description**: Interactive collaborative analysis with documented discussions, CLI-assisted exploration, and evolving understanding - -**Arguments**: `[-y|--yes] [-c|--continue] "topic or question"` - -**Category**: with-file - -**Output Directory**: `.workflow/.analysis/{session-id}/` - -**4-Phase Workflow**: -1. Phase 1: Topic Understanding -2. Phase 2: CLI Exploration (cli-explore-agent + perspectives) -3. Phase 3: Interactive Discussion (multi-round) -4. Phase 4: Synthesis & Conclusion - -**Decision Recording Protocol**: Must record direction choices, key findings, assumption changes, user feedback - ---- - -### /workflow:debug-with-file - -**Description**: Interactive hypothesis-driven debugging with documented exploration, understanding evolution, and Gemini-assisted correction - -**Arguments**: `[-y|--yes] "bug description or error message"` - -**Category**: with-file - -**Output Directory**: `.workflow/.debug/{session-id}/` - -**Core Workflow**: Explore → Document → Log → Analyze → Correct Understanding → Fix → Verify - -**Output Artifacts**: -- `debug.log` - NDJSON execution evidence -- `understanding.md` - Exploration timeline + consolidated understanding -- `hypotheses.json` - Hypothesis history with verdicts - ---- - -### /workflow:collaborative-plan-with-file - -**Description**: Multi-agent collaborative planning with Plan Note shared doc - -**Category**: with-file - ---- - -### /workflow:roadmap-with-file - -**Description**: Strategic requirement roadmap → issue creation → execution-plan.json - -**Category**: with-file - ---- - -### /workflow:unified-execute-with-file - -**Description**: Universal execution engine - consumes plan output from collaborative-plan, roadmap, brainstorm - -**Category**: with-file - ---- - -## 6. Cycle Workflows - -### /workflow:integration-test-cycle - -**Description**: Self-iterating integration test with reflection - explore → test dev → test-fix cycle → reflection - -**Category**: cycle - -**Output Directory**: `.workflow/.test-cycle/` - ---- - -### /workflow:refactor-cycle - -**Description**: Tech debt discovery → prioritize → execute → validate - -**Category**: cycle - -**Output Directory**: `.workflow/.refactor-cycle/` - ---- - -## 7. CLI Commands - -### /cli:codex-review - -**Description**: Interactive code review using Codex CLI via ccw endpoint with configurable review target, model, and custom instructions - -**Arguments**: `[--uncommitted|--base |--commit ] [--model ] [--title ] [prompt]` - -**Category**: cli - -**Review Targets**: - -| Target | Flag | Description | -|--------|------|-------------| -| Uncommitted changes | `--uncommitted` | Review staged, unstaged, and untracked changes | -| Compare to branch | `--base <BRANCH>` | Review changes against base branch | -| Specific commit | `--commit <SHA>` | Review changes introduced by a commit | - -**Focus Areas**: General review, Security focus, Performance focus, Code quality - -**Important**: Target flags and prompt are mutually exclusive - ---- - -### /cli:cli-init - -**Description**: Initialize CLI configuration for ccw endpoint - -**Category**: cli - ---- - -## 8. Memory Commands - -### /memory:prepare - -**Description**: Prepare memory context for session - -**Category**: memory - ---- - -### /memory:style-skill-memory - -**Description**: Style and skill memory management - -**Category**: memory - ---- - -## 9. Team Skills - -### Team Lifecycle Skills - -| Skill | Description | +| Field | Description | |-------|-------------| -| team-lifecycle | Full team lifecycle with role-spec-driven worker agents | -| team-planex | Planner + executor wave pipeline (for large issue batches or roadmap outputs) | -| team-coordinate | Team coordination and orchestration | -| team-executor | Task execution with worker agents | -| team-arch-opt | Architecture optimization skill | +| **Who** | Developer starting any task | +| **When** | Entry point for workflow orchestration | +| **What** | Main workflow orchestrator that analyzes intent, dispatches to appropriate skill chain. Example: `/ccw "implement user authentication"` | +| **How** | Parses intent -> Selects skill chain -> Executes orchestrator | +| **Output** | Delegates to workflow-plan, issue-manage, or other skills | +| **Done** | Appropriate skill completes execution | +| **Failure & Recovery** | Fallback to manual skill selection if intent unclear | +| **Impact & Boundary** | Project-wide orchestration entry point | -### Team Domain Skills +#### `/ccw-coordinator` -| Skill | Description | +| Field | Description | |-------|-------------| -| team-brainstorm | Multi-perspective brainstorming | -| team-review | Code review workflow | -| team-testing | Testing workflow | -| team-frontend | Frontend development workflow | -| team-issue | Issue management workflow | -| team-iterdev | Iterative development workflow | -| team-perf-opt | Performance optimization workflow | -| team-quality-assurance | QA workflow | -| team-roadmap-dev | Roadmap development workflow | -| team-tech-debt | Technical debt management | -| team-uidesign | UI design workflow | -| team-ultra-analyze | Deep analysis workflow | +| **Who** | System needing command orchestration | +| **When** | Multi-command coordination required | +| **What** | Command orchestration tool that analyzes requirements and dispatches commands. Example: `/ccw-coordinator "review and fix auth module"` | +| **How** | Requirement analysis -> Command selection -> Sequential execution | +| **Output** | Coordinated command execution results | +| **Done** | All dispatched commands complete | +| **Failure & Recovery** | Partial results preserved, user notified of failures | +| **Impact & Boundary** | Cross-command coordination | ---- +#### `/flow-create` -## 10. Workflow Skills - -| Skill | Internal Pipeline | Description | -|-------|-------------------|-------------| -| workflow-lite-plan | explore → plan → confirm → execute | Lightweight merged-mode planning | -| workflow-plan | session → context → convention → gen → verify/replan | Full planning with architecture design | -| workflow-execute | session discovery → task processing → commit | Execute from planning session | -| workflow-tdd-plan | 6-phase TDD plan → verify | TDD workflow planning | -| workflow-test-fix | session → context → analysis → gen → cycle | Test generation and fix cycle | -| workflow-multi-cli-plan | ACE context → CLI discussion → plan → execute | Multi-CLI collaborative planning | -| workflow-skill-designer | - | Workflow skill design and generation | - ---- - -## 11. Utility Skills - -| Skill | Description | +| Field | Description | |-------|-------------| -| brainstorm | Unified brainstorming skill (auto-parallel + role analysis) | -| review-code | Code review skill | -| review-cycle | Session/module review → fix orchestration | -| spec-generator | Product-brief → PRD → architecture → epics | -| skill-generator | Generate new skills | -| skill-tuning | Tune existing skills | -| command-generator | Generate new commands | -| memory-capture | Capture session memories | -| memory-manage | Manage stored memories | -| issue-manage | Issue management utility | -| ccw-help | CCW help and documentation | +| **Who** | Developer creating reusable workflow templates | +| **When** | Need to document and share workflow patterns | +| **What** | Flow template generator for creating reusable command chains. Example: `/flow-create "auth-feature-flow"` | +| **How** | Template definition -> Parameter extraction -> Flow file generation | +| **Output** | Flow template file in `.claude/flows/` | +| **Done** | Template file created and validated | +| **Failure & Recovery** | Validation errors show specific issues | +| **Impact & Boundary** | Workflow template creation only | --- -## 12. Codex Capabilities +### DDD (Document-Driven Development) -### Codex Review Mode +#### `/ddd:scan` -**Command**: `ccw cli --tool codex --mode review [OPTIONS]` +| Field | Description | +|-------|-------------| +| **Who** | Developer onboarding to existing project without specs | +| **When** | Starting doc-driven workflow on legacy codebase | +| **What** | Scans codebase to build doc-index by reverse-engineering structure. Example: `/ddd:scan -y "existing project"` | +| **How** | Framework detection -> Component discovery -> Feature inference -> Requirement extraction -> doc-index.json | +| **Output** | `.workflow/.doc-index/doc-index.json` + feature-maps/ + tech-registry/ | +| **Done** | doc-index.json created with components, features, IREQ entries | +| **Failure & Recovery** | Graceful degradation if DeepWiki unavailable | +| **Impact & Boundary** | Code-first entry point, can upgrade to spec-first later | -| Option | Description | -|--------|-------------| -| `[PROMPT]` | Custom review instructions (positional, no target flags) | -| `-c model=<model>` | Override model via config | -| `--uncommitted` | Review staged, unstaged, and untracked changes | -| `--base <BRANCH>` | Review changes against base branch | -| `--commit <SHA>` | Review changes introduced by a commit | -| `--title <TITLE>` | Optional commit title for review summary | +#### `/ddd:index-build` -**Available Models**: -- Default: gpt-5.2 -- o3: OpenAI o3 reasoning model -- gpt-4.1: GPT-4.1 model -- o4-mini: OpenAI o4-mini (faster) +| Field | Description | +|-------|-------------| +| **Who** | Developer with existing spec-generator outputs | +| **When** | Building index from REQ, ADR, EPIC documents | +| **What** | Builds doc-index from spec outputs and maps entities to code. Example: `/ddd:index-build --spec SPEC-auth-2026-03-08` | +| **How** | Parse specs -> Codebase mapping via CLI -> Feature grouping -> doc-index.json | +| **Output** | `.workflow/.doc-index/doc-index.json` with spec-first traceability | +| **Done** | All spec entities linked to code components | +| **Failure & Recovery** | Orphan components flagged for review | +| **Impact & Boundary** | Spec-first entry point, merges with existing code-first index | -**Constraints**: -- Target flags (`--uncommitted`, `--base`, `--commit`) **cannot** be used with positional `[PROMPT]` -- Custom prompts only supported WITHOUT target flags (reviews uncommitted by default) +#### `/ddd:plan` -### Codex Integration Points +| Field | Description | +|-------|-------------| +| **Who** | Developer planning document-driven task | +| **When** | Before any development task in DDD workflow | +| **What** | Queries doc-index, explores codebase with doc-aware angles, produces plan.json. Example: `/ddd:plan -y "add rate limiting"` | +| **How** | Doc-index query -> Guided exploration -> Clarification -> Task planning -> Handoff | +| **Output** | `.workflow/.doc-index/planning/{session}/plan.json` + TASK-*.json | +| **Done** | Plan with doc_context traceability generated | +| **Failure & Recovery** | Schema version mismatch warns but continues | +| **Impact & Boundary** | Requires existing doc-index.json | -| Integration Point | Description | -|-------------------|-------------| -| CLI endpoint | `ccw cli --tool codex --mode <analysis\|write\|review>` | -| Multi-CLI planning | Pragmatic perspective in workflow-multi-cli-plan | -| Code review | `/cli:codex-review` command | -| Issue execution | Recommended executor for `/issue:execute` | -| Devil's advocate | Challenge mode in brainstorm refinement | +#### `/ddd:execute` -### Codex Mode Summary +| Field | Description | +|-------|-------------| +| **Who** | Developer executing document-aware tasks | +| **When** | After /ddd:plan produces plan.json | +| **What** | Document-aware execution engine with doc-context loading. Example: `/ddd:execute --in-memory` | +| **How** | Load plan -> Read doc-context -> Execute task -> Update doc-index | +| **Output** | Code changes + updated doc-index traceability | +| **Done** | All tasks executed, doc-index updated | +| **Failure & Recovery** | Task failures logged, recovery options presented | +| **Impact & Boundary** | Requires plan.json from /ddd:plan | -| Mode | Permission | Use Case | -|------|------------|----------| -| analysis | Read-only | Code analysis, architecture review | -| write | Full access | Implementation, file modifications | -| review | Read-only output | Git-aware code review | +#### `/ddd:doc-generate` + +| Field | Description | +|-------|-------------| +| **Who** | Developer regenerating documentation | +| **When** | After doc-index built or needs refresh | +| **What** | Generates full document tree from doc-index.json. Example: `/ddd:doc-generate --force --layer all` | +| **How** | Layer 3 (components) -> Layer 2 (features) -> Layer 1 (indexes) | +| **Output** | tech-registry/*.md, feature-maps/*.md, README.md, ARCHITECTURE.md | +| **Done** | All layers generated, SCHEMA.md created | +| **Failure & Recovery** | Existing docs warning, --force to overwrite | +| **Impact & Boundary** | Read-only from doc-index, generates MD files | + +#### `/ddd:doc-refresh` + +| Field | Description | +|-------|-------------| +| **Who** | Developer after incremental code changes | +| **When** | Code changed, need targeted doc updates | +| **What** | Incrementally updates affected documents after code changes. Example: `/ddd:doc-refresh -y` | +| **How** | Detect changed files -> Find affected docs -> Regenerate only affected | +| **Output** | Updated subset of documentation files | +| **Done** | Affected docs updated, unchanged docs preserved | +| **Failure & Recovery** | Falls back to full regeneration if detection fails | +| **Impact & Boundary** | Incremental update, more efficient than full regenerate | + +#### `/ddd:sync` + +| Field | Description | +|-------|-------------| +| **Who** | Developer after task completion | +| **When** | Post-task synchronization to update index | +| **What** | Post-task synchronization updates doc-index with completed work. Example: `/ddd:sync -y "auth feature complete"` | +| **How** | Detect changes -> Update components -> Update requirements status -> Add action log | +| **Output** | Updated doc-index.json with action entries | +| **Done** | Index reflects current codebase state | +| **Failure & Recovery** | Merge conflicts resolved automatically | +| **Impact & Boundary** | Post-execution sync only | + +#### `/ddd:update` + +| Field | Description | +|-------|-------------| +| **Who** | Developer maintaining doc-index | +| **When** | Detecting drift between code and docs | +| **What** | Incremental index update detecting code changes. Example: `/ddd:update --scope src/auth` | +| **How** | File hash comparison -> Detect changes -> Update affected entries | +| **Output** | Updated doc-index.json entries | +| **Done** | Index entries match current code | +| **Failure & Recovery** | Unchanged files skipped | +| **Impact & Boundary** | Lightweight incremental update | + +#### `/ddd:auto` + +| Field | Description | +|-------|-------------| +| **Who** | Developer wanting full automation | +| **When** | Quick feature implementation with docs | +| **What** | Chain command for automated DDD workflow. Example: `/ddd:auto -y "implement search feature"` | +| **How** | plan -> execute -> sync in single command | +| **Output** | Complete implementation + updated docs | +| **Done** | Feature implemented and documented | +| **Failure & Recovery** | Stops at first failing phase | +| **Impact & Boundary** | Full automation, less control | --- -## Summary Statistics +### Issue -| Category | Count | -|----------|-------| -| Main Orchestrator Commands | 3 | -| Workflow Session Commands | 6 | -| Issue Workflow Commands | 6 | -| IDAW Commands | 5 | -| With-File Workflows | 6 | -| Cycle Workflows | 2 | -| CLI Commands | 2 | -| Memory Commands | 2 | -| Team Skills | 17 | -| Workflow Skills | 7 | -| Utility Skills | 11 | -| **Total Commands** | 32 | -| **Total Skills** | 35 | +#### `/issue:new` + +| Field | Description | +|-------|-------------| +| **Who** | Developer creating structured issue | +| **When** | Starting issue tracking for a task | +| **What** | Creates structured issue from GitHub URL or description. Example: `/issue:new "Fix login timeout bug"` | +| **How** | Parse input -> Structure issue -> Create in issues.jsonl | +| **Output** | Issue entry in `.workflow/issues/issues.jsonl` | +| **Done** | Issue created with status "registered" | +| **Failure & Recovery** | Duplicate detection warns user | +| **Impact & Boundary** | Issue creation only, no planning | + +#### `/issue:discover` + +| Field | Description | +|-------|-------------| +| **Who** | Developer finding potential issues | +| **When** | Starting issue management workflow | +| **What** | Discovers potential issues from multiple sources. Example: `/issue:discover --scope src/auth` | +| **How** | Scan codebase -> Detect patterns -> Generate issue candidates | +| **Output** | List of discovered issue candidates | +| **Done** | Candidates presented for user selection | +| **Failure & Recovery** | Empty results suggest manual creation | +| **Impact & Boundary** | Discovery only, no automatic creation | + +#### `/issue:discover-by-prompt` + +| Field | Description | +|-------|-------------| +| **Who** | Developer with natural language query | +| **When** | Finding issues via description | +| **What** | Discovers issues from user prompt with Gemini analysis. Example: `/issue:discover-by-prompt "authentication problems"` | +| **How** | Gemini analysis -> Pattern matching -> Issue suggestions | +| **Output** | Issue candidates matching prompt | +| **Done** | Candidates presented for confirmation | +| **Failure & Recovery** | Falls back to keyword search | +| **Impact & Boundary** | Natural language discovery | + +#### `/issue:from-brainstorm` + +| Field | Description | +|-------|-------------| +| **Who** | Developer converting ideas to issues | +| **When** | After brainstorm session | +| **What** | Converts brainstorm session ideas into issues. Example: `/issue:from-brainstorm BRAIN-2026-03-08` | +| **How** | Parse brainstorm -> Extract actionables -> Create issues | +| **Output** | Multiple issues from brainstorm artifacts | +| **Done** | All actionables converted to issues | +| **Failure & Recovery** | Partial conversion on parse errors | +| **Impact & Boundary** | Requires completed brainstorm session | + +#### `/issue:plan` + +| Field | Description | +|-------|-------------| +| **Who** | Developer planning issue resolution | +| **When** | Issue registered, needs solution | +| **What** | Batch plans issue resolution using issue-planning-agent. Example: `/issue:plan ISS-001 ISS-002` | +| **How** | Load issues -> Generate solutions -> Bind to issues | +| **Output** | Solution files in `.workflow/issues/solutions/` | +| **Done** | Issues have bound solutions | +| **Failure & Recovery** | Partial planning on complex issues | +| **Impact & Boundary** | Planning only, no execution | + +#### `/issue:queue` + +| Field | Description | +|-------|-------------| +| **Who** | Developer forming execution queue | +| **When** | Solutions planned, ready to execute | +| **What** | Forms execution queue from bound solutions. Example: `/issue:queue ISS-001 ISS-002` | +| **How** | Build DAG -> Resolve dependencies -> Create queue | +| **Output** | Queue file in `.workflow/issues/queues/` | +| **Done** | Queue ready for execution | +| **Failure & Recovery** | Circular dependency detection | +| **Impact & Boundary** | Queue formation only | + +#### `/issue:execute` + +| Field | Description | +|-------|-------------| +| **Who** | Developer executing queued issues | +| **When** | Queue formed, ready to run | +| **What** | Executes queue with DAG-based parallel orchestration. Example: `/issue:execute -y` | +| **How** | DAG traversal -> Parallel execution -> Progress tracking | +| **Output** | Task execution results, code changes | +| **Done** | All queued tasks completed | +| **Failure & Recovery** | Failed tasks skipped, dependents notified | +| **Impact & Boundary** | Execution engine for issue workflow | + +#### `/issue:convert-to-plan` + +| Field | Description | +|-------|-------------| +| **Who** | Developer with existing planning artifacts | +| **When** | Converting lite-plan or brainstorm to issue | +| **What** | Converts planning artifacts to issue format. Example: `/issue:convert-to-plan plan.json` | +| **How** | Parse artifact -> Extract tasks -> Create issue + solution | +| **Output** | Issue and solution from plan | +| **Done** | Plan converted to trackable issue | +| **Failure & Recovery** | Partial conversion preserved | +| **Impact & Boundary** | Artifact conversion only | --- -## Invocation Patterns +### IDAW (Iterative Development Automation Workflow) -### Slash Command Invocation +#### `/idaw:status` + +| Field | Description | +|-------|-------------| +| **Who** | Developer checking IDAW progress | +| **When** | During IDAW session | +| **What** | Views IDAW task and session progress. Example: `/idaw:status` | +| **How** | Read session state -> Display progress | +| **Output** | Status summary of active IDAW session | +| **Done** | Status displayed | +| **Failure & Recovery** | No active session message | +| **Impact & Boundary** | Read-only status check | + +#### `/idaw:add` + +| Field | Description | +|-------|-------------| +| **Who** | Developer adding IDAW tasks | +| **When** | Building IDAW task list | +| **What** | Adds IDAW tasks via manual creation or import. Example: `/idaw:add "Implement caching layer"` | +| **How** | Parse input -> Create task entry -> Add to session | +| **Output** | Task added to IDAW session | +| **Done** | Task registered in session | +| **Failure & Recovery** | Duplicate task warning | +| **Impact & Boundary** | Task creation only | + +#### `/idaw:run` + +| Field | Description | +|-------|-------------| +| **Who** | Developer starting IDAW execution | +| **When** | Tasks added, ready to run | +| **What** | IDAW orchestrator executing task skill chain. Example: `/idaw:run -y` | +| **How** | Task dispatch -> Skill execution -> Progress tracking | +| **Output** | Task execution results | +| **Done** | All tasks processed | +| **Failure & Recovery** | Failed tasks logged, continue others | +| **Impact & Boundary** | Main IDAW execution engine | + +#### `/idaw:run-coordinate` + +| Field | Description | +|-------|-------------| +| **Who** | Developer needing coordinated execution | +| **When** | Complex multi-task IDAW session | +| **What** | IDAW coordinator executing task skill chain. Example: `/idaw:run-coordinate` | +| **How** | Coordinate multiple task executions -> Handle dependencies | +| **Output** | Coordinated execution results | +| **Done** | All coordinated tasks complete | +| **Failure & Recovery** | Dependency failures handled | +| **Impact & Boundary** | Coordinated execution mode | + +#### `/idaw:resume` + +| Field | Description | +|-------|-------------| +| **Who** | Developer resuming interrupted IDAW | +| **When** | IDAW session interrupted | +| **What** | Resumes interrupted IDAW session from last checkpoint. Example: `/idaw:resume` | +| **How** | Load state -> Resume from checkpoint -> Continue execution | +| **Output** | Continued execution from interruption point | +| **Done** | Session completes | +| **Failure & Recovery** | Checkpoint validation on load | +| **Impact & Boundary** | Resume capability for IDAW | + +--- + +### Workflow + +#### `/workflow:session:start` + +| Field | Description | +|-------|-------------| +| **Who** | Developer starting workflow session | +| **When** | Beginning any workflow work | +| **What** | Discovers or starts workflow session with conflict detection. Example: `/workflow:session:start --auto "implement OAuth2"` | +| **How** | Check active -> Detect conflicts -> Create/reuse session | +| **Output** | `SESSION_ID: WFS-{slug}` | +| **Done** | Session ready for work | +| **Failure & Recovery** | Multiple sessions warning | +| **Impact & Boundary** | Session initialization, calls /workflow:spec:setup if needed | + +#### `/workflow:session:list` + +| Field | Description | +|-------|-------------| +| **Who** | Developer reviewing sessions | +| **When** | Checking available sessions | +| **What** | Lists all workflow sessions with status filtering. Example: `/workflow:session:list --status active` | +| **How** | Scan .workflow/active -> Parse session metadata -> Display | +| **Output** | Session list with status, dates | +| **Done** | List displayed | +| **Failure & Recovery** | Empty list if no sessions | +| **Impact & Boundary** | Read-only listing | + +#### `/workflow:session:sync` + +| Field | Description | +|-------|-------------| +| **Who** | Developer syncing session work | +| **When** | After completing work in session | +| **What** | Quick-sync session work to specs/*.md and project-tech. Example: `/workflow:session:sync -y "auth complete"` | +| **How** | Gather context -> Extract updates -> Write specs + project-tech | +| **Output** | Updated specs/*.md and project-tech.json | +| **Done** | Sync complete message | +| **Failure & Recovery** | Duplicate rules skipped silently | +| **Impact & Boundary** | Updates project guidelines | + +#### `/workflow:session:resume` + +| Field | Description | +|-------|-------------| +| **Who** | Developer resuming paused session | +| **When** | Returning to paused work | +| **What** | Resumes most recently paused workflow session. Example: `/workflow:session:resume` | +| **How** | Find paused session -> Load state -> Continue | +| **Output** | Session context restored | +| **Done** | Ready to continue work | +| **Failure & Recovery** | No paused session error | +| **Impact & Boundary** | Session resumption | + +#### `/workflow:session:complete` + +| Field | Description | +|-------|-------------| +| **Who** | Developer finishing session | +| **When** | Session work complete | +| **What** | Archives completed session and removes from active. Example: `/workflow:session:complete -y` | +| **How** | Finalize state -> Archive -> Remove from active | +| **Output** | Archived session in .workflow/archived/ | +| **Done** | Session archived, specs updated | +| **Failure & Recovery** | Pending tasks warning | +| **Impact & Boundary** | Session finalization | + +#### `/workflow:spec:setup` + +| Field | Description | +|-------|-------------| +| **Who** | Developer initializing project specs | +| **When** | First time setup or regenerating | +| **What** | Initializes project-level state via cli-explore-agent analysis. Example: `/workflow:spec:setup --regenerate` | +| **How** | cli-explore-agent -> Generate project-tech.json -> Interactive questionnaire -> Write specs | +| **Output** | `.workflow/project-tech.json` + `.ccw/specs/*.md` | +| **Done** | Project specs configured | +| **Failure & Recovery** | Agent failure falls back to basic init | +| **Impact & Boundary** | Project-level initialization | + +#### `/workflow:spec:add` + +| Field | Description | +|-------|-------------| +| **Who** | Developer adding project rules | +| **When** | Adding conventions, constraints, or learnings | +| **What** | Adds specs, conventions, constraints to project guidelines. Example: `/workflow:spec:add -y "Use functional components"` | +| **How** | Parse input -> Auto-detect type -> Append to spec file | +| **Output** | Updated spec file in .ccw/specs/ | +| **Done** | Rule added confirmation | +| **Failure & Recovery** | Duplicate detection | +| **Impact & Boundary** | Single rule addition | + +#### `/workflow:clean` + +| Field | Description | +|-------|-------------| +| **Who** | Developer cleaning code | +| **When** | Before commits or after refactoring | +| **What** | Intelligent code cleanup with mainline detection. Example: `/workflow:clean -y` | +| **How** | Detect unused -> Remove dead code -> Format | +| **Output** | Cleaned code files | +| **Done** | Cleanup report displayed | +| **Failure & Recovery** | Preserves files with unclear usage | +| **Impact & Boundary** | Code cleanup only | + +#### `/workflow:debug-with-file` + +| Field | Description | +|-------|-------------| +| **Who** | Developer debugging issues | +| **When** | Encountering bugs or errors | +| **What** | Interactive hypothesis-driven debugging with file output. Example: `/workflow:debug-with-file "login fails on timeout"` | +| **How** | Hypothesis generation -> Evidence collection -> Validation -> Fix | +| **Output** | Debug report + potential fixes | +| **Done** | Root cause identified or fix applied | +| **Failure & Recovery** | Multiple hypothesis iteration | +| **Impact & Boundary** | Debugging workflow | + +#### `/workflow:analyze-with-file` + +| Field | Description | +|-------|-------------| +| **Who** | Developer analyzing code | +| **When** | Understanding codebase or issues | +| **What** | Interactive collaborative analysis with multi-CLI support. Example: `/workflow:analyze-with-file "analyze auth flow"` | +| **How** | Discovery -> Analysis -> Synthesis -> Report | +| **Output** | Analysis report in session folder | +| **Done** | Analysis complete with insights | +| **Failure & Recovery** | Partial analysis on errors | +| **Impact & Boundary** | Analysis workflow | + +#### `/workflow:brainstorm-with-file` + +| Field | Description | +|-------|-------------| +| **Who** | Developer exploring solutions | +| **When** | Starting new feature or solving complex problem | +| **What** | Interactive brainstorming with multi-CLI support. Example: `/workflow:brainstorm-with-file "caching strategy"` | +| **How** | Multi-perspective analysis -> Idea synthesis -> Recommendations | +| **Output** | Brainstorm report with actionables | +| **Done** | Ideas documented and prioritized | +| **Failure & Recovery** | Partial results preserved | +| **Impact & Boundary** | Ideation workflow | + +#### `/workflow:collaborative-plan-with-file` + +| Field | Description | +|-------|-------------| +| **Who** | Developer planning collaboratively | +| **When** | Complex feature planning | +| **What** | Collaborative planning with Plan Note output. Example: `/workflow:collaborative-plan-with-file "user dashboard redesign"` | +| **How** | Context gathering -> Planning -> Plan Note generation | +| **Output** | Plan with structured notes | +| **Done** | Plan ready for execution | +| **Failure & Recovery** | Iterative refinement | +| **Impact & Boundary** | Planning workflow | + +#### `/workflow:integration-test-cycle` + +| Field | Description | +|-------|-------------| +| **Who** | Developer running integration tests | +| **When** | After implementation, before merge | +| **What** | Self-iterating integration test workflow with reflection log. Example: `/workflow:integration-test-cycle -y "test auth flow"` | +| **How** | Generate tests -> Execute -> Reflect -> Iterate until pass | +| **Output** | Passing tests + reflection-log.md | +| **Done** | All tests passing | +| **Failure & Recovery** | Reflection-driven adjustment loop | +| **Impact & Boundary** | Integration testing workflow | + +#### `/workflow:refactor-cycle` + +| Field | Description | +|-------|-------------| +| **Who** | Developer addressing tech debt | +| **When** | Systematic code improvement | +| **What** | Tech debt discovery and self-iterating refactoring. Example: `/workflow:refactor-cycle -y "src/auth module"` | +| **How** | Debt discovery -> Prioritization -> Refactor -> Validate -> Reflect | +| **Output** | reflection-log.md + state.json + code changes | +| **Done** | All queued debt items processed | +| **Failure & Recovery** | Per-item validation with rollback | +| **Impact & Boundary** | Tech debt lifecycle management | + +#### `/workflow:roadmap-with-file` + +| Field | Description | +|-------|-------------| +| **Who** | Developer planning strategic requirements | +| **When** | Large feature or project planning | +| **What** | Strategic requirement roadmap with iterative decomposition. Example: `/workflow:roadmap-with-file -y "implement auth system"` | +| **How** | Understand -> Decompose -> Iterate -> Validate -> Handoff | +| **Output** | roadmap.md + issues.jsonl | +| **Done** | Roadmap approved, issues ready | +| **Failure & Recovery** | Max iteration rounds force proceed | +| **Impact & Boundary** | Strategic planning workflow | + +#### `/workflow:unified-execute-with-file` + +| Field | Description | +|-------|-------------| +| **Who** | Developer executing plans | +| **When** | After planning, ready to implement | +| **What** | Universal execution engine for any planning output. Example: `/workflow:unified-execute-with-file -y plan.json` | +| **How** | Load plan -> Validate -> Wave execution -> Track progress | +| **Output** | Code changes + execution-events.md | +| **Done** | All tasks executed | +| **Failure & Recovery** | Per-task retry with rollback | +| **Impact & Boundary** | Universal execution engine | + +#### UI Design Commands + +| Command | Who | When | What | Output | +|---------|-----|------|------|--------| +| `/workflow:ui-design:explore-auto` | Designer/Developer | Starting UI design | Interactive exploratory workflow | Style variants + layout templates + prototypes | +| `/workflow:ui-design:imitate-auto` | Designer/Developer | Imitating reference | UI design imitation workflow | Prototypes matching reference style | +| `/workflow:ui-design:generate` | Designer/Developer | Assembling prototypes | Pure assembler combining layouts + tokens | HTML/CSS prototypes | +| `/workflow:ui-design:style-extract` | Designer/Developer | Extracting styles | Extract design tokens from images | design-tokens.json + style-guide.md | +| `/workflow:ui-design:layout-extract` | Designer/Developer | Extracting layouts | Extract layout templates | layout-*.json files | +| `/workflow:ui-design:animation-extract` | Designer/Developer | Extracting animations | Extract animation patterns | animation-tokens.json | +| `/workflow:ui-design:codify-style` | Developer | From code to design | Extract styles from code files | Design tokens from CSS/SCSS | +| `/workflow:ui-design:import-from-code` | Developer | Code-based design | Import design from existing code | Design system from codebase | +| `/workflow:ui-design:design-sync` | Designer | Syncing design | Synchronize design references | Updated design system docs | +| `/workflow:ui-design:reference-page-generator` | Developer | Reference docs | Generate component reference pages | Multi-component reference pages | + +--- + +### Memory + +#### `/memory:prepare` + +| Field | Description | +|-------|-------------| +| **Who** | Developer preparing memory capture | +| **When** | Before capturing session knowledge | +| **What** | Delegates to universal-executor agent to prepare memory. Example: `/memory:prepare "auth session"` | +| **How** | Context gathering -> Memory structure preparation | +| **Output** | Prepared memory structure | +| **Done** | Ready for memory capture | +| **Failure & Recovery** | Agent failure handled | +| **Impact & Boundary** | Memory preparation only | + +#### `/memory:style-skill-memory` + +| Field | Description | +|-------|-------------| +| **Who** | Developer documenting style knowledge | +| **When** | After learning project patterns | +| **What** | Generates SKILL memory package from style patterns. Example: `/memory:style-skill-memory "React patterns"` | +| **How** | Pattern extraction -> Skill memory generation | +| **Output** | SKILL memory package | +| **Done** | Skill memory documented | +| **Failure & Recovery** | Partial patterns preserved | +| **Impact & Boundary** | Style-specific memory | + +--- + +### CLI + +#### `/cli:codex-review` + +| Field | Description | +|-------|-------------| +| **Who** | Developer reviewing code | +| **When** | Code review needed | +| **What** | Interactive code review using Codex CLI. Example: `/cli:codex-review --uncommitted` | +| **How** | Codex CLI -> Review analysis -> Interactive feedback | +| **Output** | Code review report | +| **Done** | Review complete with recommendations | +| **Failure & Recovery** | Codex unavailability fallback | +| **Impact & Boundary** | Git-aware code review | + +#### `/cli:cli-init` + +| Field | Description | +|-------|-------------| +| **Who** | Developer setting up CLI config | +| **When** | First time setup | +| **What** | Generates .gemini/ and .qwen/ config directories. Example: `/cli:cli-init` | +| **How** | Create directories -> Generate default configs | +| **Output** | CLI configuration directories | +| **Done** | Configs ready for customization | +| **Failure & Recovery** | Existing configs preserved | +| **Impact & Boundary** | CLI configuration setup | + +--- + +## Section 2: Skills + +### Workflow Skills + +#### `workflow-plan` + +| Field | Description | +|-------|-------------| +| **Who** | Developer planning tasks | +| **When** | Starting any planned work | +| **What** | Unified 4-phase planning: session discovery -> context gathering -> conflict resolution -> task generation | +| **How** | Phase 0: Session -> Phase 1: Context -> Phase 2: Conflicts -> Phase 3: Tasks | +| **Output** | plan.json + TASK-*.json in session folder | +| **Done** | Plan with TodoWrite tracking complete | +| **Failure & Recovery** | Conflict resolution prompts user | +| **Impact & Boundary** | Core planning skill | + +#### `workflow-execute` + +| Field | Description | +|-------|-------------| +| **Who** | Developer executing planned tasks | +| **When** | After workflow-plan | +| **What** | Agent execution orchestration with lazy task loading, auto-commit | +| **How** | Load plan -> Spawn agents -> Execute -> Commit | +| **Output** | Code changes + task completion status | +| **Done** | All tasks executed or user-stopped | +| **Failure & Recovery** | Per-task retry, auto-rollback | +| **Impact & Boundary** | Core execution skill | + +#### `workflow-lite-plan` + +| Field | Description | +|-------|-------------| +| **Who** | Developer needing quick planning | +| **When** | Simple tasks without full session | +| **What** | Lightweight planning - task analysis + breakdown | +| **How** | Analyze -> Break down -> Generate tasks | +| **Output** | Simplified plan.json | +| **Done** | Quick plan ready | +| **Failure & Recovery** | Falls back to workflow-plan for complex cases | +| **Impact & Boundary** | Lightweight alternative | + +#### `workflow-lite-execute` + +| Field | Description | +|-------|-------------| +| **Who** | Developer executing simple plans | +| **When** | After lite-plan or standalone | +| **What** | Lightweight execution engine - multi-model collaboration | +| **How** | Load tasks -> Execute -> Verify | +| **Output** | Code changes | +| **Done** | Tasks completed | +| **Failure & Recovery** | Simple retry mechanism | +| **Impact & Boundary** | Lightweight alternative | + +#### `workflow-tdd-plan` + +| Field | Description | +|-------|-------------| +| **Who** | Developer using TDD approach | +| **When** | Test-driven development | +| **What** | TDD workflow combining 6-phase planning with test-first | +| **How** | Plan tests -> Write tests -> Implement -> Verify | +| **Output** | Tests + implementation | +| **Done** | All tests passing | +| **Failure & Recovery** | Test failure iteration | +| **Impact & Boundary** | TDD-specific workflow | + +#### `workflow-test-fix` + +| Field | Description | +|-------|-------------| +| **Who** | Developer fixing test failures | +| **When** | Tests failing | +| **What** | Test-fix pipeline combining test runner with fix agent | +| **How** | Run tests -> Identify failures -> Fix -> Re-run | +| **Output** | Passing tests | +| **Done** | All tests pass | +| **Failure & Recovery** | Iterative fix loop | +| **Impact & Boundary** | Test fixing workflow | + +#### `workflow-multi-cli-plan` + +| Field | Description | +|-------|-------------| +| **Who** | Developer using multiple CLIs | +| **When** | Complex multi-perspective planning | +| **What** | Multi-CLI collaborative planning with ACE integration | +| **How** | Parallel CLI analysis -> Merge perspectives -> Generate plan | +| **Output** | Comprehensive plan from multiple models | +| **Done** | Merged plan complete | +| **Failure & Recovery** | Partial results merged | +| **Impact & Boundary** | Multi-model planning | + +#### `workflow-skill-designer` + +| Field | Description | +|-------|-------------| +| **Who** | Developer creating skills | +| **When** | Building new workflow skills | +| **What** | Meta-skill for designing orchestrator+phase skills | +| **How** | Design -> Template -> Generate skill files | +| **Output** | New skill SKILL.md + phases | +| **Done** | Skill ready for use | +| **Failure & Recovery** | Validation errors guide fixes | +| **Impact & Boundary** | Skill meta-creation | + +--- + +### Team Skills + +#### `team-coordinate` + +| Field | Description | +|-------|-------------| +| **Who** | Developer coordinating multi-agent work | +| **When** | Complex multi-role tasks | +| **What** | Universal team coordination with dynamic role generation | +| **How** | Analyze task -> Generate role-specs -> Dispatch workers -> Execute -> Deliver | +| **Output** | Coordinated multi-agent results | +| **Done** | Pipeline complete, artifacts delivered | +| **Failure & Recovery** | Role regeneration on capability gaps | +| **Impact & Boundary** | Universal team orchestrator | + +#### `team-edict` + +| Field | Description | +|-------|-------------| +| **Who** | Developer using Edict architecture | +| **When** | Large-scale multi-agent coordination | +| **What** | Three-Six Ministry multi-agent framework replicating Edict architecture | +| **How** | Ministry-based role assignment -> Task dispatch -> Report aggregation | +| **Output** | Comprehensive multi-role deliverables | +| **Done** | All ministries report complete | +| **Failure & Recovery** | Ministry-level retry | +| **Impact & Boundary** | Large-scale coordination | + +#### `team-planex` + +| Field | Description | +|-------|-------------| +| **Who** | Developer planning and executing | +| **When** | Plan-and-execute workflow | +| **What** | Unified team skill for plan-and-execute team | +| **How** | Plan -> Execute -> Verify | +| **Output** | Planned and executed work | +| **Done** | Plan executed completely | +| **Failure & Recovery** | Plan adjustment on failures | +| **Impact & Boundary** | Plan-execute team | + +#### `team-frontend` + +| Field | Description | +|-------|-------------| +| **Who** | Frontend developer | +| **When** | Frontend development work | +| **What** | Unified team skill for frontend development | +| **How** | Component design -> Implementation -> Testing | +| **Output** | Frontend components and features | +| **Done** | Frontend work complete | +| **Failure & Recovery** | Component-level retry | +| **Impact & Boundary** | Frontend-specific team | + +#### `team-frontend-debug` + +| Field | Description | +|-------|-------------| +| **Who** | Frontend developer debugging | +| **When** | Frontend issues | +| **What** | Frontend debugging team using Chrome DevTools MCP | +| **How** | Inspect -> Diagnose -> Fix -> Verify | +| **Output** | Fixed frontend issues | +| **Done** | Issues resolved | +| **Failure & Recovery** | Iterative debugging | +| **Impact & Boundary** | Frontend debugging specific | + +#### `team-testing` + +| Field | Description | +|-------|-------------| +| **Who** | Developer writing tests | +| **When** | Test generation needed | +| **What** | Unified team skill for testing team | +| **How** | Test planning -> Generation -> Execution | +| **Output** | Test suites | +| **Done** | Tests passing | +| **Failure & Recovery** | Test iteration | +| **Impact & Boundary** | Testing-specific team | + +#### `team-review` + +| Field | Description | +|-------|-------------| +| **Who** | Developer reviewing code | +| **When** | Code review needed | +| **What** | Unified team skill for code review | +| **How** | Multi-perspective review -> Feedback aggregation | +| **Output** | Review reports | +| **Done** | Review complete | +| **Failure & Recovery** | Partial review preserved | +| **Impact & Boundary** | Review-specific team | + +#### `team-quality-assurance` + +| Field | Description | +|-------|-------------| +| **Who** | QA engineer | +| **When** | Quality verification | +| **What** | Unified team skill for quality assurance | +| **How** | Quality checks -> Issue identification -> Remediation | +| **Output** | QA reports and fixes | +| **Done** | Quality verified | +| **Failure & Recovery** | Issue-driven iteration | +| **Impact & Boundary** | QA-specific team | + +#### `team-arch-opt` + +| Field | Description | +|-------|-------------| +| **Who** | Developer optimizing architecture | +| **When** | Architecture improvement | +| **What** | Unified team skill for architecture optimization | +| **How** | Analysis -> Optimization plan -> Implementation | +| **Output** | Improved architecture | +| **Done** | Optimization complete | +| **Failure & Recovery** | Gradual optimization | +| **Impact & Boundary** | Architecture-specific team | + +#### `team-perf-opt` + +| Field | Description | +|-------|-------------| +| **Who** | Developer optimizing performance | +| **When** | Performance issues | +| **What** | Unified team skill for performance optimization | +| **How** | Profiling -> Bottleneck identification -> Optimization | +| **Output** | Performance improvements | +| **Done** | Performance targets met | +| **Failure & Recovery** | Iterative optimization | +| **Impact & Boundary** | Performance-specific team | + +#### `team-tech-debt` + +| Field | Description | +|-------|-------------| +| **Who** | Developer addressing tech debt | +| **When** | Tech debt cleanup | +| **What** | Unified team skill for tech debt identification | +| **How** | Detection -> Prioritization -> Resolution | +| **Output** | Tech debt reduction | +| **Done** | Debt items resolved | +| **Failure & Recovery** | Prioritized resolution | +| **Impact & Boundary** | Tech debt specific | + +#### `team-ux-improve` + +| Field | Description | +|-------|-------------| +| **Who** | UX designer/developer | +| **When** | UX improvements | +| **What** | Unified team skill for UX improvement | +| **How** | UX audit -> Improvement plan -> Implementation | +| **Output** | UX improvements | +| **Done** | UX enhanced | +| **Failure & Recovery** | User feedback iteration | +| **Impact & Boundary** | UX-specific team | + +#### `team-uidesign` + +| Field | Description | +|-------|-------------| +| **Who** | UI designer | +| **When** | UI design work | +| **What** | Unified team skill for UI design team | +| **How** | Design system -> Components -> Prototypes | +| **Output** | UI designs and prototypes | +| **Done** | Design complete | +| **Failure & Recovery** | Design iteration | +| **Impact & Boundary** | UI design specific | + +#### `team-brainstorm` + +| Field | Description | +|-------|-------------| +| **Who** | Team brainstorming | +| **When** | Ideation sessions | +| **What** | Unified team skill for brainstorming team | +| **How** | Multi-perspective ideation -> Synthesis | +| **Output** | Brainstorm results | +| **Done** | Ideas documented | +| **Failure & Recovery** | Partial synthesis | +| **Impact & Boundary** | Brainstorming specific | + +#### `team-issue` + +| Field | Description | +|-------|-------------| +| **Who** | Developer managing issues | +| **When** | Issue resolution workflow | +| **What** | Unified team skill for issue resolution | +| **How** | Issue analysis -> Resolution -> Verification | +| **Output** | Resolved issues | +| **Done** | Issues closed | +| **Failure & Recovery** | Issue-specific handling | +| **Impact & Boundary** | Issue-specific team | + +#### `team-iterdev` + +| Field | Description | +|-------|-------------| +| **Who** | Developer in iterative mode | +| **When** | Iterative development | +| **What** | Unified team skill for iterative development | +| **How** | Iteration -> Feedback -> Refinement | +| **Output** | Iteratively improved code | +| **Done** | Iteration goals met | +| **Failure & Recovery** | Iteration adjustment | +| **Impact & Boundary** | Iterative development team | + +#### `team-roadmap-dev` + +| Field | Description | +|-------|-------------| +| **Who** | Developer on roadmap features | +| **When** | Roadmap-driven development | +| **What** | Unified team skill for roadmap-driven development | +| **How** | Roadmap parsing -> Feature development -> Tracking | +| **Output** | Roadmap feature completions | +| **Done** | Roadmap items complete | +| **Failure & Recovery** | Roadmap adjustment | +| **Impact & Boundary** | Roadmap-specific team | + +#### `team-ultra-analyze` + +| Field | Description | +|-------|-------------| +| **Who** | Developer needing deep analysis | +| **When** | Complex analysis required | +| **What** | Deep collaborative analysis team skill | +| **How** | Multi-angle analysis -> Deep dive -> Synthesis | +| **Output** | Comprehensive analysis reports | +| **Done** | Analysis complete | +| **Failure & Recovery** | Partial analysis preserved | +| **Impact & Boundary** | Deep analysis team | + +#### `team-executor` + +| Field | Description | +|-------|-------------| +| **Who** | Developer executing tasks | +| **When** | Task execution needed | +| **What** | Lightweight session execution skill | +| **How** | Load session -> Execute tasks -> Report | +| **Output** | Task execution results | +| **Done** | Session tasks complete | +| **Failure & Recovery** | Task-level retry | +| **Impact & Boundary** | Lightweight execution | + +#### `team-lifecycle-v4` + +| Field | Description | +|-------|-------------| +| **Who** | Developer managing full lifecycle | +| **When** | Complete feature lifecycle | +| **What** | Full lifecycle team skill with clean architecture | +| **How** | Plan -> Develop -> Test -> Deploy -> Monitor | +| **Output** | Complete feature lifecycle | +| **Done** | Feature fully delivered | +| **Failure & Recovery** | Lifecycle stage retry | +| **Impact & Boundary** | Full lifecycle management | + +#### `team-designer` + +| Field | Description | +|-------|-------------| +| **Who** | Developer designing teams | +| **When** | Creating new team skills | +| **What** | Meta-skill for generating team skills for different domains | +| **How** | Domain analysis -> Role definition -> Skill generation | +| **Output** | New team skill files | +| **Done** | Team skill ready | +| **Failure & Recovery** | Template validation | +| **Impact & Boundary** | Team skill meta-creation | + +--- + +### Utility Skills + +#### `brainstorm` + +| Field | Description | +|-------|-------------| +| **Who** | Developer exploring ideas | +| **When** | Starting new work, exploring solutions | +| **What** | Unified brainstorming with dual-mode (auto/single-role) and 9 available roles | +| **How** | Role selection -> Perspective analysis -> Idea synthesis | +| **Output** | Brainstorm report with actionables | +| **Done** | Ideas documented | +| **Failure & Recovery** | Partial analysis preserved | +| **Impact & Boundary** | Ideation support | + +#### `spec-generator` + +| Field | Description | +|-------|-------------| +| **Who** | Developer creating specifications | +| **When** | Starting new project or feature | +| **What** | 6-phase specification chain producing product brief, PRD, architecture, epics | +| **How** | Phase 1-6 chain: Brief -> PRD -> Architecture -> Epics -> Docs | +| **Output** | Complete specification documents | +| **Done** | All spec documents generated | +| **Failure & Recovery** | Phase-level retry | +| **Impact & Boundary** | Specification generation | + +#### `issue-manage` + +| Field | Description | +|-------|-------------| +| **Who** | Developer managing issues | +| **When** | Issue CRUD operations | +| **What** | Interactive menu-driven interface for issue CRUD via ccw issue CLI | +| **How** | Menu selection -> CLI execution -> Result display | +| **Output** | Issue management operations | +| **Done** | Operation complete | +| **Failure & Recovery** | CLI error handling | +| **Impact & Boundary** | Issue CRUD only | + +#### `review-code` + +| Field | Description | +|-------|-------------| +| **Who** | Developer reviewing code | +| **When** | Code review needed | +| **What** | Multi-dimensional code review with 6 dimensions: correctness, readability, performance, security, testing, architecture | +| **How** | Collect context -> Quick scan -> Deep review -> Generate report | +| **Output** | Structured review report | +| **Done** | Review complete | +| **Failure & Recovery** | Partial review preserved | +| **Impact & Boundary** | Code review only | + +#### `review-cycle` + +| Field | Description | +|-------|-------------| +| **Who** | Developer in review cycle | +| **When** | Iterative code review | +| **What** | Unified multi-dimensional code review with iterative cycle | +| **How** | Review -> Feedback -> Fix -> Re-review | +| **Output** | Iteratively improved code | +| **Done** | All issues addressed | +| **Failure & Recovery** | Cycle iteration | +| **Impact & Boundary** | Iterative review | + +#### `memory-capture` + +| Field | Description | +|-------|-------------| +| **Who** | Developer capturing knowledge | +| **When** | After important learnings | +| **What** | Unified memory capture with routing - session/tech/module context | +| **How** | Context detection -> Memory extraction -> Storage | +| **Output** | Captured memory entries | +| **Done** | Memory captured | +| **Failure & Recovery** | Partial capture preserved | +| **Impact & Boundary** | Memory capture only | + +#### `memory-manage` + +| Field | Description | +|-------|-------------| +| **Who** | Developer managing memory | +| **When** | Memory maintenance | +| **What** | Unified memory management - CLAUDE.md updates and memory cleanup | +| **How** | Load memory -> Organize -> Update CLAUDE.md | +| **Output** | Updated memory files | +| **Done** | Memory organized | +| **Failure & Recovery** | Backup before changes | +| **Impact & Boundary** | Memory management | + +#### `skill-tuning` + +| Field | Description | +|-------|-------------| +| **Who** | Developer improving skills | +| **When** | Skill optimization needed | +| **What** | Universal skill diagnosis and optimization | +| **How** | Diagnose -> Optimize -> Validate | +| **Output** | Improved skill files | +| **Done** | Skill optimized | +| **Failure & Recovery** | Incremental improvement | +| **Impact & Boundary** | Skill optimization | + +#### `skill-simplify` + +| Field | Description | +|-------|-------------| +| **Who** | Developer simplifying skills | +| **When** | Skill too complex | +| **What** | SKILL.md simplification with functional preservation | +| **How** | Analyze -> Simplify -> Verify functionality | +| **Output** | Simplified skill file | +| **Done** | Skill simplified | +| **Failure & Recovery** | Functional verification | +| **Impact & Boundary** | Skill simplification | + +#### `skill-generator` + +| Field | Description | +|-------|-------------| +| **Who** | Developer creating skills | +| **When** | New skill needed | +| **What** | Meta-skill for creating new Claude Code skills | +| **How** | Requirements -> Template -> Skill generation | +| **Output** | New skill SKILL.md + supporting files | +| **Done** | Skill ready for use | +| **Failure & Recovery** | Template validation | +| **Impact & Boundary** | Skill creation | + +#### `command-generator` + +| Field | Description | +|-------|-------------| +| **Who** | Developer creating commands | +| **When** | New slash command needed | +| **What** | Command file generator - 5 phase workflow | +| **How** | Requirements -> Template -> Command generation | +| **Output** | New command .md file | +| **Done** | Command ready for use | +| **Failure & Recovery** | Schema validation | +| **Impact & Boundary** | Command creation | + +#### `ccw-help` + +| Field | Description | +|-------|-------------| +| **Who** | Developer seeking help | +| **When** | Learning CCW system | +| **What** | CCW command help system - search, browse, documentation | +| **How** | Query -> Search -> Display help | +| **Output** | Help information | +| **Done** | Help displayed | +| **Failure & Recovery** | Fuzzy matching | +| **Impact & Boundary** | Help system only | + +--- + +## Appendix A: Quick Reference Table + +### Commands by Category + +| Category | Commands | Count | +|----------|----------|-------| +| Core | ccw, ccw-coordinator, flow-create | 3 | +| DDD | scan, index-build, plan, execute, doc-generate, doc-refresh, sync, update, auto | 9 | +| Issue | new, discover, discover-by-prompt, from-brainstorm, plan, queue, execute, convert-to-plan | 8 | +| IDAW | status, add, run, run-coordinate, resume | 5 | +| Workflow Session | start, list, sync, resume, complete | 5 | +| Workflow Spec | setup, add | 2 | +| Workflow Core | clean, debug-with-file, analyze-with-file, brainstorm-with-file, collaborative-plan-with-file | 5 | +| Workflow Cycle | integration-test-cycle, refactor-cycle, roadmap-with-file, unified-execute-with-file | 4 | +| Workflow UI Design | explore-auto, imitate-auto, generate, style-extract, layout-extract, animation-extract, codify-style, import-from-code, design-sync, reference-page-generator | 10 | +| Memory | prepare, style-skill-memory | 2 | +| CLI | codex-review, cli-init | 2 | +| **Total Commands** | | **55** | + +### Skills by Category + +| Category | Skills | Count | +|----------|--------|-------| +| Workflow | workflow-plan, workflow-execute, workflow-lite-plan, workflow-lite-execute, workflow-tdd-plan, workflow-test-fix, workflow-multi-cli-plan, workflow-skill-designer | 8 | +| Team | team-coordinate, team-edict, team-planex, team-frontend, team-frontend-debug, team-testing, team-review, team-quality-assurance, team-arch-opt, team-perf-opt, team-tech-debt, team-ux-improve, team-uidesign, team-brainstorm, team-issue, team-iterdev, team-roadmap-dev, team-ultra-analyze, team-executor, team-lifecycle-v4, team-designer | 21 | +| Utility | brainstorm, spec-generator, issue-manage, review-code, review-cycle, memory-capture, memory-manage, skill-tuning, skill-simplify, skill-generator, command-generator, ccw-help | 12 | +| **Total Skills** | | **41** | + +--- + +## Appendix B: Command Chain Examples + +### Document-Driven Development Flow ``` -/<namespace>:<command> [arguments] [flags] +/ddd:scan # Code-first: scan existing codebase + -> /ddd:plan "add feature" # Plan with doc context + -> /ddd:execute # Execute with doc awareness + -> /ddd:sync # Sync changes to docs ``` -Examples: -- `/ccw "Add user authentication"` -- `/workflow:session:start --auto "implement feature"` -- `/issue:new https://github.com/org/repo/issues/123` -- `/cli:codex-review --base main` +### Spec-First Development Flow -### Skill Invocation (from code) - -```javascript -Skill({ skill: "workflow-lite-plan", args: '"task description"' }) -Skill({ skill: "brainstorm", args: '"topic or question"' }) -Skill({ skill: "review-cycle", args: '--session="WFS-xxx"' }) +``` +Skill: spec-generator # Generate specifications + -> /ddd:index-build # Build index from specs + -> /ddd:plan # Plan with spec context + -> /ddd:execute # Execute + -> /ddd:doc-refresh # Refresh affected docs ``` -### CLI Tool Invocation +### Issue Resolution Flow -```bash -ccw cli -p "PURPOSE: ... TASK: ... MODE: analysis|write" --tool <tool> --mode <mode> +``` +/issue:new "bug description" # Create issue + -> /issue:plan ISS-001 # Generate solution + -> /issue:queue ISS-001 # Add to queue + -> /issue:execute # Execute queue +``` + +### Team Coordination Flow + +``` +Skill: team-coordinate "implement auth" + -> Dynamic role generation + -> Parallel worker execution + -> Result aggregation + -> Completion action +``` + +### UI Design Flow + +``` +/workflow:ui-design:explore-auto --input "modern dashboard" + -> /workflow:ui-design:style-extract # Extract styles + -> /workflow:ui-design:layout-extract # Extract layouts + -> /workflow:ui-design:generate # Assemble prototypes +``` + +### Integration Test Flow + +``` +/workflow:integration-test-cycle "test auth flow" + -> Generate tests + -> Execute tests + -> Reflect on failures + -> Iterate until pass + -> Reflection log +``` + +### Refactoring Flow + +``` +/workflow:refactor-cycle "src/auth" + -> Debt discovery + -> Prioritization + -> Per-item refactor + -> Validation + -> Reflection ``` --- -## Related Documentation +## Summary -- [Workflow Comparison Table](../workflows/comparison-table.md) - Workflow selection guide -- [Workflow Overview](../workflows/index.md) - 4-Level workflow system -- [Claude Workflow Skills](../skills/claude-workflow.md) - Detailed skill documentation +| Metric | Count | +|--------|-------| +| **Total Commands** | 55 | +| **Total Skills** | 41 | +| **DDD Commands** | 9 | +| **Issue Commands** | 8 | +| **Team Skills** | 21 | +| **Workflow Skills** | 8 | + +--- + +*End of Reference Manual* diff --git a/docs/zh/reference/commands-skills.md b/docs/zh/reference/commands-skills.md index 61a7dffe..4bb9b11c 100644 --- a/docs/zh/reference/commands-skills.md +++ b/docs/zh/reference/commands-skills.md @@ -1,736 +1,1321 @@ -# 命令与技能参考 +# CCW Commands & Skills Reference Manual -> **快速参考**: Claude 命令、技能和 Codex 能力的完整目录 +> Generated: 2026-03-08 | Project: Claude Code Workspace (CCW) + +This reference manual provides quick lookup for all slash commands and skills in the CCW system. --- -## 快速参考表 +## Table of Contents -### 命令快速参考 - -| 类别 | 命令 | 描述 | 参数 | -|----------|---------|-------------|-----------| -| **编排器** | `/ccw` | 主工作流编排器 | `"任务描述"` | -| **编排器** | `/ccw-coordinator` | 命令编排工具 | `[任务描述]` | -| **会话** | `/workflow:session:start` | 启动工作流会话 | `[--type] [--auto|--new] [任务]` | -| **会话** | `/workflow:session:resume` | 恢复暂停的会话 | - | -| **会话** | `/workflow:session:complete` | 完成活动会话 | `[-y] [--detailed]` | -| **会话** | `/workflow:session:list` | 列出所有会话 | - | -| **会话** | `/workflow:session:sync` | 同步会话到规格 | `[-y] ["完成内容"]` | -| **会话** | `/workflow:session:solidify` | 固化学习成果 | `[--type] [--category] "规则"` | -| **Issue** | `/issue:new` | 创建结构化 Issue | `<url|文本> [--priority 1-5]` | -| **Issue** | `/issue:discover` | 发现潜在问题 | `<路径> [--perspectives=...]` | -| **Issue** | `/issue:plan` | 规划 Issue 解决 | `--all-pending <ids>` | -| **Issue** | `/issue:queue` | 形成执行队列 | `[--queues <n>] [--issue <id>]` | -| **Issue** | `/issue:execute` | 执行队列 | `--queue <id> [--worktree]` | -| **IDAW** | `/idaw:run` | IDAW 编排器 | `[--task <ids>] [--dry-run]` | -| **IDAW** | `/idaw:add` | 添加任务到队列 | - | -| **IDAW** | `/idaw:resume` | 恢复 IDAW 会话 | - | -| **IDAW** | `/idaw:status` | 显示队列状态 | - | -| **With-File** | `/workflow:brainstorm-with-file` | 交互式头脑风暴 | `[-c] [-m creative|structured] "主题"` | -| **With-File** | `/workflow:analyze-with-file` | 协作分析 | `[-c] "主题"` | -| **With-File** | `/workflow:debug-with-file` | 假设驱动调试 | `"Bug描述"` | -| **With-File** | `/workflow:collaborative-plan-with-file` | 多代理规划 | - | -| **With-File** | `/workflow:roadmap-with-file` | 战略路线图 | - | -| **Cycle** | `/workflow:integration-test-cycle` | 集成测试循环 | - | -| **Cycle** | `/workflow:refactor-cycle` | 重构循环 | - | -| **CLI** | `/cli:codex-review` | Codex 代码审查 | `[--uncommitted|--base|--commit]` | -| **CLI** | `/cli:cli-init` | 初始化 CLI 配置 | - | -| **Memory** | `/memory:prepare` | 准备记忆上下文 | - | -| **Memory** | `/memory:style-skill-memory` | 样式/技能记忆 | - | - -### 技能快速参考 - -| 类别 | 技能 | 内部流水线 | 用例 | -|----------|-------|-------------------|----------| -| **Workflow** | workflow-lite-plan | explore → plan → confirm → execute | 快速功能、Bug 修复 | -| **Workflow** | workflow-plan | session → context → convention → gen → verify/replan | 复杂功能规划 | -| **Workflow** | workflow-execute | session discovery → task processing → commit | 执行预生成的计划 | -| **Workflow** | workflow-tdd-plan | 6阶段 TDD plan → verify | TDD 开发 | -| **Workflow** | workflow-test-fix | session → context → analysis → gen → cycle | 测试生成与修复 | -| **Workflow** | workflow-multi-cli-plan | ACE context → CLI discussion → plan → execute | 多视角规划 | -| **Workflow** | workflow-skill-designer | - | 创建新技能 | -| **Team** | team-lifecycle | spec pipeline → impl pipeline | 完整生命周期 | -| **Team** | team-planex | planner wave → executor wave | Issue 批量执行 | -| **Team** | team-arch-opt | architecture analysis → optimization | 架构优化 | -| **Utility** | brainstorm | framework → parallel analysis → synthesis | 多视角创意 | -| **Utility** | review-cycle | discovery → analysis → aggregation → deep-dive | 代码审查 | -| **Utility** | spec-generator | study → brief → PRD → architecture → epics | 规格文档包 | +- [Section 1: Slash Commands](#section-1-slash-commands) + - [Core](#core) + - [DDD (Document-Driven Development)](#ddd-document-driven-development) + - [Issue](#issue) + - [IDAW (Iterative Development Automation Workflow)](#idaw-iterative-development-automation-workflow) + - [Workflow](#workflow) + - [Memory](#memory) + - [CLI](#cli) +- [Section 2: Skills](#section-2-skills) + - [Workflow Skills](#workflow-skills) + - [Team Skills](#team-skills) + - [Utility Skills](#utility-skills) +- [Appendix A: Quick Reference Table](#appendix-a-quick-reference-table) +- [Appendix B: Command Chain Examples](#appendix-b-command-chain-examples) --- -## 1. 主编排器命令 +## Section 1: Slash Commands -### /ccw +### Core -**描述**: 主工作流编排器 - 分析意图、选择工作流、在主进程中执行命令链 +#### `/ccw` -**参数**: `"任务描述"` - -**类别**: orchestrator - -**5阶段工作流**: -1. Phase 1: 分析意图 (检测任务类型、复杂度、清晰度) -2. Phase 1.5: 需求澄清 (如果清晰度 < 2) -3. Phase 2: 选择工作流并构建命令链 -4. Phase 3: 用户确认 -5. Phase 4: 设置 TODO 跟踪和状态文件 -6. Phase 5: 执行命令链 - -**技能映射**: - -| 技能 | 内部流水线 | -|-------|-------------------| -| workflow-lite-plan | explore → plan → confirm → execute | -| workflow-plan | session → context → convention → gen → verify/replan | -| workflow-execute | session discovery → task processing → commit | -| workflow-tdd-plan | 6阶段 TDD plan → verify | -| workflow-test-fix | session → context → analysis → gen → cycle | -| workflow-multi-cli-plan | ACE context → CLI discussion → plan → execute | -| review-cycle | session/module review → fix orchestration | -| brainstorm | auto/single-role → artifacts → analysis → synthesis | -| spec-generator | product-brief → PRD → architecture → epics | - -**自动模式**: `-y` 或 `--yes` 标志跳过确认，传播到所有技能 - ---- - -### /ccw-coordinator - -**描述**: 命令编排工具 - 分析需求、推荐链、带状态持久化顺序执行 - -**参数**: `[任务描述]` - -**类别**: orchestrator - -**3阶段工作流**: -1. Phase 1: 分析需求 -2. Phase 2: 发现命令并推荐链 -3. Phase 3: 顺序执行命令链 - -**最小执行单元**: - -| 单元 | 命令 | 用途 | -|------|----------|---------| -| 快速实现 | lite-plan (plan → execute) | 轻量级规划和执行 | -| 多CLI规划 | multi-cli-plan | 多视角规划 | -| Bug修复 | lite-plan --bugfix | Bug诊断和修复 | -| 完整规划+执行 | plan → execute | 详细规划 | -| 验证规划+执行 | plan → plan-verify → execute | 带验证的规划 | -| TDD规划+执行 | tdd-plan → execute | TDD工作流 | -| Issue工作流 | discover → plan → queue → execute | 完整Issue生命周期 | - ---- - -### /flow-create - -**描述**: 元技能/flow-coordinator 的流程模板生成器 - -**参数**: `[模板名称] [--output <路径>]` - -**类别**: utility - -**执行流程**: -1. Phase 1: 模板设计 (名称 + 描述 + 级别) -2. Phase 2: 步骤定义 (命令类别 → 具体命令 → 执行单元 → 模式) -3. Phase 3: 生成 JSON - ---- - -## 2. 工作流会话命令 - -### /workflow:session:start - -**描述**: 发现现有会话或启动新工作流会话，具有智能会话管理和冲突检测 - -**参数**: `[--type <workflow|review|tdd|test|docs>] [--auto|--new] [任务描述]` - -**类别**: session-management - -**会话类型**: - -| 类型 | 描述 | 默认对应技能 | -|------|-------------|-------------| -| workflow | 标准实现 | workflow-plan skill | -| review | 代码审查会话 | review-cycle skill | -| tdd | TDD开发 | workflow-tdd-plan skill | -| test | 测试生成/修复 | workflow-test-fix skill | -| docs | 文档会话 | memory-manage skill | - -**模式**: -- **发现模式** (默认): 列出活动会话，提示用户 -- **自动模式** (`--auto`): 智能会话选择 -- **强制新建模式** (`--new`): 创建新会话 - ---- - -### /workflow:session:resume - -**描述**: 恢复最近暂停的工作流会话，自动发现会话并更新状态 - -**类别**: session-management - ---- - -### /workflow:session:complete - -**描述**: 标记活动工作流会话为完成，归档并记录经验教训，更新清单，移除活动标志 - -**参数**: `[-y|--yes] [--detailed]` - -**类别**: session-management - -**执行阶段**: -1. 查找会话 -2. 生成清单条目 -3. 原子提交 (移至归档) -4. 自动同步项目状态 - ---- - -### /workflow:session:list - -**描述**: 列出所有工作流会话，支持状态过滤，显示会话元数据和进度信息 - -**类别**: session-management - ---- - -### /workflow:session:sync - -**描述**: 快速同步会话工作到 specs/*.md 和 project-tech - -**参数**: `[-y|--yes] ["完成内容"]` - -**类别**: session-management - -**流程**: -1. 收集上下文 (git diff, session, summary) -2. 提取更新 (guidelines, tech) -3. 预览并确认 -4. 写入两个文件 - ---- - -### /workflow:session:solidify - -**描述**: 将会话学习成果和用户定义约束固化为永久项目指南，或压缩近期记忆 - -**参数**: `[-y|--yes] [--type <convention|constraint|learning|compress>] [--category <类别>] [--limit <N>] "规则或见解"` - -**类别**: session-management - -**类型类别**: - -| 类型 | 子类别 | -|------|---------------| -| convention | coding_style, naming_patterns, file_structure, documentation | -| constraint | architecture, tech_stack, performance, security | -| learning | architecture, performance, security, testing, process, other | -| compress | (操作核心记忆) | - ---- - -## 3. Issue 工作流命令 - -### /issue:new - -**描述**: 从 GitHub URL 或文本描述创建结构化 Issue - -**参数**: `[-y|--yes] <github-url | 文本描述> [--priority 1-5]` - -**类别**: issue - -**执行流程**: -1. 输入分析与清晰度检测 -2. 数据提取 (GitHub 或文本) -3. 轻量级上下文提示 (ACE 用于中等清晰度) -4. 条件性澄清 -5. GitHub 发布决策 -6. 创建 Issue - ---- - -### /issue:discover - -**描述**: 使用 CLI explore 从多视角发现潜在问题。支持 Exa 外部研究用于安全和最佳实践视角。 - -**参数**: `[-y|--yes] <路径模式> [--perspectives=bug,ux,...] [--external]` - -**类别**: issue - -**可用视角**: - -| 视角 | 关注点 | 类别 | -|-------------|-------|------------| -| bug | 潜在Bug | edge-case, null-check, resource-leak, race-condition | -| ux | 用户体验 | error-message, loading-state, feedback, accessibility | -| test | 测试覆盖 | missing-test, edge-case-test, integration-gap | -| quality | 代码质量 | complexity, duplication, naming, documentation | -| security | 安全问题 | injection, auth, encryption, input-validation | -| performance | 性能 | n-plus-one, memory-usage, caching, algorithm | -| maintainability | 可维护性 | coupling, cohesion, tech-debt, extensibility | -| best-practices | 最佳实践 | convention, pattern, framework-usage, anti-pattern | - ---- - -### /issue:plan - -**描述**: 使用 issue-plan-agent 批量规划 Issue 解决方案 (探索 + 计划闭环) - -**参数**: `[-y|--yes] --all-pending <issue-id>[,<issue-id>,...] [--batch-size 3]` - -**类别**: issue - -**执行过程**: -1. Issue 加载与智能分组 -2. 统一探索 + 规划 (issue-plan-agent) -3. 解决方案注册与绑定 -4. 汇总 - ---- - -### /issue:queue - -**描述**: 使用 issue-queue-agent 从绑定解决方案形成执行队列 (解决方案级别) - -**参数**: `[-y|--yes] [--queues <n>] [--issue <id>]` - -**类别**: issue - -**核心能力**: -- 代理驱动的排序逻辑 -- 解决方案级别粒度 -- 冲突澄清 -- 并行/顺序组分配 - ---- - -### /issue:execute - -**描述**: 使用基于 DAG 的并行编排执行队列 (每个解决方案一次提交) - -**参数**: `[-y|--yes] --queue <queue-id> [--worktree [<现有路径>]]` - -**类别**: issue - -**执行流程**: -1. 验证队列 ID (必需) -2. 获取 DAG 和用户选择 -3. 分发并行批次 (DAG 驱动) -4. 下一批次 (重复) -5. Worktree 完成 - -**推荐执行器**: Codex (2小时超时, 完整写入权限) - ---- - -### /issue:from-brainstorm - -**描述**: 将头脑风暴会话想法转换为带可执行解决方案的 Issue - -**参数**: `SESSION="<session-id>" [--idea=<index>] [--auto] [-y|--yes]` - -**类别**: issue - -**执行流程**: -1. 会话加载 -2. 想法选择 -3. 丰富 Issue 上下文 -4. 创建 Issue -5. 生成解决方案任务 -6. 绑定解决方案 - ---- - -## 4. IDAW 命令 - -### /idaw:run - -**描述**: IDAW 编排器 - 带 Git 检查点顺序执行任务技能链 - -**参数**: `[-y|--yes] [--task <id>[,<id>,...]] [--dry-run]` - -**类别**: idaw - -**技能链映射**: - -| 任务类型 | 技能链 | -|-----------|-------------| -| bugfix | workflow-lite-plan → workflow-test-fix | -| bugfix-hotfix | workflow-lite-plan | -| feature | workflow-lite-plan → workflow-test-fix | -| feature-complex | workflow-plan → workflow-execute → workflow-test-fix | -| refactor | workflow:refactor-cycle | -| tdd | workflow-tdd-plan → workflow-execute | -| test | workflow-test-fix | -| test-fix | workflow-test-fix | -| review | review-cycle | -| docs | workflow-lite-plan | - -**6阶段执行**: -1. 加载任务 -2. 会话设置 -3. 启动协议 -4. 主循环 (顺序，一次一个任务) -5. 检查点 (每个任务) -6. 报告 - ---- - -### /idaw:add - -**描述**: 添加任务到 IDAW 队列，自动推断任务类型和技能链 - -**类别**: idaw - ---- - -### /idaw:resume - -**描述**: 带崩溃恢复的 IDAW 会话恢复 - -**类别**: idaw - ---- - -### /idaw:status - -**描述**: 显示 IDAW 队列状态 - -**类别**: idaw - ---- - -### /idaw:run-coordinate - -**描述**: 带并行任务协调的多代理 IDAW 执行 - -**类别**: idaw - ---- - -## 5. With-File 工作流 - -### /workflow:brainstorm-with-file - -**描述**: 交互式头脑风暴，具有多 CLI 协作、想法扩展和文档化思维演进 - -**参数**: `[-y|--yes] [-c|--continue] [-m|--mode creative|structured] "想法或主题"` - -**类别**: with-file - -**输出目录**: `.workflow/.brainstorm/{session-id}/` - -**4阶段工作流**: -1. Phase 1: 种子理解 (解析主题, 选择角色, 扩展向量) -2. Phase 2: 发散探索 (cli-explore-agent + 多 CLI 视角) -3. Phase 3: 交互式精炼 (多轮) -4. Phase 4: 收敛与结晶 - -**输出产物**: -- `brainstorm.md` - 完整思维演进时间线 -- `exploration-codebase.json` - 代码库上下文 -- `perspectives.json` - 多 CLI 发现 -- `synthesis.json` - 最终综合 - ---- - -### /workflow:analyze-with-file - -**描述**: 交互式协作分析，具有文档化讨论、CLI 辅助探索和演进理解 - -**参数**: `[-y|--yes] [-c|--continue] "主题或问题"` - -**类别**: with-file - -**输出目录**: `.workflow/.analysis/{session-id}/` - -**4阶段工作流**: -1. Phase 1: 主题理解 -2. Phase 2: CLI 探索 (cli-explore-agent + 视角) -3. Phase 3: 交互式讨论 (多轮) -4. Phase 4: 综合与结论 - -**决策记录协议**: 必须记录方向选择、关键发现、假设变更、用户反馈 - ---- - -### /workflow:debug-with-file - -**描述**: 交互式假设驱动调试，具有文档化探索、理解演进和 Gemini 辅助纠正 - -**参数**: `[-y|--yes] "Bug 描述或错误信息"` - -**类别**: with-file - -**输出目录**: `.workflow/.debug/{session-id}/` - -**核心工作流**: 探索 → 文档 → 日志 → 分析 → 纠正理解 → 修复 → 验证 - -**输出产物**: -- `debug.log` - NDJSON 执行证据 -- `understanding.md` - 探索时间线 + 整合理解 -- `hypotheses.json` - 带结论的假设历史 - ---- - -### /workflow:collaborative-plan-with-file - -**描述**: 带 Plan Note 共享文档的多代理协作规划 - -**类别**: with-file - ---- - -### /workflow:roadmap-with-file - -**描述**: 战略需求路线图 → Issue 创建 → execution-plan.json - -**类别**: with-file - ---- - -### /workflow:unified-execute-with-file - -**描述**: 通用执行引擎 - 消费来自 collaborative-plan、roadmap、brainstorm 的计划输出 - -**类别**: with-file - ---- - -## 6. 循环工作流 - -### /workflow:integration-test-cycle - -**描述**: 带反思的自迭代集成测试 - 探索 → 测试开发 → 测试修复循环 → 反思 - -**类别**: cycle - -**输出目录**: `.workflow/.test-cycle/` - ---- - -### /workflow:refactor-cycle - -**描述**: 技术债务发现 → 优先级排序 → 执行 → 验证 - -**类别**: cycle - -**输出目录**: `.workflow/.refactor-cycle/` - ---- - -## 7. CLI 命令 - -### /cli:codex-review - -**描述**: 使用 Codex CLI 通过 ccw 端点进行交互式代码审查，支持可配置审查目标、模型和自定义指令 - -**参数**: `[--uncommitted|--base <分支>|--commit <sha>] [--model <模型>] [--title <标题>] [提示]` - -**类别**: cli - -**审查目标**: - -| 目标 | 标志 | 描述 | -|--------|------|-------------| -| 未提交更改 | `--uncommitted` | 审查已暂存、未暂存和未跟踪的更改 | -| 与分支比较 | `--base <BRANCH>` | 审查与基础分支的差异 | -| 特定提交 | `--commit <SHA>` | 审查提交引入的更改 | - -**关注领域**: 一般审查、安全重点、性能重点、代码质量 - -**重要**: 目标标志和提示互斥 - ---- - -### /cli:cli-init - -**描述**: 初始化 ccw 端点的 CLI 配置 - -**类别**: cli - ---- - -## 8. 记忆命令 - -### /memory:prepare - -**描述**: 为会话准备记忆上下文 - -**类别**: memory - ---- - -### /memory:style-skill-memory - -**描述**: 样式和技能记忆管理 - -**类别**: memory - ---- - -## 9. 团队技能 - -### 团队生命周期技能 - -| 技能 | 描述 | +| Field | Description | |-------|-------------| -| team-lifecycle | 带角色规格驱动工作代理的完整团队生命周期 | -| team-planex | 规划器 + 执行器波流水线 (用于大批量 Issue 或路线图输出) | -| team-coordinate | 团队协调和编排 | -| team-executor | 带工作代理的任务执行 | -| team-arch-opt | 架构优化技能 | +| **Who** | Developer starting any task | +| **When** | Entry point for workflow orchestration | +| **What** | Main workflow orchestrator that analyzes intent, dispatches to appropriate skill chain. Example: `/ccw "implement user authentication"` | +| **How** | Parses intent -> Selects skill chain -> Executes orchestrator | +| **Output** | Delegates to workflow-plan, issue-manage, or other skills | +| **Done** | Appropriate skill completes execution | +| **Failure & Recovery** | Fallback to manual skill selection if intent unclear | +| **Impact & Boundary** | Project-wide orchestration entry point | -### 团队领域技能 +#### `/ccw-coordinator` -| 技能 | 描述 | +| Field | Description | |-------|-------------| -| team-brainstorm | 多视角头脑风暴 | -| team-review | 代码审查工作流 | -| team-testing | 测试工作流 | -| team-frontend | 前端开发工作流 | -| team-issue | Issue 管理工作流 | -| team-iterdev | 迭代开发工作流 | -| team-perf-opt | 性能优化工作流 | -| team-quality-assurance | QA 工作流 | -| team-roadmap-dev | 路线图开发工作流 | -| team-tech-debt | 技术债务管理 | -| team-uidesign | UI 设计工作流 | -| team-ultra-analyze | 深度分析工作流 | +| **Who** | System needing command orchestration | +| **When** | Multi-command coordination required | +| **What** | Command orchestration tool that analyzes requirements and dispatches commands. Example: `/ccw-coordinator "review and fix auth module"` | +| **How** | Requirement analysis -> Command selection -> Sequential execution | +| **Output** | Coordinated command execution results | +| **Done** | All dispatched commands complete | +| **Failure & Recovery** | Partial results preserved, user notified of failures | +| **Impact & Boundary** | Cross-command coordination | ---- +#### `/flow-create` -## 10. 工作流技能 - -| 技能 | 内部流水线 | 描述 | -|-------|-------------------|-------------| -| workflow-lite-plan | explore → plan → confirm → execute | 轻量级合并模式规划 | -| workflow-plan | session → context → convention → gen → verify/replan | 带架构设计的完整规划 | -| workflow-execute | session discovery → task processing → commit | 从规划会话执行 | -| workflow-tdd-plan | 6阶段 TDD plan → verify | TDD 工作流规划 | -| workflow-test-fix | session → context → analysis → gen → cycle | 测试生成与修复循环 | -| workflow-multi-cli-plan | ACE context → CLI discussion → plan → execute | 多 CLI 协作规划 | -| workflow-skill-designer | - | 工作流技能设计和生成 | - ---- - -## 11. 实用技能 - -| 技能 | 描述 | +| Field | Description | |-------|-------------| -| brainstorm | 统一头脑风暴技能 (自动并行 + 角色分析) | -| review-code | 代码审查技能 | -| review-cycle | 会话/模块审查 → 修复编排 | -| spec-generator | 产品简介 → PRD → 架构 → Epics | -| skill-generator | 生成新技能 | -| skill-tuning | 调优现有技能 | -| command-generator | 生成新命令 | -| memory-capture | 捕获会话记忆 | -| memory-manage | 管理存储的记忆 | -| issue-manage | Issue 管理工具 | -| ccw-help | CCW 帮助和文档 | +| **Who** | Developer creating reusable workflow templates | +| **When** | Need to document and share workflow patterns | +| **What** | Flow template generator for creating reusable command chains. Example: `/flow-create "auth-feature-flow"` | +| **How** | Template definition -> Parameter extraction -> Flow file generation | +| **Output** | Flow template file in `.claude/flows/` | +| **Done** | Template file created and validated | +| **Failure & Recovery** | Validation errors show specific issues | +| **Impact & Boundary** | Workflow template creation only | --- -## 12. Codex 能力 +### DDD (Document-Driven Development) -### Codex 审查模式 +#### `/ddd:scan` -**命令**: `ccw cli --tool codex --mode review [选项]` +| Field | Description | +|-------|-------------| +| **Who** | Developer onboarding to existing project without specs | +| **When** | Starting doc-driven workflow on legacy codebase | +| **What** | Scans codebase to build doc-index by reverse-engineering structure. Example: `/ddd:scan -y "existing project"` | +| **How** | Framework detection -> Component discovery -> Feature inference -> Requirement extraction -> doc-index.json | +| **Output** | `.workflow/.doc-index/doc-index.json` + feature-maps/ + tech-registry/ | +| **Done** | doc-index.json created with components, features, IREQ entries | +| **Failure & Recovery** | Graceful degradation if DeepWiki unavailable | +| **Impact & Boundary** | Code-first entry point, can upgrade to spec-first later | -| 选项 | 描述 | -|--------|-------------| -| `[提示]` | 自定义审查指令 (位置参数, 无目标标志) | -| `-c model=<模型>` | 通过配置覆盖模型 | -| `--uncommitted` | 审查已暂存、未暂存和未跟踪的更改 | -| `--base <BRANCH>` | 审查与基础分支的差异 | -| `--commit <SHA>` | 审查提交引入的更改 | -| `--title <TITLE>` | 可选的提交标题用于审查摘要 | +#### `/ddd:index-build` -**可用模型**: -- 默认: gpt-5.2 -- o3: OpenAI o3 推理模型 -- gpt-4.1: GPT-4.1 模型 -- o4-mini: OpenAI o4-mini (更快) +| Field | Description | +|-------|-------------| +| **Who** | Developer with existing spec-generator outputs | +| **When** | Building index from REQ, ADR, EPIC documents | +| **What** | Builds doc-index from spec outputs and maps entities to code. Example: `/ddd:index-build --spec SPEC-auth-2026-03-08` | +| **How** | Parse specs -> Codebase mapping via CLI -> Feature grouping -> doc-index.json | +| **Output** | `.workflow/.doc-index/doc-index.json` with spec-first traceability | +| **Done** | All spec entities linked to code components | +| **Failure & Recovery** | Orphan components flagged for review | +| **Impact & Boundary** | Spec-first entry point, merges with existing code-first index | -**约束**: -- 目标标志 (`--uncommitted`, `--base`, `--commit`) **不能**与位置参数 `[提示]` 一起使用 -- 自定义提示仅支持不带目标标志的情况 (默认审查未提交更改) +#### `/ddd:plan` -### Codex 集成点 +| Field | Description | +|-------|-------------| +| **Who** | Developer planning document-driven task | +| **When** | Before any development task in DDD workflow | +| **What** | Queries doc-index, explores codebase with doc-aware angles, produces plan.json. Example: `/ddd:plan -y "add rate limiting"` | +| **How** | Doc-index query -> Guided exploration -> Clarification -> Task planning -> Handoff | +| **Output** | `.workflow/.doc-index/planning/{session}/plan.json` + TASK-*.json | +| **Done** | Plan with doc_context traceability generated | +| **Failure & Recovery** | Schema version mismatch warns but continues | +| **Impact & Boundary** | Requires existing doc-index.json | -| 集成点 | 描述 | -|-------------------|-------------| -| CLI 端点 | `ccw cli --tool codex --mode <analysis\|write\|review>` | -| 多 CLI 规划 | workflow-multi-cli-plan 中的务实视角 | -| 代码审查 | `/cli:codex-review` 命令 | -| Issue 执行 | `/issue:execute` 的推荐执行器 | -| 魔鬼代言人 | 头脑风暴精炼中的挑战模式 | +#### `/ddd:execute` -### Codex 模式汇总 +| Field | Description | +|-------|-------------| +| **Who** | Developer executing document-aware tasks | +| **When** | After /ddd:plan produces plan.json | +| **What** | Document-aware execution engine with doc-context loading. Example: `/ddd:execute --in-memory` | +| **How** | Load plan -> Read doc-context -> Execute task -> Update doc-index | +| **Output** | Code changes + updated doc-index traceability | +| **Done** | All tasks executed, doc-index updated | +| **Failure & Recovery** | Task failures logged, recovery options presented | +| **Impact & Boundary** | Requires plan.json from /ddd:plan | -| 模式 | 权限 | 用例 | -|------|------------|----------| -| analysis | 只读 | 代码分析、架构审查 | -| write | 完整访问 | 实现、文件修改 | -| review | 只读输出 | Git 感知的代码审查 | +#### `/ddd:doc-generate` + +| Field | Description | +|-------|-------------| +| **Who** | Developer regenerating documentation | +| **When** | After doc-index built or needs refresh | +| **What** | Generates full document tree from doc-index.json. Example: `/ddd:doc-generate --force --layer all` | +| **How** | Layer 3 (components) -> Layer 2 (features) -> Layer 1 (indexes) | +| **Output** | tech-registry/*.md, feature-maps/*.md, README.md, ARCHITECTURE.md | +| **Done** | All layers generated, SCHEMA.md created | +| **Failure & Recovery** | Existing docs warning, --force to overwrite | +| **Impact & Boundary** | Read-only from doc-index, generates MD files | + +#### `/ddd:doc-refresh` + +| Field | Description | +|-------|-------------| +| **Who** | Developer after incremental code changes | +| **When** | Code changed, need targeted doc updates | +| **What** | Incrementally updates affected documents after code changes. Example: `/ddd:doc-refresh -y` | +| **How** | Detect changed files -> Find affected docs -> Regenerate only affected | +| **Output** | Updated subset of documentation files | +| **Done** | Affected docs updated, unchanged docs preserved | +| **Failure & Recovery** | Falls back to full regeneration if detection fails | +| **Impact & Boundary** | Incremental update, more efficient than full regenerate | + +#### `/ddd:sync` + +| Field | Description | +|-------|-------------| +| **Who** | Developer after task completion | +| **When** | Post-task synchronization to update index | +| **What** | Post-task synchronization updates doc-index with completed work. Example: `/ddd:sync -y "auth feature complete"` | +| **How** | Detect changes -> Update components -> Update requirements status -> Add action log | +| **Output** | Updated doc-index.json with action entries | +| **Done** | Index reflects current codebase state | +| **Failure & Recovery** | Merge conflicts resolved automatically | +| **Impact & Boundary** | Post-execution sync only | + +#### `/ddd:update` + +| Field | Description | +|-------|-------------| +| **Who** | Developer maintaining doc-index | +| **When** | Detecting drift between code and docs | +| **What** | Incremental index update detecting code changes. Example: `/ddd:update --scope src/auth` | +| **How** | File hash comparison -> Detect changes -> Update affected entries | +| **Output** | Updated doc-index.json entries | +| **Done** | Index entries match current code | +| **Failure & Recovery** | Unchanged files skipped | +| **Impact & Boundary** | Lightweight incremental update | + +#### `/ddd:auto` + +| Field | Description | +|-------|-------------| +| **Who** | Developer wanting full automation | +| **When** | Quick feature implementation with docs | +| **What** | Chain command for automated DDD workflow. Example: `/ddd:auto -y "implement search feature"` | +| **How** | plan -> execute -> sync in single command | +| **Output** | Complete implementation + updated docs | +| **Done** | Feature implemented and documented | +| **Failure & Recovery** | Stops at first failing phase | +| **Impact & Boundary** | Full automation, less control | --- -## 统计汇总 +### Issue -| 类别 | 数量 | -|----------|-------| -| 主编排器命令 | 3 | -| 工作流会话命令 | 6 | -| Issue 工作流命令 | 6 | -| IDAW 命令 | 5 | -| With-File 工作流 | 6 | -| 循环工作流 | 2 | -| CLI 命令 | 2 | -| 记忆命令 | 2 | -| 团队技能 | 17 | -| 工作流技能 | 7 | -| 实用技能 | 11 | -| **命令总数** | 32 | -| **技能总数** | 35 | +#### `/issue:new` + +| Field | Description | +|-------|-------------| +| **Who** | Developer creating structured issue | +| **When** | Starting issue tracking for a task | +| **What** | Creates structured issue from GitHub URL or description. Example: `/issue:new "Fix login timeout bug"` | +| **How** | Parse input -> Structure issue -> Create in issues.jsonl | +| **Output** | Issue entry in `.workflow/issues/issues.jsonl` | +| **Done** | Issue created with status "registered" | +| **Failure & Recovery** | Duplicate detection warns user | +| **Impact & Boundary** | Issue creation only, no planning | + +#### `/issue:discover` + +| Field | Description | +|-------|-------------| +| **Who** | Developer finding potential issues | +| **When** | Starting issue management workflow | +| **What** | Discovers potential issues from multiple sources. Example: `/issue:discover --scope src/auth` | +| **How** | Scan codebase -> Detect patterns -> Generate issue candidates | +| **Output** | List of discovered issue candidates | +| **Done** | Candidates presented for user selection | +| **Failure & Recovery** | Empty results suggest manual creation | +| **Impact & Boundary** | Discovery only, no automatic creation | + +#### `/issue:discover-by-prompt` + +| Field | Description | +|-------|-------------| +| **Who** | Developer with natural language query | +| **When** | Finding issues via description | +| **What** | Discovers issues from user prompt with Gemini analysis. Example: `/issue:discover-by-prompt "authentication problems"` | +| **How** | Gemini analysis -> Pattern matching -> Issue suggestions | +| **Output** | Issue candidates matching prompt | +| **Done** | Candidates presented for confirmation | +| **Failure & Recovery** | Falls back to keyword search | +| **Impact & Boundary** | Natural language discovery | + +#### `/issue:from-brainstorm` + +| Field | Description | +|-------|-------------| +| **Who** | Developer converting ideas to issues | +| **When** | After brainstorm session | +| **What** | Converts brainstorm session ideas into issues. Example: `/issue:from-brainstorm BRAIN-2026-03-08` | +| **How** | Parse brainstorm -> Extract actionables -> Create issues | +| **Output** | Multiple issues from brainstorm artifacts | +| **Done** | All actionables converted to issues | +| **Failure & Recovery** | Partial conversion on parse errors | +| **Impact & Boundary** | Requires completed brainstorm session | + +#### `/issue:plan` + +| Field | Description | +|-------|-------------| +| **Who** | Developer planning issue resolution | +| **When** | Issue registered, needs solution | +| **What** | Batch plans issue resolution using issue-planning-agent. Example: `/issue:plan ISS-001 ISS-002` | +| **How** | Load issues -> Generate solutions -> Bind to issues | +| **Output** | Solution files in `.workflow/issues/solutions/` | +| **Done** | Issues have bound solutions | +| **Failure & Recovery** | Partial planning on complex issues | +| **Impact & Boundary** | Planning only, no execution | + +#### `/issue:queue` + +| Field | Description | +|-------|-------------| +| **Who** | Developer forming execution queue | +| **When** | Solutions planned, ready to execute | +| **What** | Forms execution queue from bound solutions. Example: `/issue:queue ISS-001 ISS-002` | +| **How** | Build DAG -> Resolve dependencies -> Create queue | +| **Output** | Queue file in `.workflow/issues/queues/` | +| **Done** | Queue ready for execution | +| **Failure & Recovery** | Circular dependency detection | +| **Impact & Boundary** | Queue formation only | + +#### `/issue:execute` + +| Field | Description | +|-------|-------------| +| **Who** | Developer executing queued issues | +| **When** | Queue formed, ready to run | +| **What** | Executes queue with DAG-based parallel orchestration. Example: `/issue:execute -y` | +| **How** | DAG traversal -> Parallel execution -> Progress tracking | +| **Output** | Task execution results, code changes | +| **Done** | All queued tasks completed | +| **Failure & Recovery** | Failed tasks skipped, dependents notified | +| **Impact & Boundary** | Execution engine for issue workflow | + +#### `/issue:convert-to-plan` + +| Field | Description | +|-------|-------------| +| **Who** | Developer with existing planning artifacts | +| **When** | Converting lite-plan or brainstorm to issue | +| **What** | Converts planning artifacts to issue format. Example: `/issue:convert-to-plan plan.json` | +| **How** | Parse artifact -> Extract tasks -> Create issue + solution | +| **Output** | Issue and solution from plan | +| **Done** | Plan converted to trackable issue | +| **Failure & Recovery** | Partial conversion preserved | +| **Impact & Boundary** | Artifact conversion only | --- -## 调用模式 +### IDAW (Iterative Development Automation Workflow) -### 斜杠命令调用 +#### `/idaw:status` + +| Field | Description | +|-------|-------------| +| **Who** | Developer checking IDAW progress | +| **When** | During IDAW session | +| **What** | Views IDAW task and session progress. Example: `/idaw:status` | +| **How** | Read session state -> Display progress | +| **Output** | Status summary of active IDAW session | +| **Done** | Status displayed | +| **Failure & Recovery** | No active session message | +| **Impact & Boundary** | Read-only status check | + +#### `/idaw:add` + +| Field | Description | +|-------|-------------| +| **Who** | Developer adding IDAW tasks | +| **When** | Building IDAW task list | +| **What** | Adds IDAW tasks via manual creation or import. Example: `/idaw:add "Implement caching layer"` | +| **How** | Parse input -> Create task entry -> Add to session | +| **Output** | Task added to IDAW session | +| **Done** | Task registered in session | +| **Failure & Recovery** | Duplicate task warning | +| **Impact & Boundary** | Task creation only | + +#### `/idaw:run` + +| Field | Description | +|-------|-------------| +| **Who** | Developer starting IDAW execution | +| **When** | Tasks added, ready to run | +| **What** | IDAW orchestrator executing task skill chain. Example: `/idaw:run -y` | +| **How** | Task dispatch -> Skill execution -> Progress tracking | +| **Output** | Task execution results | +| **Done** | All tasks processed | +| **Failure & Recovery** | Failed tasks logged, continue others | +| **Impact & Boundary** | Main IDAW execution engine | + +#### `/idaw:run-coordinate` + +| Field | Description | +|-------|-------------| +| **Who** | Developer needing coordinated execution | +| **When** | Complex multi-task IDAW session | +| **What** | IDAW coordinator executing task skill chain. Example: `/idaw:run-coordinate` | +| **How** | Coordinate multiple task executions -> Handle dependencies | +| **Output** | Coordinated execution results | +| **Done** | All coordinated tasks complete | +| **Failure & Recovery** | Dependency failures handled | +| **Impact & Boundary** | Coordinated execution mode | + +#### `/idaw:resume` + +| Field | Description | +|-------|-------------| +| **Who** | Developer resuming interrupted IDAW | +| **When** | IDAW session interrupted | +| **What** | Resumes interrupted IDAW session from last checkpoint. Example: `/idaw:resume` | +| **How** | Load state -> Resume from checkpoint -> Continue execution | +| **Output** | Continued execution from interruption point | +| **Done** | Session completes | +| **Failure & Recovery** | Checkpoint validation on load | +| **Impact & Boundary** | Resume capability for IDAW | + +--- + +### Workflow + +#### `/workflow:session:start` + +| Field | Description | +|-------|-------------| +| **Who** | Developer starting workflow session | +| **When** | Beginning any workflow work | +| **What** | Discovers or starts workflow session with conflict detection. Example: `/workflow:session:start --auto "implement OAuth2"` | +| **How** | Check active -> Detect conflicts -> Create/reuse session | +| **Output** | `SESSION_ID: WFS-{slug}` | +| **Done** | Session ready for work | +| **Failure & Recovery** | Multiple sessions warning | +| **Impact & Boundary** | Session initialization, calls /workflow:spec:setup if needed | + +#### `/workflow:session:list` + +| Field | Description | +|-------|-------------| +| **Who** | Developer reviewing sessions | +| **When** | Checking available sessions | +| **What** | Lists all workflow sessions with status filtering. Example: `/workflow:session:list --status active` | +| **How** | Scan .workflow/active -> Parse session metadata -> Display | +| **Output** | Session list with status, dates | +| **Done** | List displayed | +| **Failure & Recovery** | Empty list if no sessions | +| **Impact & Boundary** | Read-only listing | + +#### `/workflow:session:sync` + +| Field | Description | +|-------|-------------| +| **Who** | Developer syncing session work | +| **When** | After completing work in session | +| **What** | Quick-sync session work to specs/*.md and project-tech. Example: `/workflow:session:sync -y "auth complete"` | +| **How** | Gather context -> Extract updates -> Write specs + project-tech | +| **Output** | Updated specs/*.md and project-tech.json | +| **Done** | Sync complete message | +| **Failure & Recovery** | Duplicate rules skipped silently | +| **Impact & Boundary** | Updates project guidelines | + +#### `/workflow:session:resume` + +| Field | Description | +|-------|-------------| +| **Who** | Developer resuming paused session | +| **When** | Returning to paused work | +| **What** | Resumes most recently paused workflow session. Example: `/workflow:session:resume` | +| **How** | Find paused session -> Load state -> Continue | +| **Output** | Session context restored | +| **Done** | Ready to continue work | +| **Failure & Recovery** | No paused session error | +| **Impact & Boundary** | Session resumption | + +#### `/workflow:session:complete` + +| Field | Description | +|-------|-------------| +| **Who** | Developer finishing session | +| **When** | Session work complete | +| **What** | Archives completed session and removes from active. Example: `/workflow:session:complete -y` | +| **How** | Finalize state -> Archive -> Remove from active | +| **Output** | Archived session in .workflow/archived/ | +| **Done** | Session archived, specs updated | +| **Failure & Recovery** | Pending tasks warning | +| **Impact & Boundary** | Session finalization | + +#### `/workflow:spec:setup` + +| Field | Description | +|-------|-------------| +| **Who** | Developer initializing project specs | +| **When** | First time setup or regenerating | +| **What** | Initializes project-level state via cli-explore-agent analysis. Example: `/workflow:spec:setup --regenerate` | +| **How** | cli-explore-agent -> Generate project-tech.json -> Interactive questionnaire -> Write specs | +| **Output** | `.workflow/project-tech.json` + `.ccw/specs/*.md` | +| **Done** | Project specs configured | +| **Failure & Recovery** | Agent failure falls back to basic init | +| **Impact & Boundary** | Project-level initialization | + +#### `/workflow:spec:add` + +| Field | Description | +|-------|-------------| +| **Who** | Developer adding project rules | +| **When** | Adding conventions, constraints, or learnings | +| **What** | Adds specs, conventions, constraints to project guidelines. Example: `/workflow:spec:add -y "Use functional components"` | +| **How** | Parse input -> Auto-detect type -> Append to spec file | +| **Output** | Updated spec file in .ccw/specs/ | +| **Done** | Rule added confirmation | +| **Failure & Recovery** | Duplicate detection | +| **Impact & Boundary** | Single rule addition | + +#### `/workflow:clean` + +| Field | Description | +|-------|-------------| +| **Who** | Developer cleaning code | +| **When** | Before commits or after refactoring | +| **What** | Intelligent code cleanup with mainline detection. Example: `/workflow:clean -y` | +| **How** | Detect unused -> Remove dead code -> Format | +| **Output** | Cleaned code files | +| **Done** | Cleanup report displayed | +| **Failure & Recovery** | Preserves files with unclear usage | +| **Impact & Boundary** | Code cleanup only | + +#### `/workflow:debug-with-file` + +| Field | Description | +|-------|-------------| +| **Who** | Developer debugging issues | +| **When** | Encountering bugs or errors | +| **What** | Interactive hypothesis-driven debugging with file output. Example: `/workflow:debug-with-file "login fails on timeout"` | +| **How** | Hypothesis generation -> Evidence collection -> Validation -> Fix | +| **Output** | Debug report + potential fixes | +| **Done** | Root cause identified or fix applied | +| **Failure & Recovery** | Multiple hypothesis iteration | +| **Impact & Boundary** | Debugging workflow | + +#### `/workflow:analyze-with-file` + +| Field | Description | +|-------|-------------| +| **Who** | Developer analyzing code | +| **When** | Understanding codebase or issues | +| **What** | Interactive collaborative analysis with multi-CLI support. Example: `/workflow:analyze-with-file "analyze auth flow"` | +| **How** | Discovery -> Analysis -> Synthesis -> Report | +| **Output** | Analysis report in session folder | +| **Done** | Analysis complete with insights | +| **Failure & Recovery** | Partial analysis on errors | +| **Impact & Boundary** | Analysis workflow | + +#### `/workflow:brainstorm-with-file` + +| Field | Description | +|-------|-------------| +| **Who** | Developer exploring solutions | +| **When** | Starting new feature or solving complex problem | +| **What** | Interactive brainstorming with multi-CLI support. Example: `/workflow:brainstorm-with-file "caching strategy"` | +| **How** | Multi-perspective analysis -> Idea synthesis -> Recommendations | +| **Output** | Brainstorm report with actionables | +| **Done** | Ideas documented and prioritized | +| **Failure & Recovery** | Partial results preserved | +| **Impact & Boundary** | Ideation workflow | + +#### `/workflow:collaborative-plan-with-file` + +| Field | Description | +|-------|-------------| +| **Who** | Developer planning collaboratively | +| **When** | Complex feature planning | +| **What** | Collaborative planning with Plan Note output. Example: `/workflow:collaborative-plan-with-file "user dashboard redesign"` | +| **How** | Context gathering -> Planning -> Plan Note generation | +| **Output** | Plan with structured notes | +| **Done** | Plan ready for execution | +| **Failure & Recovery** | Iterative refinement | +| **Impact & Boundary** | Planning workflow | + +#### `/workflow:integration-test-cycle` + +| Field | Description | +|-------|-------------| +| **Who** | Developer running integration tests | +| **When** | After implementation, before merge | +| **What** | Self-iterating integration test workflow with reflection log. Example: `/workflow:integration-test-cycle -y "test auth flow"` | +| **How** | Generate tests -> Execute -> Reflect -> Iterate until pass | +| **Output** | Passing tests + reflection-log.md | +| **Done** | All tests passing | +| **Failure & Recovery** | Reflection-driven adjustment loop | +| **Impact & Boundary** | Integration testing workflow | + +#### `/workflow:refactor-cycle` + +| Field | Description | +|-------|-------------| +| **Who** | Developer addressing tech debt | +| **When** | Systematic code improvement | +| **What** | Tech debt discovery and self-iterating refactoring. Example: `/workflow:refactor-cycle -y "src/auth module"` | +| **How** | Debt discovery -> Prioritization -> Refactor -> Validate -> Reflect | +| **Output** | reflection-log.md + state.json + code changes | +| **Done** | All queued debt items processed | +| **Failure & Recovery** | Per-item validation with rollback | +| **Impact & Boundary** | Tech debt lifecycle management | + +#### `/workflow:roadmap-with-file` + +| Field | Description | +|-------|-------------| +| **Who** | Developer planning strategic requirements | +| **When** | Large feature or project planning | +| **What** | Strategic requirement roadmap with iterative decomposition. Example: `/workflow:roadmap-with-file -y "implement auth system"` | +| **How** | Understand -> Decompose -> Iterate -> Validate -> Handoff | +| **Output** | roadmap.md + issues.jsonl | +| **Done** | Roadmap approved, issues ready | +| **Failure & Recovery** | Max iteration rounds force proceed | +| **Impact & Boundary** | Strategic planning workflow | + +#### `/workflow:unified-execute-with-file` + +| Field | Description | +|-------|-------------| +| **Who** | Developer executing plans | +| **When** | After planning, ready to implement | +| **What** | Universal execution engine for any planning output. Example: `/workflow:unified-execute-with-file -y plan.json` | +| **How** | Load plan -> Validate -> Wave execution -> Track progress | +| **Output** | Code changes + execution-events.md | +| **Done** | All tasks executed | +| **Failure & Recovery** | Per-task retry with rollback | +| **Impact & Boundary** | Universal execution engine | + +#### UI Design Commands + +| Command | Who | When | What | Output | +|---------|-----|------|------|--------| +| `/workflow:ui-design:explore-auto` | Designer/Developer | Starting UI design | Interactive exploratory workflow | Style variants + layout templates + prototypes | +| `/workflow:ui-design:imitate-auto` | Designer/Developer | Imitating reference | UI design imitation workflow | Prototypes matching reference style | +| `/workflow:ui-design:generate` | Designer/Developer | Assembling prototypes | Pure assembler combining layouts + tokens | HTML/CSS prototypes | +| `/workflow:ui-design:style-extract` | Designer/Developer | Extracting styles | Extract design tokens from images | design-tokens.json + style-guide.md | +| `/workflow:ui-design:layout-extract` | Designer/Developer | Extracting layouts | Extract layout templates | layout-*.json files | +| `/workflow:ui-design:animation-extract` | Designer/Developer | Extracting animations | Extract animation patterns | animation-tokens.json | +| `/workflow:ui-design:codify-style` | Developer | From code to design | Extract styles from code files | Design tokens from CSS/SCSS | +| `/workflow:ui-design:import-from-code` | Developer | Code-based design | Import design from existing code | Design system from codebase | +| `/workflow:ui-design:design-sync` | Designer | Syncing design | Synchronize design references | Updated design system docs | +| `/workflow:ui-design:reference-page-generator` | Developer | Reference docs | Generate component reference pages | Multi-component reference pages | + +--- + +### Memory + +#### `/memory:prepare` + +| Field | Description | +|-------|-------------| +| **Who** | Developer preparing memory capture | +| **When** | Before capturing session knowledge | +| **What** | Delegates to universal-executor agent to prepare memory. Example: `/memory:prepare "auth session"` | +| **How** | Context gathering -> Memory structure preparation | +| **Output** | Prepared memory structure | +| **Done** | Ready for memory capture | +| **Failure & Recovery** | Agent failure handled | +| **Impact & Boundary** | Memory preparation only | + +#### `/memory:style-skill-memory` + +| Field | Description | +|-------|-------------| +| **Who** | Developer documenting style knowledge | +| **When** | After learning project patterns | +| **What** | Generates SKILL memory package from style patterns. Example: `/memory:style-skill-memory "React patterns"` | +| **How** | Pattern extraction -> Skill memory generation | +| **Output** | SKILL memory package | +| **Done** | Skill memory documented | +| **Failure & Recovery** | Partial patterns preserved | +| **Impact & Boundary** | Style-specific memory | + +--- + +### CLI + +#### `/cli:codex-review` + +| Field | Description | +|-------|-------------| +| **Who** | Developer reviewing code | +| **When** | Code review needed | +| **What** | Interactive code review using Codex CLI. Example: `/cli:codex-review --uncommitted` | +| **How** | Codex CLI -> Review analysis -> Interactive feedback | +| **Output** | Code review report | +| **Done** | Review complete with recommendations | +| **Failure & Recovery** | Codex unavailability fallback | +| **Impact & Boundary** | Git-aware code review | + +#### `/cli:cli-init` + +| Field | Description | +|-------|-------------| +| **Who** | Developer setting up CLI config | +| **When** | First time setup | +| **What** | Generates .gemini/ and .qwen/ config directories. Example: `/cli:cli-init` | +| **How** | Create directories -> Generate default configs | +| **Output** | CLI configuration directories | +| **Done** | Configs ready for customization | +| **Failure & Recovery** | Existing configs preserved | +| **Impact & Boundary** | CLI configuration setup | + +--- + +## Section 2: Skills + +### Workflow Skills + +#### `workflow-plan` + +| Field | Description | +|-------|-------------| +| **Who** | Developer planning tasks | +| **When** | Starting any planned work | +| **What** | Unified 4-phase planning: session discovery -> context gathering -> conflict resolution -> task generation | +| **How** | Phase 0: Session -> Phase 1: Context -> Phase 2: Conflicts -> Phase 3: Tasks | +| **Output** | plan.json + TASK-*.json in session folder | +| **Done** | Plan with TodoWrite tracking complete | +| **Failure & Recovery** | Conflict resolution prompts user | +| **Impact & Boundary** | Core planning skill | + +#### `workflow-execute` + +| Field | Description | +|-------|-------------| +| **Who** | Developer executing planned tasks | +| **When** | After workflow-plan | +| **What** | Agent execution orchestration with lazy task loading, auto-commit | +| **How** | Load plan -> Spawn agents -> Execute -> Commit | +| **Output** | Code changes + task completion status | +| **Done** | All tasks executed or user-stopped | +| **Failure & Recovery** | Per-task retry, auto-rollback | +| **Impact & Boundary** | Core execution skill | + +#### `workflow-lite-plan` + +| Field | Description | +|-------|-------------| +| **Who** | Developer needing quick planning | +| **When** | Simple tasks without full session | +| **What** | Lightweight planning - task analysis + breakdown | +| **How** | Analyze -> Break down -> Generate tasks | +| **Output** | Simplified plan.json | +| **Done** | Quick plan ready | +| **Failure & Recovery** | Falls back to workflow-plan for complex cases | +| **Impact & Boundary** | Lightweight alternative | + +#### `workflow-lite-execute` + +| Field | Description | +|-------|-------------| +| **Who** | Developer executing simple plans | +| **When** | After lite-plan or standalone | +| **What** | Lightweight execution engine - multi-model collaboration | +| **How** | Load tasks -> Execute -> Verify | +| **Output** | Code changes | +| **Done** | Tasks completed | +| **Failure & Recovery** | Simple retry mechanism | +| **Impact & Boundary** | Lightweight alternative | + +#### `workflow-tdd-plan` + +| Field | Description | +|-------|-------------| +| **Who** | Developer using TDD approach | +| **When** | Test-driven development | +| **What** | TDD workflow combining 6-phase planning with test-first | +| **How** | Plan tests -> Write tests -> Implement -> Verify | +| **Output** | Tests + implementation | +| **Done** | All tests passing | +| **Failure & Recovery** | Test failure iteration | +| **Impact & Boundary** | TDD-specific workflow | + +#### `workflow-test-fix` + +| Field | Description | +|-------|-------------| +| **Who** | Developer fixing test failures | +| **When** | Tests failing | +| **What** | Test-fix pipeline combining test runner with fix agent | +| **How** | Run tests -> Identify failures -> Fix -> Re-run | +| **Output** | Passing tests | +| **Done** | All tests pass | +| **Failure & Recovery** | Iterative fix loop | +| **Impact & Boundary** | Test fixing workflow | + +#### `workflow-multi-cli-plan` + +| Field | Description | +|-------|-------------| +| **Who** | Developer using multiple CLIs | +| **When** | Complex multi-perspective planning | +| **What** | Multi-CLI collaborative planning with ACE integration | +| **How** | Parallel CLI analysis -> Merge perspectives -> Generate plan | +| **Output** | Comprehensive plan from multiple models | +| **Done** | Merged plan complete | +| **Failure & Recovery** | Partial results merged | +| **Impact & Boundary** | Multi-model planning | + +#### `workflow-skill-designer` + +| Field | Description | +|-------|-------------| +| **Who** | Developer creating skills | +| **When** | Building new workflow skills | +| **What** | Meta-skill for designing orchestrator+phase skills | +| **How** | Design -> Template -> Generate skill files | +| **Output** | New skill SKILL.md + phases | +| **Done** | Skill ready for use | +| **Failure & Recovery** | Validation errors guide fixes | +| **Impact & Boundary** | Skill meta-creation | + +--- + +### Team Skills + +#### `team-coordinate` + +| Field | Description | +|-------|-------------| +| **Who** | Developer coordinating multi-agent work | +| **When** | Complex multi-role tasks | +| **What** | Universal team coordination with dynamic role generation | +| **How** | Analyze task -> Generate role-specs -> Dispatch workers -> Execute -> Deliver | +| **Output** | Coordinated multi-agent results | +| **Done** | Pipeline complete, artifacts delivered | +| **Failure & Recovery** | Role regeneration on capability gaps | +| **Impact & Boundary** | Universal team orchestrator | + +#### `team-edict` + +| Field | Description | +|-------|-------------| +| **Who** | Developer using Edict architecture | +| **When** | Large-scale multi-agent coordination | +| **What** | Three-Six Ministry multi-agent framework replicating Edict architecture | +| **How** | Ministry-based role assignment -> Task dispatch -> Report aggregation | +| **Output** | Comprehensive multi-role deliverables | +| **Done** | All ministries report complete | +| **Failure & Recovery** | Ministry-level retry | +| **Impact & Boundary** | Large-scale coordination | + +#### `team-planex` + +| Field | Description | +|-------|-------------| +| **Who** | Developer planning and executing | +| **When** | Plan-and-execute workflow | +| **What** | Unified team skill for plan-and-execute team | +| **How** | Plan -> Execute -> Verify | +| **Output** | Planned and executed work | +| **Done** | Plan executed completely | +| **Failure & Recovery** | Plan adjustment on failures | +| **Impact & Boundary** | Plan-execute team | + +#### `team-frontend` + +| Field | Description | +|-------|-------------| +| **Who** | Frontend developer | +| **When** | Frontend development work | +| **What** | Unified team skill for frontend development | +| **How** | Component design -> Implementation -> Testing | +| **Output** | Frontend components and features | +| **Done** | Frontend work complete | +| **Failure & Recovery** | Component-level retry | +| **Impact & Boundary** | Frontend-specific team | + +#### `team-frontend-debug` + +| Field | Description | +|-------|-------------| +| **Who** | Frontend developer debugging | +| **When** | Frontend issues | +| **What** | Frontend debugging team using Chrome DevTools MCP | +| **How** | Inspect -> Diagnose -> Fix -> Verify | +| **Output** | Fixed frontend issues | +| **Done** | Issues resolved | +| **Failure & Recovery** | Iterative debugging | +| **Impact & Boundary** | Frontend debugging specific | + +#### `team-testing` + +| Field | Description | +|-------|-------------| +| **Who** | Developer writing tests | +| **When** | Test generation needed | +| **What** | Unified team skill for testing team | +| **How** | Test planning -> Generation -> Execution | +| **Output** | Test suites | +| **Done** | Tests passing | +| **Failure & Recovery** | Test iteration | +| **Impact & Boundary** | Testing-specific team | + +#### `team-review` + +| Field | Description | +|-------|-------------| +| **Who** | Developer reviewing code | +| **When** | Code review needed | +| **What** | Unified team skill for code review | +| **How** | Multi-perspective review -> Feedback aggregation | +| **Output** | Review reports | +| **Done** | Review complete | +| **Failure & Recovery** | Partial review preserved | +| **Impact & Boundary** | Review-specific team | + +#### `team-quality-assurance` + +| Field | Description | +|-------|-------------| +| **Who** | QA engineer | +| **When** | Quality verification | +| **What** | Unified team skill for quality assurance | +| **How** | Quality checks -> Issue identification -> Remediation | +| **Output** | QA reports and fixes | +| **Done** | Quality verified | +| **Failure & Recovery** | Issue-driven iteration | +| **Impact & Boundary** | QA-specific team | + +#### `team-arch-opt` + +| Field | Description | +|-------|-------------| +| **Who** | Developer optimizing architecture | +| **When** | Architecture improvement | +| **What** | Unified team skill for architecture optimization | +| **How** | Analysis -> Optimization plan -> Implementation | +| **Output** | Improved architecture | +| **Done** | Optimization complete | +| **Failure & Recovery** | Gradual optimization | +| **Impact & Boundary** | Architecture-specific team | + +#### `team-perf-opt` + +| Field | Description | +|-------|-------------| +| **Who** | Developer optimizing performance | +| **When** | Performance issues | +| **What** | Unified team skill for performance optimization | +| **How** | Profiling -> Bottleneck identification -> Optimization | +| **Output** | Performance improvements | +| **Done** | Performance targets met | +| **Failure & Recovery** | Iterative optimization | +| **Impact & Boundary** | Performance-specific team | + +#### `team-tech-debt` + +| Field | Description | +|-------|-------------| +| **Who** | Developer addressing tech debt | +| **When** | Tech debt cleanup | +| **What** | Unified team skill for tech debt identification | +| **How** | Detection -> Prioritization -> Resolution | +| **Output** | Tech debt reduction | +| **Done** | Debt items resolved | +| **Failure & Recovery** | Prioritized resolution | +| **Impact & Boundary** | Tech debt specific | + +#### `team-ux-improve` + +| Field | Description | +|-------|-------------| +| **Who** | UX designer/developer | +| **When** | UX improvements | +| **What** | Unified team skill for UX improvement | +| **How** | UX audit -> Improvement plan -> Implementation | +| **Output** | UX improvements | +| **Done** | UX enhanced | +| **Failure & Recovery** | User feedback iteration | +| **Impact & Boundary** | UX-specific team | + +#### `team-uidesign` + +| Field | Description | +|-------|-------------| +| **Who** | UI designer | +| **When** | UI design work | +| **What** | Unified team skill for UI design team | +| **How** | Design system -> Components -> Prototypes | +| **Output** | UI designs and prototypes | +| **Done** | Design complete | +| **Failure & Recovery** | Design iteration | +| **Impact & Boundary** | UI design specific | + +#### `team-brainstorm` + +| Field | Description | +|-------|-------------| +| **Who** | Team brainstorming | +| **When** | Ideation sessions | +| **What** | Unified team skill for brainstorming team | +| **How** | Multi-perspective ideation -> Synthesis | +| **Output** | Brainstorm results | +| **Done** | Ideas documented | +| **Failure & Recovery** | Partial synthesis | +| **Impact & Boundary** | Brainstorming specific | + +#### `team-issue` + +| Field | Description | +|-------|-------------| +| **Who** | Developer managing issues | +| **When** | Issue resolution workflow | +| **What** | Unified team skill for issue resolution | +| **How** | Issue analysis -> Resolution -> Verification | +| **Output** | Resolved issues | +| **Done** | Issues closed | +| **Failure & Recovery** | Issue-specific handling | +| **Impact & Boundary** | Issue-specific team | + +#### `team-iterdev` + +| Field | Description | +|-------|-------------| +| **Who** | Developer in iterative mode | +| **When** | Iterative development | +| **What** | Unified team skill for iterative development | +| **How** | Iteration -> Feedback -> Refinement | +| **Output** | Iteratively improved code | +| **Done** | Iteration goals met | +| **Failure & Recovery** | Iteration adjustment | +| **Impact & Boundary** | Iterative development team | + +#### `team-roadmap-dev` + +| Field | Description | +|-------|-------------| +| **Who** | Developer on roadmap features | +| **When** | Roadmap-driven development | +| **What** | Unified team skill for roadmap-driven development | +| **How** | Roadmap parsing -> Feature development -> Tracking | +| **Output** | Roadmap feature completions | +| **Done** | Roadmap items complete | +| **Failure & Recovery** | Roadmap adjustment | +| **Impact & Boundary** | Roadmap-specific team | + +#### `team-ultra-analyze` + +| Field | Description | +|-------|-------------| +| **Who** | Developer needing deep analysis | +| **When** | Complex analysis required | +| **What** | Deep collaborative analysis team skill | +| **How** | Multi-angle analysis -> Deep dive -> Synthesis | +| **Output** | Comprehensive analysis reports | +| **Done** | Analysis complete | +| **Failure & Recovery** | Partial analysis preserved | +| **Impact & Boundary** | Deep analysis team | + +#### `team-executor` + +| Field | Description | +|-------|-------------| +| **Who** | Developer executing tasks | +| **When** | Task execution needed | +| **What** | Lightweight session execution skill | +| **How** | Load session -> Execute tasks -> Report | +| **Output** | Task execution results | +| **Done** | Session tasks complete | +| **Failure & Recovery** | Task-level retry | +| **Impact & Boundary** | Lightweight execution | + +#### `team-lifecycle-v4` + +| Field | Description | +|-------|-------------| +| **Who** | Developer managing full lifecycle | +| **When** | Complete feature lifecycle | +| **What** | Full lifecycle team skill with clean architecture | +| **How** | Plan -> Develop -> Test -> Deploy -> Monitor | +| **Output** | Complete feature lifecycle | +| **Done** | Feature fully delivered | +| **Failure & Recovery** | Lifecycle stage retry | +| **Impact & Boundary** | Full lifecycle management | + +#### `team-designer` + +| Field | Description | +|-------|-------------| +| **Who** | Developer designing teams | +| **When** | Creating new team skills | +| **What** | Meta-skill for generating team skills for different domains | +| **How** | Domain analysis -> Role definition -> Skill generation | +| **Output** | New team skill files | +| **Done** | Team skill ready | +| **Failure & Recovery** | Template validation | +| **Impact & Boundary** | Team skill meta-creation | + +--- + +### Utility Skills + +#### `brainstorm` + +| Field | Description | +|-------|-------------| +| **Who** | Developer exploring ideas | +| **When** | Starting new work, exploring solutions | +| **What** | Unified brainstorming with dual-mode (auto/single-role) and 9 available roles | +| **How** | Role selection -> Perspective analysis -> Idea synthesis | +| **Output** | Brainstorm report with actionables | +| **Done** | Ideas documented | +| **Failure & Recovery** | Partial analysis preserved | +| **Impact & Boundary** | Ideation support | + +#### `spec-generator` + +| Field | Description | +|-------|-------------| +| **Who** | Developer creating specifications | +| **When** | Starting new project or feature | +| **What** | 6-phase specification chain producing product brief, PRD, architecture, epics | +| **How** | Phase 1-6 chain: Brief -> PRD -> Architecture -> Epics -> Docs | +| **Output** | Complete specification documents | +| **Done** | All spec documents generated | +| **Failure & Recovery** | Phase-level retry | +| **Impact & Boundary** | Specification generation | + +#### `issue-manage` + +| Field | Description | +|-------|-------------| +| **Who** | Developer managing issues | +| **When** | Issue CRUD operations | +| **What** | Interactive menu-driven interface for issue CRUD via ccw issue CLI | +| **How** | Menu selection -> CLI execution -> Result display | +| **Output** | Issue management operations | +| **Done** | Operation complete | +| **Failure & Recovery** | CLI error handling | +| **Impact & Boundary** | Issue CRUD only | + +#### `review-code` + +| Field | Description | +|-------|-------------| +| **Who** | Developer reviewing code | +| **When** | Code review needed | +| **What** | Multi-dimensional code review with 6 dimensions: correctness, readability, performance, security, testing, architecture | +| **How** | Collect context -> Quick scan -> Deep review -> Generate report | +| **Output** | Structured review report | +| **Done** | Review complete | +| **Failure & Recovery** | Partial review preserved | +| **Impact & Boundary** | Code review only | + +#### `review-cycle` + +| Field | Description | +|-------|-------------| +| **Who** | Developer in review cycle | +| **When** | Iterative code review | +| **What** | Unified multi-dimensional code review with iterative cycle | +| **How** | Review -> Feedback -> Fix -> Re-review | +| **Output** | Iteratively improved code | +| **Done** | All issues addressed | +| **Failure & Recovery** | Cycle iteration | +| **Impact & Boundary** | Iterative review | + +#### `memory-capture` + +| Field | Description | +|-------|-------------| +| **Who** | Developer capturing knowledge | +| **When** | After important learnings | +| **What** | Unified memory capture with routing - session/tech/module context | +| **How** | Context detection -> Memory extraction -> Storage | +| **Output** | Captured memory entries | +| **Done** | Memory captured | +| **Failure & Recovery** | Partial capture preserved | +| **Impact & Boundary** | Memory capture only | + +#### `memory-manage` + +| Field | Description | +|-------|-------------| +| **Who** | Developer managing memory | +| **When** | Memory maintenance | +| **What** | Unified memory management - CLAUDE.md updates and memory cleanup | +| **How** | Load memory -> Organize -> Update CLAUDE.md | +| **Output** | Updated memory files | +| **Done** | Memory organized | +| **Failure & Recovery** | Backup before changes | +| **Impact & Boundary** | Memory management | + +#### `skill-tuning` + +| Field | Description | +|-------|-------------| +| **Who** | Developer improving skills | +| **When** | Skill optimization needed | +| **What** | Universal skill diagnosis and optimization | +| **How** | Diagnose -> Optimize -> Validate | +| **Output** | Improved skill files | +| **Done** | Skill optimized | +| **Failure & Recovery** | Incremental improvement | +| **Impact & Boundary** | Skill optimization | + +#### `skill-simplify` + +| Field | Description | +|-------|-------------| +| **Who** | Developer simplifying skills | +| **When** | Skill too complex | +| **What** | SKILL.md simplification with functional preservation | +| **How** | Analyze -> Simplify -> Verify functionality | +| **Output** | Simplified skill file | +| **Done** | Skill simplified | +| **Failure & Recovery** | Functional verification | +| **Impact & Boundary** | Skill simplification | + +#### `skill-generator` + +| Field | Description | +|-------|-------------| +| **Who** | Developer creating skills | +| **When** | New skill needed | +| **What** | Meta-skill for creating new Claude Code skills | +| **How** | Requirements -> Template -> Skill generation | +| **Output** | New skill SKILL.md + supporting files | +| **Done** | Skill ready for use | +| **Failure & Recovery** | Template validation | +| **Impact & Boundary** | Skill creation | + +#### `command-generator` + +| Field | Description | +|-------|-------------| +| **Who** | Developer creating commands | +| **When** | New slash command needed | +| **What** | Command file generator - 5 phase workflow | +| **How** | Requirements -> Template -> Command generation | +| **Output** | New command .md file | +| **Done** | Command ready for use | +| **Failure & Recovery** | Schema validation | +| **Impact & Boundary** | Command creation | + +#### `ccw-help` + +| Field | Description | +|-------|-------------| +| **Who** | Developer seeking help | +| **When** | Learning CCW system | +| **What** | CCW command help system - search, browse, documentation | +| **How** | Query -> Search -> Display help | +| **Output** | Help information | +| **Done** | Help displayed | +| **Failure & Recovery** | Fuzzy matching | +| **Impact & Boundary** | Help system only | + +--- + +## Appendix A: Quick Reference Table + +### Commands by Category + +| Category | Commands | Count | +|----------|----------|-------| +| Core | ccw, ccw-coordinator, flow-create | 3 | +| DDD | scan, index-build, plan, execute, doc-generate, doc-refresh, sync, update, auto | 9 | +| Issue | new, discover, discover-by-prompt, from-brainstorm, plan, queue, execute, convert-to-plan | 8 | +| IDAW | status, add, run, run-coordinate, resume | 5 | +| Workflow Session | start, list, sync, resume, complete | 5 | +| Workflow Spec | setup, add | 2 | +| Workflow Core | clean, debug-with-file, analyze-with-file, brainstorm-with-file, collaborative-plan-with-file | 5 | +| Workflow Cycle | integration-test-cycle, refactor-cycle, roadmap-with-file, unified-execute-with-file | 4 | +| Workflow UI Design | explore-auto, imitate-auto, generate, style-extract, layout-extract, animation-extract, codify-style, import-from-code, design-sync, reference-page-generator | 10 | +| Memory | prepare, style-skill-memory | 2 | +| CLI | codex-review, cli-init | 2 | +| **Total Commands** | | **55** | + +### Skills by Category + +| Category | Skills | Count | +|----------|--------|-------| +| Workflow | workflow-plan, workflow-execute, workflow-lite-plan, workflow-lite-execute, workflow-tdd-plan, workflow-test-fix, workflow-multi-cli-plan, workflow-skill-designer | 8 | +| Team | team-coordinate, team-edict, team-planex, team-frontend, team-frontend-debug, team-testing, team-review, team-quality-assurance, team-arch-opt, team-perf-opt, team-tech-debt, team-ux-improve, team-uidesign, team-brainstorm, team-issue, team-iterdev, team-roadmap-dev, team-ultra-analyze, team-executor, team-lifecycle-v4, team-designer | 21 | +| Utility | brainstorm, spec-generator, issue-manage, review-code, review-cycle, memory-capture, memory-manage, skill-tuning, skill-simplify, skill-generator, command-generator, ccw-help | 12 | +| **Total Skills** | | **41** | + +--- + +## Appendix B: Command Chain Examples + +### Document-Driven Development Flow ``` -/<命名空间>:<命令> [参数] [标志] +/ddd:scan # Code-first: scan existing codebase + -> /ddd:plan "add feature" # Plan with doc context + -> /ddd:execute # Execute with doc awareness + -> /ddd:sync # Sync changes to docs ``` -示例: -- `/ccw "添加用户认证"` -- `/workflow:session:start --auto "实现功能"` -- `/issue:new https://github.com/org/repo/issues/123` -- `/cli:codex-review --base main` +### Spec-First Development Flow -### 技能调用 (从代码) - -```javascript -Skill({ skill: "workflow-lite-plan", args: '"任务描述"' }) -Skill({ skill: "brainstorm", args: '"主题或问题"' }) -Skill({ skill: "review-cycle", args: '--session="WFS-xxx"' }) +``` +Skill: spec-generator # Generate specifications + -> /ddd:index-build # Build index from specs + -> /ddd:plan # Plan with spec context + -> /ddd:execute # Execute + -> /ddd:doc-refresh # Refresh affected docs ``` -### CLI 工具调用 +### Issue Resolution Flow -```bash -ccw cli -p "PURPOSE: ... TASK: ... MODE: analysis|write" --tool <工具> --mode <模式> +``` +/issue:new "bug description" # Create issue + -> /issue:plan ISS-001 # Generate solution + -> /issue:queue ISS-001 # Add to queue + -> /issue:execute # Execute queue +``` + +### Team Coordination Flow + +``` +Skill: team-coordinate "implement auth" + -> Dynamic role generation + -> Parallel worker execution + -> Result aggregation + -> Completion action +``` + +### UI Design Flow + +``` +/workflow:ui-design:explore-auto --input "modern dashboard" + -> /workflow:ui-design:style-extract # Extract styles + -> /workflow:ui-design:layout-extract # Extract layouts + -> /workflow:ui-design:generate # Assemble prototypes +``` + +### Integration Test Flow + +``` +/workflow:integration-test-cycle "test auth flow" + -> Generate tests + -> Execute tests + -> Reflect on failures + -> Iterate until pass + -> Reflection log +``` + +### Refactoring Flow + +``` +/workflow:refactor-cycle "src/auth" + -> Debt discovery + -> Prioritization + -> Per-item refactor + -> Validation + -> Reflection ``` --- -## 相关文档 +## Summary -- [工作流对比表](../workflows/comparison-table.md) - 工作流选择指南 -- [工作流概览](../workflows/index.md) - 4级工作流系统 -- [Claude 工作流技能](../skills/claude-workflow.md) - 详细技能文档 +| Metric | Count | +|--------|-------| +| **Total Commands** | 55 | +| **Total Skills** | 41 | +| **DDD Commands** | 9 | +| **Issue Commands** | 8 | +| **Team Skills** | 21 | +| **Workflow Skills** | 8 | + +--- + +*End of Reference Manual*