feat: migrate test-task-generate to agent-driven architecture

- Refactor test-task-generate.md to use action-planning-agent
- Add two-phase execution flow (Discovery → Agent Execution)
- Integrate Memory-First principle and MCP tool enhancements
- Support both agent-mode (default) and cli-execute-mode
- Add test-specific context package with TEST_ANALYSIS_RESULTS.md
- Align with task-generate-agent.md architecture
- Remove 556 lines of redundant old content (Phase 1-4 old structure)
- Update test-gen.md and test-fix-gen.md to reflect agent-driven changes

Changes include:
- Core Philosophy with agent-driven principles
- Agent Context Package structure for test sessions
- Discovery Actions for test context loading
- Agent Invocation with test-specific requirements
- Test Task Structure Reference
- Updated Integration & Usage sections
- Enhanced Related Commands documentation

Now test task generation uses autonomous agent planning with MCP enhancements for better test coverage analysis and generation.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

.claude/agents/action-planning-agent.md

@@ -151,9 +151,17 @@ Generate individual `.task/IMPL-*.json` files with:
     "agent": "@code-developer"
   },
   "context": {
-    "requirements": ["from analysis_results"],
-    "focus_paths": ["src/paths"],
-    "acceptance": ["measurable criteria"],
+    "requirements": [
+      "Implement 3 features: [authentication, authorization, session management]",
+      "Create 5 files: [auth.service.ts, auth.controller.ts, auth.middleware.ts, auth.types.ts, auth.test.ts]",
+      "Modify 2 existing functions: [validateUser() in users.service.ts lines 45-60, hashPassword() in utils.ts lines 120-135]"
+    ],
+    "focus_paths": ["src/auth", "tests/auth"],
+    "acceptance": [
+      "3 features implemented: verify by npm test -- auth (exit code 0)",
+      "5 files created: verify by ls src/auth/*.ts | wc -l = 5",
+      "Test coverage >=80%: verify by npm test -- --coverage | grep auth"
+    ],
     "depends_on": ["IMPL-N"],
     "artifacts": [
       {
@@ -181,23 +189,50 @@ Generate individual `.task/IMPL-*.json` files with:
       {
         "step": 1,
         "title": "Load and analyze role analyses",
-        "description": "Load role analyses from artifacts and extract requirements",
-        "modification_points": ["Load role analyses", "Extract requirements and design patterns"],
-        "logic_flow": ["Read role analyses from artifacts", "Parse architecture decisions", "Extract implementation requirements"],
+        "description": "Load 3 role analysis files and extract quantified requirements",
+        "modification_points": [
+          "Load 3 role analysis files: [system-architect/analysis.md, product-manager/analysis.md, ui-designer/analysis.md]",
+          "Extract 15 requirements from role analyses",
+          "Parse 8 architecture decisions from system-architect analysis"
+        ],
+        "logic_flow": [
+          "Read 3 role analyses from artifacts inventory",
+          "Parse architecture decisions (8 total)",
+          "Extract implementation requirements (15 total)",
+          "Build consolidated requirements list"
+        ],
         "depends_on": [],
         "output": "synthesis_requirements"
       },
       {
         "step": 2,
         "title": "Implement following specification",
-        "description": "Implement task requirements following consolidated role analyses",
-        "modification_points": ["Apply requirements from [synthesis_requirements]", "Modify target files", "Integrate with existing code"],
-        "logic_flow": ["Apply changes based on [synthesis_requirements]", "Implement core logic", "Validate against acceptance criteria"],
+        "description": "Implement 3 features across 5 files following consolidated role analyses",
+        "modification_points": [
+          "Create 5 new files in src/auth/: [auth.service.ts (180 lines), auth.controller.ts (120 lines), auth.middleware.ts (60 lines), auth.types.ts (40 lines), auth.test.ts (200 lines)]",
+          "Modify 2 functions: [validateUser() in users.service.ts lines 45-60, hashPassword() in utils.ts lines 120-135]",
+          "Implement 3 core features: [JWT authentication, role-based authorization, session management]"
+        ],
+        "logic_flow": [
+          "Apply 15 requirements from [synthesis_requirements]",
+          "Implement 3 features across 5 new files (600 total lines)",
+          "Modify 2 existing functions (30 lines total)",
+          "Write 25 test cases covering all features",
+          "Validate against 3 acceptance criteria"
+        ],
         "depends_on": [1],
         "output": "implementation"
       }
     ],
-    "target_files": ["file:function:lines", "path/to/NewFile.ts"]
+    "target_files": [
+      "src/auth/auth.service.ts",
+      "src/auth/auth.controller.ts",
+      "src/auth/auth.middleware.ts",
+      "src/auth/auth.types.ts",
+      "tests/auth/auth.test.ts",
+      "src/users/users.service.ts:validateUser:45-60",
+      "src/utils/utils.ts:hashPassword:120-135"
+    ]
   }
 }
 ```
@@ -285,6 +320,35 @@ Use `analysis_results.complexity` or task count to determine structure:
 - **Re-scope required**: Maximum 10 tasks hard limit
 - If analysis_results contains >10 tasks, consolidate or request re-scoping
 
+## Quantification Requirements (MANDATORY)
+
+**Purpose**: Eliminate ambiguity by enforcing explicit counts and enumerations in all task specifications.
+
+**Core Rules**:
+1. **Extract Counts from Analysis**: Search for HOW MANY items and list them explicitly
+2. **Enforce Explicit Lists**: Every deliverable uses format `{count} {type}: [{explicit_list}]`
+3. **Make Acceptance Measurable**: Include verification commands (e.g., `ls ... | wc -l = N`)
+4. **Quantify Modification Points**: Specify exact targets (files, functions with line numbers)
+5. **Avoid Vague Language**: Replace "complete", "comprehensive", "reorganize" with quantified statements
+
+**Standard Formats**:
+- **Requirements**: `"Implement N items: [item1, item2, ...]"` or `"Modify N files: [file1:func:lines, ...]"`
+- **Acceptance**: `"N items exist: verify by [command]"` or `"Coverage >= X%: verify by [test command]"`
+- **Modification Points**: `"Create N files: [list]"` or `"Modify N functions: [func() in file lines X-Y]"`
+
+**Validation Checklist** (Apply to every generated task JSON):
+- [ ] Every requirement contains explicit count or enumerated list
+- [ ] Every acceptance criterion is measurable with verification command
+- [ ] Every modification_point specifies exact targets (files/functions/lines)
+- [ ] No vague language ("complete", "comprehensive", "reorganize" without counts)
+- [ ] Each implementation step has its own acceptance criteria
+
+**Examples**:
+- ✅ GOOD: `"Implement 5 commands: [cmd1, cmd2, cmd3, cmd4, cmd5]"`
+- ❌ BAD: `"Implement new commands"`
+- ✅ GOOD: `"5 files created: verify by ls .claude/commands/*.md | wc -l = 5"`
+- ❌ BAD: `"All commands implemented successfully"`
+
 ## Quality Standards
 
 **Planning Principles:**
@@ -305,6 +369,7 @@ Use `analysis_results.complexity` or task count to determine structure:
 ## Key Reminders
 
 **ALWAYS:**
+- **Apply Quantification Requirements**: All requirements, acceptance criteria, and modification points MUST include explicit counts and enumerations
 - **Use provided context package**: Extract all information from structured context
 - **Respect memory-first rule**: Use provided content (already loaded from memory/file)
 - **Follow 5-field schema**: All task JSONs must have id, title, status, meta, context, flow_control
@@ -313,6 +378,7 @@ Use `analysis_results.complexity` or task count to determine structure:
 - **Validate task count**: Maximum 10 tasks hard limit, request re-scope if exceeded
 - **Use session paths**: Construct all paths using provided session_id
 - **Link documents properly**: Use correct linking format (📋 for JSON, ✅ for summaries)
+- **Run validation checklist**: Verify all quantification requirements before finalizing task JSONs
 
 **NEVER:**
 - Load files directly (use provided context package instead)

.claude/commands/cli/analyze.md

@@ -1,6 +1,6 @@
 ---
 name: analyze
-description: Quick codebase analysis using CLI tools (codex/gemini/qwen)
+description: Read-only codebase analysis using Gemini (default), Qwen, or Codex with auto-pattern detection and template selection
 argument-hint: "[--agent] [--tool codex|gemini|qwen] [--enhance] analysis target"
 allowed-tools: SlashCommand(*), Bash(*), TodoWrite(*), Read(*), Glob(*), Task(*)
 ---

.claude/commands/cli/chat.md

@@ -1,6 +1,6 @@
 ---
 name: chat
-description: Simple CLI interaction command for direct codebase analysis
+description: Read-only Q&A interaction with Gemini/Qwen/Codex for codebase questions with automatic context inference
 argument-hint: "[--agent] [--tool codex|gemini|qwen] [--enhance] inquiry"
 allowed-tools: SlashCommand(*), Bash(*), Task(*)
 ---

.claude/commands/cli/cli-init.md

@@ -1,6 +1,6 @@
 ---
 name: cli-init
-description: Initialize CLI tool configurations (Gemini and Qwen) based on workspace analysis
+description: Generate .gemini/ and .qwen/ config directories with settings.json and ignore files based on workspace technology detection
 argument-hint: "[--tool gemini|qwen|all] [--output path] [--preview]"
 allowed-tools: Bash(*), Read(*), Write(*), Glob(*)
 ---

.claude/commands/cli/codex-execute.md

@@ -1,6 +1,6 @@
 ---
 name: codex-execute
-description: Automated task decomposition and execution with Codex using resume mechanism
+description: Multi-stage Codex execution with automatic task decomposition into grouped subtasks using resume mechanism for context continuity
 argument-hint: "[--verify-git] task description or task-id"
 allowed-tools: SlashCommand(*), Bash(*), TodoWrite(*), Read(*), Glob(*)
 ---

.claude/commands/cli/discuss-plan.md

@@ -1,6 +1,6 @@
 ---
 name: discuss-plan
-description: Orchestrates an iterative, multi-model discussion for planning and analysis without implementation.
+description: Multi-round collaborative planning using Gemini, Codex, and Claude synthesis with iterative discussion cycles (read-only, no code changes)
 argument-hint: "[--topic '...'] [--task-id '...'] [--rounds N]"
 allowed-tools: SlashCommand(*), Bash(*), TodoWrite(*), Read(*), Glob(*)
 ---

.claude/commands/cli/execute.md

@@ -1,6 +1,6 @@
 ---
 name: execute
-description: Auto-execution of implementation tasks with YOLO permissions and intelligent context inference
+description: Autonomous code implementation with YOLO auto-approval using Gemini/Qwen/Codex, supports task ID or description input with automatic file pattern detection
 argument-hint: "[--agent] [--tool codex|gemini|qwen] [--enhance] description or task-id"
 allowed-tools: SlashCommand(*), Bash(*), Task(*)
 ---

.claude/commands/cli/mode/bug-diagnosis.md

@@ -1,6 +1,6 @@
 ---
 name: bug-diagnosis
-description: Bug diagnosis and fix suggestions using CLI tools with specialized template
+description: Read-only bug root cause analysis using Gemini/Qwen/Codex with systematic diagnosis template for fix suggestions
 argument-hint: "[--agent] [--tool codex|gemini|qwen] [--enhance] [--cd path] bug description"
 allowed-tools: SlashCommand(*), Bash(*), Task(*)
 ---
@@ -9,7 +9,7 @@ allowed-tools: SlashCommand(*), Bash(*), Task(*)
 
 ## Purpose
 
-Systematic bug diagnosis with root cause analysis template (`~/.claude/workflows/cli-templates/prompts/development/bug-diagnosis.txt`).
+Systematic bug diagnosis with root cause analysis template (`~/.claude/workflows/cli-templates/prompts/analysis/01-diagnose-bug-root-cause.txt`).
 
 **Tool Selection**:
 - **gemini** (default) - Best for bug diagnosis
@@ -48,7 +48,7 @@ Systematic bug diagnosis with root cause analysis template (`~/.claude/workflows
 1. Parse tool selection (default: gemini)
 2. Optional: enhance with `/enhance-prompt`
 3. Detect directory from `--cd` or auto-infer
-4. Build command with bug-diagnosis template
+4. Build command with template
 5. Execute diagnosis (read-only)
 6. Save to `.workflow/WFS-[id]/.chat/`
 
@@ -65,7 +65,7 @@ Task(
     Mode: bug-diagnosis
     Tool: ${tool_flag || 'auto-select'}  // gemini|qwen|codex
     Directory: ${cd_path || 'auto-detect'}
-    Template: bug-diagnosis
+    Template: ~/.claude/workflows/cli-templates/prompts/analysis/01-diagnose-bug-root-cause.txt
 
     Agent responsibilities:
     1. Context Discovery:
@@ -76,7 +76,7 @@ Task(
     2. CLI Command Generation:
        - Build Gemini/Qwen/Codex command
        - Include diagnostic context
-       - Apply bug-diagnosis.txt template
+       - Apply ~/.claude/workflows/cli-templates/prompts/analysis/01-diagnose-bug-root-cause.txt template
 
     3. Execution & Output:
        - Execute root cause analysis
@@ -89,7 +89,7 @@ Task(
 ## Core Rules
 
 - **Read-only**: Diagnoses bugs, does NOT modify code
-- **Template**: Uses `bug-diagnosis.txt` for root cause analysis
+- **Template**: Uses `~/.claude/workflows/cli-templates/prompts/analysis/01-diagnose-bug-root-cause.txt` for root cause analysis
 - **Output**: Saves to `.workflow/WFS-[id]/.chat/`
 
 ## CLI Command Templates
@@ -102,7 +102,7 @@ TASK: Root cause analysis
 MODE: analysis
 CONTEXT: @**/*
 EXPECTED: Diagnosis, fix plan
-RULES: $(cat ~/.claude/workflows/cli-templates/prompts/development/bug-diagnosis.txt)
+RULES: $(cat ~/.claude/workflows/cli-templates/prompts/analysis/01-diagnose-bug-root-cause.txt)
 "
 # Qwen: Replace 'gemini' with 'qwen'
 ```
@@ -115,7 +115,7 @@ TASK: Bug diagnosis
 MODE: analysis
 CONTEXT: @**/*
 EXPECTED: Diagnosis, fix suggestions
-RULES: $(cat ~/.claude/workflows/cli-templates/prompts/development/bug-diagnosis.txt)
+RULES: $(cat ~/.claude/workflows/cli-templates/prompts/analysis/01-diagnose-bug-root-cause.txt)
 " -m gpt-5 --skip-git-repo-check -s danger-full-access
 ```
 
@@ -126,5 +126,5 @@ RULES: $(cat ~/.claude/workflows/cli-templates/prompts/development/bug-diagnosis
 
 ## Notes
 
-- Template: `~/.claude/workflows/cli-templates/prompts/development/bug-diagnosis.txt`
+- Template: `~/.claude/workflows/cli-templates/prompts/analysis/01-diagnose-bug-root-cause.txt`
 - See `intelligent-tools-strategy.md` for detailed tool usage

.claude/commands/cli/mode/code-analysis.md

@@ -1,6 +1,6 @@
 ---
 name: code-analysis
-description: Deep code analysis and debugging using CLI tools with specialized template
+description: Read-only execution path tracing using Gemini/Qwen/Codex with specialized analysis template for call flow and optimization
 argument-hint: "[--agent] [--tool codex|gemini|qwen] [--enhance] [--cd path] analysis target"
 allowed-tools: SlashCommand(*), Bash(*), Task(*)
 ---
@@ -9,7 +9,7 @@ allowed-tools: SlashCommand(*), Bash(*), Task(*)
 
 ## Purpose
 
-Systematic code analysis with execution path tracing template (`~/.claude/workflows/cli-templates/prompts/analysis/code-execution-tracing.txt`).
+Systematic code analysis with execution path tracing template (`~/.claude/workflows/cli-templates/prompts/analysis/01-trace-code-execution.txt`).
 
 **Tool Selection**:
 - **gemini** (default) - Best for code analysis and tracing
@@ -52,7 +52,7 @@ Systematic code analysis with execution path tracing template (`~/.claude/workfl
 1. Parse tool selection (default: gemini)
 2. Optional: enhance analysis target with `/enhance-prompt`
 3. Detect target directory from `--cd` or auto-infer
-4. Build command with execution-tracing template
+4. Build command with template
 5. Execute analysis (read-only)
 6. Save to `.workflow/WFS-[id]/.chat/code-analysis-[timestamp].md`
 
@@ -63,7 +63,7 @@ Delegates to `cli-execution-agent` for intelligent context discovery and analysi
 ## Core Rules
 
 - **Read-only**: Analyzes code, does NOT modify files
-- **Template**: Uses `code-execution-tracing.txt` for systematic analysis
+- **Template**: Uses `~/.claude/workflows/cli-templates/prompts/analysis/01-trace-code-execution.txt` for systematic analysis
 - **Output**: Saves to `.workflow/WFS-[id]/.chat/`
 
 ## CLI Command Templates
@@ -76,7 +76,7 @@ TASK: Execution path tracing
 MODE: analysis
 CONTEXT: @**/*
 EXPECTED: Trace, call diagram
-RULES: $(cat ~/.claude/workflows/cli-templates/prompts/analysis/code-execution-tracing.txt)
+RULES: $(cat ~/.claude/workflows/cli-templates/prompts/analysis/01-trace-code-execution.txt)
 "
 # Qwen: Replace 'gemini' with 'qwen'
 ```
@@ -89,7 +89,7 @@ TASK: Path analysis
 MODE: analysis
 CONTEXT: @**/*
 EXPECTED: Trace, optimization
-RULES: $(cat ~/.claude/workflows/cli-templates/prompts/analysis/code-execution-tracing.txt)
+RULES: $(cat ~/.claude/workflows/cli-templates/prompts/analysis/01-trace-code-execution.txt)
 " -m gpt-5 --skip-git-repo-check -s danger-full-access
 ```
 
@@ -106,7 +106,7 @@ Task(
     Mode: code-analysis
     Tool: ${tool_flag || 'auto-select'}  // gemini|qwen|codex
     Directory: ${cd_path || 'auto-detect'}
-    Template: code-execution-tracing
+    Template: ~/.claude/workflows/cli-templates/prompts/analysis/01-trace-code-execution.txt
 
     Agent responsibilities:
     1. Context Discovery:
@@ -117,7 +117,7 @@ Task(
     2. CLI Command Generation:
        - Build Gemini/Qwen/Codex command
        - Include discovered context
-       - Apply code-execution-tracing.txt template
+       - Apply ~/.claude/workflows/cli-templates/prompts/analysis/01-trace-code-execution.txt template
 
     3. Execution & Output:
        - Execute analysis with selected tool
@@ -133,5 +133,5 @@ Task(
 
 ## Notes
 
-- Template: `~/.claude/workflows/cli-templates/prompts/analysis/code-execution-tracing.txt`
+- Template: `~/.claude/workflows/cli-templates/prompts/analysis/01-trace-code-execution.txt`
 - See `intelligent-tools-strategy.md` for detailed tool usage

.claude/commands/cli/mode/plan.md

@@ -1,6 +1,6 @@
 ---
 name: plan
-description: Project planning and architecture analysis using CLI tools
+description: Read-only architecture planning using Gemini/Qwen/Codex with strategic planning template for modification plans and impact analysis
 argument-hint: "[--agent] [--tool codex|gemini|qwen] [--enhance] [--cd path] topic"
 allowed-tools: SlashCommand(*), Bash(*), Task(*)
 ---
@@ -9,7 +9,7 @@ allowed-tools: SlashCommand(*), Bash(*), Task(*)
 
 ## Purpose
 
-Strategic software architecture planning template (`~/.claude/workflows/cli-templates/prompts/planning/architecture-planning.txt`).
+Strategic software architecture planning template (`~/.claude/workflows/cli-templates/prompts/planning/01-plan-architecture-design.txt`).
 
 **Tool Selection**:
 - **gemini** (default) - Best for architecture planning
@@ -47,7 +47,7 @@ Strategic software architecture planning template (`~/.claude/workflows/cli-temp
 1. Parse tool selection (default: gemini)
 2. Optional: enhance with `/enhance-prompt`
 3. Detect directory from `--cd` or auto-infer
-4. Build command with architecture-planning template
+4. Build command with template
 5. Execute planning (read-only, no code generation)
 6. Save to `.workflow/WFS-[id]/.chat/`
 
@@ -64,7 +64,7 @@ Task(
     Mode: architecture-planning
     Tool: ${tool_flag || 'auto-select'}  // gemini|qwen|codex
     Directory: ${cd_path || 'auto-detect'}
-    Template: architecture-planning
+    Template: ~/.claude/workflows/cli-templates/prompts/planning/01-plan-architecture-design.txt
 
     Agent responsibilities:
     1. Context Discovery:
@@ -75,7 +75,7 @@ Task(
     2. CLI Command Generation:
        - Build Gemini/Qwen/Codex command
        - Include architecture context
-       - Apply architecture-planning.txt template
+       - Apply ~/.claude/workflows/cli-templates/prompts/planning/01-plan-architecture-design.txt template
 
     3. Execution & Output:
        - Execute strategic planning
@@ -88,7 +88,7 @@ Task(
 ## Core Rules
 
 - **Planning only**: Creates modification plans, does NOT generate code
-- **Template**: Uses `architecture-planning.txt` for strategic planning
+- **Template**: Uses `~/.claude/workflows/cli-templates/prompts/planning/01-plan-architecture-design.txt` for strategic planning
 - **Output**: Saves to `.workflow/WFS-[id]/.chat/`
 
 ## CLI Command Templates
@@ -101,7 +101,7 @@ TASK: Architecture planning
 MODE: analysis
 CONTEXT: @**/*
 EXPECTED: Modification plan, impact analysis
-RULES: $(cat ~/.claude/workflows/cli-templates/prompts/planning/architecture-planning.txt)
+RULES: $(cat ~/.claude/workflows/cli-templates/prompts/planning/01-plan-architecture-design.txt)
 "
 # Qwen: Replace 'gemini' with 'qwen'
 ```
@@ -114,7 +114,7 @@ TASK: Architecture planning
 MODE: analysis
 CONTEXT: @**/*
 EXPECTED: Plan, implementation roadmap
-RULES: $(cat ~/.claude/workflows/cli-templates/prompts/planning/architecture-planning.txt)
+RULES: $(cat ~/.claude/workflows/cli-templates/prompts/planning/01-plan-architecture-design.txt)
 " -m gpt-5 --skip-git-repo-check -s danger-full-access
 ```
 
@@ -125,5 +125,5 @@ RULES: $(cat ~/.claude/workflows/cli-templates/prompts/planning/architecture-pla
 
 ## Notes
 
-- Template: `~/.claude/workflows/cli-templates/prompts/planning/architecture-planning.txt`
+- Template: `~/.claude/workflows/cli-templates/prompts/planning/01-plan-architecture-design.txt`
 - See `intelligent-tools-strategy.md` for detailed tool usage

.claude/commands/enhance-prompt.md

@@ -1,6 +1,6 @@
 ---
 name: enhance-prompt
-description: Context-aware prompt enhancement using session memory and codebase analysis
+description: Enhanced prompt transformation using session memory and codebase analysis with --enhance flag detection
 argument-hint: "user input to enhance"
 ---
 

.claude/commands/memory/docs.md

@@ -1,6 +1,6 @@
 ---
 name: docs
-description: Documentation planning and orchestration - creates structured documentation tasks for execution
+description: Plan documentation workflow with dynamic grouping (≤10 docs/task), generates IMPL tasks for parallel module trees, README, ARCHITECTURE, and HTTP API docs
 argument-hint: "[path] [--tool <gemini|qwen|codex>] [--mode <full|partial>] [--cli-execute]"
 ---
 

.claude/commands/memory/load-skill-memory.md

@@ -1,6 +1,6 @@
 ---
 name: load-skill-memory
-description: Activate SKILL package (auto-detect or manual) and load documentation based on task intent
+description: Activate SKILL package (auto-detect from paths/keywords or manual) and intelligently load documentation based on task intent keywords
 argument-hint: "[skill_name] \"task intent description\""
 allowed-tools: Bash(*), Read(*), Skill(*)
 ---

.claude/commands/memory/load.md

@@ -1,6 +1,6 @@
 ---
 name: load
-description: Load project memory by delegating to agent, returns structured core content package for subsequent operations
+description: Delegate to universal-executor agent to analyze project via Gemini/Qwen CLI and return JSON core content package for task context
 argument-hint: "[--tool gemini|qwen] \"task context description\""
 allowed-tools: Task(*), Bash(*)
 examples:

.claude/commands/memory/skill-memory.md

@@ -1,6 +1,6 @@
 ---
 name: skill-memory
-description: Generate SKILL package index from project documentation
+description: 4-phase autonomous orchestrator: check docs → /memory:docs planning → /workflow:execute → generate SKILL.md with progressive loading index (skips phases 2-3 if docs exist)
 argument-hint: "[path] [--tool <gemini|qwen|codex>] [--regenerate] [--mode <full|partial>] [--cli-execute]"
 allowed-tools: SlashCommand(*), TodoWrite(*), Bash(*), Read(*), Write(*)
 ---

.claude/commands/memory/tech-research.md

@@ -1,6 +1,6 @@
 ---
 name: tech-research
-description: Generate tech stack SKILL packages using Exa research via agent delegation
+description: 3-phase orchestrator: extract tech stack from session/name → delegate to agent for Exa research and module generation → generate SKILL.md index (skips phase 2 if exists)
 argument-hint: "[session-id | tech-stack-name] [--regenerate] [--tool <gemini|qwen>]"
 allowed-tools: SlashCommand(*), TodoWrite(*), Bash(*), Read(*), Write(*), Task(*)
 ---

.claude/commands/memory/update-full.md

@@ -1,6 +1,6 @@
 ---
 name: update-full
-description: Complete project-wide CLAUDE.md documentation update with agent-based parallel execution and tool fallback
+description: Update all CLAUDE.md files using layer-based execution (Layer 3→1) with batched agents (4 modules/agent) and gemini→qwen→codex fallback, <20 modules uses direct parallel
 argument-hint: "[--tool gemini|qwen|codex] [--path <directory>]"
 ---
 

.claude/commands/memory/update-related.md

@@ -1,6 +1,6 @@
 ---
 name: update-related
-description: Context-aware CLAUDE.md documentation updates based on recent changes with agent-based execution and tool fallback
+description: Update CLAUDE.md for git-changed modules using batched agent execution (4 modules/agent) with gemini→qwen→codex fallback, <15 modules uses direct execution
 argument-hint: "[--tool gemini|qwen|codex]"
 ---
 

.claude/commands/memory/workflow-skill-memory.md

@@ -1,6 +1,6 @@
 ---
 name: workflow-skill-memory
-description: Generate SKILL package from archived workflow sessions for progressive context loading
+description: Process WFS-* archived sessions using universal-executor agents with Gemini analysis to generate workflow-progress SKILL package (sessions-timeline, lessons, conflicts)
 argument-hint: "session <session-id> | all"
 allowed-tools: Task(*), TodoWrite(*), Bash(*), Read(*), Write(*)
 ---

.claude/commands/task/breakdown.md

@@ -1,6 +1,6 @@
 ---
 name: breakdown
-description: Intelligent task decomposition with context-aware subtask generation
+description: Decompose complex task into subtasks with dependency mapping, creates child task JSONs with parent references and execution order
 argument-hint: "task-id"
 ---
 

.claude/commands/task/create.md

@@ -1,6 +1,6 @@
 ---
 name: create
-description: Create implementation tasks with automatic context awareness
+description: Generate task JSON from natural language description with automatic file pattern detection, scope inference, and dependency analysis
 argument-hint: "\"task title\""
 ---
 

.claude/commands/task/execute.md

@@ -1,6 +1,6 @@
 ---
 name: execute
-description: Execute tasks with appropriate agents and context-aware orchestration
+description: Execute task JSON using appropriate agent (@doc-generator/@implementation-agent/@test-agent) with pre-analysis context loading and status tracking
 argument-hint: "task-id"
 ---
 
@@ -189,7 +189,7 @@ This is the simplified data structure loaded to provide context for task executi
       "pre_analysis": [
         {
           "action": "analyze patterns",
-          "template": "~/.claude/workflows/cli-templates/prompts/analysis/pattern.txt",
+          "template": "~/.claude/workflows/cli-templates/prompts/analysis/02-analyze-code-patterns.txt",
           "method": "gemini"
         }
       ]

.claude/commands/task/replan.md

@@ -1,6 +1,6 @@
 ---
 name: replan
-description: Replan individual tasks with detailed user input and change tracking
+description: Update task JSON with new requirements or batch-update multiple tasks from verification report, tracks changes in task-changes.json
 argument-hint: "task-id [\"text\"|file.md] | --batch [verification-report.md]"
 allowed-tools: Read(*), Write(*), Edit(*), TodoWrite(*), Glob(*), Bash(*)
 ---

.claude/commands/version.md

@@ -1,6 +1,6 @@
 ---
 name: version
-description: Display version information and check for updates
+description: Display Claude Code version information and check for updates
 allowed-tools: Bash(*)
 ---
 

.claude/commands/workflow/action-plan-verify.md

@@ -1,6 +1,6 @@
 ---
 name: action-plan-verify
-description: Perform non-destructive cross-artifact consistency and quality analysis of IMPL_PLAN.md and task.json before execution
+description: Perform non-destructive cross-artifact consistency analysis between IMPL_PLAN.md and task JSONs with quality gate validation
 argument-hint: "[optional: --session session-id]"
 allowed-tools: Read(*), TodoWrite(*), Glob(*), Bash(*)
 ---

.claude/commands/workflow/brainstorm/api-designer.md

@@ -1,6 +1,6 @@
 ---
 name: api-designer
-description: Generate or update api-designer/analysis.md addressing guidance-specification discussion points
+description: Generate or update api-designer/analysis.md addressing guidance-specification discussion points for API design perspective
 argument-hint: "optional topic - uses existing framework if available"
 allowed-tools: Task(conceptual-planning-agent), TodoWrite(*), Read(*), Write(*)
 ---

.claude/commands/workflow/brainstorm/artifacts.md

@@ -1,6 +1,6 @@
 ---
 name: artifacts
-description: Interactive clarification generating confirmed guidance specification
+description: Interactive clarification generating confirmed guidance specification through role-based analysis and synthesis
 argument-hint: "topic or challenge description [--count N]"
 allowed-tools: TodoWrite(*), Read(*), Write(*), Glob(*)
 ---

.claude/commands/workflow/brainstorm/auto-parallel.md

@@ -1,6 +1,6 @@
 ---
 name: auto-parallel
-description: Parallel brainstorming automation with dynamic role selection and concurrent execution
+description: Parallel brainstorming automation with dynamic role selection and concurrent execution across multiple perspectives
 argument-hint: "topic or challenge description" [--count N]
 allowed-tools: SlashCommand(*), Task(*), TodoWrite(*), Read(*), Write(*), Bash(*), Glob(*)
 ---

.claude/commands/workflow/brainstorm/data-architect.md

@@ -1,6 +1,6 @@
 ---
 name: data-architect
-description: Generate or update data-architect/analysis.md addressing guidance-specification discussion points
+description: Generate or update data-architect/analysis.md addressing guidance-specification discussion points for data architecture perspective
 argument-hint: "optional topic - uses existing framework if available"
 allowed-tools: Task(conceptual-planning-agent), TodoWrite(*), Read(*), Write(*)
 ---

.claude/commands/workflow/brainstorm/product-manager.md

@@ -1,6 +1,6 @@
 ---
 name: product-manager
-description: Generate or update product-manager/analysis.md addressing guidance-specification discussion points
+description: Generate or update product-manager/analysis.md addressing guidance-specification discussion points for product management perspective
 argument-hint: "optional topic - uses existing framework if available"
 allowed-tools: Task(conceptual-planning-agent), TodoWrite(*), Read(*), Write(*)
 ---

.claude/commands/workflow/brainstorm/product-owner.md

@@ -1,6 +1,6 @@
 ---
 name: product-owner
-description: Generate or update product-owner/analysis.md addressing guidance-specification discussion points
+description: Generate or update product-owner/analysis.md addressing guidance-specification discussion points for product ownership perspective
 argument-hint: "optional topic - uses existing framework if available"
 allowed-tools: Task(conceptual-planning-agent), TodoWrite(*), Read(*), Write(*)
 ---

.claude/commands/workflow/brainstorm/scrum-master.md

@@ -1,6 +1,6 @@
 ---
 name: scrum-master
-description: Generate or update scrum-master/analysis.md addressing guidance-specification discussion points
+description: Generate or update scrum-master/analysis.md addressing guidance-specification discussion points for Agile process perspective
 argument-hint: "optional topic - uses existing framework if available"
 allowed-tools: Task(conceptual-planning-agent), TodoWrite(*), Read(*), Write(*)
 ---

.claude/commands/workflow/brainstorm/subject-matter-expert.md

@@ -1,6 +1,6 @@
 ---
 name: subject-matter-expert
-description: Generate or update subject-matter-expert/analysis.md addressing guidance-specification discussion points
+description: Generate or update subject-matter-expert/analysis.md addressing guidance-specification discussion points for domain expertise perspective
 argument-hint: "optional topic - uses existing framework if available"
 allowed-tools: Task(conceptual-planning-agent), TodoWrite(*), Read(*), Write(*)
 ---

.claude/commands/workflow/brainstorm/synthesis.md

@@ -1,6 +1,6 @@
 ---
 name: synthesis
-description: Clarify and refine role analyses through intelligent Q&A and targeted updates
+description: Clarify and refine role analyses through intelligent Q&A and targeted updates with synthesis agent
 argument-hint: "[optional: --session session-id]"
 allowed-tools: Task(conceptual-planning-agent), TodoWrite(*), Read(*), Write(*), Edit(*), Glob(*)
 ---

.claude/commands/workflow/brainstorm/system-architect.md

@@ -1,6 +1,6 @@
 ---
 name: system-architect
-description: Generate or update system-architect/analysis.md addressing guidance-specification discussion points
+description: Generate or update system-architect/analysis.md addressing guidance-specification discussion points for system architecture perspective
 argument-hint: "optional topic - uses existing framework if available"
 allowed-tools: Task(conceptual-planning-agent), TodoWrite(*), Read(*), Write(*)
 ---

.claude/commands/workflow/brainstorm/ui-designer.md

@@ -1,6 +1,6 @@
 ---
 name: ui-designer
-description: Generate or update ui-designer/analysis.md addressing guidance-specification discussion points
+description: Generate or update ui-designer/analysis.md addressing guidance-specification discussion points for UI design perspective
 argument-hint: "optional topic - uses existing framework if available"
 allowed-tools: Task(conceptual-planning-agent), TodoWrite(*), Read(*), Write(*)
 ---

.claude/commands/workflow/brainstorm/ux-expert.md

@@ -1,6 +1,6 @@
 ---
 name: ux-expert
-description: Generate or update ux-expert/analysis.md addressing guidance-specification discussion points
+description: Generate or update ux-expert/analysis.md addressing guidance-specification discussion points for UX perspective
 argument-hint: "optional topic - uses existing framework if available"
 allowed-tools: Task(conceptual-planning-agent), TodoWrite(*), Read(*), Write(*)
 ---

.claude/commands/workflow/execute.md

@@ -1,6 +1,6 @@
 ---
 name: execute
-description: Coordinate agents for existing workflow tasks with automatic discovery
+description: Coordinate agent execution for workflow tasks with automatic session discovery, parallel task processing, and status tracking
 argument-hint: "[--resume-session=\"session-id\"]"
 ---
 

.claude/commands/workflow/plan.md

@@ -1,7 +1,7 @@
 ---
 name: plan
-description: Orchestrate 5-phase planning workflow with quality gate, executing commands and passing context between phases
-argument-hint: "[--agent] [--cli-execute] \"text description\"|file.md"
+description: 5-phase planning workflow with action-planning-agent task generation, outputs IMPL_PLAN.md and task JSONs with optional CLI auto-execution
+argument-hint: "[--cli-execute] \"text description\"|file.md"
 allowed-tools: SlashCommand(*), TodoWrite(*), Read(*), Bash(*)
 ---
 
@@ -20,7 +20,7 @@ This workflow runs **fully autonomously** once triggered. Phase 3 (conflict reso
 2. **Phase 1 executes** → Session discovery → Auto-continues
 3. **Phase 2 executes** → Context gathering → Auto-continues
 4. **Phase 3 executes** (optional, if conflict_risk ≥ medium) → Conflict resolution → Auto-continues
-5. **Phase 4 executes** (task-generate-agent if --agent) → Task generation → Reports final summary
+5. **Phase 4 executes** → Task generation (task-generate-agent) → Reports final summary
 
 **Auto-Continue Mechanism**:
 - TodoList tracks current phase status
@@ -28,11 +28,6 @@ This workflow runs **fully autonomously** once triggered. Phase 3 (conflict reso
 - All phases run autonomously without user interaction (clarification handled in brainstorm phase)
 - Progress updates shown at each phase for visibility
 
-**Execution Modes**:
-- **Manual Mode** (default): Use `/workflow:tools:task-generate`
-- **Agent Mode** (`--agent`): Use `/workflow:tools:task-generate-agent`
-- **CLI Execute Mode** (`--cli-execute`): Generate tasks with Codex execution commands
-
 ## Core Rules
 
 1. **Start Immediately**: First action is TodoWrite initialization, second action is Phase 1 command execution
@@ -159,24 +154,18 @@ CONTEXT: Existing user database schema, REST API endpoints
 - Task generation translates high-level role analyses into concrete, actionable work items
 - **Intent priority**: Current user prompt > role analysis.md files > guidance-specification.md
 
-**Command Selection**:
-- Manual: `SlashCommand(command="/workflow:tools:task-generate --session [sessionId]")`
-- Agent: `SlashCommand(command="/workflow:tools:task-generate-agent --session [sessionId]")`
-- CLI Execute: Add `--cli-execute` flag to either command
-
-**Flag Combination**:
-- `--cli-execute` alone: Manual task generation with CLI execution
-- `--agent --cli-execute`: Agent task generation with CLI execution
-
-**Command Examples**:
+**Command**:
 ```bash
-# Manual with CLI execution
-/workflow:tools:task-generate --session WFS-auth --cli-execute
+# Default (agent mode)
+SlashCommand(command="/workflow:tools:task-generate-agent --session [sessionId]")
 
-# Agent with CLI execution
-/workflow:tools:task-generate-agent --session WFS-auth --cli-execute
+# With CLI execution
+SlashCommand(command="/workflow:tools:task-generate-agent --session [sessionId] --cli-execute")
 ```
 
+**Flag**:
+- `--cli-execute`: Generate tasks with Codex execution commands
+
 **Input**: `sessionId` from Phase 1
 
 **Validation**:
@@ -296,7 +285,7 @@ Phase 3: conflict-resolution [AUTO-TRIGGERED if conflict_risk ≥ medium]
     ↓ Output: Modified brainstorm artifacts (NO report file)
     ↓ Skip if conflict_risk is none/low → proceed directly to Phase 4
     ↓
-Phase 4: task-generate[--agent] --session sessionId
+Phase 4: task-generate-agent --session sessionId [--cli-execute]
     ↓ Input: sessionId + resolved brainstorm artifacts + session memory
     ↓ Output: IMPL_PLAN.md, task JSONs, TODO_LIST.md
     ↓
@@ -333,9 +322,8 @@ Return summary to user
 - **If conflict_risk ≥ medium**: Launch Phase 3 conflict-resolution with sessionId and contextPath
 - Wait for Phase 3 completion (if executed), verify CONFLICT_RESOLUTION.md created
 - **If conflict_risk is none/low**: Skip Phase 3, proceed directly to Phase 4
-- **Build Phase 4 command** based on flags:
-  - Base command: `/workflow:tools:task-generate` (or `-agent` if `--agent` flag)
-  - Add `--session [sessionId]`
+- **Build Phase 4 command**:
+  - Base command: `/workflow:tools:task-generate-agent --session [sessionId]`
   - Add `--cli-execute` if flag present
 - Pass session ID to Phase 4 command
 - Verify all Phase 4 outputs
@@ -380,8 +368,7 @@ CONSTRAINTS: [Limitations or boundaries]
 - `/workflow:tools:context-gather` - Phase 2: Gather project context and analyze codebase
 - `/workflow:tools:conflict-resolution` - Phase 3: Detect and resolve conflicts (auto-triggered if conflict_risk ≥ medium)
 - `/compact` - Phase 3: Memory optimization (if context approaching limits)
-- `/workflow:tools:task-generate` - Phase 4: Generate task JSON files with manual approach
-- `/workflow:tools:task-generate-agent` - Phase 4: Generate task JSON files with agent-driven approach (when `--agent` flag used)
+- `/workflow:tools:task-generate-agent` - Phase 4: Generate task JSON files with agent-driven approach
 
 **Follow-up Commands**:
 - `/workflow:action-plan-verify` - Recommended: Verify plan quality and catch issues before execution

.claude/commands/workflow/resume.md

@@ -1,6 +1,6 @@
 ---
 name: resume
-description: Intelligent workflow session resumption with automatic progress analysis
+description: Resume paused workflow session with automatic progress analysis, pending task identification, and conflict detection
 argument-hint: "session-id for workflow session to resume"
 allowed-tools: SlashCommand(*), TodoWrite(*), Read(*), Bash(*)
 ---

.claude/commands/workflow/review.md

@@ -1,6 +1,6 @@
 ---
 name: review
-description: Optional specialized review (security, architecture, docs) for completed implementation
+description: Post-implementation review with specialized types (security/architecture/action-items/quality) using analysis agents and Gemini
 argument-hint: "[--type=security|architecture|action-items|quality] [optional: session-id]"
 ---
 

.claude/commands/workflow/session/complete.md

@@ -1,6 +1,6 @@
 ---
 name: complete
-description: Mark the active workflow session as complete, archive it with lessons learned, and remove active flag
+description: Mark active workflow session as complete, archive with lessons learned, update manifest, remove active flag
 examples:
   - /workflow:session:complete
   - /workflow:session:complete --detailed

.claude/commands/workflow/session/list.md

@@ -1,6 +1,6 @@
 ---
 name: list
-description: List all workflow sessions with status
+description: List all workflow sessions with status filtering, shows session metadata and progress information
 examples:
   - /workflow:session:list
 ---

.claude/commands/workflow/session/resume.md

@@ -1,6 +1,6 @@
 ---
 name: resume
-description: Resume the most recently paused workflow session
+description: Resume the most recently paused workflow session with automatic session discovery and status update
 ---
 
 # Resume Workflow Session (/workflow:session:resume)

.claude/commands/workflow/session/start.md

@@ -1,6 +1,6 @@
 ---
 name: start
-description: Discover existing sessions or start a new workflow session with intelligent session management
+description: Discover existing sessions or start new workflow session with intelligent session management and conflict detection
 argument-hint: [--auto|--new] [optional: task description for new session]
 examples:
   - /workflow:session:start

.claude/commands/workflow/status.md

@@ -1,6 +1,6 @@
 ---
 name: workflow:status
-description: Generate on-demand views from JSON task data
+description: Generate on-demand task status views from JSON task data with optional task-id filtering for detailed view
 argument-hint: "[optional: task-id]"
 ---
 

.claude/commands/workflow/tdd-plan.md

@@ -1,7 +1,7 @@
 ---
 name: tdd-plan
-description: Orchestrate TDD workflow planning with Red-Green-Refactor task chains
-argument-hint: "[--agent] \"feature description\"|file.md"
+description: TDD workflow planning with Red-Green-Refactor task chain generation, test-first development structure, and cycle tracking
+argument-hint: "[--cli-execute] \"feature description\"|file.md"
 allowed-tools: SlashCommand(*), TodoWrite(*), Read(*), Bash(*)
 ---
 
@@ -12,8 +12,8 @@ allowed-tools: SlashCommand(*), TodoWrite(*), Read(*), Bash(*)
 **This command is a pure orchestrator**: Execute 5 slash commands in sequence, parse outputs, pass context, and ensure complete TDD workflow creation.
 
 **Execution Modes**:
-- **Manual Mode** (default): Use `/workflow:tools:task-generate-tdd`
-- **Agent Mode** (`--agent`): Use `/workflow:tools:task-generate-tdd --agent`
+- **Agent Mode** (default): Use `/workflow:tools:task-generate-tdd` (autonomous agent-driven)
+- **CLI Mode** (`--cli-execute`): Use `/workflow:tools:task-generate-tdd --cli-execute` (Gemini/Qwen)
 
 ## Core Rules
 
@@ -129,8 +129,8 @@ TEST_FOCUS: [Test scenarios]
 
 ### Phase 5: TDD Task Generation
 **Command**:
-- Manual: `/workflow:tools:task-generate-tdd --session [sessionId]`
-- Agent: `/workflow:tools:task-generate-tdd --session [sessionId] --agent`
+- Agent Mode (default): `/workflow:tools:task-generate-tdd --session [sessionId]`
+- CLI Mode (`--cli-execute`): `/workflow:tools:task-generate-tdd --session [sessionId] --cli-execute`
 
 **Parse**: Extract feature count, task count (not chain count - tasks now contain internal TDD cycles)
 
@@ -373,8 +373,8 @@ Supports action-planning-agent for more autonomous TDD planning with:
 - `/workflow:tools:test-context-gather` - Phase 3: Analyze existing test patterns and coverage
 - `/workflow:tools:conflict-resolution` - Phase 4: Detect and resolve conflicts (auto-triggered if conflict_risk ≥ medium)
 - `/compact` - Phase 4: Memory optimization (if context approaching limits)
-- `/workflow:tools:task-generate-tdd` - Phase 5: Generate TDD task chains with Red-Green-Refactor cycles
-- `/workflow:tools:task-generate-tdd --agent` - Phase 5: Generate TDD tasks with agent-driven approach (when `--agent` flag used)
+- `/workflow:tools:task-generate-tdd` - Phase 5: Generate TDD tasks with agent-driven approach (default, autonomous)
+- `/workflow:tools:task-generate-tdd --cli-execute` - Phase 5: Generate TDD tasks with CLI tools (Gemini/Qwen, when `--cli-execute` flag used)
 
 **Follow-up Commands**:
 - `/workflow:action-plan-verify` - Recommended: Verify TDD plan quality and structure before execution

.claude/commands/workflow/tdd-verify.md

@@ -1,6 +1,6 @@
 ---
 name: tdd-verify
-description: Verify TDD workflow compliance and generate quality report
+description: Verify TDD workflow compliance against Red-Green-Refactor cycles, generate quality report with coverage analysis
 
 argument-hint: "[optional: WFS-session-id]"
 allowed-tools: SlashCommand(*), TodoWrite(*), Read(*), Bash(gemini:*)

.claude/commands/workflow/test-cycle-execute.md

@@ -1,6 +1,6 @@
 ---
 name: test-cycle-execute
-description: Execute test-fix workflow with dynamic task generation and iterative fix cycles
+description: Execute test-fix workflow with dynamic task generation and iterative fix cycles until all tests pass or max iterations reached
 argument-hint: "[--resume-session=\"session-id\"] [--max-iterations=N]"
 allowed-tools: SlashCommand(*), TodoWrite(*), Read(*), Bash(*), Task(*)
 ---

.claude/commands/workflow/test-fix-gen.md

@@ -1,6 +1,6 @@
 ---
 name: test-fix-gen
-description: Create independent test-fix workflow session from existing implementation (session or prompt-based)
+description: Create test-fix workflow session from session ID, description, or file path with test strategy generation and task planning
 argument-hint: "[--use-codex] [--cli-execute] (source-session-id | \"feature description\" | /path/to/file.md)"
 allowed-tools: SlashCommand(*), TodoWrite(*), Read(*), Bash(*)
 ---
@@ -473,9 +473,9 @@ WFS-test-[session]/
 - `/workflow:tools:test-context-gather` - Phase 2 (Session Mode): Gather source session context
 - `/workflow:tools:context-gather` - Phase 2 (Prompt Mode): Analyze codebase directly
 - `/workflow:tools:test-concept-enhanced` - Phase 3: Generate test requirements using Gemini
-- `/workflow:tools:test-task-generate` - Phase 4: Generate test task JSONs with fix cycle specification
-- `/workflow:tools:test-task-generate --use-codex` - Phase 4: With automated Codex fixes (when `--use-codex` flag used)
-- `/workflow:tools:test-task-generate --cli-execute` - Phase 4: With CLI execution mode (when `--cli-execute` flag used)
+- `/workflow:tools:test-task-generate` - Phase 4: Generate test task JSONs using action-planning-agent (autonomous, default)
+- `/workflow:tools:test-task-generate --use-codex` - Phase 4: With automated Codex fixes for IMPL-002 (when `--use-codex` flag used)
+- `/workflow:tools:test-task-generate --cli-execute` - Phase 4: With CLI execution mode for IMPL-001 test generation (when `--cli-execute` flag used)
 
 **Follow-up Commands**:
 - `/workflow:status` - Review generated test tasks

.claude/commands/workflow/test-gen.md

@@ -1,6 +1,6 @@
 ---
 name: test-gen
-description: Create independent test-fix workflow session by analyzing completed implementation
+description: Create independent test-fix workflow session from completed implementation session, analyzes code to generate test tasks
 argument-hint: "[--use-codex] [--cli-execute] source-session-id"
 allowed-tools: SlashCommand(*), TodoWrite(*), Read(*), Bash(*)
 ---
@@ -337,9 +337,9 @@ See `/workflow:tools:test-task-generate` for complete JSON schemas.
 - `/workflow:session:start` - Phase 1: Create independent test workflow session
 - `/workflow:tools:test-context-gather` - Phase 2: Analyze test coverage and gather source session context
 - `/workflow:tools:test-concept-enhanced` - Phase 3: Generate test requirements and strategy using Gemini
-- `/workflow:tools:test-task-generate` - Phase 4: Generate test generation and execution task JSONs
-- `/workflow:tools:test-task-generate --use-codex` - Phase 4: With automated Codex fixes (when `--use-codex` flag used)
-- `/workflow:tools:test-task-generate --cli-execute` - Phase 4: With CLI execution mode (when `--cli-execute` flag used)
+- `/workflow:tools:test-task-generate` - Phase 4: Generate test task JSONs using action-planning-agent (autonomous, default)
+- `/workflow:tools:test-task-generate --use-codex` - Phase 4: With automated Codex fixes for IMPL-002 (when `--use-codex` flag used)
+- `/workflow:tools:test-task-generate --cli-execute` - Phase 4: With CLI execution mode for IMPL-001 test generation (when `--cli-execute` flag used)
 
 **Follow-up Commands**:
 - `/workflow:status` - Review generated test tasks

.claude/commands/workflow/tools/conflict-resolution.md

@@ -1,6 +1,6 @@
 ---
 name: conflict-resolution
-description: Detect and resolve conflicts between plan and existing codebase using CLI-powered analysis
+description: Detect and resolve conflicts between plan and existing codebase using CLI-powered analysis with Gemini/Qwen
 argument-hint: "--session WFS-session-id --context path/to/context-package.json"
 examples:
   - /workflow:tools:conflict-resolution --session WFS-auth --context .workflow/WFS-auth/.process/context-package.json
@@ -24,6 +24,7 @@ Analyzes conflicts between implementation plans and existing codebase, generatin
 | **Generate Strategies** | Provide 2-4 resolution options per conflict |
 | **CLI Analysis** | Use Gemini/Qwen (Claude fallback) |
 | **User Decision** | Present options, never auto-apply |
+| **Direct Text Output** | Output questions via text directly, NEVER use bash echo/printf |
 | **Single Output** | `CONFLICT_RESOLUTION.md` with findings |
 
 ## Conflict Categories

.claude/commands/workflow/tools/context-gather.md

@@ -1,6 +1,6 @@
 ---
 name: gather
-description: Intelligently collect project context using context-search-agent based on task description and package into standardized JSON
+description: Intelligently collect project context using context-search-agent based on task description, packages into standardized JSON
 argument-hint: "--session WFS-session-id \"task description\""
 examples:
   - /workflow:tools:context-gather --session WFS-user-auth "Implement user authentication system"

.claude/commands/workflow/tools/task-generate-agent.md

@@ -1,6 +1,6 @@
 ---
 name: task-generate-agent
-description: Autonomous task generation using action-planning-agent with discovery and output phases
+description: Autonomous task generation using action-planning-agent with discovery and output phases for workflow planning
 argument-hint: "--session WFS-session-id [--cli-execute]"
 examples:
   - /workflow:tools:task-generate-agent --session WFS-auth
@@ -163,155 +163,50 @@ If conflict_risk was medium/high, modifications have been applied to:
 
 ## Phase 2: Document Generation Task
 
-### Task Decomposition Standards
-**Core Principle**: Task Merging Over Decomposition
-- **Merge Rule**: Execute together when possible
-- **Decompose Only When**:
-  - Excessive workload (>2500 lines or >6 files)
-  - Different tech stacks or domains
-  - Sequential dependency blocking
-  - Parallel execution needed
+**Agent Configuration Reference**: All task generation rules, quantification requirements, quality standards, and execution details are defined in action-planning-agent.
 
-**Task Limits**:
-- **Maximum 10 tasks** (hard limit)
-- **Function-based**: Complete units (logic + UI + tests + config)
-- **Hierarchy**: Flat (≤5) | Two-level (6-10) | Re-scope (>10)
+Refer to: @.claude/agents/action-planning-agent.md for:
+- Task Decomposition Standards
+- Quantification Requirements (MANDATORY)
+- 5-Field Task JSON Schema
+- IMPL_PLAN.md Structure
+- TODO_LIST.md Format
+- Execution Flow & Quality Validation
 
-### Required Outputs
+### Required Outputs Summary
 
 #### 1. Task JSON Files (.task/IMPL-*.json)
-**Location**: .workflow/{session-id}/.task/
-**Template**: Read from the template path provided above
-
-**Task JSON Template Loading**:
-\`\`\`
-Read({template_path})
-\`\`\`
-
-**Important**:
-- Read the template from the path provided in context
-- Use the template structure exactly as written
-- Replace placeholder variables ({synthesis_spec_path}, {role_analysis_path}, etc.) with actual session-specific paths
-- Include MCP tool integration in pre_analysis steps
-- Map artifacts based on task domain (UI → ui-designer, Backend → system-architect)
+- **Location**: `.workflow/{session-id}/.task/`
+- **Template**: Read from `{template_path}` (pre-selected by command based on `--cli-execute` flag)
+- **Schema**: 5-field structure (id, title, status, meta, context, flow_control) with artifacts integration
+- **Details**: See action-planning-agent.md § Task JSON Generation
 
 #### 2. IMPL_PLAN.md
-**Location**: .workflow/{session-id}/IMPL_PLAN.md
-
-**IMPL_PLAN Template**:
-\`\`\`
-$(cat ~/.claude/workflows/cli-templates/prompts/workflow/impl-plan-template.txt)
-\`\`\`
-
-**Important**:
-- Use the template above for IMPL_PLAN.md generation
-- Replace all {placeholder} variables with actual session-specific values
-- Populate CCW Workflow Context based on actual phase progression
-- Extract content from role analyses and context-package.json
-- List all detected brainstorming artifacts with correct paths (role analyses, guidance-specification.md)
-- Include conflict resolution status if CONFLICT_RESOLUTION.md exists
+- **Location**: `.workflow/{session-id}/IMPL_PLAN.md`
+- **Template**: `~/.claude/workflows/cli-templates/prompts/workflow/impl-plan-template.txt`
+- **Details**: See action-planning-agent.md § Implementation Plan Creation
 
 #### 3. TODO_LIST.md
-**Location**: .workflow/{session-id}/TODO_LIST.md
-**Structure**:
-\`\`\`markdown
-# Tasks: {Session Topic}
+- **Location**: `.workflow/{session-id}/TODO_LIST.md`
+- **Format**: Hierarchical task list with status indicators (▸, [ ], [x]) and JSON links
+- **Details**: See action-planning-agent.md § TODO List Generation
 
-## Task Progress
-▸ **IMPL-001**: [Main Task Group] → [📋](./.task/IMPL-001.json)
-  - [ ] **IMPL-001.1**: [Subtask] → [📋](./.task/IMPL-001.1.json)
-  - [ ] **IMPL-001.2**: [Subtask] → [📋](./.task/IMPL-001.2.json)
+### Agent Execution Summary
 
-- [ ] **IMPL-002**: [Simple Task] → [📋](./.task/IMPL-002.json)
+**Key Steps** (Detailed instructions in action-planning-agent.md):
+1. Load task JSON template from provided path
+2. Extract and decompose tasks with quantification
+3. Generate task JSON files enforcing quantification requirements
+4. Create IMPL_PLAN.md using template
+5. Generate TODO_LIST.md matching task JSONs
+6. Update session state
 
-## Status Legend
-- \`▸\` = Container task (has subtasks)
-- \`- [ ]\` = Pending leaf task
-- \`- [x]\` = Completed leaf task
-\`\`\`
-
-### Execution Instructions for Agent
-
-**Agent Task**: Generate task JSON files, IMPL_PLAN.md, and TODO_LIST.md based on analysis results
-
-**Note**: The correct task JSON template path has been pre-selected by the command based on the `--cli-execute` flag and is provided in the context as `{template_path}`.
-
-**Step 1: Load Task JSON Template**
-- Read template from the provided path: `Read({template_path})`
-- This template is already the correct one based on execution mode
-
-**Step 2: Extract and Decompose Tasks**
-- Parse role analysis.md files for requirements, design specs, and task recommendations
-- Review synthesis enhancements and clarifications in role analyses
-- Apply conflict resolution strategies (if CONFLICT_RESOLUTION.md exists)
-- Apply task merging rules (merge when possible, decompose only when necessary)
-- Map artifacts to tasks based on domain (UI → ui-designer, Backend → system-architect, Data → data-architect)
-- Ensure task count ≤10
-
-**Step 3: Generate Task JSON Files**
-- Use the template structure from Step 1
-- Create .task/IMPL-*.json files with proper structure
-- Replace all {placeholder} variables with actual session paths
-- Embed artifacts array with brainstorming outputs
-- Include MCP tool integration in pre_analysis steps
-
-**Step 4: Create IMPL_PLAN.md**
-- Use IMPL_PLAN template
-- Populate all sections with session-specific content
-- List artifacts with priorities and usage guidelines
-- Document execution strategy and dependencies
-
-**Step 5: Generate TODO_LIST.md**
-- Create task progress checklist matching generated JSONs
-- Use proper status indicators (▸, [ ], [x])
-- Link to task JSON files
-
-**Step 6: Update Session State**
-- Update workflow-session.json with task count and artifact inventory
-- Mark session ready for execution
-
-### MCP Enhancement Examples
-
-**Code Index Usage**:
-\`\`\`javascript
-// Discover authentication-related files
-bash(find . -name "*auth*" -type f)
-
-// Search for OAuth patterns
-bash(rg "oauth|jwt|authentication" -g "*.{ts,js}")
-
-// Get file summary for key components
-bash(rg "^(class|function|export|interface)" src/auth/index.ts)
-\`\`\`
-
-**Exa Research Usage**:
-\`\`\`javascript
-// Get best practices for task implementation
-mcp__exa__get_code_context_exa(
-  query="TypeScript OAuth2 implementation patterns",
-  tokensNum="dynamic"
-)
-
-// Research specific API usage
-mcp__exa__get_code_context_exa(
-  query="Express.js JWT middleware examples",
-  tokensNum=5000
-)
-\`\`\`
-
-### Quality Validation
-
-Before completion, verify:
-- [ ] All task JSON files created in .task/ directory
-- [ ] Each task JSON has 5 required fields
-- [ ] Artifact references correctly mapped
-- [ ] Flow control includes artifact loading steps
-- [ ] MCP tool integration added where appropriate
-- [ ] IMPL_PLAN.md follows required structure
-- [ ] TODO_LIST.md matches task JSONs
-- [ ] Dependency graph is acyclic
-- [ ] Task count within limits (≤10)
-- [ ] Session state updated
+**Quality Gates** (Full checklist in action-planning-agent.md):
+- ✓ Quantification requirements enforced (explicit counts, measurable acceptance, exact targets)
+- ✓ Task count ≤10 (hard limit)
+- ✓ Artifact references mapped correctly
+- ✓ MCP tool integration added
+- ✓ Documents follow template structure
 
 ## Output
 

.claude/commands/workflow/tools/task-generate-tdd.md

@@ -1,14 +1,28 @@
 ---
 name: task-generate-tdd
-description: Generate TDD task chains with Red-Green-Refactor dependencies
-argument-hint: "--session WFS-session-id [--agent]"
-allowed-tools: Read(*), Write(*), Bash(gemini:*), TodoWrite(*)
+description: Autonomous TDD task generation using action-planning-agent with Red-Green-Refactor cycles, test-first structure, and cycle validation
+argument-hint: "--session WFS-session-id [--cli-execute]"
+examples:
+  - /workflow:tools:task-generate-tdd --session WFS-auth
+  - /workflow:tools:task-generate-tdd --session WFS-auth --cli-execute
 ---
 
-# TDD Task Generation Command
+# Autonomous TDD Task Generation Command
 
 ## Overview
-Generate TDD-specific tasks from analysis results with complete Red-Green-Refactor cycles contained within each task.
+Autonomous TDD task JSON and IMPL_PLAN.md generation using action-planning-agent with two-phase execution: discovery and document generation. Supports both agent-driven execution (default) and CLI tool execution modes. Generates complete Red-Green-Refactor cycles contained within each task.
+
+## Core Philosophy
+- **Agent-Driven**: Delegate execution to action-planning-agent for autonomous operation
+- **Two-Phase Flow**: Discovery (context gathering) → Output (document generation)
+- **Memory-First**: Reuse loaded documents from conversation memory
+- **MCP-Enhanced**: Use MCP tools for advanced code analysis and research
+- **Pre-Selected Templates**: Command selects correct TDD template based on `--cli-execute` flag **before** invoking agent
+- **Agent Simplicity**: Agent receives pre-selected template and focuses only on content generation
+- **Path Clarity**: All `focus_paths` prefer absolute paths (e.g., `D:\\project\\src\\module`), or clear relative paths from project root (e.g., `./src/module`)
+- **TDD-First**: Every feature starts with a failing test (Red phase)
+- **Feature-Complete Tasks**: Each task contains complete Red-Green-Refactor cycle
+- **Quantification-Enforced**: All test cases, coverage requirements, and implementation scope MUST include explicit counts and enumerations
 
 ## Task Strategy & Philosophy
 
@@ -44,359 +58,329 @@ Generate TDD-specific tasks from analysis results with complete Red-Green-Refact
 - **Current approach**: 1 feature = 1 task (IMPL-N with internal Red-Green-Refactor phases)
 - **Complex features**: 1 container (IMPL-N) + subtasks (IMPL-N.M) when necessary
 
-### Core Principles
-- **TDD-First**: Every feature starts with a failing test (Red phase)
-- **Feature-Complete Tasks**: Each task contains complete Red-Green-Refactor cycle
-- **Phase-Explicit**: Internal phases clearly marked in flow_control.implementation_approach
-- **Task Merging**: Prefer single task per feature over decomposition
-- **Path Clarity**: All `focus_paths` prefer absolute paths (e.g., `D:\\project\\src\\module`), or clear relative paths from project root (e.g., `./src/module`)
-- **Artifact-Aware**: Integrates brainstorming outputs
-- **Memory-First**: Reuse loaded documents from memory
-- **Context-Aware**: Analyzes existing codebase and test patterns
-- **Iterative Green Phase**: Auto-diagnose and fix test failures with Gemini + optional Codex
-- **Safety-First**: Auto-revert on max iterations to prevent broken state
-
-## Core Responsibilities
-- Parse analysis results and identify testable features
-- Generate feature-complete tasks with internal TDD cycles (1 task per simple feature)
-- Apply task merging strategy by default, create subtasks only when complexity requires
-- Generate IMPL_PLAN.md with TDD Implementation Tasks section
-- Generate TODO_LIST.md with internal TDD phase indicators
-- Update session state for TDD execution with task count compliance
-
 ## Execution Lifecycle
 
-### Phase 1: Input Validation & Discovery
-**Memory-First Rule**: Skip file loading if documents already in conversation memory
+### Phase 1: Discovery & Context Loading
+**⚡ Memory-First Rule**: Skip file loading if documents already in conversation memory
 
-1. **Session Validation**
-   - If session metadata in memory → Skip loading
-   - Else: Load `.workflow/{session_id}/workflow-session.json`
-
-2. **Conflict Resolution Check** (NEW - Priority Input)
-   - If CONFLICT_RESOLUTION.md exists → Load selected strategies
-   - Else: Skip to brainstorming artifacts
-   - Path: `.workflow/{session_id}/.process/CONFLICT_RESOLUTION.md`
-
-3. **Artifact Discovery**
-   - If artifact inventory in memory → Skip scanning
-   - Else: Scan `.workflow/{session_id}/.brainstorming/` directory
-   - Detect: role analysis documents, guidance-specification.md, role analyses
-
-4. **Context Package Loading**
-   - Load `.workflow/{session_id}/.process/context-package.json`
-   - Load `.workflow/{session_id}/.process/test-context-package.json` (if exists)
-
-### Phase 2: TDD Task JSON Generation
-
-**Input Sources** (priority order):
-1. **Conflict Resolution** (if exists): `.process/CONFLICT_RESOLUTION.md` - Selected resolution strategies
-2. **Brainstorming Artifacts**: Role analysis documents (system-architect, product-owner, etc.)
-3. **Context Package**: `.process/context-package.json` - Project structure and requirements
-4. **Test Context**: `.process/test-context-package.json` - Existing test patterns
-
-**TDD Task Structure includes**:
-- Feature list with testable requirements
-- Test cases for Red phase
-- Implementation requirements for Green phase (with test-fix cycle)
-- Refactoring opportunities
-- Task dependencies and execution order
-- Conflict resolution decisions (if applicable)
-
-### Phase 3: Task JSON & IMPL_PLAN.md Generation
-
-#### Task Structure (Feature-Complete with Internal TDD)
-For each feature, generate task(s) with ID format:
-- **IMPL-N** - Single task containing complete TDD cycle (Red-Green-Refactor)
-- **IMPL-N.M** - Sub-tasks only when feature is complex (>2500 lines or technical blocking)
-
-**Task Dependency Rules**:
-- **Sequential features**: IMPL-2 depends_on ["IMPL-1"] if Feature 2 needs Feature 1
-- **Independent features**: No dependencies, can execute in parallel
-- **Complex features**: IMPL-N.2 depends_on ["IMPL-N.1"] for subtask ordering
-
-**Agent Assignment**:
-- **All IMPL tasks** → `@code-developer` (handles full TDD cycle)
-- Agent executes Red, Green, Refactor phases sequentially within task
-
-**Meta Fields**:
-- `meta.type`: "feature" (TDD-driven feature implementation)
-- `meta.agent`: "@code-developer"
-- `meta.tdd_workflow`: true (enables TDD-specific flow)
-- `meta.tdd_phase`: Not used (phases are in flow_control.implementation_approach)
-- `meta.max_iterations`: 3 (for Green phase test-fix cycle)
-- `meta.use_codex`: false (manual fixes by default)
-
-#### Task JSON Structure Reference
-
-**Simple Feature Task (IMPL-N.json)** - Recommended for most features:
-```json
+**Agent Context Package**:
+```javascript
 {
-  "id": "IMPL-N",                                  // Task identifier
-  "title": "Feature description with TDD",         // Human-readable title
-  "status": "pending",                             // pending | in_progress | completed | container
-  "context_package_path": ".workflow/{session-id}/.process/context-package.json", // Path to smart context package
-  "meta": {
-    "type": "feature",                             // Task type
-    "agent": "@code-developer",                    // Assigned agent
-    "tdd_workflow": true,                          // REQUIRED: Enables TDD flow
-    "max_iterations": 3,                           // Green phase test-fix cycle limit
-    "use_codex": false                             // false=manual fixes, true=Codex automated fixes
+  "session_id": "WFS-[session-id]",
+  "execution_mode": "agent-mode" | "cli-execute-mode",  // Determined by flag
+  "task_json_template_path": "~/.claude/workflows/cli-templates/prompts/workflow/task-json-agent-mode.txt"
+                           | "~/.claude/workflows/cli-templates/prompts/workflow/task-json-cli-mode.txt",
+  // Path selected by command based on --cli-execute flag, agent reads it
+  "workflow_type": "tdd",
+  "session_metadata": {
+    // If in memory: use cached content
+    // Else: Load from .workflow/{session-id}/workflow-session.json
   },
-  "context": {
-    "requirements": [                              // Feature requirements with TDD phases
-      "Feature description",
-      "Red: Test scenarios to write",
-      "Green: Implementation approach with test-fix cycle",
-      "Refactor: Code quality improvements"
-    ],
-    "tdd_cycles": [                                // OPTIONAL: Detailed test cycles
+  "brainstorm_artifacts": {
+    // Loaded from context-package.json → brainstorm_artifacts section
+    "role_analyses": [
       {
-        "cycle": 1,
-        "feature": "Specific functionality",
-        "test_focus": "What to test",
-        "expected_failure": "Why test should fail initially"
+        "role": "system-architect",
+        "files": [{"path": "...", "type": "primary|supplementary"}]
       }
     ],
-    "focus_paths": ["D:\\project\\src\\path", "./tests/path"],  // Absolute or clear relative paths from project root
-    "acceptance": [                                // Success criteria
-      "All tests pass (Red → Green)",
-      "Code refactored (Refactor complete)",
-      "Test coverage ≥80%"
-    ],
-    "depends_on": []                               // Task dependencies
+    "guidance_specification": {"path": "...", "exists": true},
+    "synthesis_output": {"path": "...", "exists": true},
+    "conflict_resolution": {"path": "...", "exists": true}  // if conflict_risk >= medium
   },
-  "flow_control": {
-    "pre_analysis": [                              // OPTIONAL: Pre-execution checks
-      {
-        "step": "check_test_framework",
-        "action": "Verify test framework",
-        "command": "bash(npm list jest)",
-        "output_to": "test_framework_info",
-        "on_error": "warn"
-      }
-    ],
-    "implementation_approach": [                   // REQUIRED: 3 TDD phases
-      {
-        "step": 1,
-        "title": "RED Phase: Write failing tests",
-        "tdd_phase": "red",                        // REQUIRED: Phase identifier
-        "description": "Write comprehensive failing tests",
-        "modification_points": ["Files/changes to make"],
-        "logic_flow": ["Step-by-step process"],
-        "acceptance": ["Phase success criteria"],
-        "depends_on": [],
-        "output": "failing_tests"
-      },
-      {
-        "step": 2,
-        "title": "GREEN Phase: Implement to pass tests",
-        "tdd_phase": "green",                      // REQUIRED: Phase identifier
-        "description": "Minimal implementation with test-fix cycle",
-        "modification_points": ["Implementation files"],
-        "logic_flow": [
-          "Implement minimal code",
-          "Run tests",
-          "If fail → Enter iteration loop (max 3):",
-          "  1. Extract failure messages",
-          "  2. Gemini bug-fix diagnosis",
-          "  3. Apply fixes",
-          "  4. Rerun tests",
-          "If max_iterations → Auto-revert"
-        ],
-        "acceptance": ["All tests pass"],
-        "command": "bash(npm test -- tests/path/)",
-        "depends_on": [1],
-        "output": "passing_implementation"
-      },
-      {
-        "step": 3,
-        "title": "REFACTOR Phase: Improve code quality",
-        "tdd_phase": "refactor",                   // REQUIRED: Phase identifier
-        "description": "Refactor while keeping tests green",
-        "modification_points": ["Quality improvements"],
-        "logic_flow": ["Incremental refactoring with test verification"],
-        "acceptance": ["Tests still pass", "Code quality improved"],
-        "command": "bash(npm run lint && npm test)",
-        "depends_on": [2],
-        "output": "refactored_implementation"
-      }
-    ],
-    "post_completion": [                           // OPTIONAL: Final verification
-      {
-        "step": "verify_full_tdd_cycle",
-        "action": "Confirm complete TDD cycle",
-        "command": "bash(npm test && echo 'TDD complete')",
-        "output_to": "final_validation",
-        "on_error": "fail"
-      }
-    ],
-    "error_handling": {                            // OPTIONAL: Error recovery
-      "green_phase_max_iterations": {
-        "action": "revert_all_changes",
-        "commands": ["bash(git reset --hard HEAD)"],
-        "report": "Generate failure report"
-      }
-    }
+  "context_package_path": ".workflow/{session-id}/.process/context-package.json",
+  "context_package": {
+    // If in memory: use cached content
+    // Else: Load from .workflow/{session-id}/.process/context-package.json
+  },
+  "test_context_package_path": ".workflow/{session-id}/.process/test-context-package.json",
+  "test_context_package": {
+    // Existing test patterns and coverage analysis
+  },
+  "mcp_capabilities": {
+    "code_index": true,
+    "exa_code": true,
+    "exa_web": true
   }
 }
 ```
 
-**Key JSON Fields Summary**:
-- `meta.tdd_workflow`: Must be `true`
-- `meta.max_iterations`: Green phase fix cycle limit (default: 3)
-- `meta.use_codex`: Automated fixes (false=manual, true=Codex)
-- `flow_control.implementation_approach`: Exactly 3 steps with `tdd_phase`: "red", "green", "refactor"
-- `context.tdd_cycles`: Optional detailed test cycle specifications
-- `context.parent`: Required for subtasks (IMPL-N.M)
+**Discovery Actions**:
+1. **Load Session Context** (if not in memory)
+   ```javascript
+   if (!memory.has("workflow-session.json")) {
+     Read(.workflow/{session-id}/workflow-session.json)
+   }
+   ```
 
-#### IMPL_PLAN.md Structure
+2. **Load Context Package** (if not in memory)
+   ```javascript
+   if (!memory.has("context-package.json")) {
+     Read(.workflow/{session-id}/.process/context-package.json)
+   }
+   ```
 
-Generate IMPL_PLAN.md with 8-section structure:
+3. **Load Test Context Package** (if not in memory)
+   ```javascript
+   if (!memory.has("test-context-package.json")) {
+     Read(.workflow/{session-id}/.process/test-context-package.json)
+   }
+   ```
 
-**Frontmatter** (required fields):
-```yaml
----
-identifier: WFS-{session-id}
-source: "User requirements" | "File: path"
-conflict_resolution: .workflow/{session-id}/.process/CONFLICT_RESOLUTION.md  # if exists
-context_package: .workflow/{session-id}/.process/context-package.json
-context_package_path: .workflow/{session-id}/.process/context-package.json
-test_context: .workflow/{session-id}/.process/test-context-package.json  # if exists
-workflow_type: "tdd"
-verification_history:
-  conflict_resolution: "executed | skipped" # based on conflict_risk
-  action_plan_verify: "pending"
-phase_progression: "brainstorm → context → test_context → conflict_resolution → tdd_planning"
-feature_count: N
-task_count: N  # ≤10 total
-task_breakdown:
-  simple_features: K
-  complex_features: L
-  total_subtasks: M
-tdd_workflow: true
----
+4. **Extract & Load Role Analyses** (from context-package.json)
+   ```javascript
+   // Extract role analysis paths from context package
+   const roleAnalysisPaths = contextPackage.brainstorm_artifacts.role_analyses
+     .flatMap(role => role.files.map(f => f.path));
+
+   // Load each role analysis file
+   roleAnalysisPaths.forEach(path => Read(path));
+   ```
+
+5. **Load Conflict Resolution** (from context-package.json, if exists)
+   ```javascript
+   if (contextPackage.brainstorm_artifacts.conflict_resolution?.exists) {
+     Read(contextPackage.brainstorm_artifacts.conflict_resolution.path)
+   }
+   ```
+
+6. **Code Analysis with Native Tools** (optional - enhance understanding)
+   ```bash
+   # Find relevant test files and patterns
+   find . -name "*test*" -type f
+   rg "describe|it\(|test\(" -g "*.ts"
+   ```
+
+7. **MCP External Research** (optional - gather TDD best practices)
+   ```javascript
+   // Get external TDD examples and patterns
+   mcp__exa__get_code_context_exa(
+     query="TypeScript TDD best practices Red-Green-Refactor",
+     tokensNum="dynamic"
+   )
+   ```
+
+### Phase 2: Agent Execution (Document Generation)
+
+**Pre-Agent Template Selection** (Command decides path before invoking agent):
+```javascript
+// Command checks flag and selects template PATH (not content)
+const templatePath = hasCliExecuteFlag
+  ? "~/.claude/workflows/cli-templates/prompts/workflow/task-json-cli-mode.txt"
+  : "~/.claude/workflows/cli-templates/prompts/workflow/task-json-agent-mode.txt";
 ```
 
-**8 Sections Structure**:
+**Agent Invocation**:
+```javascript
+Task(
+  subagent_type="action-planning-agent",
+  description="Generate TDD task JSON and implementation plan",
+  prompt=`
+## Execution Context
 
-```markdown
-# Implementation Plan: {Project Title}
+**Session ID**: WFS-{session-id}
+**Workflow Type**: TDD
+**Execution Mode**: {agent-mode | cli-execute-mode}
+**Task JSON Template Path**: {template_path}
 
-## 1. Summary
-- Core requirements and objectives (2-3 paragraphs)
-- TDD-specific technical approach
+## Phase 1: Discovery Results (Provided Context)
 
-## 2. Context Analysis
-- CCW Workflow Context (Phase progression, Quality gates)
-- Context Package Summary (Focus paths, Test context)
-- Project Profile (Type, Scale, Tech Stack, Timeline)
-- Module Structure (Directory tree)
-- Dependencies (Primary, Testing, Development)
-- Patterns & Conventions
+### Session Metadata
+{session_metadata_content}
 
-## 3. Brainstorming Artifacts Reference
-- Artifact Usage Strategy
-  - CONFLICT_RESOLUTION.md (if exists - selected resolution strategies)
-  - role analysis documents (primary reference)
-  - test-context-package.json (test patterns)
-  - context-package.json (smart context)
-- Artifact Priority in Development
+### Role Analyses (Enhanced by Synthesis)
+{role_analyses_content}
+- Includes requirements, design specs, enhancements, and clarifications from synthesis phase
 
-## 4. Implementation Strategy
-- Execution Strategy (TDD Cycles: Red-Green-Refactor)
-- Architectural Approach
-- Key Dependencies (Task dependency graph)
-- Testing Strategy (Coverage targets, Quality gates)
+### Artifacts Inventory
+- **Guidance Specification**: {guidance_spec_path}
+- **Role Analyses**: {role_analyses_list}
 
-## 5. TDD Implementation Tasks
-- Feature-by-Feature TDD Tasks
-  - Each task: IMPL-N with internal Red → Green → Refactor
-  - Dependencies and complexity metrics
-- Complex Feature Examples (when subtasks needed)
-- TDD Task Breakdown Summary
+### Context Package
+{context_package_summary}
+- Includes conflict_risk assessment
 
-## 6. Implementation Plan (Detailed Phased Breakdown)
-- Execution Strategy (feature-by-feature sequential)
-- Phase breakdown (Phase 1, Phase 2, etc.)
-- Resource Requirements (Team, Dependencies, Infrastructure)
+### Test Context Package
+{test_context_package_summary}
+- Existing test patterns, framework config, coverage analysis
 
-## 7. Risk Assessment & Mitigation
-- Risk table (Risk, Impact, Probability, Mitigation, Owner)
-- Critical Risks (TDD-specific)
-- Monitoring Strategy
+### Conflict Resolution (Conditional)
+If conflict_risk was medium/high, modifications have been applied to:
+- **guidance-specification.md**: Design decisions updated to resolve conflicts
+- **Role analyses (*.md)**: Recommendations adjusted for compatibility
+- **context-package.json**: Marked as "resolved" with conflict IDs
+- NO separate CONFLICT_RESOLUTION.md file (conflicts resolved in-place)
 
-## 8. Success Criteria
-- Functional Completeness
-- Technical Quality (Test coverage ≥80%)
-- Operational Readiness
-- TDD Compliance
+### MCP Analysis Results (Optional)
+**Code Structure**: {mcp_code_index_results}
+**External Research**: {mcp_exa_research_results}
+
+## Phase 2: TDD Document Generation Task
+
+**Agent Configuration Reference**: All TDD task generation rules, quantification requirements, Red-Green-Refactor cycle structure, quality standards, and execution details are defined in action-planning-agent.
+
+Refer to: @.claude/agents/action-planning-agent.md for:
+- TDD Task Decomposition Standards
+- Red-Green-Refactor Cycle Requirements
+- Quantification Requirements (MANDATORY)
+- 5-Field Task JSON Schema
+- IMPL_PLAN.md Structure (TDD variant)
+- TODO_LIST.md Format
+- TDD Execution Flow & Quality Validation
+
+### TDD-Specific Requirements Summary
+
+#### Task Structure Philosophy
+- **1 feature = 1 task** containing complete TDD cycle internally
+- Each task executes Red-Green-Refactor phases sequentially
+- Task count = Feature count (typically 5 features = 5 tasks)
+- Subtasks only when complexity >2500 lines or >6 files per cycle
+- **Maximum 10 tasks** (hard limit for TDD workflows)
+
+#### TDD Cycle Mapping
+- **Simple features**: IMPL-N with internal Red-Green-Refactor phases
+- **Complex features**: IMPL-N (container) + IMPL-N.M (subtasks)
+- Each cycle includes: test_count, test_cases array, implementation_scope, expected_coverage
+
+#### Required Outputs Summary
+
+##### 1. TDD Task JSON Files (.task/IMPL-*.json)
+- **Location**: `.workflow/{session-id}/.task/`
+- **Template**: Read from `{template_path}` (pre-selected by command based on `--cli-execute` flag)
+- **Schema**: 5-field structure with TDD-specific metadata
+  - `meta.tdd_workflow`: true (REQUIRED)
+  - `meta.max_iterations`: 3 (Green phase test-fix cycle limit)
+  - `meta.use_codex`: false (manual fixes by default)
+  - `context.tdd_cycles`: Array with quantified test cases and coverage
+  - `flow_control.implementation_approach`: Exactly 3 steps with `tdd_phase` field
+    1. Red Phase (`tdd_phase: "red"`): Write failing tests
+    2. Green Phase (`tdd_phase: "green"`): Implement to pass tests
+    3. Refactor Phase (`tdd_phase: "refactor"`): Improve code quality
+- **Details**: See action-planning-agent.md § TDD Task JSON Generation
+
+##### 2. IMPL_PLAN.md (TDD Variant)
+- **Location**: `.workflow/{session-id}/IMPL_PLAN.md`
+- **Template**: `~/.claude/workflows/cli-templates/prompts/workflow/impl-plan-template.txt`
+- **TDD-Specific Frontmatter**: workflow_type="tdd", tdd_workflow=true, feature_count, task_breakdown
+- **TDD Implementation Tasks Section**: Feature-by-feature with internal Red-Green-Refactor cycles
+- **Details**: See action-planning-agent.md § TDD Implementation Plan Creation
+
+##### 3. TODO_LIST.md
+- **Location**: `.workflow/{session-id}/TODO_LIST.md`
+- **Format**: Hierarchical task list with internal TDD phase indicators (Red → Green → Refactor)
+- **Status**: ▸ (container), [ ] (pending), [x] (completed)
+- **Details**: See action-planning-agent.md § TODO List Generation
+
+### Quantification Requirements (MANDATORY)
+
+**Core Rules**:
+1. **Explicit Test Case Counts**: Red phase specifies exact number with enumerated list
+2. **Quantified Coverage**: Acceptance includes measurable percentage (e.g., ">=85%")
+3. **Detailed Implementation Scope**: Green phase enumerates files, functions, line counts
+4. **Enumerated Refactoring Targets**: Refactor phase lists specific improvements with counts
+
+**TDD Phase Formats**:
+- **Red Phase**: "Write N test cases: [test1, test2, ...]"
+- **Green Phase**: "Implement N functions in file lines X-Y: [func1() X1-Y1, func2() X2-Y2, ...]"
+- **Refactor Phase**: "Apply N refactorings: [improvement1 (details), improvement2 (details), ...]"
+- **Acceptance**: "All N tests pass with >=X% coverage: verify by [test command]"
+
+**Validation Checklist**:
+- [ ] Every Red phase specifies exact test case count with enumerated list
+- [ ] Every Green phase enumerates files, functions, and estimated line counts
+- [ ] Every Refactor phase lists specific improvements with counts
+- [ ] Every acceptance criterion includes measurable coverage percentage
+- [ ] tdd_cycles array contains test_count and test_cases for each cycle
+- [ ] No vague language ("comprehensive", "complete", "thorough")
+
+### Agent Execution Summary
+
+**Key Steps** (Detailed instructions in action-planning-agent.md):
+1. Load task JSON template from provided path
+2. Extract and decompose features with TDD cycles
+3. Generate TDD task JSON files enforcing quantification requirements
+4. Create IMPL_PLAN.md using TDD template variant
+5. Generate TODO_LIST.md with TDD phase indicators
+6. Update session state with TDD metadata
+
+**Quality Gates** (Full checklist in action-planning-agent.md):
+- ✓ Quantification requirements enforced (explicit counts, measurable acceptance, exact targets)
+- ✓ Task count ≤10 (hard limit)
+- ✓ Each task has meta.tdd_workflow: true
+- ✓ Each task has exactly 3 implementation steps with tdd_phase field
+- ✓ Green phase includes test-fix cycle logic
+- ✓ Artifact references mapped correctly
+- ✓ MCP tool integration added
+- ✓ Documents follow TDD template structure
+
+## Output
+
+Generate all three documents and report completion status:
+- TDD task JSON files created: N files (IMPL-*.json)
+- TDD cycles configured: N cycles with quantified test cases
+- Artifacts integrated: synthesis-spec, guidance-specification, N role analyses
+- Test context integrated: existing patterns and coverage
+- MCP enhancements: code-index, exa-research
+- Session ready for TDD execution: /workflow:execute
+`
+)
 ```
 
-### Phase 4: TODO_LIST.md Generation
+### Agent Context Passing
 
-Generate task list with internal TDD phase indicators:
+**Memory-Aware Context Assembly**:
+```javascript
+// Assemble context package for agent
+const agentContext = {
+  session_id: "WFS-[id]",
+  workflow_type: "tdd",
 
-**For Simple Features (1 task per feature)**:
-```markdown
-## TDD Implementation Tasks
+  // Use memory if available, else load
+  session_metadata: memory.has("workflow-session.json")
+    ? memory.get("workflow-session.json")
+    : Read(.workflow/WFS-[id]/workflow-session.json),
 
-### Feature 1: {Feature Name}
-- [ ] **IMPL-1**: Implement {feature} with TDD → [Task](./.task/IMPL-1.json)
-  - Internal phases: Red → Green → Refactor
-  - Dependencies: None
+  context_package_path: ".workflow/WFS-[id]/.process/context-package.json",
 
-### Feature 2: {Feature Name}
-- [ ] **IMPL-2**: Implement {feature} with TDD → [Task](./.task/IMPL-2.json)
-  - Internal phases: Red → Green → Refactor
-  - Dependencies: IMPL-1
-```
+  context_package: memory.has("context-package.json")
+    ? memory.get("context-package.json")
+    : Read(".workflow/WFS-[id]/.process/context-package.json"),
 
-**For Complex Features (with subtasks)**:
-```markdown
-### Feature 3: {Complex Feature Name}
-▸ **IMPL-3**: Implement {complex feature} with TDD → [Task](./.task/IMPL-3.json)
-  - [ ] **IMPL-3.1**: {Sub-feature A} with TDD → [Task](./.task/IMPL-3.1.json)
-    - Internal phases: Red → Green → Refactor
-  - [ ] **IMPL-3.2**: {Sub-feature B} with TDD → [Task](./.task/IMPL-3.2.json)
-    - Internal phases: Red → Green → Refactor
-    - Dependencies: IMPL-3.1
-```
+  test_context_package_path: ".workflow/WFS-[id]/.process/test-context-package.json",
 
-**Status Legend**:
-```markdown
-## Status Legend
-- ▸ = Container task (has subtasks)
-- [ ] = Pending task
-- [x] = Completed task
-- Red = Write failing tests
-- Green = Implement to pass tests (with test-fix cycle)
-- Refactor = Improve code quality
-```
+  test_context_package: memory.has("test-context-package.json")
+    ? memory.get("test-context-package.json")
+    : Read(".workflow/WFS-[id]/.process/test-context-package.json"),
 
-### Phase 5: Session State Update
+  // Extract brainstorm artifacts from context package
+  brainstorm_artifacts: extractBrainstormArtifacts(context_package),
 
-Update workflow-session.json with TDD metadata:
-```json
-{
-  "workflow_type": "tdd",
-  "feature_count": 5,
-  "task_count": 5,
-  "task_breakdown": {
-    "simple_features": 4,
-    "complex_features": 1,
-    "total_subtasks": 2
-  },
-  "tdd_workflow": true,
-  "task_limit_compliance": true
+  // Load role analyses using paths from context package
+  role_analyses: brainstorm_artifacts.role_analyses
+    .flatMap(role => role.files)
+    .map(file => Read(file.path)),
+
+  // Load conflict resolution if exists (from context package)
+  conflict_resolution: brainstorm_artifacts.conflict_resolution?.exists
+    ? Read(brainstorm_artifacts.conflict_resolution.path)
+    : null,
+
+  // Optional MCP enhancements
+  mcp_analysis: executeMcpDiscovery()
 }
 ```
 
-**Task Count Calculation**:
-- **Simple features**: 1 task each (IMPL-N with internal TDD cycle)
-- **Complex features**: 1 container + M subtasks (IMPL-N + IMPL-N.M)
-- **Total**: Simple feature count + Complex feature subtask count
-- **Example**: 4 simple + 1 complex (with 2 subtasks) = 6 total tasks (not 15)
+## TDD Task Structure Reference
+
+This section provides quick reference for TDD task JSON structure. For complete implementation details, see the agent invocation prompt in Phase 2 above.
+
+**Quick Reference**:
+- Each TDD task contains complete Red-Green-Refactor cycle
+- Task ID format: `IMPL-N` (simple) or `IMPL-N.M` (complex subtasks)
+- Required metadata: `meta.tdd_workflow: true`, `meta.max_iterations: 3`
+- Flow control: Exactly 3 steps with `tdd_phase` field (red, green, refactor)
+- Context: `tdd_cycles` array with quantified test cases and coverage
+- See Phase 2 agent prompt for full schema and requirements
 
 ## Output Files Structure
 ```
@@ -465,52 +449,30 @@ Update workflow-session.json with TDD metadata:
 
 ## Integration & Usage
 
-### Command Chain
-- **Called By**: `/workflow:tdd-plan` (Phase 4)
-- **Calls**: Gemini CLI for TDD breakdown
-- **Followed By**: `/workflow:execute`, `/workflow:tdd-verify`
+**Command Chain**:
+- Called by: `/workflow:tdd-plan` (Phase 4)
+- Invokes: `action-planning-agent` for autonomous task generation
+- Followed by: `/workflow:execute`, `/workflow:tdd-verify`
 
-### Basic Usage
+**Basic Usage**:
 ```bash
-# Manual mode (default)
+# Agent mode (default, autonomous execution)
 /workflow:tools:task-generate-tdd --session WFS-auth
 
-# Agent mode (autonomous task generation)
-/workflow:tools:task-generate-tdd --session WFS-auth --agent
+# CLI tool mode (use Gemini/Qwen for generation)
+/workflow:tools:task-generate-tdd --session WFS-auth --cli-execute
 ```
 
-### Expected Output
-```
-TDD task generation complete for session: WFS-auth
+**Execution Modes**:
+- **Agent mode** (default): Uses `action-planning-agent` with agent-mode task template
+- **CLI mode** (`--cli-execute`): Uses Gemini/Qwen with cli-mode task template
 
-Features analyzed: 5
-Total tasks: 5 (1 task per feature with internal TDD cycles)
-
-Task breakdown:
-- Simple features: 4 tasks (IMPL-1 to IMPL-4)
-- Complex features: 1 task with 2 subtasks (IMPL-5, IMPL-5.1, IMPL-5.2)
-- Total task count: 6 (within 10-task limit)
-
-Structure:
-- IMPL-1: User Authentication (Internal: Red → Green → Refactor)
-- IMPL-2: Password Reset (Internal: Red → Green → Refactor)
-- IMPL-3: Email Verification (Internal: Red → Green → Refactor)
-- IMPL-4: Role Management (Internal: Red → Green → Refactor)
-- IMPL-5: Payment System (Container)
-  - IMPL-5.1: Gateway Integration (Internal: Red → Green → Refactor)
-  - IMPL-5.2: Transaction Management (Internal: Red → Green → Refactor)
-
-Plans generated:
-- Unified Plan: .workflow/WFS-auth/IMPL_PLAN.md (includes TDD Implementation Tasks section)
-- Task List: .workflow/WFS-auth/TODO_LIST.md (with internal TDD phase indicators)
-
-TDD Configuration:
-- Each task contains complete Red-Green-Refactor cycle
-- Green phase includes test-fix cycle (max 3 iterations)
-- Auto-revert on max iterations reached
-
-Next: /workflow:action-plan-verify --session WFS-auth (recommended) or /workflow:execute --session WFS-auth
-```
+**Output**:
+- TDD task JSON files in `.task/` directory (IMPL-N.json format)
+- IMPL_PLAN.md with TDD Implementation Tasks section
+- TODO_LIST.md with internal TDD phase indicators
+- Session state updated with task count and TDD metadata
+- MCP enhancements integrated (if available)
 
 ## Test Coverage Analysis Integration
 

.claude/commands/workflow/tools/task-generate.md

@@ -1,6 +1,6 @@
 --- 
 name: task-generate
-description: Generate task JSON files and IMPL_PLAN.md from analysis results with artifacts integration
+description: Generate task JSON files and IMPL_PLAN.md from analysis results using action-planning-agent with artifact integration
 argument-hint: "--session WFS-session-id [--cli-execute]"
 examples:
   - /workflow:tools:task-generate --session WFS-auth
@@ -45,8 +45,33 @@ This command is built on a set of core principles to ensure efficient and reliab
 - **Memory-First**: Prioritizes using documents already loaded in conversation memory to avoid redundant file operations
 - **Mode-Flexible**: Supports both agent-driven execution (default) and CLI tool execution (with `--cli-execute` flag)
 - **Multi-Step Support**: Complex tasks can use multiple sequential steps in `implementation_approach` with codex resume mechanism
+- **Quantification-Enforced**: **NEW** - All requirements, acceptance criteria, and modification points MUST include explicit counts and enumerations to prevent ambiguity (e.g., "17 commands: [list]" not "implement commands")
 - **Responsibility**: Parses analysis, detects artifacts, generates enhanced task JSONs, creates `IMPL_PLAN.md` and `TODO_LIST.md`, updates session state
 
+## 3.5. Quantification Requirements (MANDATORY)
+
+**Purpose**: Eliminate ambiguity by enforcing explicit counts and enumerations in all task specifications.
+
+**Core Rules**:
+1. **Extract Counts from Analysis**: Search for HOW MANY items and list them explicitly
+2. **Enforce Explicit Lists**: Every deliverable uses format `{count} {type}: [{explicit_list}]`
+3. **Make Acceptance Measurable**: Include verification commands (e.g., `ls ... | wc -l = N`)
+4. **Quantify Modification Points**: Specify exact targets (files, functions with line numbers)
+5. **Avoid Vague Language**: Replace "complete", "comprehensive", "reorganize" with quantified statements
+
+**Standard Formats**:
+
+- **Requirements**: `"Implement N items: [item1, item2, ...]"` or `"Modify N files: [file1:func:lines, ...]"`
+- **Acceptance**: `"N items exist: verify by [command]"` or `"Coverage >= X%: verify by [test command]"`
+- **Modification Points**: `"Create N files: [list]"` or `"Modify N functions: [func() in file lines X-Y]"`
+
+**Validation Checklist**:
+- [ ] Every requirement contains explicit count or enumerated list
+- [ ] Every acceptance criterion is measurable with verification command
+- [ ] Every modification_point specifies exact targets (files/functions/lines)
+- [ ] No vague language ("complete", "comprehensive", "reorganize" without counts)
+- [ ] Each implementation step has its own acceptance criteria
+
 ## 4. Execution Flow
 The command follows a streamlined, three-step process to convert analysis into executable tasks.
 
@@ -59,13 +84,39 @@ The process begins by gathering all necessary inputs. It follows a **Memory-Firs
 
 ### Step 2: Task Decomposition & Grouping
 Once all inputs are loaded, the command analyzes the tasks defined in the analysis results and groups them based on shared context.
-1.  **Task Definition Parsing**: Extracts task definitions, requirements, and dependencies.
-2.  **Context Signature Analysis**: Computes a unique hash (`context_signature`) for each task based on its `focus_paths` and referenced `artifacts`.
+
+**Phase 2.1: Quantification Extraction (NEW - CRITICAL)**
+1. **Count Extraction**: Scan analysis documents for quantifiable information:
+   - Search for numbers + nouns (e.g., "5 files", "17 commands", "3 features")
+   - Identify enumerated lists (bullet points, numbered lists, comma-separated items)
+   - Extract explicit counts from tables, diagrams, or structured data
+   - Store extracted counts with their context (what is being counted)
+
+2. **List Enumeration**: Build explicit lists for each deliverable:
+   - If analysis says "implement session commands", enumerate ALL commands: [start, resume, list, complete, archive]
+   - If analysis mentions "create categories", list ALL categories: [literature, experiment, data-analysis, visualization, context]
+   - If analysis describes "modify functions", list ALL functions with line numbers
+   - Maintain full enumerations (no "..." unless list exceeds 20 items)
+
+3. **Verification Method Assignment**: For each deliverable, determine verification approach:
+   - File count: `ls {path}/*.{ext} | wc -l = {count}`
+   - Directory existence: `ls {parent}/ | grep -E '(name1|name2|...)' | wc -l = {count}`
+   - Test coverage: `pytest --cov={module} --cov-report=term | grep TOTAL | awk '{print $4}' >= {percentage}`
+   - Function existence: `grep -E '(func1|func2|...)' {file} | wc -l = {count}`
+
+4. **Ambiguity Detection**: Flag vague language for replacement:
+   - Detect words: "complete", "comprehensive", "reorganize", "refactor", "implement", "create" without counts
+   - Require quantification: "implement" → "implement {N} {items}: [{list}]"
+   - Reject unquantified deliverables
+
+**Phase 2.2: Task Definition & Grouping**
+1.  **Task Definition Parsing**: Extracts task definitions, requirements, and dependencies from quantified analysis
+2.  **Context Signature Analysis**: Computes a unique hash (`context_signature`) for each task based on its `focus_paths` and referenced `artifacts`
 3.  **Task Grouping**:
-    *   Tasks with the **same signature** are candidates for merging, as they operate on the same context.
-    *   Tasks with **different signatures** and no dependencies are grouped for parallel execution.
-    *   Tasks with `depends_on` relationships are marked for sequential execution.
-4.  **Modification Target Determination**: Extracts specific code locations (`file:function:lines`) from the analysis to populate the `target_files` field.
+    *   Tasks with the **same signature** are candidates for merging, as they operate on the same context
+    *   Tasks with **different signatures** and no dependencies are grouped for parallel execution
+    *   Tasks with `depends_on` relationships are marked for sequential execution
+4.  **Modification Target Determination**: Extracts specific code locations (`file:function:lines`) from the analysis to populate the `target_files` field
 
 ### Step 3: Output Generation
 Finally, the command generates all the necessary output files.
@@ -167,38 +218,82 @@ function assignExecutionGroups(tasks) {
 The command produces three key documents and a directory of task files.
 
 ### 6.1. Task JSON Schema (`.task/IMPL-*.json`)
-This enhanced 5-field schema embeds all necessary context, artifacts, and execution steps.
+Each task JSON embeds all necessary context, artifacts, and execution steps using this schema:
 
+**Top-Level Fields**:
+- `id`: Task identifier (format: `IMPL-N` or `IMPL-N.M` for subtasks)
+- `title`: Descriptive task name
+- `status`: Task state (`pending|active|completed|blocked|container`)
+- `context_package_path`: Path to context package (`.workflow/WFS-[session]/.process/context-package.json`)
+- `meta`: Task metadata
+- `context`: Task-specific context and requirements
+- `flow_control`: Execution steps and workflow
+
+**Meta Object**:
+- `type`: Task category (`feature|bugfix|refactor|test-gen|test-fix|docs`)
+- `agent`: Assigned agent (`@code-developer|@test-fix-agent|@universal-executor`)
+- `execution_group`: Parallelization group ID or null
+- `context_signature`: Hash for context-based grouping
+
+**Context Object**:
+- `requirements`: Quantified implementation requirements (with counts and explicit lists)
+- `focus_paths`: Target directories/files (absolute or relative paths)
+- `acceptance`: Measurable acceptance criteria (with verification commands)
+- `parent`: Parent task ID for subtasks
+- `depends_on`: Prerequisite task IDs
+- `inherited`: Shared patterns and dependencies from parent
+- `shared_context`: Tech stack and conventions
+- `artifacts`: Referenced brainstorm artifacts with paths, priority, and usage
+
+**Flow Control Object**:
+- `pre_analysis`: Context loading and preparation steps
+  - `load_context_package`: Load smart context and artifact catalog
+  - `load_role_analysis_artifacts`: Load role analyses dynamically from context package
+  - `load_planning_context`: Load finalized decisions with resolved conflicts
+  - `codebase_exploration`: Discover existing patterns
+  - `analyze_task_patterns`: Identify modification targets
+- `implementation_approach`: Execution steps
+  - **Agent Mode**: Steps contain `modification_points` and `logic_flow` (agent executes autonomously)
+  - **CLI Mode**: Steps include `command` field with CLI tool invocation
+- `target_files`: Specific files/functions/lines to modify
+
+**Key Characteristics**:
+- **Quantification**: All requirements/acceptance use explicit counts and enumerations
+- **Mode Flexibility**: Supports both agent execution (default) and CLI tool execution (`--cli-execute`)
+- **Context Intelligence**: References context-package.json for smart context and artifact paths
+- **Artifact Integration**: Dynamically loads role analyses and brainstorm artifacts
+
+**Example Task JSON**:
 ```json
 {
-  "id": "IMPL-N[.M]",
-  "title": "Descriptive task name",
-  "status": "pending|active|completed|blocked|container",
-  "context_package_path": ".workflow/WFS-[session]/.process/context-package.json",
+  "id": "IMPL-1",
+  "title": "Implement feature X with Y components",
+  "status": "pending",
+  "context_package_path": ".workflow/WFS-session/.process/context-package.json",
   "meta": {
-    "type": "feature|bugfix|refactor|test-gen|test-fix|docs",
-    "agent": "@code-developer|@test-fix-agent|@universal-executor",
-    "execution_group": "group-id|null",
-    "context_signature": "hash-of-focus_paths-and-artifacts"
+    "type": "feature",
+    "agent": "@code-developer",
+    "execution_group": "parallel-abc123",
+    "context_signature": "hash-value"
   },
   "context": {
-    "requirements": ["Clear requirement from analysis"],
-    "focus_paths": ["D:\\project\\src\\module\\path", "./tests/module/path"],
-    "acceptance": ["Measurable acceptance criterion"],
-    "parent": "IMPL-N",
-    "depends_on": ["IMPL-N.M"],
-    "inherited": {"shared_patterns": [], "common_dependencies": []},
-    "shared_context": {"tech_stack": [], "conventions": []},
+    "requirements": [
+      "Implement 5 commands: [cmd1, cmd2, cmd3, cmd4, cmd5]",
+      "Create 3 directories: [dir1/, dir2/, dir3/]",
+      "Modify 2 functions: [funcA() in file1.ts lines 10-25, funcB() in file2.ts lines 40-60]"
+    ],
+    "focus_paths": ["D:\\project\\src\\module", "./tests/module"],
+    "acceptance": [
+      "5 command files created: verify by ls .claude/commands/*/*.md | wc -l = 5",
+      "3 directories exist: verify by ls -d dir*/ | wc -l = 3",
+      "All tests pass: pytest tests/ --cov=src/module (>=80% coverage)"
+    ],
+    "depends_on": [],
     "artifacts": [
       {
-        "path": "{{from context-package.json → brainstorm_artifacts.role_analyses[].files[].path}}",
+        "path": ".workflow/WFS-session/.brainstorming/system-architect/analysis.md",
         "priority": "highest",
-        "usage": "Role-specific requirements, design specs, enhanced by synthesis. Paths loaded dynamically from context-package.json (supports multiple files per role: analysis.md, analysis-01.md, analysis-api.md, etc.). Common roles: product-manager, system-architect, ui-designer, data-architect, ux-expert."
-      },
-      {
-        "path": ".workflow/WFS-[session]/.brainstorming/guidance-specification.md",
-        "priority": "high",
-        "usage": "Finalized design decisions (potentially modified by conflict resolution if conflict_risk was medium/high). Use for: understanding resolved requirements, design choices, conflict resolutions applied in-place"
+        "usage": "Architecture decisions and API specifications"
       }
     ]
   },
@@ -206,18 +301,14 @@ This enhanced 5-field schema embeds all necessary context, artifacts, and execut
     "pre_analysis": [
       {
         "step": "load_context_package",
-        "action": "Load context package for artifact paths",
-        "note": "Context package path is now at top-level field: context_package_path",
-        "commands": [
-          "Read({{context_package_path}})"
-        ],
+        "action": "Load context package for artifact paths and smart context",
+        "commands": ["Read({{context_package_path}})"],
         "output_to": "context_package",
         "on_error": "fail"
       },
       {
         "step": "load_role_analysis_artifacts",
-        "action": "Load role analyses from context-package.json (supports multiple files per role)",
-        "note": "Paths loaded from context-package.json → brainstorm_artifacts.role_analyses[]. Supports analysis*.md automatically.",
+        "action": "Load role analyses from context-package.json",
         "commands": [
           "Read({{context_package_path}})",
           "Extract(brainstorm_artifacts.role_analyses[].files[].path)",
@@ -225,73 +316,36 @@ This enhanced 5-field schema embeds all necessary context, artifacts, and execut
         ],
         "output_to": "role_analysis_artifacts",
         "on_error": "skip_optional"
-      },
-      {
-        "step": "load_planning_context",
-        "action": "Load plan-generated context intelligence with resolved conflicts",
-        "note": "CRITICAL: context-package.json (from context_package_path) provides smart context (focus paths, dependencies, patterns) and conflict resolution status. If conflict_risk was medium/high, conflicts have been resolved in guidance-specification.md and role analyses.",
-        "commands": [
-          "Read({{context_package_path}})",
-          "Read(.workflow/WFS-[session]/.brainstorming/guidance-specification.md)"
-        ],
-        "output_to": "planning_context",
-        "on_error": "fail",
-        "usage_guidance": {
-          "context-package.json": "Use for focus_paths validation, dependency resolution, existing pattern discovery, module structure understanding, conflict_risk status (resolved/none/low)",
-          "guidance-specification.md": "Use for finalized design decisions (includes applied conflict resolutions if any)"
-        }
-      },
-      {
-        "step": "codebase_exploration",
-        "action": "Explore codebase using native tools",
-        "command": "bash(find . -name \"[patterns]\" -type f && rg \"[patterns]\")",
-        "output_to": "codebase_structure"
-      },
-      {
-        "step": "analyze_task_patterns",
-        "action": "Analyze existing code patterns and identify modification targets",
-        "commands": [
-          "bash(cd \"[focus_paths]\")",
-          "bash(gemini \"PURPOSE: Identify modification targets TASK: Analyze '[title]' and locate specific files/functions/lines to modify CONTEXT: [role_analyses] [individual_artifacts] EXPECTED: Code locations in format 'file:function:lines' RULES: Consult role analyses for requirements, identify exact modification points\")"
-        ],
-        "output_to": "task_context_with_targets",
-        "on_error": "fail"
       }
     ],
     "implementation_approach": [
       {
         "step": 1,
-        "title": "Implement task following role analyses and context",
-        "description": "Implement '[title]' following this priority: 1) role analysis.md files (requirements, design specs, enhancements from synthesis), 2) guidance-specification.md (finalized decisions with resolved conflicts), 3) context-package.json (smart context, focus paths, patterns). Role analyses are enhanced by synthesis phase with concept improvements and clarifications. If conflict_risk was medium/high, conflict resolutions are already applied in-place.",
+        "title": "Implement feature following role analyses",
+        "description": "Implement feature X using requirements from role analyses and context package",
         "modification_points": [
-          "Apply requirements and design specs from role analysis documents",
-          "Use enhancements and clarifications from synthesis phase",
-          "Use finalized decisions from guidance-specification.md (includes resolved conflicts)",
-          "Use context-package.json for focus paths and dependency resolution",
-          "Consult specific role artifacts for implementation details when needed",
-          "Integrate with existing patterns"
+          "Create 5 command files: [cmd1.md, cmd2.md, cmd3.md, cmd4.md, cmd5.md]",
+          "Modify funcA() in file1.ts lines 10-25: add validation logic",
+          "Modify funcB() in file2.ts lines 40-60: integrate with new API"
         ],
         "logic_flow": [
-          "Load role analyses (requirements, design, enhancements from synthesis)",
-          "Load guidance-specification.md (finalized decisions with resolved conflicts if any)",
-          "Load context-package.json (smart context: focus paths, dependencies, patterns, conflict_risk status)",
-          "Extract requirements and design decisions from role documents",
-          "Review synthesis enhancements and clarifications",
-          "Use finalized decisions (conflicts already resolved if applicable)",
-          "Identify modification targets using context package",
-          "Implement following role requirements and design specs",
-          "Consult role artifacts for detailed specifications when needed",
+          "Load role analyses and context package",
+          "Extract requirements and design decisions",
+          "Implement commands following existing patterns",
+          "Update functions with new logic",
           "Validate against acceptance criteria"
         ],
         "depends_on": [],
         "output": "implementation"
       }
     ],
-    "target_files": ["file:function:lines"]
+    "target_files": ["file1.ts:funcA:10-25", "file2.ts:funcB:40-60"]
   }
 }
 ```
 
+**Note**: In CLI Execute Mode (`--cli-execute`), `implementation_approach` steps include a `command` field with the CLI tool invocation (e.g., `bash(codex ...)`).
+
 ### 6.2. IMPL_PLAN.md Structure
 This document provides a high-level overview of the entire implementation plan.
 
@@ -585,194 +639,7 @@ Artifacts are mapped to tasks based on their relevance to the task's domain.
 
 This ensures that each task has access to the most relevant and detailed specifications from role-specific analyses.
 
-## 8. CLI Execute Mode Details
-When using `--cli-execute`, each step in `implementation_approach` includes a `command` field with the execution command.
-
-**Key Points**:
-- **Sequential Steps**: Steps execute in order defined in `implementation_approach` array
-    - **Context Delivery**: Each codex command receives context via CONTEXT field: `@{context_package_path}` (role analyses loaded dynamically from context package)- **Multi-Step Tasks**: First step provides full context, subsequent steps use `resume --last` to maintain session continuity
-- **Step Dependencies**: Later steps reference outputs from earlier steps via `depends_on` field
-
-### Example 1: Agent Mode - Simple Task (Default, No Command)
-```json
-{
-  "id": "IMPL-001",
-  "title": "Implement user authentication module",
-  "context_package_path": ".workflow/WFS-session/.process/context-package.json",
-  "context": {
-    "depends_on": [],
-    "focus_paths": ["src/auth"],
-    "requirements": ["JWT-based authentication", "Login and registration endpoints"],
-    "acceptance": [
-      "JWT token generation working",
-      "Login and registration endpoints implemented",
-      "Tests passing with >70% coverage"
-    ]
-  },
-  "flow_control": {
-    "pre_analysis": [
-      {
-        "step": "load_role_analyses",
-        "action": "Load role analyses from context-package.json",
-        "commands": [
-          "Read({{context_package_path}})",
-          "Extract(brainstorm_artifacts.role_analyses[].files[].path)",
-          "Read(each extracted path)"
-        ],
-        "output_to": "role_analyses",
-        "on_error": "fail"
-      },
-      {
-        "step": "load_context",
-        "action": "Load context package for project structure",
-        "commands": ["Read({{context_package_path}})"],
-        "output_to": "context_pkg",
-        "on_error": "fail"
-      }
-    ],
-    "implementation_approach": [
-      {
-        "step": 1,
-        "title": "Implement JWT-based authentication",
-        "description": "Create authentication module using JWT following [role_analyses] requirements and [context_pkg] patterns",
-        "modification_points": [
-          "Create auth service with JWT generation",
-          "Implement login endpoint with credential validation",
-          "Implement registration endpoint with user creation",
-          "Add JWT middleware for route protection"
-        ],
-        "logic_flow": [
-          "User registers → validate input → hash password → create user",
-          "User logs in → validate credentials → generate JWT → return token",
-          "Protected routes → validate JWT → extract user → allow access"
-        ],
-        "depends_on": [],
-        "output": "auth_implementation"
-      }
-    ],
-    "target_files": ["src/auth/service.ts", "src/auth/middleware.ts", "src/routes/auth.ts"]
-  }
-}
-```
-
-### Example 2: CLI Execute Mode - Single Codex Step
-```json
-{
-  "id": "IMPL-002",
-  "title": "Implement user authentication module",
-  "context_package_path": ".workflow/WFS-session/.process/context-package.json",
-  "context": {
-    "depends_on": [],
-    "focus_paths": ["src/auth"],
-    "requirements": ["JWT-based authentication", "Login and registration endpoints"],
-    "acceptance": ["JWT generation working", "Endpoints implemented", "Tests passing"]
-  },
-  "flow_control": {
-    "pre_analysis": [
-      {
-        "step": "load_role_analyses",
-        "action": "Load role analyses from context-package.json",
-        "commands": [
-          "Read({{context_package_path}})",
-          "Extract(brainstorm_artifacts.role_analyses[].files[].path)",
-          "Read(each extracted path)"
-        ],
-        "output_to": "role_analyses",
-        "on_error": "fail"
-      }
-    ],
-    "implementation_approach": [
-      {
-        "step": 1,
-        "title": "Implement authentication with Codex",
-        "description": "Create JWT-based authentication module",
-        "command": "bash(codex -C src/auth --full-auto exec \"PURPOSE: Implement user authentication TASK: JWT-based auth with login/registration MODE: auto CONTEXT: @{{context_package_path}} EXPECTED: Complete auth module with tests RULES: Load role analyses from context-package.json → brainstorm_artifacts\" --skip-git-repo-check -s danger-full-access)",
-        "modification_points": ["Create auth service", "Implement endpoints", "Add JWT middleware"],
-        "logic_flow": ["Validate credentials", "Generate JWT", "Return token"],
-        "depends_on": [],
-        "output": "auth_implementation"
-      }
-    ],
-    "target_files": ["src/auth/service.ts", "src/auth/middleware.ts"]
-  }
-}
-```
-
-### Example 3: CLI Execute Mode - Multi-Step with Resume
-```json
-{
-  "id": "IMPL-003",
-  "title": "Implement role-based access control",
-  "context_package_path": ".workflow/WFS-session/.process/context-package.json",
-  "context": {
-    "depends_on": ["IMPL-002"],
-    "focus_paths": ["src/auth", "src/middleware"],
-    "requirements": ["User roles and permissions", "Route protection middleware"],
-    "acceptance": ["RBAC models created", "Middleware working", "Management API complete"]
-  },
-  "flow_control": {
-    "pre_analysis": [
-      {
-        "step": "load_context",
-        "action": "Load context and role analyses from context-package.json",
-        "commands": [
-          "Read({{context_package_path}})",
-          "Extract(brainstorm_artifacts.role_analyses[].files[].path)",
-          "Read(each extracted path)"
-        ],
-        "output_to": "full_context",
-        "on_error": "fail"
-      }
-    ],
-    "implementation_approach": [
-      {
-        "step": 1,
-        "title": "Create RBAC models",
-        "description": "Define role and permission data models",
-        "command": "bash(codex -C src/auth --full-auto exec \"PURPOSE: Create RBAC models TASK: Role and permission models MODE: auto CONTEXT: @{{context_package_path}} EXPECTED: Models with migrations RULES: Load role analyses from context-package.json → brainstorm_artifacts\" --skip-git-repo-check -s danger-full-access)",
-        "modification_points": ["Define role model", "Define permission model", "Create migrations"],
-        "logic_flow": ["Design schema", "Implement models", "Generate migrations"],
-        "depends_on": [],
-        "output": "rbac_models"
-      },
-      {
-        "step": 2,
-        "title": "Implement RBAC middleware",
-        "description": "Create route protection middleware using models from step 1",
-        "command": "bash(codex --full-auto exec \"PURPOSE: Create RBAC middleware TASK: Route protection middleware MODE: auto CONTEXT: RBAC models from step 1 EXPECTED: Middleware for route protection RULES: Use session patterns\" resume --last --skip-git-repo-check -s danger-full-access)",
-        "modification_points": ["Create permission checker", "Add route decorators", "Integrate with auth"],
-        "logic_flow": ["Check user role", "Validate permissions", "Allow/deny access"],
-        "depends_on": [1],
-        "output": "rbac_middleware"
-      },
-      {
-        "step": 3,
-        "title": "Add role management API",
-        "description": "Create CRUD endpoints for roles and permissions",
-        "command": "bash(codex --full-auto exec \"PURPOSE: Role management API TASK: CRUD endpoints for roles/permissions MODE: auto CONTEXT: Models and middleware from previous steps EXPECTED: Complete API with validation RULES: Maintain consistency\" resume --last --skip-git-repo-check -s danger-full-access)",
-        "modification_points": ["Create role endpoints", "Create permission endpoints", "Add validation"],
-        "logic_flow": ["Define routes", "Implement controllers", "Add authorization"],
-        "depends_on": [2],
-        "output": "role_management_api"
-      }
-    ],
-    "target_files": [
-      "src/models/Role.ts",
-      "src/models/Permission.ts",
-      "src/middleware/rbac.ts",
-      "src/routes/roles.ts"
-    ]
-  }
-}
-```
-
-**Pattern Summary**:
-- **Agent Mode (Example 1)**: No `command` field - agent executes via `modification_points` and `logic_flow`
-- **CLI Mode Single-Step (Example 2)**: One `command` field with full context package
-- **CLI Mode Multi-Step (Example 3)**: First step uses full context, subsequent steps use `resume --last`
-- **Context Delivery**: Context package provided via `@{...}` references in CONTEXT field
-
-## 9. Error Handling
+## 8. Error Handling
 
 ### Input Validation Errors
 | Error | Cause | Resolution |
@@ -795,21 +662,19 @@ When using `--cli-execute`, each step in `implementation_approach` includes a `c
 | Invalid format | Corrupted file | Skip artifact loading |
 | Path invalid | Moved/deleted | Update references |
 
-## 10. Integration & Usage
+## 10. Usage & Related Commands
 
-### Command Chain
-- **Called By**: `/workflow:plan` (Phase 4)
-- **Calls**: None (terminal command)
-- **Followed By**: `/workflow:execute`, `/workflow:status`
-
-### Basic Usage
+**Basic Usage**:
 ```bash
-/workflow:tools:task-generate --session WFS-auth
+/workflow:tools:task-generate --session WFS-auth [--cli-execute]
 ```
 
-## 11. Related Commands
-- `/workflow:plan` - Orchestrates entire planning
-- `/workflow:plan --cli-execute` - Planning with CLI execution mode
-- `/workflow:tools:context-gather` - Provides context package
-- `/workflow:tools:conflict-resolution` - Provides conflict resolution strategies (optional)
+**Workflow Integration**:
+- Called by: `/workflow:plan` (task generation phase)
+- Followed by: `/workflow:execute`, `/workflow:status`
+
+**Related Commands**:
+- `/workflow:plan` - Orchestrates entire planning workflow
+- `/workflow:tools:context-gather` - Provides context package input
+- `/workflow:tools:conflict-resolution` - Provides conflict resolution (if needed)
 - `/workflow:execute` - Executes generated tasks

.claude/commands/workflow/tools/tdd-coverage-analysis.md

@@ -1,6 +1,6 @@
 ---
 name: tdd-coverage-analysis
-description: Analyze test coverage and TDD cycle execution
+description: Analyze test coverage and TDD cycle execution with Red-Green-Refactor compliance verification
 argument-hint: "--session WFS-session-id"
 allowed-tools: Read(*), Write(*), Bash(*)
 ---

.claude/commands/workflow/tools/test-concept-enhanced.md

@@ -1,6 +1,6 @@
 ---
 name: test-concept-enhanced
-description: Analyze test requirements and generate test generation strategy using Gemini
+description: Analyze test requirements and generate test generation strategy using Gemini with test-context package
 argument-hint: "--session WFS-test-session-id --context path/to/test-context-package.json"
 examples:
   - /workflow:tools:test-concept-enhanced --session WFS-test-auth --context .workflow/WFS-test-auth/.process/test-context-package.json

.claude/commands/workflow/tools/test-context-gather.md

@@ -1,6 +1,6 @@
 ---
 name: test-context-gather
-description: Intelligently collect test coverage context using test-context-search-agent and package into standardized test-context JSON
+description: Collect test coverage context using test-context-search-agent and package into standardized test-context JSON
 argument-hint: "--session WFS-test-session-id"
 examples:
   - /workflow:tools:test-context-gather --session WFS-test-auth

.claude/commands/workflow/tools/test-task-generate.md

@@ -1,6 +1,6 @@
 ---
 name: test-task-generate
-description: Generate test-fix task JSON with iterative test-fix-retest cycle specification
+description: Autonomous test-fix task generation using action-planning-agent with test-fix-retest cycle specification and discovery phase
 argument-hint: "[--use-codex] [--cli-execute] --session WFS-test-session-id"
 examples:
   - /workflow:tools:test-task-generate --session WFS-test-auth
@@ -9,10 +9,23 @@ examples:
   - /workflow:tools:test-task-generate --cli-execute --use-codex --session WFS-test-auth
 ---
 
-# Test Task Generation Command
+# Autonomous Test Task Generation Command
 
 ## Overview
-Generate specialized test-fix task JSON with comprehensive test-fix-retest cycle specification, including Gemini diagnosis (using bug-fix template) and manual fix workflow (Codex automation only when explicitly requested).
+Autonomous test-fix task JSON generation using action-planning-agent with two-phase execution: discovery and document generation. Supports both agent-driven execution (default) and CLI tool execution modes. Generates specialized test-fix tasks with comprehensive test-fix-retest cycle specification.
+
+## Core Philosophy
+- **Agent-Driven**: Delegate execution to action-planning-agent for autonomous operation
+- **Two-Phase Flow**: Discovery (context gathering) → Output (document generation)
+- **Memory-First**: Reuse loaded documents from conversation memory
+- **MCP-Enhanced**: Use MCP tools for advanced code analysis and test research
+- **Pre-Selected Templates**: Command selects correct test template based on `--cli-execute` flag **before** invoking agent
+- **Agent Simplicity**: Agent receives pre-selected template and focuses only on content generation
+- **Path Clarity**: All `focus_paths` prefer absolute paths (e.g., `D:\\project\\src\\module`), or clear relative paths from project root
+- **Test-First**: Generate comprehensive test coverage before execution
+- **Iterative Refinement**: Test-fix-retest cycle until all tests pass
+- **Surgical Fixes**: Minimal code changes, no refactoring during test fixes
+- **Auto-Revert**: Rollback all changes if max iterations reached
 
 ## Execution Modes
 
@@ -24,583 +37,278 @@ Generate specialized test-fix task JSON with comprehensive test-fix-retest cycle
 - **Manual Mode (Default)**: Gemini diagnosis → user applies fixes
 - **Codex Mode (`--use-codex`)**: Gemini diagnosis → Codex applies fixes with resume mechanism
 
-## Core Philosophy
-- **Analysis-Driven Test Generation**: Use TEST_ANALYSIS_RESULTS.md from test-concept-enhanced
-- **Agent-Based Test Creation**: Call @code-developer agent for comprehensive test generation
-- **Coverage-First**: Generate all missing tests before execution
-- **Test Execution**: Execute complete test suite after generation
-- **Gemini Diagnosis**: Use Gemini for root cause analysis and fix suggestions (references bug-fix template)
-- **Manual Fixes First**: Apply fixes manually by default, codex only when explicitly needed
-- **Iterative Refinement**: Repeat test-analyze-fix-retest cycle until all tests pass
-- **Surgical Fixes**: Minimal code changes, no refactoring during test fixes
-- **Auto-Revert**: Rollback all changes if max iterations reached
-
-## Core Responsibilities
-- Parse TEST_ANALYSIS_RESULTS.md from test-concept-enhanced
-- Extract test requirements and generation strategy
-- Parse `--use-codex` flag to determine fix mode (manual vs automated)
-- Generate test generation subtask calling @code-developer
-- Generate test execution and fix cycle task JSON with appropriate fix mode
-- Configure Gemini diagnosis workflow (bug-fix template) and manual/Codex fix application
-- Create test-oriented IMPL_PLAN.md and TODO_LIST.md with test generation phase
-
 ## Execution Lifecycle
 
-### Phase 1: Input Validation & Discovery
+### Phase 1: Discovery & Context Loading
+**⚡ Memory-First Rule**: Skip file loading if documents already in conversation memory
 
-1. **Parameter Parsing**
-   - Parse `--use-codex` flag from command arguments → Controls IMPL-002 fix mode
-   - Parse `--cli-execute` flag from command arguments → Controls IMPL-001 generation mode
-   - Store flag values for task JSON generation
-
-2. **Test Session Validation**
-   - Load `.workflow/{test-session-id}/workflow-session.json`
-   - Verify `workflow_type: "test_session"`
-   - Extract `source_session_id` from metadata
-
-3. **Test Analysis Results Loading**
-   - **REQUIRED**: Load `.workflow/{test-session-id}/.process/TEST_ANALYSIS_RESULTS.md`
-   - Parse test requirements by file
-   - Extract test generation strategy
-   - Identify test files to create with specifications
-
-4. **Test Context Package Loading**
-   - Load `.workflow/{test-session-id}/.process/test-context-package.json`
-   - Extract test framework configuration
-   - Extract coverage gaps and priorities
-   - Load source session implementation summaries
-
-### Phase 2: Task JSON Generation
-
-Generate **TWO task JSON files**:
-1. **IMPL-001.json** - Test Generation (calls @code-developer)
-2. **IMPL-002.json** - Test Execution and Fix Cycle (calls @test-fix-agent)
-
-#### IMPL-001.json - Test Generation Task
-
-```json
+**Agent Context Package**:
+```javascript
 {
-  "id": "IMPL-001",
-  "title": "Generate comprehensive tests for [sourceSessionId]",
-  "status": "pending",
-  "meta": {
-    "type": "test-gen",
-    "agent": "@code-developer",
-    "source_session": "[sourceSessionId]",
-    "test_framework": "jest|pytest|cargo|detected"
+  "session_id": "WFS-test-[session-id]",
+  "execution_mode": "agent-mode" | "cli-execute-mode",  // Determined by flag
+  "task_json_template_path": "~/.claude/workflows/cli-templates/prompts/workflow/task-json-agent-mode.txt"
+                           | "~/.claude/workflows/cli-templates/prompts/workflow/task-json-cli-mode.txt",
+  // Path selected by command based on --cli-execute flag, agent reads it
+  "workflow_type": "test_session",
+  "use_codex": true | false,  // Determined by --use-codex flag
+  "session_metadata": {
+    // If in memory: use cached content
+    // Else: Load from .workflow/{test-session-id}/workflow-session.json
   },
-  "context": {
-    "requirements": [
-      "Generate comprehensive test files based on TEST_ANALYSIS_RESULTS.md",
-      "Follow existing test patterns and conventions from test framework",
-      "Create tests for all missing coverage identified in analysis",
-      "Include happy path, error handling, edge cases, and integration tests",
-      "Use test data and mocks as specified in analysis",
-      "Ensure tests follow project coding standards"
-    ],
-    "focus_paths": [
-      "tests/**/*",
-      "src/**/*.test.*",
-      "{paths_from_analysis}"
-    ],
-    "acceptance": [
-      "All test files from TEST_ANALYSIS_RESULTS.md section 5 are created",
-      "Tests follow existing test patterns and conventions",
-      "Test scenarios cover happy path, errors, edge cases, integration",
-      "All dependencies are properly mocked",
-      "Test files are syntactically valid and can be executed",
-      "Test coverage meets analysis requirements"
-    ],
-    "depends_on": [],
-    "source_context": {
-      "session_id": "[sourceSessionId]",
-      "test_analysis": ".workflow/[testSessionId]/.process/TEST_ANALYSIS_RESULTS.md",
-      "test_context": ".workflow/[testSessionId]/.process/test-context-package.json",
-      "implementation_summaries": [
-        ".workflow/[sourceSessionId]/.summaries/IMPL-001-summary.md"
-      ]
-    }
+  "test_analysis_results_path": ".workflow/{test-session-id}/.process/TEST_ANALYSIS_RESULTS.md",
+  "test_analysis_results": {
+    // If in memory: use cached content
+    // Else: Load from TEST_ANALYSIS_RESULTS.md
   },
-  "flow_control": {
-    "pre_analysis": [
-      {
-        "step": "load_test_analysis",
-        "action": "Load test generation requirements and strategy",
-        "commands": [
-          "Read(.workflow/[testSessionId]/.process/TEST_ANALYSIS_RESULTS.md)",
-          "Read(.workflow/[testSessionId]/.process/test-context-package.json)"
-        ],
-        "output_to": "test_generation_requirements",
-        "on_error": "fail"
-      },
-      {
-        "step": "load_implementation_context",
-        "action": "Load source implementation for test generation context",
-        "commands": [
-          "bash(for f in .workflow/[sourceSessionId]/.summaries/IMPL-*-summary.md; do echo \"=== $(basename $f) ===\"&& cat \"$f\"; done)"
-        ],
-        "output_to": "implementation_context",
-        "on_error": "skip_optional"
-      },
-      {
-        "step": "load_existing_test_patterns",
-        "action": "Study existing tests for pattern reference",
-        "commands": [
-          "bash(find . -name \"*.test.*\" -type f)",
-          "bash(# Read first 2 existing test files as examples)",
-          "bash(test_files=$(find . -name \"*.test.*\" -type f | head -2))",
-          "bash(for f in $test_files; do echo \"=== $f ===\"&& cat \"$f\"; done)"
-        ],
-        "output_to": "existing_test_patterns",
-        "on_error": "skip_optional"
-      }
-    ],
-    // Agent Mode (Default): Agent implements tests
-    "implementation_approach": [
-      {
-        "step": 1,
-        "title": "Generate comprehensive test suite",
-        "description": "Generate comprehensive test suite based on TEST_ANALYSIS_RESULTS.md. Follow test generation strategy and create all test files listed in section 5 (Implementation Targets).",
-        "modification_points": [
-          "Read TEST_ANALYSIS_RESULTS.md sections 3 and 4",
-          "Study existing test patterns",
-          "Create test files with all required scenarios",
-          "Implement happy path, error handling, edge case, and integration tests",
-          "Add required mocks and fixtures"
-        ],
-        "logic_flow": [
-          "Read TEST_ANALYSIS_RESULTS.md section 3 (Test Requirements by File)",
-          "Read TEST_ANALYSIS_RESULTS.md section 4 (Test Generation Strategy)",
-          "Study existing test patterns from test_context.test_framework.conventions",
-          "For each test file in section 5 (Implementation Targets): Create test file with specified scenarios, Implement happy path tests, Implement error handling tests, Implement edge case tests, Implement integration tests (if specified), Add required mocks and fixtures",
-          "Follow test framework conventions and project standards",
-          "Ensure all tests are executable and syntactically valid"
-        ],
-        "depends_on": [],
-        "output": "test_suite"
-      }
-    ],
-
-    // CLI Execute Mode (--cli-execute): Use Codex command (alternative format shown below)
-    "implementation_approach": [{
-      "step": 1,
-      "title": "Generate tests using Codex",
-      "description": "Use Codex CLI to autonomously generate comprehensive test suite based on TEST_ANALYSIS_RESULTS.md",
-      "modification_points": [
-        "Codex loads TEST_ANALYSIS_RESULTS.md and existing test patterns",
-        "Codex generates all test files listed in analysis section 5",
-        "Codex ensures tests follow framework conventions"
-      ],
-      "logic_flow": [
-        "Start new Codex session",
-        "Pass TEST_ANALYSIS_RESULTS.md to Codex",
-        "Codex studies existing test patterns",
-        "Codex generates comprehensive test suite",
-        "Codex validates test syntax and executability"
-      ],
-      "command": "bash(codex -C [focus_paths] --full-auto exec \"PURPOSE: Generate comprehensive test suite TASK: Create test files based on TEST_ANALYSIS_RESULTS.md section 5 MODE: write CONTEXT: @.workflow/WFS-test-[session]/.process/TEST_ANALYSIS_RESULTS.md @.workflow/WFS-test-[session]/.process/test-context-package.json EXPECTED: All test files with happy path, error handling, edge cases, integration tests RULES: Follow test framework conventions, ensure tests are executable\" --skip-git-repo-check -s danger-full-access)",
-      "depends_on": [],
-      "output": "test_generation"
-    }],
-    "target_files": [
-      "{test_file_1 from TEST_ANALYSIS_RESULTS.md section 5}",
-      "{test_file_2 from TEST_ANALYSIS_RESULTS.md section 5}",
-      "{test_file_N from TEST_ANALYSIS_RESULTS.md section 5}"
-    ]
+  "test_context_package_path": ".workflow/{test-session-id}/.process/test-context-package.json",
+  "test_context_package": {
+    // Existing test patterns and coverage analysis
+  },
+  "source_session_id": "[source-session-id]",  // if exists
+  "source_session_summaries": {
+    // Implementation context from source session
+  },
+  "mcp_capabilities": {
+    "code_index": true,
+    "exa_code": true,
+    "exa_web": true
   }
 }
 ```
 
-#### IMPL-002.json - Test Execution & Fix Cycle Task
+**Discovery Actions**:
+1. **Load Test Session Context** (if not in memory)
+   ```javascript
+   if (!memory.has("workflow-session.json")) {
+     Read(.workflow/{test-session-id}/workflow-session.json)
+   }
+   ```
 
-```json
-{
-  "id": "IMPL-002",
-  "title": "Execute and fix tests for [sourceSessionId]",
-  "status": "pending",
-  "meta": {
-    "type": "test-fix",
-    "agent": "@test-fix-agent",
-    "source_session": "[sourceSessionId]",
-    "test_framework": "jest|pytest|cargo|detected",
-    "max_iterations": 5,
-    "use_codex": false  // Set to true if --use-codex flag present
-  },
-  "context": {
-    "requirements": [
-      "Execute complete test suite (generated in IMPL-001)",
-      "Diagnose test failures using Gemini analysis with bug-fix template",
-      "Present fixes to user for manual application (default)",
-      "Use Codex ONLY if user explicitly requests automation",
-      "Iterate until all tests pass or max iterations reached",
-      "Revert changes if unable to fix within iteration limit"
-    ],
-    "focus_paths": [
-      "tests/**/*",
-      "src/**/*.test.*",
-      "{implementation_files_from_source_session}"
-    ],
-    "acceptance": [
-      "All tests pass successfully (100% pass rate)",
-      "No test failures or errors in final run",
-      "Code changes are minimal and surgical",
-      "All fixes are verified through retest",
-      "Iteration logs document fix progression"
-    ],
-    "depends_on": ["IMPL-001"],
-    "source_context": {
-      "session_id": "[sourceSessionId]",
-      "test_generation_summary": ".workflow/[testSessionId]/.summaries/IMPL-001-summary.md",
-      "implementation_summaries": [
-        ".workflow/[sourceSessionId]/.summaries/IMPL-001-summary.md"
-      ]
-    }
-  },
-  "flow_control": {
-    "pre_analysis": [
-      {
-        "step": "load_source_session_summaries",
-        "action": "Load implementation context from source session",
-        "commands": [
-          "bash(find .workflow/[sourceSessionId]/.summaries/ -name 'IMPL-*-summary.md' 2>/dev/null)",
-          "bash(for f in .workflow/[sourceSessionId]/.summaries/IMPL-*-summary.md; do echo \"=== $(basename $f) ===\"&& cat \"$f\"; done)"
-        ],
-        "output_to": "implementation_context",
-        "on_error": "skip_optional"
-      },
-      {
-        "step": "discover_test_framework",
-        "action": "Identify test framework and test command",
-        "commands": [
-          "bash(jq -r '.scripts.test // \"npm test\"' package.json 2>/dev/null || echo 'pytest' || echo 'cargo test')",
-          "bash([ -f 'package.json' ] && echo 'jest/npm' || [ -f 'pytest.ini' ] && echo 'pytest' || [ -f 'Cargo.toml' ] && echo 'cargo' || echo 'unknown')"
-        ],
-        "output_to": "test_command",
-        "on_error": "fail"
-      },
-      {
-        "step": "analyze_test_coverage",
-        "action": "Analyze test coverage and identify missing tests",
-        "commands": [
-          "bash(find . -name \"*.test.*\" -type f)",
-          "bash(rg \"test|describe|it|def test_\" -g \"*.test.*\")",
-          "bash(# Count implementation files vs test files)",
-          "bash(impl_count=$(find [changed_files_dirs] -type f \\( -name '*.ts' -o -name '*.js' -o -name '*.py' \\) ! -name '*.test.*' 2>/dev/null | wc -l))",
-          "bash(test_count=$(find . -name \"*.test.*\" -type f | wc -l))",
-          "bash(echo \"Implementation files: $impl_count, Test files: $test_count\")"
-        ],
-        "output_to": "test_coverage_analysis",
-        "on_error": "skip_optional"
-      },
-      {
-        "step": "identify_files_without_tests",
-        "action": "List implementation files that lack corresponding test files",
-        "commands": [
-          "bash(# For each changed file from source session, check if test exists)",
-          "bash(for file in [changed_files]; do test_file=$(echo $file | sed 's/\\(.*\\)\\.\\(ts\\|js\\|py\\)$/\\1.test.\\2/'); [ ! -f \"$test_file\" ] && echo \"$file\"; done)"
-        ],
-        "output_to": "files_without_tests",
-        "on_error": "skip_optional"
-      },
-      {
-        "step": "prepare_test_environment",
-        "action": "Ensure test environment is ready",
-        "commands": [
-          "bash([ -f 'package.json' ] && npm install 2>/dev/null || true)",
-          "bash([ -f 'requirements.txt' ] && pip install -q -r requirements.txt 2>/dev/null || true)"
-        ],
-        "output_to": "environment_status",
-        "on_error": "skip_optional"
-      }
-    ],
-    "implementation_approach": [
-      {
-        "step": 1,
-        "title": "Execute iterative test-fix-retest cycle",
-        "description": "Execute iterative test-fix-retest cycle using Gemini diagnosis (bug-fix template) and manual fixes (Codex only if meta.use_codex=true). Max 5 iterations with automatic revert on failure.",
-        "test_fix_cycle": {
-          "max_iterations": 5,
-          "cycle_pattern": "test → gemini_diagnose → manual_fix (or codex if needed) → retest",
-          "tools": {
-            "test_execution": "bash(test_command)",
-            "diagnosis": "gemini (MODE: analysis, uses bug-fix template)",
-            "fix_application": "manual (default) or codex exec resume --last (if explicitly needed)",
-            "verification": "bash(test_command) + regression_check"
-          },
-          "exit_conditions": {
-            "success": "all_tests_pass",
-            "failure": "max_iterations_reached",
-            "error": "test_command_not_found"
-          }
-        },
-        "modification_points": [
-        "PHASE 1: Initial Test Execution",
-        "  1.1. Discover test command from framework detection",
-        "  1.2. Execute initial test run: bash([test_command])",
-        "  1.3. Parse test output and count failures",
-        "  1.4. If all pass → Skip to PHASE 3 (success)",
-        "  1.5. If failures → Store failure output, proceed to PHASE 2",
-        "",
-        "PHASE 2: Iterative Test-Fix-Retest Cycle (max 5 iterations)",
-        "  Note: This phase handles test failures, NOT test generation failures",
-        "  Initialize: max_iterations=5, current_iteration=0",
-        "  ",
-        "  WHILE (tests failing AND current_iteration < max_iterations):",
-        "    current_iteration++",
-        "    ",
-        "    STEP 2.1: Gemini Diagnosis (using bug-fix template)",
-        "    - Prepare diagnosis context:",
-        "      * Test failure output from previous run",
-        "      * Source files from focus_paths",
-        "      * Implementation summaries from source session",
-        "    - Execute Gemini analysis with bug-fix template:",
-        "      bash(cd .workflow/WFS-test-[session]/.process && gemini \"",
-        "      PURPOSE: Diagnose test failure iteration [N] and propose minimal fix",
-        "      TASK: Systematic bug analysis and fix recommendations for test failure",
-        "      MODE: analysis",
-        "      CONTEXT: @CLAUDE.md,**/*CLAUDE.md",
-        "               Test output: [test_failures]",
-        "               Source files: [focus_paths]",
-        "               Implementation: [implementation_context]",
-        "      EXPECTED: Root cause analysis, code path tracing, targeted fixes",
-        "      RULES: $(cat ~/.claude/workflows/cli-templates/prompts/development/bug-diagnosis.txt) | Bug: [test_failure_description]",
-        "             Minimal surgical fixes only - no refactoring",
-        "      \" > fix-iteration-[N]-diagnosis.md)",
-        "    - Parse diagnosis → extract fix_suggestion and target_files",
-        "    - Present fix to user for manual application (default)",
-        "    ",
-        "    STEP 2.2: Apply Fix (Based on meta.use_codex Flag)",
-        "    ",
-        "    IF meta.use_codex = false (DEFAULT):",
-        "    - Present Gemini diagnosis to user for manual fix",
-        "    - User applies fix based on diagnosis recommendations",
-        "    - Stage changes: bash(git add -A)",
-        "    - Store fix log: .process/fix-iteration-[N]-changes.log",
-        "    ",
-        "    IF meta.use_codex = true (--use-codex flag present):",
-        "    - Stage current changes (if valid git repo): bash(git add -A)",
-        "    - First iteration: Start new Codex session",
-        "      codex -C [project_root] --full-auto exec \"",
-        "      PURPOSE: Fix test failure iteration 1",
-        "      TASK: [fix_suggestion from Gemini]",
-        "      MODE: write",
-        "      CONTEXT: Diagnosis: .workflow/.process/fix-iteration-1-diagnosis.md",
-        "               Target files: [target_files]",
-        "               Implementation context: [implementation_context]",
-        "      EXPECTED: Minimal code changes to resolve test failure",
-        "      RULES: Apply ONLY suggested changes, no refactoring",
-        "             Preserve existing code style",
-        "      \" --skip-git-repo-check -s danger-full-access",
-        "    - Subsequent iterations: Resume session for context continuity",
-        "      codex exec \"",
-        "      CONTINUE TO NEXT FIX:",
-        "      Iteration [N] of 5: Fix test failure",
-        "      ",
-        "      PURPOSE: Fix remaining test failures",
-        "      TASK: [fix_suggestion from Gemini iteration N]",
-        "      CONTEXT: Previous fixes applied, diagnosis: .process/fix-iteration-[N]-diagnosis.md",
-        "      EXPECTED: Surgical fix for current failure",
-        "      RULES: Build on previous fixes, maintain consistency",
-        "      \" resume --last --skip-git-repo-check -s danger-full-access",
-        "    - Store fix log: .process/fix-iteration-[N]-changes.log",
-        "    ",
-        "    STEP 2.3: Retest and Verification",
-        "    - Re-execute test suite: bash([test_command])",
-        "    - Capture output: .process/fix-iteration-[N]-retest.log",
-        "    - Count failures: bash(grep -c 'FAIL\\|ERROR' .process/fix-iteration-[N]-retest.log)",
-        "    - Check for regression:",
-        "      IF new_failures > previous_failures:",
-        "        WARN: Regression detected",
-        "        Include in next Gemini diagnosis context",
-        "    - Analyze results:",
-        "      IF all_tests_pass:",
-        "        BREAK loop → Proceed to PHASE 3",
-        "      ELSE:",
-        "        Update test_failures context",
-        "        CONTINUE loop",
-        "  ",
-        "  IF max_iterations reached AND tests still failing:",
-        "    EXECUTE: git reset --hard HEAD (revert all changes)",
-        "    MARK: Task status = blocked",
-        "    GENERATE: Detailed failure report with iteration logs",
-        "    EXIT: Require manual intervention",
-        "",
-        "PHASE 3: Final Validation and Certification",
-        "  3.1. Execute final confirmation test run",
-        "  3.2. Generate success summary:",
-        "       - Iterations required: [current_iteration]",
-        "       - Fixes applied: [summary from iteration logs]",
-        "       - Test results: All passing ✅",
-        "  3.3. Mark task status: completed",
-        "  3.4. Update TODO_LIST.md: Mark as ✅",
-        "  3.5. Certify code: APPROVED for deployment"
-      ],
-      "logic_flow": [
-        "Load source session implementation context",
-        "Discover test framework and command",
-        "PHASE 0: Test Coverage Check",
-        "  Analyze existing test files",
-        "  Identify files without tests",
-        "  IF tests missing:",
-        "    Report to user (no automatic generation)",
-        "    Wait for user to generate tests or request automation",
-        "  ELSE:",
-        "    Skip to Phase 1",
-        "PHASE 1: Initial Test Execution",
-        "  Execute test suite",
-        "  IF all pass → Success (Phase 3)",
-        "  ELSE → Store failures, proceed to Phase 2",
-        "PHASE 2: Iterative Fix Cycle (max 5 iterations)",
-        "  LOOP (max 5 times):",
-        "    1. Gemini diagnoses failure with bug-fix template → fix suggestion",
-        "    2. Check meta.use_codex flag:",
-        "       - IF false (default): Present fix to user for manual application",
-        "       - IF true (--use-codex): Codex applies fix with resume for continuity",
-        "    3. Retest and check results",
-        "    4. IF pass → Exit loop to Phase 3",
-        "    5. ELSE → Continue with updated context",
-        "  IF max iterations → Revert + report failure",
-        "PHASE 3: Final Validation",
-        "  Confirm all tests pass",
-        "  Generate summary (include test generation info)",
-        "  Certify code APPROVED"
-      ],
-        "error_handling": {
-          "max_iterations_reached": {
-            "action": "revert_all_changes",
-            "commands": [
-              "bash(git reset --hard HEAD)",
-              "bash(jq '.status = \"blocked\"' .workflow/[session]/.task/IMPL-001.json > temp.json && mv temp.json .workflow/[session]/.task/IMPL-001.json)"
-            ],
-            "report": "Generate failure report with iteration logs in .summaries/IMPL-001-failure-report.md"
-          },
-          "test_command_fails": {
-            "action": "treat_as_test_failure",
-            "context": "Use stderr as failure context for Gemini diagnosis"
-          },
-          "codex_apply_fails": {
-            "action": "retry_once_then_skip",
-            "fallback": "Mark iteration as skipped, continue to next"
-          },
-          "gemini_diagnosis_fails": {
-            "action": "retry_with_simplified_context",
-            "fallback": "Use previous diagnosis, continue"
-          },
-          "regression_detected": {
-            "action": "log_warning_continue",
-            "context": "Include regression info in next Gemini diagnosis"
-          }
-        },
-        "depends_on": [],
-        "output": "test_fix_results"
-      }
-    ],
-    "target_files": [
-      "Auto-discovered from test failures",
-      "Extracted from Gemini diagnosis each iteration",
-      "Format: file:function:lines or file (for new files)"
-    ],
-    "codex_session": {
-      "strategy": "resume_for_continuity",
-      "first_iteration": "codex exec \"fix iteration 1\" --full-auto",
-      "subsequent_iterations": "codex exec \"fix iteration N\" resume --last",
-      "benefits": [
-        "Maintains conversation context across fixes",
-        "Remembers previous decisions and patterns",
-        "Ensures consistency in fix approach",
-        "Reduces redundant context injection"
-      ]
-    }
-  }
+2. **Load TEST_ANALYSIS_RESULTS.md** (if not in memory, REQUIRED)
+   ```javascript
+   if (!memory.has("TEST_ANALYSIS_RESULTS.md")) {
+     Read(.workflow/{test-session-id}/.process/TEST_ANALYSIS_RESULTS.md)
+   }
+   ```
+
+3. **Load Test Context Package** (if not in memory)
+   ```javascript
+   if (!memory.has("test-context-package.json")) {
+     Read(.workflow/{test-session-id}/.process/test-context-package.json)
+   }
+   ```
+
+4. **Load Source Session Summaries** (if source_session_id exists)
+   ```javascript
+   if (sessionMetadata.source_session_id) {
+     const summaryFiles = Bash("find .workflow/{source-session-id}/.summaries/ -name 'IMPL-*-summary.md'")
+     summaryFiles.forEach(file => Read(file))
+   }
+   ```
+
+5. **Code Analysis with Native Tools** (optional - enhance understanding)
+   ```bash
+   # Find test files and patterns
+   find . -name "*test*" -type f
+   rg "describe|it\(|test\(" -g "*.ts"
+   ```
+
+6. **MCP External Research** (optional - gather test best practices)
+   ```javascript
+   // Get external test examples and patterns
+   mcp__exa__get_code_context_exa(
+     query="TypeScript test generation best practices jest",
+     tokensNum="dynamic"
+   )
+   ```
+
+### Phase 2: Agent Execution (Document Generation)
+
+**Pre-Agent Template Selection** (Command decides path before invoking agent):
+```javascript
+// Command checks flag and selects template PATH (not content)
+const templatePath = hasCliExecuteFlag
+  ? "~/.claude/workflows/cli-templates/prompts/workflow/task-json-cli-mode.txt"
+  : "~/.claude/workflows/cli-templates/prompts/workflow/task-json-agent-mode.txt";
+```
+
+**Agent Invocation**:
+```javascript
+Task(
+  subagent_type="action-planning-agent",
+  description="Generate test-fix task JSON and implementation plan",
+  prompt=`
+## Execution Context
+
+**Session ID**: WFS-test-{session-id}
+**Workflow Type**: Test Session
+**Execution Mode**: {agent-mode | cli-execute-mode}
+**Task JSON Template Path**: {template_path}
+**Use Codex**: {true | false}
+
+## Phase 1: Discovery Results (Provided Context)
+
+### Test Session Metadata
+{session_metadata_content}
+- source_session_id: {source_session_id} (if exists)
+- workflow_type: "test_session"
+
+### TEST_ANALYSIS_RESULTS.md (REQUIRED)
+{test_analysis_results_content}
+- Coverage Assessment
+- Test Framework & Conventions
+- Test Requirements by File
+- Test Generation Strategy
+- Implementation Targets
+- Success Criteria
+
+### Test Context Package
+{test_context_package_summary}
+- Existing test patterns, framework config, coverage analysis
+
+### Source Session Implementation Context (Optional)
+{source_session_summaries}
+- Implementation context from completed session
+
+### MCP Analysis Results (Optional)
+**Code Structure**: {mcp_code_index_results}
+**External Research**: {mcp_exa_research_results}
+
+## Phase 2: Test Task Document Generation
+
+**Agent Configuration Reference**: All test task generation rules, test-fix cycle structure, quality standards, and execution details are defined in action-planning-agent.
+
+Refer to: @.claude/agents/action-planning-agent.md for:
+- Test Task Decomposition Standards
+- Test-Fix-Retest Cycle Requirements
+- 5-Field Task JSON Schema
+- IMPL_PLAN.md Structure (Test variant)
+- TODO_LIST.md Format
+- Test Execution Flow & Quality Validation
+
+### Test-Specific Requirements Summary
+
+#### Task Structure Philosophy
+- **Minimum 2 tasks**: IMPL-001 (test generation) + IMPL-002 (test execution & fix)
+- **Expandable**: Add IMPL-003+ for complex projects (per-module, integration, etc.)
+- IMPL-001: Uses @code-developer or CLI execution
+- IMPL-002: Uses @test-fix-agent with iterative fix cycle
+
+#### Test-Fix Cycle Configuration
+- **Max Iterations**: 5 (for IMPL-002)
+- **Diagnosis Tool**: Gemini with bug-fix template
+- **Fix Application**: Manual (default) or Codex (if --use-codex flag)
+- **Cycle Pattern**: test → gemini_diagnose → manual_fix (or codex) → retest
+- **Exit Conditions**: All tests pass OR max iterations reached (auto-revert)
+
+#### Required Outputs Summary
+
+##### 1. Test Task JSON Files (.task/IMPL-*.json)
+- **Location**: `.workflow/{test-session-id}/.task/`
+- **Template**: Read from `{template_path}` (pre-selected by command based on `--cli-execute` flag)
+- **Schema**: 5-field structure with test-specific metadata
+  - IMPL-001: `meta.type: "test-gen"`, `meta.agent: "@code-developer"`
+  - IMPL-002: `meta.type: "test-fix"`, `meta.agent: "@test-fix-agent"`, `meta.use_codex: {use_codex}`
+  - `flow_control`: Test generation approach (IMPL-001) or test-fix cycle (IMPL-002)
+- **Details**: See action-planning-agent.md § Test Task JSON Generation
+
+##### 2. IMPL_PLAN.md (Test Variant)
+- **Location**: `.workflow/{test-session-id}/IMPL_PLAN.md`
+- **Template**: `~/.claude/workflows/cli-templates/prompts/workflow/impl-plan-template.txt`
+- **Test-Specific Frontmatter**: workflow_type="test_session", test_framework, source_session_id
+- **Test-Fix-Retest Cycle Section**: Iterative fix cycle with Gemini diagnosis
+- **Details**: See action-planning-agent.md § Test Implementation Plan Creation
+
+##### 3. TODO_LIST.md
+- **Location**: `.workflow/{test-session-id}/TODO_LIST.md`
+- **Format**: Task list with test generation and execution phases
+- **Status**: [ ] (pending), [x] (completed)
+- **Details**: See action-planning-agent.md § TODO List Generation
+
+### Agent Execution Summary
+
+**Key Steps** (Detailed instructions in action-planning-agent.md):
+1. Load task JSON template from provided path
+2. Parse TEST_ANALYSIS_RESULTS.md for test requirements
+3. Generate IMPL-001 (test generation) task JSON
+4. Generate IMPL-002 (test execution & fix) task JSON with use_codex flag
+5. Generate additional IMPL-*.json if project complexity requires
+6. Create IMPL_PLAN.md using test template variant
+7. Generate TODO_LIST.md with test task indicators
+8. Update session state with test metadata
+
+**Quality Gates** (Full checklist in action-planning-agent.md):
+- ✓ Minimum 2 tasks created (IMPL-001 + IMPL-002)
+- ✓ IMPL-001 has test generation approach from TEST_ANALYSIS_RESULTS.md
+- ✓ IMPL-002 has test-fix cycle with correct use_codex flag
+- ✓ Test framework configuration integrated
+- ✓ Source session context referenced (if exists)
+- ✓ MCP tool integration added
+- ✓ Documents follow test template structure
+
+## Output
+
+Generate all three documents and report completion status:
+- Test task JSON files created: N files (minimum 2)
+- Test requirements integrated: TEST_ANALYSIS_RESULTS.md
+- Test context integrated: existing patterns and coverage
+- Source session context: {source_session_id} summaries (if exists)
+- MCP enhancements: code-index, exa-research
+- Session ready for test execution: /workflow:execute or /workflow:test-cycle-execute
+`
+)
+```
+
+### Agent Context Passing
+
+**Memory-Aware Context Assembly**:
+```javascript
+// Assemble context package for agent
+const agentContext = {
+  session_id: "WFS-test-[id]",
+  workflow_type: "test_session",
+  use_codex: hasUseCodexFlag,
+
+  // Use memory if available, else load
+  session_metadata: memory.has("workflow-session.json")
+    ? memory.get("workflow-session.json")
+    : Read(.workflow/WFS-test-[id]/workflow-session.json),
+
+  test_analysis_results_path: ".workflow/WFS-test-[id]/.process/TEST_ANALYSIS_RESULTS.md",
+
+  test_analysis_results: memory.has("TEST_ANALYSIS_RESULTS.md")
+    ? memory.get("TEST_ANALYSIS_RESULTS.md")
+    : Read(".workflow/WFS-test-[id]/.process/TEST_ANALYSIS_RESULTS.md"),
+
+  test_context_package_path: ".workflow/WFS-test-[id]/.process/test-context-package.json",
+
+  test_context_package: memory.has("test-context-package.json")
+    ? memory.get("test-context-package.json")
+    : Read(".workflow/WFS-test-[id]/.process/test-context-package.json"),
+
+  // Load source session summaries if exists
+  source_session_id: session_metadata.source_session_id || null,
+
+  source_session_summaries: session_metadata.source_session_id
+    ? loadSourceSummaries(session_metadata.source_session_id)
+    : null,
+
+  // Optional MCP enhancements
+  mcp_analysis: executeMcpDiscovery()
 }
 ```
 
-### Phase 3: IMPL_PLAN.md Generation
+## Test Task Structure Reference
 
-#### Document Structure
-```markdown
----
-identifier: WFS-test-[session-id]
-source_session: WFS-[source-session-id]
-workflow_type: test_session
-test_framework: jest|pytest|cargo|detected
----
+This section provides quick reference for test task JSON structure. For complete implementation details, see the agent invocation prompt in Phase 2 above.
 
-# Test Validation Plan: [Source Session Topic]
-
-## Summary
-Execute comprehensive test suite for implementation from session WFS-[source-session-id].
-Diagnose and fix all test failures using iterative Gemini analysis and Codex execution.
-
-## Source Session Context
-- **Implementation Session**: WFS-[source-session-id]
-- **Completed Tasks**: IMPL-001, IMPL-002, ...
-- **Changed Files**: [list from git log]
-- **Implementation Summaries**: [references to source session summaries]
-
-## Test Framework
-- **Detected Framework**: jest|pytest|cargo|other
-- **Test Command**: npm test|pytest|cargo test
-- **Test Files**: [discovered test files]
-- **Coverage**: [estimated test coverage]
-
-## Test-Fix-Retest Cycle
-- **Max Iterations**: 5
-- **Diagnosis Tool**: Gemini (analysis mode with bug-fix template from bug-index.md)
-- **Fix Tool**: Manual (default, meta.use_codex=false) or Codex (if --use-codex flag, meta.use_codex=true)
-- **Verification**: Bash test execution + regression check
-
-### Cycle Workflow
-1. **Initial Test**: Execute full suite, capture failures
-2. **Iterative Fix Loop** (max 5 times):
-   - Gemini diagnoses failure using bug-fix template → surgical fix suggestion
-   - Check meta.use_codex flag:
-     - If false (default): Present fix to user for manual application
-     - If true (--use-codex): Codex applies fix with resume for context continuity
-   - Retest and verify (check for regressions)
-   - Continue until all pass or max iterations reached
-3. **Final Validation**: Confirm all tests pass, certify code
-
-### Error Recovery
-- **Max iterations reached**: Revert all changes, report failure
-- **Test command fails**: Treat as test failure, diagnose with Gemini
-- **Codex fails**: Retry once, skip iteration if still failing
-- **Regression detected**: Log warning, include in next diagnosis
-
-## Task Breakdown
-- **IMPL-001**: Execute and validate tests with iterative fix cycle
-
-## Implementation Strategy
-- **Phase 1**: Initial test execution and failure capture
-- **Phase 2**: Iterative Gemini diagnosis + Codex fix + retest
-- **Phase 3**: Final validation and code certification
-
-## Success Criteria
-- All tests pass (100% pass rate)
-- No test failures or errors in final run
-- Minimal, surgical code changes
-- Iteration logs document fix progression
-- Code certified APPROVED for deployment
-```
-
-### Phase 4: TODO_LIST.md Generation
-
-```markdown
-# Tasks: Test Validation for [Source Session]
-
-## Task Progress
-- [ ] **IMPL-001**: Execute and validate tests with iterative fix cycle → [📋](./.task/IMPL-001.json)
-
-## Execution Details
-- **Source Session**: WFS-[source-session-id]
-- **Test Framework**: jest|pytest|cargo
-- **Max Iterations**: 5
-- **Tools**: Gemini diagnosis + Codex resume fixes
-
-## Status Legend
-- `- [ ]` = Pending
-- `- [x]` = Completed
-```
+**Quick Reference**:
+- Minimum 2 tasks: IMPL-001 (test-gen) + IMPL-002 (test-fix)
+- Expandable for complex projects (IMPL-003+)
+- IMPL-001: `meta.agent: "@code-developer"`, test generation approach
+- IMPL-002: `meta.agent: "@test-fix-agent"`, `meta.use_codex: {flag}`, test-fix cycle
+- See Phase 2 agent prompt for full schema and requirements
 
 ## Output Files Structure
 ```
@@ -648,29 +356,52 @@ Diagnose and fix all test failures using iterative Gemini analysis and Codex exe
 ## Integration & Usage
 
 ### Command Chain
-- **Called By**: `/workflow:test-gen` (Phase 4)
-- **Calls**: None (terminal command)
-- **Followed By**: `/workflow:execute` (user-triggered)
+- **Called By**: `/workflow:test-gen` (Phase 4), `/workflow:test-fix-gen` (Phase 4)
+- **Invokes**: `action-planning-agent` for autonomous task generation
+- **Followed By**: `/workflow:execute` or `/workflow:test-cycle-execute` (user-triggered)
 
 ### Basic Usage
 ```bash
-# Manual fix mode (default)
+# Agent mode (default, autonomous execution)
 /workflow:tools:test-task-generate --session WFS-test-auth
 
-# Automated Codex fix mode
+# With automated Codex fixes for IMPL-002
 /workflow:tools:test-task-generate --use-codex --session WFS-test-auth
+
+# CLI execution mode for IMPL-001 test generation
+/workflow:tools:test-task-generate --cli-execute --session WFS-test-auth
+
+# Both flags combined
+/workflow:tools:test-task-generate --cli-execute --use-codex --session WFS-test-auth
 ```
 
+### Execution Modes
+- **Agent mode** (default): Uses `action-planning-agent` with agent-mode task template
+- **CLI mode** (`--cli-execute`): Uses Gemini/Qwen/Codex with cli-mode task template for IMPL-001
+- **Codex fixes** (`--use-codex`): Enables automated fixes in IMPL-002 task
+
 ### Flag Behavior
-- **No flag**: `meta.use_codex=false`, manual fixes presented to user
-- **--use-codex**: `meta.use_codex=true`, Codex automatically applies fixes with resume mechanism
+- **No flags**: `meta.use_codex=false` (manual fixes), agent-mode generation
+- **--use-codex**: `meta.use_codex=true` (Codex automated fixes with resume mechanism in IMPL-002)
+- **--cli-execute**: Uses CLI tool execution mode for IMPL-001 test generation
+- **Both flags**: CLI generation + automated Codex fixes
+
+### Output
+- Test task JSON files in `.task/` directory (minimum 2: IMPL-001.json + IMPL-002.json)
+- IMPL_PLAN.md with test generation and fix cycle strategy
+- TODO_LIST.md with test task indicators
+- Session state updated with test metadata
+- MCP enhancements integrated (if available)
 
 ## Related Commands
-- `/workflow:test-gen` - Creates test session and calls this tool
-- `/workflow:tools:context-gather` - Provides cross-session context
-- `/workflow:tools:concept-enhanced` - Provides test strategy analysis
-- `/workflow:execute` - Executes the generated test-fix task
-- `@test-fix-agent` - Agent that executes the iterative test-fix cycle
+- `/workflow:test-gen` - Creates test session and calls this tool (Phase 4)
+- `/workflow:test-fix-gen` - Creates test-fix session and calls this tool (Phase 4)
+- `/workflow:tools:test-context-gather` - Gathers test coverage context
+- `/workflow:tools:test-concept-enhanced` - Generates test strategy analysis (TEST_ANALYSIS_RESULTS.md)
+- `/workflow:execute` - Executes the generated test-fix tasks
+- `/workflow:test-cycle-execute` - Executes test-fix cycle with iteration management
+- `@code-developer` - Agent that executes IMPL-001 (test generation)
+- `@test-fix-agent` - Agent that executes IMPL-002 (test execution & fix)
 
 ## Agent Execution Notes
 
@@ -690,6 +421,6 @@ The `@test-fix-agent` will execute the task by following the `flow_control.imple
 6. **Phase 3**: Generate summary and certify code
 7. **Error Recovery**: Revert changes if max iterations reached
 
-**Bug Diagnosis Template**: Uses `~/.claude/workflows/cli-templates/prompts/development/bug-diagnosis.txt` template for systematic root cause analysis, code path tracing, and targeted fix recommendations.
+**Bug Diagnosis Template**: Uses `~/.claude/workflows/cli-templates/prompts/analysis/01-diagnose-bug-root-cause.txt` template for systematic root cause analysis, code path tracing, and targeted fix recommendations.
 
 **Codex Usage**: The agent uses `codex exec "..." resume --last` pattern ONLY when meta.use_codex=true (--use-codex flag present) to maintain conversation context across multiple fix iterations, ensuring consistency and learning from previous attempts.

.claude/commands/workflow/ui-design/animation-extract.md

@@ -1,6 +1,6 @@
 ---
 name: animation-extract
-description: Extract animation and transition patterns from URLs, CSS, or interactive questioning
+description: Extract animation and transition patterns from URLs, CSS, or interactive questioning for design system documentation
 argument-hint: "[--base-path <path>] [--session <id>] [--urls "<list>"] [--mode <auto|interactive>] [--focus "<types>"]"
 allowed-tools: TodoWrite(*), Read(*), Write(*), Glob(*), Bash(*), Task(ui-design-agent), mcp__chrome-devtools__navigate_page(*), mcp__chrome-devtools__evaluate_script(*)
 ---

.claude/commands/workflow/ui-design/batch-generate.md

@@ -1,6 +1,6 @@
 ---
 name: batch-generate
-description: Prompt-driven batch UI generation using target-style-centric parallel execution
+description: Prompt-driven batch UI generation using target-style-centric parallel execution with design token application
 argument-hint: [--targets "<list>"] [--target-type "page|component"] [--device-type "desktop|mobile|tablet|responsive"] [--base-path <path>] [--session <id>] [--style-variants <count>] [--layout-variants <count>]
 allowed-tools: TodoWrite(*), Read(*), Write(*), Task(ui-design-agent), Bash(*), mcp__exa__web_search_exa(*)
 ---

.claude/commands/workflow/ui-design/capture.md

@@ -1,6 +1,6 @@
 ---
 name: capture
-description: Batch screenshot capture for UI design workflows using MCP or local fallback
+description: Batch screenshot capture for UI design workflows using MCP puppeteer or local fallback with URL mapping
 argument-hint: --url-map "target:url,..." [--base-path path] [--session id]
 allowed-tools: TodoWrite(*), Read(*), Write(*), Bash(*), Glob(*), ListMcpResourcesTool(*), mcp__chrome-devtools__*, mcp__playwright__*
 ---

.claude/commands/workflow/ui-design/explore-auto.md

@@ -1,6 +1,6 @@
 ---
 name: explore-auto
-description: Exploratory UI design workflow with style-centric batch generation
+description: Exploratory UI design workflow with style-centric batch generation, creates design variants from prompts/images with parallel execution
 argument-hint: "[--prompt "<desc>"] [--images "<glob>"] [--targets "<list>"] [--target-type "page|component"] [--session <id>] [--style-variants <count>] [--layout-variants <count>] [--batch-plan]""
 allowed-tools: SlashCommand(*), TodoWrite(*), Read(*), Bash(*), Glob(*), Write(*), Task(conceptual-planning-agent)
 ---
@@ -107,7 +107,43 @@ allowed-tools: SlashCommand(*), TodoWrite(*), Read(*), Bash(*), Glob(*), Write(*
 
 ## 6-Phase Execution
 
-### Phase 0a: Intelligent Prompt Parsing
+### Phase 0a: Intelligent Path Detection & Source Selection
+```bash
+# Step 1: Detect if prompt/images contain existing file paths
+code_files_detected = false
+code_base_path = null
+has_visual_input = false
+
+IF --prompt:
+    # Extract potential file paths from prompt
+    potential_paths = extract_paths_from_text(--prompt)
+    FOR path IN potential_paths:
+        IF file_or_directory_exists(path):
+            code_files_detected = true
+            code_base_path = path
+            BREAK
+
+IF --images:
+    # Check if images parameter points to existing files
+    IF glob_matches_files(--images):
+        has_visual_input = true
+
+# Step 2: Determine design source strategy
+design_source = "unknown"
+IF code_files_detected AND has_visual_input:
+    design_source = "hybrid"  # Both code and visual
+ELSE IF code_files_detected:
+    design_source = "code_only"  # Only code files
+ELSE IF has_visual_input OR --prompt:
+    design_source = "visual_only"  # Only visual/prompt
+ELSE:
+    ERROR: "No design source provided (code files, images, or prompt required)"
+    EXIT 1
+
+STORE: design_source, code_base_path, has_visual_input
+```
+
+### Phase 0a-2: Intelligent Prompt Parsing
 ```bash
 # Parse variant counts from prompt or use explicit/default values
 IF --prompt AND (NOT --style-variants OR NOT --layout-variants):
@@ -267,29 +303,101 @@ detect_target_type(target_list):
     RETURN "component" IF component_matches > page_matches ELSE "page"
 ```
 
-### Phase 1: Style Extraction
+### Phase 0d: Code Import & Completeness Assessment (Conditional)
 ```bash
-command = "/workflow:ui-design:style-extract --base-path \"{base_path}\" " +
-          (--images ? "--images \"{images}\" " : "") +
-          (--prompt ? "--prompt \"{prompt}\" " : "") +
-          "--mode explore --variants {style_variants}"
-SlashCommand(command)
+IF design_source IN ["code_only", "hybrid"]:
+    REPORT: "🔍 Phase 0d: Code Import ({design_source})"
+    command = "/workflow:ui-design:import-from-code --base-path \"{base_path}\" --base-path \"{code_base_path}\""
+    SlashCommand(command)
 
-# Output: {style_variants} style cards with design_attributes
-# SlashCommand blocks until phase complete
-# Upon completion, IMMEDIATELY execute Phase 2.3 (auto-continue)
+    # Check file existence and assess completeness
+    style_exists = exists("{base_path}/style-extraction/style-1/design-tokens.json")
+    animation_exists = exists("{base_path}/animation-extraction/animation-tokens.json")
+    layout_exists = exists("{base_path}/layout-extraction/layout-templates.json")
+
+    style_complete = false
+    animation_complete = false
+    layout_complete = false
+    missing_categories = []
+
+    # Style completeness check
+    IF style_exists:
+        tokens = Read("{base_path}/style-extraction/style-1/design-tokens.json")
+        style_complete = (
+            tokens.colors?.brand && tokens.colors?.surface &&
+            tokens.typography?.font_family && tokens.spacing &&
+            Object.keys(tokens.colors.brand || {}).length >= 3 &&
+            Object.keys(tokens.spacing || {}).length >= 8
+        )
+        IF NOT style_complete AND tokens._metadata?.completeness?.missing_categories:
+            missing_categories.extend(tokens._metadata.completeness.missing_categories)
+    ELSE:
+        missing_categories.push("style tokens")
+
+    # Animation completeness check
+    IF animation_exists:
+        anim = Read("{base_path}/animation-extraction/animation-tokens.json")
+        animation_complete = (
+            anim.duration && anim.easing &&
+            Object.keys(anim.duration || {}).length >= 3 &&
+            Object.keys(anim.easing || {}).length >= 3
+        )
+        IF NOT animation_complete AND anim._metadata?.completeness?.missing_items:
+            missing_categories.extend(anim._metadata.completeness.missing_items)
+    ELSE:
+        missing_categories.push("animation tokens")
+
+    # Layout completeness check
+    IF layout_exists:
+        layouts = Read("{base_path}/layout-extraction/layout-templates.json")
+        layout_complete = (
+            layouts.layout_templates?.length >= 3 &&
+            layouts.extraction_metadata?.layout_system?.type &&
+            layouts.extraction_metadata?.responsive?.breakpoints
+        )
+        IF NOT layout_complete AND layouts.extraction_metadata?.completeness?.missing_items:
+            missing_categories.extend(layouts.extraction_metadata.completeness.missing_items)
+    ELSE:
+        missing_categories.push("layout templates")
+
+    needs_visual_supplement = false
+
+    IF design_source == "code_only" AND NOT (style_complete AND layout_complete):
+        REPORT: "⚠️  Missing: {', '.join(missing_categories)}"
+        REPORT: "Options: 'continue' | 'supplement: <images>' | 'cancel'"
+        user_response = WAIT_FOR_USER_INPUT()
+        MATCH user_response:
+            "continue" → needs_visual_supplement = false
+            "supplement: ..." → needs_visual_supplement = true; --images = extract_path(user_response)
+            "cancel" → EXIT 0
+            default → needs_visual_supplement = false
+    ELSE IF design_source == "hybrid":
+        needs_visual_supplement = true
+
+    STORE: needs_visual_supplement, style_complete, animation_complete, layout_complete
 ```
 
-### Phase 2.3: Animation Extraction (Optional - Interactive Mode)
+### Phase 1: Style Extraction
 ```bash
-# Animation extraction for motion design patterns
-REPORT: "🚀 Phase 2.3: Animation Extraction (interactive mode)"
-REPORT: "   → Mode: Interactive specification"
-REPORT: "   → Purpose: Define motion design patterns"
+IF design_source == "visual_only" OR needs_visual_supplement:
+    REPORT: "🎨 Phase 1: Style Extraction (variants: {style_variants})"
+    command = "/workflow:ui-design:style-extract --base-path \"{base_path}\" " +
+              (--images ? "--images \"{images}\" " : "") +
+              (--prompt ? "--prompt \"{prompt}\" " : "") +
+              "--mode explore --variants {style_variants}"
+    SlashCommand(command)
+ELSE:
+    REPORT: "✅ Phase 1: Style (Using Code Import)"
+```
 
-command = "/workflow:ui-design:animation-extract --base-path \"{base_path}\" --mode interactive"
-
-SlashCommand(command)
+### Phase 2.3: Animation Extraction
+```bash
+IF design_source == "visual_only" OR NOT animation_complete:
+    REPORT: "🚀 Phase 2.3: Animation Extraction"
+    command = "/workflow:ui-design:animation-extract --base-path \"{base_path}\" --mode interactive"
+    SlashCommand(command)
+ELSE:
+    REPORT: "✅ Phase 2.3: Animation (Using Code Import)"
 
 # Output: animation-tokens.json + animation-guide.md
 # SlashCommand blocks until phase complete
@@ -299,23 +407,16 @@ SlashCommand(command)
 ### Phase 2.5: Layout Extraction
 ```bash
 targets_string = ",".join(inferred_target_list)
-command = "/workflow:ui-design:layout-extract --base-path \"{base_path}\" " +
-          (--images ? "--images \"{images}\" " : "") +
-          (--prompt ? "--prompt \"{prompt}\" " : "") +
-          "--targets \"{targets_string}\" " +
-          "--mode explore --variants {layout_variants} " +
-          "--device-type \"{device_type}\""
 
-REPORT: "🚀 Phase 2.5: Layout Extraction (explore mode)"
-REPORT: "   → Targets: {targets_string}"
-REPORT: "   → Layout variants: {layout_variants}"
-REPORT: "   → Device: {device_type}"
-
-SlashCommand(command)
-
-# Output: layout-templates.json with {targets × layout_variants} layout structures
-# SlashCommand blocks until phase complete
-# Upon completion, IMMEDIATELY execute Phase 3 (auto-continue)
+IF (design_source == "visual_only" OR needs_visual_supplement) OR (NOT layout_complete):
+    REPORT: "🚀 Phase 2.5: Layout Extraction ({targets_string}, variants: {layout_variants}, device: {device_type})"
+    command = "/workflow:ui-design:layout-extract --base-path \"{base_path}\" " +
+              (--images ? "--images \"{images}\" " : "") +
+              (--prompt ? "--prompt \"{prompt}\" " : "") +
+              "--targets \"{targets_string}\" --mode explore --variants {layout_variants} --device-type \"{device_type}\""
+    SlashCommand(command)
+ELSE:
+    REPORT: "✅ Phase 2.5: Layout (Using Code Import)"
 ```
 
 ### Phase 3: UI Assembly

.claude/commands/workflow/ui-design/explore-layers.md

@@ -1,6 +1,6 @@
 ---
 name: explore-layers
-description: Interactive deep UI capture with depth-controlled layer exploration
+description: Interactive deep UI capture with depth-controlled layer exploration using MCP puppeteer
 argument-hint: --url <url> --depth <1-5> [--session id] [--base-path path]
 allowed-tools: TodoWrite(*), Read(*), Write(*), Bash(*), Glob(*), mcp__chrome-devtools__*
 ---

.claude/commands/workflow/ui-design/generate.md

@@ -1,6 +1,6 @@
 ---
 name: generate
-description: Assemble UI prototypes by combining layout templates with design tokens (pure assembler)
+description: Assemble UI prototypes by combining layout templates with design tokens, pure assembler without new content generation
 argument-hint: [--base-path <path>] [--session <id>] [--style-variants <count>] [--layout-variants <count>]
 allowed-tools: TodoWrite(*), Read(*), Write(*), Task(ui-design-agent), Bash(*)
 ---

.claude/commands/workflow/ui-design/imitate-auto.md

@@ -1,6 +1,6 @@
 ---
 name: imitate-auto
-description: High-speed multi-page UI replication with batch screenshot capture
+description: High-speed multi-page UI replication with batch screenshot capture and design token extraction
 argument-hint: --url-map "<map>" [--capture-mode <batch|deep>] [--depth <1-5>] [--session <id>] [--prompt "<desc>"]
 allowed-tools: SlashCommand(*), TodoWrite(*), Read(*), Write(*), Bash(*)
 ---
@@ -115,6 +115,23 @@ ELSE:
 # Create base directory
 Bash(mkdir -p "{base_path}")
 
+# Step 0.1: Intelligent Path Detection
+code_files_detected = false
+code_base_path = null
+design_source = "web"  # Default for imitate-auto
+
+IF --prompt:
+    # Extract potential file paths from prompt
+    potential_paths = extract_paths_from_text(--prompt)
+    FOR path IN potential_paths:
+        IF file_or_directory_exists(path):
+            code_files_detected = true
+            code_base_path = path
+            design_source = "hybrid"  # Web + Code
+            BREAK
+
+STORE: design_source, code_base_path
+
 # Parse url-map
 url_map_string = {--url-map}
 VALIDATE: url_map_string is not empty, "--url-map parameter is required"
@@ -196,11 +213,110 @@ TodoWrite({todos: [
 ]})
 ```
 
+### Phase 0.5: Code Import & Completeness Assessment (Conditional)
+
+```bash
+# Only execute if code files detected
+IF design_source == "hybrid":
+    REPORT: "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
+    REPORT: "🔍 Phase 0.5: Code Import & Analysis"
+    REPORT: "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
+    REPORT: "   → Source: {code_base_path}"
+    REPORT: "   → Mode: Hybrid (Web + Code)"
+
+    command = "/workflow:ui-design:import-from-code --base-path \"{base_path}\" " +
+              "--base-path \"{code_base_path}\""
+
+    TRY:
+        SlashCommand(command)
+    CATCH error:
+        WARN: "Code import failed: {error}"
+        WARN: "Falling back to web-only mode"
+        design_source = "web"
+
+    IF design_source == "hybrid":
+        # Check file existence and assess completeness
+        style_exists = exists("{base_path}/style-extraction/style-1/design-tokens.json")
+        animation_exists = exists("{base_path}/animation-extraction/animation-tokens.json")
+        layout_exists = exists("{base_path}/layout-extraction/layout-templates.json")
+
+        style_complete = false
+        animation_complete = false
+        layout_complete = false
+        missing_categories = []
+
+        # Style completeness check
+        IF style_exists:
+            tokens = Read("{base_path}/style-extraction/style-1/design-tokens.json")
+            style_complete = (
+                tokens.colors?.brand && tokens.colors?.surface &&
+                tokens.typography?.font_family && tokens.spacing &&
+                Object.keys(tokens.colors.brand || {}).length >= 3 &&
+                Object.keys(tokens.spacing || {}).length >= 8
+            )
+            IF NOT style_complete AND tokens._metadata?.completeness?.missing_categories:
+                missing_categories.extend(tokens._metadata.completeness.missing_categories)
+        ELSE:
+            missing_categories.push("style tokens")
+
+        # Animation completeness check
+        IF animation_exists:
+            anim = Read("{base_path}/animation-extraction/animation-tokens.json")
+            animation_complete = (
+                anim.duration && anim.easing &&
+                Object.keys(anim.duration || {}).length >= 3 &&
+                Object.keys(anim.easing || {}).length >= 3
+            )
+            IF NOT animation_complete AND anim._metadata?.completeness?.missing_items:
+                missing_categories.extend(anim._metadata.completeness.missing_items)
+        ELSE:
+            missing_categories.push("animation tokens")
+
+        # Layout completeness check
+        IF layout_exists:
+            layouts = Read("{base_path}/layout-extraction/layout-templates.json")
+            layout_complete = (
+                layouts.layout_templates?.length >= 3 &&
+                layouts.extraction_metadata?.layout_system?.type &&
+                layouts.extraction_metadata?.responsive?.breakpoints
+            )
+            IF NOT layout_complete AND layouts.extraction_metadata?.completeness?.missing_items:
+                missing_categories.extend(layouts.extraction_metadata.completeness.missing_items)
+        ELSE:
+            missing_categories.push("layout templates")
+
+        # Report code analysis results
+        IF len(missing_categories) > 0:
+            REPORT: ""
+            REPORT: "⚠️  Code Analysis Partial"
+            REPORT: "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
+            REPORT: "Missing Design Elements:"
+            FOR category IN missing_categories:
+                REPORT: "  • {category}"
+            REPORT: ""
+            REPORT: "Web screenshots will supplement missing elements"
+            REPORT: "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
+        ELSE:
+            REPORT: ""
+            REPORT: "✅ Code Analysis Complete"
+            REPORT: "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
+            REPORT: "All design elements extracted from code"
+            REPORT: "Web screenshots will verify and enhance findings"
+            REPORT: "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
+
+        STORE: style_complete, animation_complete, layout_complete
+
+TodoWrite(mark_completed: "Initialize and parse url-map",
+          mark_in_progress: capture_mode == "batch" ? f"Batch screenshot capture ({len(target_names)} targets)" : f"Deep exploration (depth {depth})")
+```
+
 ### Phase 1: Screenshot Capture (Dual Mode)
 
 ```bash
 REPORT: "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
 REPORT: "🚀 Phase 1: Screenshot Capture"
+IF design_source == "hybrid":
+    REPORT: "   → Purpose: Verify and supplement code analysis"
 REPORT: "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
 
 IF capture_mode == "batch":
@@ -264,161 +380,84 @@ TodoWrite(mark_completed: f"Batch screenshot capture ({len(target_names)} target
           mark_in_progress: "Extract style (visual tokens)")
 ```
 
-### Phase 2: Style Extraction (Visual Tokens)
+### Phase 2: Style Extraction
 
 ```bash
-REPORT: "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-REPORT: "🚀 Phase 2: Style Extraction"
-REPORT: "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
+# Determine if style extraction needed
+skip_style = (design_source == "hybrid" AND style_complete)
 
-# Use all screenshots as input to extract single design system
-IF capture_mode == "batch":
-    images_glob = f"{base_path}/screenshots/*.{{png,jpg,jpeg,webp}}"
-ELSE:  # deep mode
-    images_glob = f"{base_path}/screenshots/**/*.{{png,jpg,jpeg,webp}}"
-
-# Build extraction prompt
-IF --prompt:
-    user_guidance = {--prompt}
-    extraction_prompt = f"Extract visual style tokens from '{primary_target}'. User guidance: {user_guidance}"
+IF skip_style:
+    REPORT: "✅ Phase 2: Style (Using Code Import)"
 ELSE:
-    extraction_prompt = f"Extract visual style tokens from '{primary_target}' with consistency across all pages."
+    REPORT: "🚀 Phase 2: Style Extraction"
+    IF capture_mode == "batch":
+        images_glob = f"{base_path}/screenshots/*.{{png,jpg,jpeg,webp}}"
+    ELSE:
+        images_glob = f"{base_path}/screenshots/**/*.{{png,jpg,jpeg,webp}}"
 
-# Build url-map string for style-extract (enables computed styles extraction)
-url_map_for_extract = ",".join([f"{name}:{url}" for name, url in url_map.items()])
+    IF --prompt:
+        extraction_prompt = f"Extract visual style tokens from '{primary_target}'. {--prompt}"
+    ELSE:
+        IF design_source == "hybrid":
+            extraction_prompt = f"Extract visual style tokens from '{primary_target}' to supplement code-imported design tokens."
+        ELSE:
+            extraction_prompt = f"Extract visual style tokens from '{primary_target}' with consistency across all pages."
 
-# Call style-extract command (imitate mode, automatically uses single variant)
-# Pass --urls to enable auto-trigger of computed styles extraction
-extract_command = f"/workflow:ui-design:style-extract --base-path \"{base_path}\" --images \"{images_glob}\" --urls \"{url_map_for_extract}\" --prompt \"{extraction_prompt}\" --mode imitate"
-
-TRY:
+    url_map_for_extract = ",".join([f"{name}:{url}" for name, url in url_map.items()])
+    extract_command = f"/workflow:ui-design:style-extract --base-path \"{base_path}\" --images \"{images_glob}\" --urls \"{url_map_for_extract}\" --prompt \"{extraction_prompt}\" --mode imitate"
     SlashCommand(extract_command)
-CATCH error:
-    ERROR: "Style extraction failed: {error}"
-    ERROR: "Cannot proceed without visual tokens"
-    EXIT 1
 
-# Verify extraction results
-design_tokens_path = "{base_path}/style-extraction/style-1/design-tokens.json"
-style_guide_path = "{base_path}/style-extraction/style-1/style-guide.md"
-
-IF NOT exists(design_tokens_path) OR NOT exists(style_guide_path):
-    ERROR: "style-extract did not generate required files"
-    EXIT 1
-
-TodoWrite(mark_completed: "Extract style (complete design systems)",
-          mark_in_progress: "Extract animation (CSS auto mode)")
+TodoWrite(mark_completed: "Extract style", mark_in_progress: "Extract animation")
 ```
 
-### Phase 2.3: Animation Extraction (CSS Auto Mode)
+### Phase 2.3: Animation Extraction
 
 ```bash
-REPORT: "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-REPORT: "🚀 Phase 2.3: Animation Extraction"
-REPORT: "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
+skip_animation = (design_source == "hybrid" AND animation_complete)
 
-# Build URL list for animation-extract (auto mode for CSS extraction)
-url_map_for_animation = ",".join([f"{target}:{url}" for target, url in url_map.items()])
-
-# Call animation-extract command (auto mode for CSS animation extraction)
-# Pass --urls to auto-trigger CSS animation/transition extraction via Chrome DevTools
-animation_extract_command = f"/workflow:ui-design:animation-extract --base-path \"{base_path}\" --urls \"{url_map_for_animation}\" --mode auto"
-
-TRY:
+IF skip_animation:
+    REPORT: "✅ Phase 2.3: Animation (Using Code Import)"
+ELSE:
+    REPORT: "🚀 Phase 2.3: Animation Extraction"
+    url_map_for_animation = ",".join([f"{target}:{url}" for target, url in url_map.items()])
+    animation_extract_command = f"/workflow:ui-design:animation-extract --base-path \"{base_path}\" --urls \"{url_map_for_animation}\" --mode auto"
     SlashCommand(animation_extract_command)
-CATCH error:
-    ERROR: "Animation extraction failed: {error}"
-    ERROR: "Cannot proceed without animation tokens"
-    EXIT 1
 
-# Verify animation extraction results
-animation_tokens_path = "{base_path}/animation-extraction/animation-tokens.json"
-animation_guide_path = "{base_path}/animation-extraction/animation-guide.md"
-
-IF NOT exists(animation_tokens_path) OR NOT exists(animation_guide_path):
-    ERROR: "animation-extract did not generate required files"
-    EXIT 1
-
-TodoWrite(mark_completed: "Extract animation (CSS auto mode)",
-          mark_in_progress: "Extract layout (structure templates)")
 ```
 
-### Phase 2.5: Layout Extraction (Structure Templates)
+### Phase 2.5: Layout Extraction
 
 ```bash
-REPORT: "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-REPORT: "🚀 Phase 2.5: Layout Extraction"
-REPORT: "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
+skip_layout = (design_source == "hybrid" AND layout_complete)
 
-# Build URL map for layout-extract
-url_map_for_layout = ",".join([f"{target}:{url}" for target, url in url_map.items()])
-
-# Call layout-extract command (imitate mode for structure replication)
-# Pass --urls to enable auto-trigger of DOM structure extraction
-layout_extract_command = f"/workflow:ui-design:layout-extract --base-path \"{base_path}\" --images \"{images_glob}\" --urls \"{url_map_for_layout}\" --targets \"{','.join(target_names)}\" --mode imitate"
-
-TRY:
+IF skip_layout:
+    REPORT: "✅ Phase 2.5: Layout (Using Code Import)"
+ELSE:
+    REPORT: "🚀 Phase 2.5: Layout Extraction"
+    url_map_for_layout = ",".join([f"{target}:{url}" for target, url in url_map.items()])
+    layout_extract_command = f"/workflow:ui-design:layout-extract --base-path \"{base_path}\" --images \"{images_glob}\" --urls \"{url_map_for_layout}\" --targets \"{','.join(target_names)}\" --mode imitate"
     SlashCommand(layout_extract_command)
-CATCH error:
-    ERROR: "Layout extraction failed: {error}"
-    ERROR: "Cannot proceed without layout templates"
-    EXIT 1
 
-# Verify layout extraction results
-layout_templates_path = "{base_path}/layout-extraction/layout-templates.json"
-
-IF NOT exists(layout_templates_path):
-    ERROR: "layout-extract did not generate layout-templates.json"
-    EXIT 1
-
-TodoWrite(mark_completed: "Extract layout (structure templates)",
-          mark_in_progress: f"Assemble UI for {len(target_names)} targets")
+TodoWrite(mark_completed: "Extract layout", mark_in_progress: "Assemble UI")
 ```
 
-### Phase 3: Batch UI Assembly
+### Phase 3: UI Assembly
 
 ```bash
-REPORT: "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
 REPORT: "🚀 Phase 3: UI Assembly"
-REPORT: "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-
-# Call generate command (pure assembler - combines layout templates + design tokens)
 generate_command = f"/workflow:ui-design:generate --base-path \"{base_path}\" --style-variants 1 --layout-variants 1"
+SlashCommand(generate_command)
 
-TRY:
-    SlashCommand(generate_command)
-CATCH error:
-    ERROR: "UI assembly failed: {error}"
-    ERROR: "Layout templates or design tokens may be invalid"
-    EXIT 1
-
-# Verify assembly results
-prototypes_dir = "{base_path}/prototypes"
-generated_html_files = Glob(f"{prototypes_dir}/*-style-1-layout-1.html")
-generated_count = len(generated_html_files)
-
-IF generated_count < len(target_names):
-    WARN: "⚠️ Expected {len(target_names)} prototypes, assembled {generated_count}"
-
-TodoWrite(mark_completed: f"Assemble UI for {len(target_names)} targets",
-          mark_in_progress: session_id ? "Integrate design system" : "Standalone completion")
+TodoWrite(mark_completed: "Assemble UI", mark_in_progress: session_id ? "Integrate design system" : "Completion")
 ```
 
 ### Phase 4: Design System Integration
 
 ```bash
-REPORT: "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-REPORT: "🚀 Phase 4: Design System Integration"
-REPORT: "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
-
 IF session_id:
+    REPORT: "🚀 Phase 4: Design System Integration"
     update_command = f"/workflow:ui-design:update --session {session_id}"
-
-    TRY:
-        SlashCommand(update_command)
-    CATCH error:
-        WARN: "⚠️ Design system integration failed: {error}"
-        WARN: "Prototypes available at {base_path}/prototypes/"
+    SlashCommand(update_command)
 
 # Update metadata
 metadata = Read("{base_path}/.run-metadata.json")

.claude/commands/workflow/ui-design/import-from-code.md

@@ -0,0 +1,785 @@
+---
+name: workflow:ui-design:import-from-code
+description: Import design system from code files (CSS/JS/HTML/SCSS) using parallel agent analysis with final synthesis
+argument-hint: "[--base-path <path>] [--css \"<glob>\"] [--js \"<glob>\"] [--scss \"<glob>\"] [--html \"<glob>\"] [--style-files \"<glob>\"] [--session <id>]"
+allowed-tools: Read,Write,Bash,Glob,Grep,Task,TodoWrite
+auto-continue: true
+---
+
+# UI Design: Import from Code
+
+## Overview
+
+Extract design system tokens from source code files (CSS/SCSS/JS/TS/HTML) using parallel agent analysis. Each agent can reference any file type for cross-source token extraction, and directly generates completeness reports with findings and gaps.
+
+**Key Characteristics**:
+- Executes parallel agent analysis (3 agents: Style, Animation, Layout)
+- Each agent can read ALL file types (CSS/SCSS/JS/TS/HTML) for cross-reference
+- Direct completeness reporting without synthesis phase
+- Graceful failure handling with detailed missing content analysis
+- Returns concrete analysis results with recommendations
+
+## Core Functionality
+
+- **File Discovery**: Auto-discover or target specific CSS/SCSS/JS/HTML files
+- **Parallel Analysis**: 3 agents extract tokens simultaneously with cross-file-type support
+- **Completeness Reporting**: Each agent reports found tokens, missing content, and recommendations
+- **Cross-Source Extraction**: Agents can reference any file type (e.g., Style agent can read JS theme configs)
+
+## Usage
+
+### Command Syntax
+
+```bash
+/workflow:ui-design:import-from-code [FLAGS]
+
+# Flags
+--base-path <path>      Base directory for analysis (default: current directory)
+--css "<glob>"          CSS file glob pattern (e.g., "theme/*.css")
+--scss "<glob>"         SCSS file glob pattern (e.g., "styles/*.scss")
+--js "<glob>"           JavaScript file glob pattern (e.g., "theme/*.js")
+--html "<glob>"         HTML file glob pattern (e.g., "pages/*.html")
+--style-files "<glob>"  Universal style file glob (applies to CSS/SCSS/JS)
+--session <id>          Session identifier for workflow tracking
+```
+
+### Usage Examples
+
+```bash
+# Basic usage - auto-discover all files
+/workflow:ui-design:import-from-code --base-path ./
+
+# Target specific directories
+/workflow:ui-design:import-from-code --base-path ./src --css "theme/*.css" --js "theme/*.js"
+
+# Tailwind config only
+/workflow:ui-design:import-from-code --js "tailwind.config.js"
+
+# CSS framework import
+/workflow:ui-design:import-from-code --css "styles/**/*.scss" --html "components/**/*.html"
+
+# Universal style files
+/workflow:ui-design:import-from-code --style-files "**/theme.*"
+```
+
+---
+
+## Execution Process
+
+### Step 1: Setup & File Discovery
+
+**Purpose**: Initialize session, discover and categorize code files
+
+**Operations**:
+
+```bash
+# 1. Initialize directories
+base_path="${base_path:-.}"
+intermediates_dir="${base_path}/.intermediates/import-analysis"
+mkdir -p "$intermediates_dir"
+
+echo "[Phase 0] File Discovery Started"
+```
+
+<!-- TodoWrite: Initialize todo list -->
+
+**TodoWrite**:
+```json
+[
+  {"content": "Phase 0: 发现和分类代码文件", "status": "in_progress", "activeForm": "发现代码文件"},
+  {"content": "Phase 1: 并行Agent分析并生成completeness-report.json", "status": "pending", "activeForm": "生成design system"}
+]
+```
+
+**File Discovery Logic**:
+
+```bash
+# 2. Discover files by type
+cd "$base_path" || exit 1
+
+# CSS files
+if [ -n "$css" ]; then
+  find . -type f -name "*.css" | grep -E "$css" > "$intermediates_dir/css-files.txt"
+elif [ -n "$style_files" ]; then
+  find . -type f -name "*.css" | grep -E "$style_files" > "$intermediates_dir/css-files.txt"
+else
+  find . -type f -name "*.css" -not -path "*/node_modules/*" -not -path "*/dist/*" > "$intermediates_dir/css-files.txt"
+fi
+
+# SCSS files
+if [ -n "$scss" ]; then
+  find . -type f \( -name "*.scss" -o -name "*.sass" \) | grep -E "$scss" > "$intermediates_dir/scss-files.txt"
+elif [ -n "$style_files" ]; then
+  find . -type f \( -name "*.scss" -o -name "*.sass" \) | grep -E "$style_files" > "$intermediates_dir/scss-files.txt"
+else
+  find . -type f \( -name "*.scss" -o -name "*.sass" \) -not -path "*/node_modules/*" -not -path "*/dist/*" > "$intermediates_dir/scss-files.txt"
+fi
+
+# JavaScript files (theme/style related)
+if [ -n "$js" ]; then
+  find . -type f \( -name "*.js" -o -name "*.ts" -o -name "*.jsx" -o -name "*.tsx" \) | grep -E "$js" > "$intermediates_dir/js-files.txt"
+elif [ -n "$style_files" ]; then
+  find . -type f \( -name "*.js" -o -name "*.ts" -o -name "*.jsx" -o -name "*.tsx" \) | grep -E "$style_files" > "$intermediates_dir/js-files.txt"
+else
+  # Look for common theme/style file patterns
+  find . -type f \( -name "*.js" -o -name "*.ts" -o -name "*.jsx" -o -name "*.tsx" \) -not -path "*/node_modules/*" -not -path "*/dist/*" | \
+    grep -iE "(theme|style|color|token|design)" > "$intermediates_dir/js-files.txt" || touch "$intermediates_dir/js-files.txt"
+fi
+
+# HTML files
+if [ -n "$html" ]; then
+  find . -type f \( -name "*.html" -o -name "*.htm" \) | grep -E "$html" > "$intermediates_dir/html-files.txt"
+else
+  find . -type f \( -name "*.html" -o -name "*.htm" \) -not -path "*/node_modules/*" -not -path "*/dist/*" > "$intermediates_dir/html-files.txt"
+fi
+
+# 3. Count discovered files
+css_count=$(wc -l < "$intermediates_dir/css-files.txt" 2>/dev/null || echo 0)
+scss_count=$(wc -l < "$intermediates_dir/scss-files.txt" 2>/dev/null || echo 0)
+js_count=$(wc -l < "$intermediates_dir/js-files.txt" 2>/dev/null || echo 0)
+html_count=$(wc -l < "$intermediates_dir/html-files.txt" 2>/dev/null || echo 0)
+
+echo "[Phase 0] Discovered: CSS=$css_count, SCSS=$scss_count, JS=$js_count, HTML=$html_count"
+```
+
+<!-- TodoWrite: Mark Phase 0 complete, start Phase 1 -->
+
+**TodoWrite**:
+```json
+[
+  {"content": "Phase 0: 发现和分类代码文件", "status": "completed", "activeForm": "发现代码文件"},
+  {"content": "Phase 1: 并行Agent分析并生成completeness-report.json", "status": "in_progress", "activeForm": "生成design system"}
+]
+```
+
+---
+
+### Step 2: Parallel Agent Analysis
+
+**Purpose**: Three agents analyze all file types in parallel, each producing completeness-report.json
+
+**Operations**:
+- **Style Agent**: Extracts visual tokens (colors, typography, spacing) from ALL files (CSS/SCSS/JS/HTML)
+- **Animation Agent**: Extracts animations/transitions from ALL files
+- **Layout Agent**: Extracts layout patterns/component structures from ALL files
+
+**Validation**:
+- Each agent can reference any file type (not restricted to single type)
+- Direct output: Each agent generates completeness-report.json with findings + missing content
+- No synthesis needed: Agents produce final output directly
+
+```bash
+echo "[Phase 1] Starting parallel agent analysis (3 agents)"
+```
+
+#### Style Agent Task (style-completeness-report.json)
+
+**Agent Task**:
+
+```javascript
+Task(ui-design-agent): `
+  [STYLE_TOKENS_EXTRACTION]
+  Extract visual design tokens (colors, typography, spacing, shadows, borders) from ALL file types
+
+  MODE: style-extraction | BASE_PATH: ${base_path}
+
+  ## Input Files (Can reference ANY file type)
+
+  **CSS/SCSS files (${css_count})**:
+  $(cat "${intermediates_dir}/css-files.txt" 2>/dev/null | head -20)
+
+  **JavaScript/TypeScript files (${js_count})**:
+  $(cat "${intermediates_dir}/js-files.txt" 2>/dev/null | head -20)
+
+  **HTML files (${html_count})**:
+  $(cat "${intermediates_dir}/html-files.txt" 2>/dev/null | head -20)
+
+  ## Extraction Strategy
+
+  **You can read ALL file types** - Cross-reference for better extraction:
+  1. **CSS/SCSS**: Primary source for colors, typography, spacing, shadows, borders
+  2. **JavaScript/TypeScript**: Theme objects (styled-components, Tailwind config, CSS-in-JS tokens)
+  3. **HTML**: Inline styles, class usage patterns, component examples
+
+  **Smart inference** - Fill gaps using cross-source data:
+  - Missing CSS colors? Check JS theme objects
+  - Missing spacing scale? Infer from existing values in any file type
+  - Missing typography? Check font-family usage in CSS + HTML + JS configs
+
+  ## Output Requirements
+
+  Generate 2 files in ${base_path}/style-extraction/style-1/:
+  1. design-tokens.json (production-ready design tokens)
+  2. style-guide.md (design philosophy and usage guide)
+
+  ### design-tokens.json Structure:
+  {
+    "colors": {
+      "brand": {
+        "primary": {"value": "#0066cc", "source": "file.css:23"},
+        "secondary": {"value": "#6c757d", "source": "file.css:24"}
+      },
+      "surface": {
+        "background": {"value": "#ffffff", "source": "file.css:10"},
+        "card": {"value": "#f8f9fa", "source": "file.css:11"}
+      },
+      "semantic": {
+        "success": {"value": "#28a745", "source": "file.css:30"},
+        "warning": {"value": "#ffc107", "source": "file.css:31"},
+        "error": {"value": "#dc3545", "source": "file.css:32"}
+      },
+      "text": {
+        "primary": {"value": "#212529", "source": "file.css:15"},
+        "secondary": {"value": "#6c757d", "source": "file.css:16"}
+      },
+      "border": {
+        "default": {"value": "#dee2e6", "source": "file.css:20"}
+      }
+    },
+    "typography": {
+      "font_family": {
+        "base": {"value": "system-ui, sans-serif", "source": "theme.js:12"},
+        "heading": {"value": "Georgia, serif", "source": "theme.js:13"}
+      },
+      "font_size": {
+        "xs": {"value": "0.75rem", "source": "styles.css:5"},
+        "sm": {"value": "0.875rem", "source": "styles.css:6"},
+        "base": {"value": "1rem", "source": "styles.css:7"},
+        "lg": {"value": "1.125rem", "source": "styles.css:8"},
+        "xl": {"value": "1.25rem", "source": "styles.css:9"}
+      },
+      "font_weight": {
+        "normal": {"value": "400", "source": "styles.css:12"},
+        "medium": {"value": "500", "source": "styles.css:13"},
+        "bold": {"value": "700", "source": "styles.css:14"}
+      },
+      "line_height": {
+        "tight": {"value": "1.25", "source": "styles.css:18"},
+        "normal": {"value": "1.5", "source": "styles.css:19"},
+        "relaxed": {"value": "1.75", "source": "styles.css:20"}
+      },
+      "letter_spacing": {
+        "tight": {"value": "-0.025em", "source": "styles.css:24"},
+        "normal": {"value": "0", "source": "styles.css:25"},
+        "wide": {"value": "0.025em", "source": "styles.css:26"}
+      }
+    },
+    "spacing": {
+      "0": {"value": "0", "source": "styles.css:30"},
+      "1": {"value": "0.25rem", "source": "styles.css:31"},
+      "2": {"value": "0.5rem", "source": "styles.css:32"},
+      "3": {"value": "0.75rem", "source": "styles.css:33"},
+      "4": {"value": "1rem", "source": "styles.css:34"},
+      "6": {"value": "1.5rem", "source": "styles.css:35"},
+      "8": {"value": "2rem", "source": "styles.css:36"},
+      "12": {"value": "3rem", "source": "styles.css:37"}
+    },
+    "opacity": {
+      "0": {"value": "0", "source": "styles.css:40"},
+      "50": {"value": "0.5", "source": "styles.css:41"},
+      "100": {"value": "1", "source": "styles.css:42"}
+    },
+    "border_radius": {
+      "none": {"value": "0", "source": "styles.css:45"},
+      "sm": {"value": "0.125rem", "source": "styles.css:46"},
+      "base": {"value": "0.25rem", "source": "styles.css:47"},
+      "lg": {"value": "0.5rem", "source": "styles.css:48"},
+      "full": {"value": "9999px", "source": "styles.css:49"}
+    },
+    "shadows": {
+      "sm": {"value": "0 1px 2px rgba(0,0,0,0.05)", "source": "theme.css:45"},
+      "base": {"value": "0 1px 3px rgba(0,0,0,0.1)", "source": "theme.css:46"},
+      "md": {"value": "0 4px 6px rgba(0,0,0,0.1)", "source": "theme.css:47"},
+      "lg": {"value": "0 10px 15px rgba(0,0,0,0.1)", "source": "theme.css:48"}
+    },
+    "breakpoints": {
+      "sm": {"value": "640px", "source": "media.scss:3"},
+      "md": {"value": "768px", "source": "media.scss:4"},
+      "lg": {"value": "1024px", "source": "media.scss:5"},
+      "xl": {"value": "1280px", "source": "media.scss:6"}
+    },
+    "_metadata": {
+      "extraction_source": "code_import",
+      "files_analyzed": {
+        "css": ["list of CSS/SCSS files read"],
+        "js": ["list of JS/TS files read"],
+        "html": ["list of HTML files read"]
+      },
+      "completeness": {
+        "colors": "complete | partial | minimal",
+        "typography": "complete | partial | minimal",
+        "spacing": "complete | partial | minimal",
+        "missing_categories": ["accent", "warning"],
+        "recommendations": [
+          "Define accent color for interactive elements",
+          "Add semantic colors (warning, error, success)"
+        ]
+      }
+    }
+  }
+
+  ### style-guide.md Structure:
+ 
+  # Design System Style Guide
+
+  ## Overview
+  Extracted from code files: [list of source files]
+
+  ## Colors
+  - **Brand**: Primary, Secondary
+  - **Surface**: Background, Card
+  - **Semantic**: Success, Warning, Error
+  - **Text**: Primary, Secondary
+  - **Border**: Default
+
+  ## Typography
+  - **Font Families**: Base (system-ui), Heading (Georgia)
+  - **Font Sizes**: xs to xl (0.75rem - 1.25rem)
+  - **Font Weights**: Normal (400), Medium (500), Bold (700)
+
+  ## Spacing
+  System: 8px-grid (0, 0.25rem, 0.5rem, ..., 3rem)
+
+  ## Missing Elements
+  - Accent colors for interactive elements
+  - Extended shadow scale
+
+  ## Usage
+  All tokens are production-ready and can be used with CSS variables.
+  
+
+  ## Completeness Criteria
+  - **colors**: ≥5 categories (brand, semantic, surface, text, border), ≥10 tokens
+  - **typography**: ≥3 font families, ≥8 sizes, ≥5 weights
+  - **spacing**: ≥8 values in consistent system
+  - **shadows**: ≥3 elevation levels
+  - **borders**: ≥3 radius values, ≥2 widths
+
+  ## Critical Requirements
+  - ✅ Can read ANY file type (CSS/SCSS/JS/TS/HTML) - not restricted to CSS only
+  - ✅ Use Read() tool for each file you want to analyze
+  - ✅ Cross-reference between file types for better extraction
+  - ✅ Extract all visual token types systematically
+  - ✅ Create style-extraction/style-1/ directory first: Bash(mkdir -p "${base_path}/style-extraction/style-1")
+  - ✅ Use Write() to save both files:
+    - ${base_path}/style-extraction/style-1/design-tokens.json
+    - ${base_path}/style-extraction/style-1/style-guide.md
+  - ✅ Include _metadata.completeness field to track missing content
+  - ❌ NO external research or MCP calls
+`
+```
+
+#### Animation Agent Task
+
+**Agent Task**:
+
+```javascript
+Task(ui-design-agent): `
+  [ANIMATION_TOKENS_EXTRACTION]
+  Extract animation/transition tokens from ALL file types
+
+  MODE: animation-extraction | BASE_PATH: ${base_path}
+
+  ## Input Files (Can reference ANY file type)
+
+  **CSS/SCSS files (${css_count})**:
+  $(cat "${intermediates_dir}/css-files.txt" 2>/dev/null | head -20)
+
+  **JavaScript/TypeScript files (${js_count})**:
+  $(cat "${intermediates_dir}/js-files.txt" 2>/dev/null | head -20)
+
+  **HTML files (${html_count})**:
+  $(cat "${intermediates_dir}/html-files.txt" 2>/dev/null | head -20)
+
+  ## Extraction Strategy
+
+  **You can read ALL file types** - Find animations anywhere:
+  1. **CSS/SCSS**: @keyframes, transition properties, animation properties
+  2. **JavaScript/TypeScript**: Animation configs (Framer Motion, GSAP, CSS-in-JS animations)
+  3. **HTML**: Inline animation styles, data-animation attributes
+
+  **Cross-reference**:
+  - CSS animations referenced in JS configs
+  - JS animation libraries with CSS class triggers
+  - HTML elements with animation classes/attributes
+
+  ## Output Requirements
+
+  Generate 2 files in ${base_path}/animation-extraction/:
+  1. animation-tokens.json (production-ready animation tokens)
+  2. animation-guide.md (animation usage guide)
+
+  ### animation-tokens.json Structure:
+  {
+    "duration": {
+      "instant": {"value": "0ms", "source": "animations.css:10"},
+      "fast": {"value": "150ms", "source": "animations.css:12"},
+      "base": {"value": "250ms", "source": "animations.css:13"},
+      "slow": {"value": "500ms", "source": "animations.css:14"}
+    },
+    "easing": {
+      "linear": {"value": "linear", "source": "animations.css:20"},
+      "ease-in": {"value": "cubic-bezier(0.4, 0, 1, 1)", "source": "theme.js:45"},
+      "ease-out": {"value": "cubic-bezier(0, 0, 0.2, 1)", "source": "theme.js:46"},
+      "ease-in-out": {"value": "cubic-bezier(0.4, 0, 0.2, 1)", "source": "theme.js:47"}
+    },
+    "transitions": {
+      "color": {
+        "property": "color",
+        "duration": "var(--duration-fast)",
+        "easing": "var(--ease-out)",
+        "source": "transitions.css:30"
+      },
+      "transform": {
+        "property": "transform",
+        "duration": "var(--duration-base)",
+        "easing": "var(--ease-in-out)",
+        "source": "transitions.css:35"
+      },
+      "opacity": {
+        "property": "opacity",
+        "duration": "var(--duration-fast)",
+        "easing": "var(--ease-out)",
+        "source": "transitions.css:40"
+      }
+    },
+    "keyframes": {
+      "fadeIn": {
+        "name": "fadeIn",
+        "keyframes": {
+          "0%": {"opacity": "0"},
+          "100%": {"opacity": "1"}
+        },
+        "source": "styles.css:67"
+      },
+      "slideInUp": {
+        "name": "slideInUp",
+        "keyframes": {
+          "0%": {"transform": "translateY(20px)", "opacity": "0"},
+          "100%": {"transform": "translateY(0)", "opacity": "1"}
+        },
+        "source": "styles.css:75"
+      }
+    },
+    "interactions": {
+      "button-hover": {
+        "trigger": "hover",
+        "properties": ["background-color", "transform"],
+        "duration": "var(--duration-fast)",
+        "easing": "var(--ease-out)",
+        "source": "button.css:45"
+      }
+    },
+    "_metadata": {
+      "extraction_source": "code_import",
+      "framework_detected": "css-animations | framer-motion | gsap | none",
+      "files_analyzed": {
+        "css": ["list of CSS/SCSS files read"],
+        "js": ["list of JS/TS files read"],
+        "html": ["list of HTML files read"]
+      },
+      "completeness": {
+        "durations": "complete | partial | minimal",
+        "easing": "complete | partial | minimal",
+        "keyframes": "complete | partial | minimal",
+        "missing_items": ["bounce easing", "slide animations"],
+        "recommendations": [
+          "Add slow duration for complex animations",
+          "Define spring/bounce easing for interactive feedback"
+        ]
+      }
+    }
+  }
+
+  ### animation-guide.md Structure:
+  
+  # Animation System Guide
+
+  ## Overview
+  Extracted from code files: [list of source files]
+  Framework detected: [css-animations | framer-motion | gsap | none]
+
+  ## Durations
+  - **Instant**: 0ms
+  - **Fast**: 150ms (UI feedback)
+  - **Base**: 250ms (standard transitions)
+  - **Slow**: 500ms (complex animations)
+
+  ## Easing Functions
+  - **Linear**: Constant speed
+  - **Ease-out**: Fast start, slow end (entering elements)
+  - **Ease-in-out**: Smooth acceleration and deceleration
+
+  ## Keyframe Animations
+  - **fadeIn**: Opacity 0 → 1
+  - **slideInUp**: Slide from bottom with fade
+
+  ## Missing Elements
+  - Bounce/spring easing for playful interactions
+  - Slide-out animations
+
+  ## Usage
+  All animation tokens use CSS variables and can be referenced in transitions.
+
+
+  ## Completeness Criteria
+  - **durations**: ≥3 (fast, medium, slow)
+  - **easing**: ≥3 functions (ease-in, ease-out, ease-in-out)
+  - **keyframes**: ≥3 animation types (fade, scale, slide)
+  - **transitions**: ≥5 properties defined
+
+  ## Critical Requirements
+  - ✅ Can read ANY file type (CSS/SCSS/JS/TS/HTML)
+  - ✅ Use Read() tool for each file you want to analyze
+  - ✅ Detect animation framework if used
+  - ✅ Extract all animation-related tokens
+  - ✅ Create animation-extraction/ directory first: Bash(mkdir -p "${base_path}/animation-extraction")
+  - ✅ Use Write() to save both files:
+    - ${base_path}/animation-extraction/animation-tokens.json
+    - ${base_path}/animation-extraction/animation-guide.md
+  - ✅ Include _metadata.completeness field to track missing content
+  - ❌ NO external research or MCP calls
+`
+```
+
+#### Layout Agent Task
+
+**Agent Task**:
+
+```javascript
+Task(ui-design-agent): `
+  [LAYOUT_PATTERNS_EXTRACTION]
+  Extract layout patterns and component structures from ALL file types
+
+  MODE: layout-extraction | BASE_PATH: ${base_path}
+
+  ## Input Files (Can reference ANY file type)
+
+  **CSS/SCSS files (${css_count})**:
+  $(cat "${intermediates_dir}/css-files.txt" 2>/dev/null | head -20)
+
+  **JavaScript/TypeScript files (${js_count})**:
+  $(cat "${intermediates_dir}/js-files.txt" 2>/dev/null | head -20)
+
+  **HTML files (${html_count})**:
+  $(cat "${intermediates_dir}/html-files.txt" 2>/dev/null | head -20)
+
+  ## Extraction Strategy
+
+  **You can read ALL file types** - Find layout patterns anywhere:
+  1. **CSS/SCSS**: Grid systems, flexbox utilities, layout classes, media queries
+  2. **JavaScript/TypeScript**: Layout components (React/Vue), grid configurations, responsive logic
+  3. **HTML**: Layout structures, semantic patterns, component hierarchies
+
+  **Cross-reference**:
+  - HTML structure + CSS classes → layout system
+  - JS components + CSS styles → component patterns
+  - Responsive classes across all file types
+
+  ## Output Requirements
+
+  Generate 1 file: ${base_path}/layout-extraction/layout-templates.json
+
+  ### layout-templates.json Structure:
+  {
+    "extraction_metadata": {
+      "extraction_source": "code_import",
+      "analysis_time": "ISO8601 timestamp",
+      "files_analyzed": {
+        "css": ["list of CSS/SCSS files read"],
+        "js": ["list of JS/TS files read"],
+        "html": ["list of HTML files read"]
+      },
+      "naming_convention": "BEM | SMACSS | utility-first | css-modules | custom",
+      "layout_system": {
+        "type": "12-column | flexbox | css-grid | custom",
+        "confidence": "high | medium | low",
+        "container_classes": ["container", "wrapper"],
+        "row_classes": ["row"],
+        "column_classes": ["col-1", "col-md-6"],
+        "source_files": ["grid.css", "Layout.jsx"]
+      },
+      "responsive": {
+        "breakpoint_prefixes": ["sm:", "md:", "lg:", "xl:"],
+        "mobile_first": true,
+        "breakpoints": {
+          "sm": "640px",
+          "md": "768px",
+          "lg": "1024px",
+          "xl": "1280px"
+        },
+        "source": "responsive.scss:5"
+      },
+      "completeness": {
+        "layout_system": "complete | partial | minimal",
+        "components": "complete | partial | minimal",
+        "responsive": "complete | partial | minimal",
+        "missing_items": ["gap utilities", "modal", "dropdown"],
+        "recommendations": [
+          "Add gap utilities for consistent spacing in grid layouts",
+          "Define modal/dropdown/tabs component patterns"
+        ]
+      }
+    },
+    "layout_templates": [
+      {
+        "target": "button",
+        "variant_id": "layout-1",
+        "device_type": "responsive",
+        "component_type": "component",
+        "dom_structure": {
+          "tag": "button",
+          "classes": ["btn", "btn-primary"],
+          "children": [
+            {"tag": "span", "classes": ["btn-text"], "content": "{{text}}"}
+          ],
+          "variants": {
+            "primary": {"classes": ["btn", "btn-primary"]},
+            "secondary": {"classes": ["btn", "btn-secondary"]}
+          },
+          "sizes": {
+            "sm": {"classes": ["btn-sm"]},
+            "base": {"classes": []},
+            "lg": {"classes": ["btn-lg"]}
+          },
+          "states": ["hover", "active", "disabled"]
+        },
+        "css_layout_rules": "display: inline-flex; align-items: center; justify-content: center; padding: var(--spacing-2) var(--spacing-4); border-radius: var(--radius-base);",
+        "source": "button.css:12"
+      },
+      {
+        "target": "card",
+        "variant_id": "layout-1",
+        "device_type": "responsive",
+        "component_type": "component",
+        "dom_structure": {
+          "tag": "div",
+          "classes": ["card"],
+          "children": [
+            {"tag": "div", "classes": ["card-header"], "content": "{{title}}"},
+            {"tag": "div", "classes": ["card-body"], "content": "{{content}}"},
+            {"tag": "div", "classes": ["card-footer"], "content": "{{footer}}"}
+          ]
+        },
+        "css_layout_rules": "display: flex; flex-direction: column; border: 1px solid var(--color-border); border-radius: var(--radius-lg); padding: var(--spacing-4); background: var(--color-surface-card);",
+        "source": "card.css:25"
+      }
+    ]
+  }
+
+  ## Completeness Criteria
+  - **layout_system**: Clear grid/flexbox system identified
+  - **components**: ≥5 component patterns (button, card, input, modal, dropdown)
+  - **responsive**: ≥3 breakpoints, clear mobile-first strategy
+  - **naming_convention**: Consistent pattern identified
+
+  ## Critical Requirements
+  - ✅ Can read ANY file type (CSS/SCSS/JS/TS/HTML)
+  - ✅ Use Read() tool for each file you want to analyze
+  - ✅ Identify naming conventions and layout systems
+  - ✅ Extract component patterns with variants and states
+  - ✅ Create layout-extraction/ directory first: Bash(mkdir -p "${base_path}/layout-extraction")
+  - ✅ Use Write() to save: ${base_path}/layout-extraction/layout-templates.json
+  - ✅ Include extraction_metadata.completeness field to track missing content
+  - ❌ NO external research or MCP calls
+`
+```
+
+**Wait for All Agents**:
+
+```bash
+# Note: Agents run in parallel and write separate completeness reports
+# Each agent generates its own completeness-report.json directly
+# No synthesis phase needed
+echo "[Phase 1] Parallel agent analysis complete"
+```
+
+<!-- TodoWrite: Mark all complete -->
+
+**TodoWrite**:
+```json
+[
+  {"content": "Phase 0: 发现和分类代码文件", "status": "completed", "activeForm": "发现代码文件"},
+  {"content": "Phase 1: 并行Agent分析并生成completeness-report.json", "status": "completed", "activeForm": "生成design system"}
+]
+```
+
+---
+
+## Output Files
+
+### Generated Files
+
+**Location**: `${base_path}/`
+
+**Directory Structure**:
+```
+${base_path}/
+├── style-extraction/
+│   └── style-1/
+│       ├── design-tokens.json       # Production-ready design tokens
+│       └── style-guide.md           # Design philosophy and usage
+├── animation-extraction/
+│   ├── animation-tokens.json        # Animation/transition tokens
+│   └── animation-guide.md           # Animation usage guide
+├── layout-extraction/
+│   └── layout-templates.json        # Layout patterns and component structures
+└── .intermediates/
+    └── import-analysis/
+        ├── css-files.txt            # Discovered CSS/SCSS files
+        ├── js-files.txt             # Discovered JS/TS files
+        └── html-files.txt           # Discovered HTML files
+```
+
+**Files**:
+1. **style-extraction/style-1/design-tokens.json**
+   - Production-ready design tokens
+   - Categories: colors, typography, spacing, opacity, border_radius, shadows, breakpoints
+   - Metadata: extraction_source, files_analyzed, completeness assessment
+
+2. **style-extraction/style-1/style-guide.md**
+   - Design system overview
+   - Token categories and usage
+   - Missing elements and recommendations
+
+3. **animation-extraction/animation-tokens.json**
+   - Animation tokens: duration, easing, transitions, keyframes, interactions
+   - Framework detection: css-animations, framer-motion, gsap, etc.
+   - Metadata: extraction_source, completeness assessment
+
+4. **animation-extraction/animation-guide.md**
+   - Animation system overview
+   - Usage guidelines and examples
+
+5. **layout-extraction/layout-templates.json**
+   - Layout templates for each discovered component
+   - Extraction metadata: naming_convention, layout_system, responsive strategy
+   - Component patterns with DOM structure and CSS rules
+
+**Intermediate Files**: `.intermediates/import-analysis/`
+- `css-files.txt` - Discovered CSS/SCSS files
+- `js-files.txt` - Discovered JS/TS files
+- `html-files.txt` - Discovered HTML files
+
+---
+
+## Error Handling
+
+### Common Errors
+
+| Error | Cause | Resolution |
+|-------|-------|------------|
+| No files discovered | Glob patterns too restrictive or wrong base-path | Check glob patterns and base-path, verify file locations |
+| Agent reports "failed" status | No tokens found in any file | Review file content, check if files contain design tokens |
+| Empty completeness reports | Files exist but contain no extractable tokens | Manually verify token definitions in source files |
+| Missing file type | Specific file type not discovered | Use explicit glob flags (--css, --js, --html, --scss) |
+
+---
+
+## Best Practices
+
+1. **Use auto-discovery for full projects**: Omit glob flags to discover all files automatically
+2. **Target specific directories for speed**: Use `--base-path` + specific globs for focused analysis
+3. **Cross-reference agent reports**: Compare all three completeness reports to identify gaps
+4. **Review missing content**: Check `missing` field in reports for actionable improvements
+5. **Verify file discovery**: Check `.intermediates/import-analysis/*-files.txt` if agents report no data

.claude/commands/workflow/ui-design/layout-extract.md

@@ -1,6 +1,6 @@
 ---
 name: layout-extract
-description: Extract structural layout information from reference images, URLs, or text prompts
+description: Extract structural layout information from reference images, URLs, or text prompts using Claude analysis
 argument-hint: [--base-path <path>] [--session <id>] [--images "<glob>"] [--urls "<list>"] [--prompt "<desc>"] [--targets "<list>"] [--mode <imitate|explore>] [--variants <count>] [--device-type <desktop|mobile|tablet|responsive>]
 allowed-tools: TodoWrite(*), Read(*), Write(*), Glob(*), Bash(*), Task(ui-design-agent), mcp__exa__web_search_exa(*)
 ---

.claude/commands/workflow/ui-design/style-extract.md

@@ -1,6 +1,6 @@
 ---
 name: style-extract
-description: Extract design style from reference images or text prompts using Claude's analysis
+description: Extract design style from reference images or text prompts using Claude analysis with variant generation
 argument-hint: "[--base-path <path>] [--session <id>] [--images "<glob>"] [--urls "<list>"] [--prompt "<desc>"] [--mode <imitate|explore>] [--variants <count>]"
 allowed-tools: TodoWrite(*), Read(*), Write(*), Glob(*), mcp__chrome-devtools__navigate_page(*), mcp__chrome-devtools__evaluate_script(*)
 ---

.claude/commands/workflow/ui-design/update.md

@@ -1,6 +1,6 @@
 ---
 name: update
-description: Update brainstorming artifacts with finalized design system references
+description: Update brainstorming artifacts with finalized design system references from selected prototypes
 argument-hint: --session <session_id> [--selected-prototypes "<list>"]
 allowed-tools: Read(*), Write(*), Edit(*), TodoWrite(*), Glob(*), Bash(*)
 ---

.claude/scripts/update_module_claude.sh

@@ -192,7 +192,7 @@ update_module_claude() {
     fi
 
     # Use unified template for all modules
-    local template_path="$HOME/.claude/workflows/cli-templates/prompts/memory/claude-module-unified.txt"
+    local template_path="$HOME/.claude/workflows/cli-templates/prompts/memory/02-document-module-structure.txt"
 
     # Read template content directly
     local template_content=""

.claude/skills/command-guide/SKILL.md

@@ -0,0 +1,347 @@
+---
+name: command-guide
+description: Workflow command guide for Claude DMS3 (69 commands). Search/browse commands, get next-step recommendations, view documentation, report issues. Triggers "CCW-help", "CCW-issue", "ccw-help", "ccw-issue", "ccw"
+allowed-tools: Read, Grep, Glob, AskUserQuestion
+---
+
+# Command Guide Skill
+
+Comprehensive command guide for Claude DMS3 workflow system covering 69 commands across 4 categories (workflow, cli, memory, task).
+
+## 🧠 Core Principle: Intelligent Integration
+
+**⚠️ IMPORTANT**: This SKILL provides **reference materials** for intelligent integration, NOT templates for direct copying.
+
+**Response Strategy**:
+1. **Analyze user's specific context** - Understand their exact need, workflow stage, and technical level
+2. **Extract relevant information** - Select only the pertinent parts from reference guides
+3. **Synthesize and customize** - Combine multiple sources, add context-specific examples
+4. **Deliver targeted response** - Provide concise, actionable guidance tailored to the user's situation
+
+**Never**:
+- ❌ Copy-paste entire template sections verbatim
+- ❌ Return raw reference documentation without processing
+- ❌ Provide generic responses that ignore user context
+
+**Always**:
+- ✅ Understand the user's specific situation first
+- ✅ Integrate information from multiple sources (indexes, guides, reference docs)
+- ✅ Customize examples and explanations to match user's use case
+- ✅ Provide progressive depth - brief answers with "more detail available" prompts
+
+---
+
+## 🎯 Operation Modes
+
+### Mode 1: Command Search 🔍
+
+**When**: User searches by keyword, category, or use-case
+
+**Triggers**: "搜索命令", "find command", "planning 相关", "search"
+
+**Process**:
+1. Identify search type (keyword/category/use-case)
+2. Query appropriate index (all-commands/by-category/by-use-case)
+3. **Intelligently filter and rank** results based on user's implied context
+4. **Synthesize concise response** with command names, brief descriptions, and use-case fit
+5. **Suggest next steps** - related commands or workflow patterns
+
+**Example**: "搜索 planning 命令" → Analyze user's likely goal → Present top 3-5 most relevant planning commands with context-specific usage hints, NOT raw JSON dump
+
+---
+
+### Mode 2: Smart Recommendations 🤖
+
+**When**: User asks for next steps after a command
+
+**Triggers**: "下一步", "what's next", "after /workflow:plan", "推荐"
+
+**Process**:
+1. **Analyze workflow context** - Understand where user is in their development cycle
+2. Query `index/command-relationships.json` for possible next commands
+3. **Evaluate and prioritize** recommendations based on:
+   - User's stated goals
+   - Common workflow patterns
+   - Project complexity indicators
+4. **Craft contextual guidance** - Explain WHY each recommendation fits, not just WHAT to run
+5. **Provide workflow examples** - Show complete flow, not isolated commands
+
+**Example**: "执行完 /workflow:plan 后做什么？" → Analyze plan output quality → Recommend `/workflow:action-plan-verify` (if complex) OR `/workflow:execute` (if straightforward) with reasoning for each choice
+
+---
+
+### Mode 3: Full Documentation 📖
+
+**When**: User requests command details
+
+**Triggers**: "参数说明", "怎么用", "how to use", "详情"
+
+**Process**:
+1. Locate command in `index/all-commands.json`
+2. Read original command file for full details
+3. **Extract user-relevant sections** - Focus on what they asked about (parameters OR examples OR workflow)
+4. **Enhance with context** - Add use-case specific examples if user's scenario is clear
+5. **Progressive disclosure** - Provide core info first, offer "need more details?" prompts
+
+**Example**: "/workflow:plan 的参数是什么？" → Identify user's experience level → Present parameters with context-appropriate explanations (beginner: verbose + examples; advanced: concise + edge cases), NOT raw documentation dump
+
+---
+
+### Mode 4: Beginner Onboarding 🎓
+
+**When**: New user needs guidance
+
+**Triggers**: "新手", "getting started", "如何开始", "常用命令", **"从0到1"**, **"全新项目"**
+
+**Process**:
+1. **Assess user background** - Ask clarifying questions if needed (coding experience? project type?)
+2. **⚠️ Identify project stage** - FROM-ZERO-TO-ONE vs FEATURE-ADDITION:
+   - **从0到1场景** (全新项目/产品/架构决策) → **MUST START with brainstorming workflow**
+   - **功能新增场景** (已有项目中添加功能) → Start with planning workflow
+3. **Design personalized learning path** based on their goals and stage
+4. **Curate essential commands** from `index/essential-commands.json` - Select 3-5 most relevant for their use case
+5. **Provide guided first example** - Walk through ONE complete workflow with explanation, **emphasizing brainstorming for 0-to-1 scenarios**
+6. **Set clear next steps** - What to try next, where to get help
+
+**Example 1 (从0到1)**: "我是新手，如何开始全新项目？" → Identify as FROM-ZERO-TO-ONE → Emphasize brainstorming workflow (`/workflow:brainstorm:artifacts`) as mandatory first step → Explain brainstorm → plan → execute flow
+
+**Example 2 (功能新增)**: "我是新手，如何在已有项目中添加功能？" → Identify as FEATURE-ADDITION → Guide to planning workflow (`/workflow:plan`) → Explain plan → execute → test flow
+
+**Example 3 (探索)**: "我是新手，如何开始？" → Ask clarifying question: "是全新项目启动（从0到1）还是在已有项目中添加功能？" → Based on answer, route to appropriate workflow
+
+---
+
+### Mode 5: Issue Reporting 📝
+
+**When**: User wants to report issue or request feature
+
+**Triggers**: **"CCW-issue"**, **"CCW-help"**, **"ccw-issue"**, **"ccw-help"**, **"ccw"**, "报告 bug", "功能建议", "问题咨询", "交互式诊断"
+
+**Process**:
+1. **Understand issue context** - Use AskUserQuestion to confirm type AND gather initial context
+2. **Intelligently guide information collection**:
+   - Adapt questions based on previous answers
+   - Skip irrelevant sections
+   - Probe for missing critical details
+3. **Select and customize template**:
+   - `issue-diagnosis.md`, `issue-bug.md`, `issue-feature.md`, or `issue-question.md`
+   - **Adapt template sections** to match user's specific scenario
+4. **Synthesize coherent issue report**:
+   - Integrate collected information with appropriate template sections
+   - **Highlight key details** - Don't bury critical info in boilerplate
+   - Add privacy-protected command history
+5. **Provide actionable next steps** - Immediate troubleshooting OR submission guidance
+
+**Example**: "CCW-issue" → Detect user frustration level → For urgent: fast-track to critical info collection; For exploratory: comprehensive diagnostic flow, NOT one-size-fits-all questionnaire
+
+**🆕 Enhanced Features**:
+- Complete command history with privacy protection
+- Interactive diagnostic checklists
+- Decision tree navigation (diagnosis template)
+- Execution environment capture
+
+---
+
+### Mode 6: Deep Command Analysis 🔬
+
+**When**: User asks detailed questions about specific commands or agents
+
+**Triggers**: "详细说明", "命令原理", "agent 如何工作", "实现细节", specific command/agent name mentioned
+
+**Data Sources**:
+- `reference/agents/*.md` - All agent documentation (11 agents)
+- `reference/commands/**/*.md` - All command documentation (69 commands)
+
+**Process**:
+
+**Simple Query** (direct documentation lookup):
+1. Identify target command/agent from user query
+2. Locate corresponding markdown file in `reference/`
+3. **Extract contextually relevant sections** - Not entire document
+4. **Synthesize focused explanation**:
+   - Address user's specific question
+   - Add context-appropriate examples
+   - Link related concepts
+5. **Offer progressive depth** - "Want to know more about X?"
+
+**Complex Query** (CLI-assisted analysis):
+1. **Detect complexity indicators** (多个命令对比、工作流程分析、最佳实践)
+2. **Design targeted analysis prompt** for gemini/qwen:
+   - Frame user's question precisely
+   - Specify required analysis depth
+   - Request structured comparison/synthesis
+   ```bash
+   gemini -p "
+   PURPOSE: Analyze command documentation to answer user query
+   TASK: [extracted user question with context]
+   MODE: analysis
+   CONTEXT: @**/*
+   EXPECTED: Comprehensive answer with examples and recommendations
+   RULES: $(cat ~/.claude/workflows/cli-templates/prompts/analysis/02-analyze-code-patterns.txt) | Focus on practical usage | analysis=READ-ONLY
+   " -m gemini-3-pro-preview-11-2025 --include-directories ~/.claude/skills/command-guide/reference
+   ```
+   Note: Use absolute path `~/.claude/skills/command-guide/reference` for reference documentation access
+3. **Process and integrate CLI analysis**:
+   - Extract key insights from CLI output
+   - Add context-specific examples
+   - Synthesize actionable recommendations
+4. **Deliver tailored response** - Not raw CLI output
+
+**Query Classification**:
+- **Simple**: Single command explanation, parameter list, basic usage
+- **Complex**: Cross-command workflows, performance comparison, architectural analysis, best practices across multiple commands
+
+**Examples**:
+
+*Simple Query*:
+```
+User: "action-planning-agent 如何工作？"
+→ Read reference/agents/action-planning-agent.md
+→ **Identify user's knowledge gap** (mechanism? inputs/outputs? when to use?)
+→ **Extract relevant sections** addressing their need
+→ **Synthesize focused explanation** with examples
+→ NOT: Dump entire agent documentation
+```
+
+*Complex Query*:
+```
+User: "对比 workflow:plan 和 workflow:tdd-plan 的使用场景和最佳实践"
+→ Detect: 多命令对比 + 最佳实践
+→ **Design comparison framework** (when to use, trade-offs, workflow integration)
+→ Use gemini to analyze both commands with structured comparison prompt
+→ **Synthesize insights** into decision matrix and usage guidelines
+→ NOT: Raw command documentation side-by-side
+```
+
+---
+
+## 📚 Index Files
+
+All command metadata is stored in JSON indexes for fast querying:
+
+- **all-commands.json** - Complete catalog (69 commands) with full metadata
+- **by-category.json** - Hierarchical organization (workflow/cli/memory/task)
+- **by-use-case.json** - Grouped by scenario (planning/implementation/testing/docs/session)
+- **essential-commands.json** - Top 14 most-used commands
+- **command-relationships.json** - Next-step recommendations and dependencies
+
+📖 Detailed structure: [Index Structure Reference](guides/index-structure.md)
+
+---
+
+## 🗂️ Supporting Guides
+
+- **[Getting Started](guides/getting-started.md)** - 5-minute quickstart for beginners
+- **[Workflow Patterns](guides/workflow-patterns.md)** - Common workflow examples (Plan→Execute, TDD, UI design)
+- **[CLI Tools Guide](guides/cli-tools-guide.md)** - Gemini/Qwen/Codex usage
+- **[Troubleshooting](guides/troubleshooting.md)** - Common issues and solutions
+- **[Implementation Details](guides/implementation-details.md)** - Detailed logic for each mode
+- **[Usage Examples](guides/examples.md)** - Example dialogues and edge cases
+
+## 📦 Reference Documentation
+
+Complete backup of all command and agent documentation for deep analysis:
+
+- **[reference/agents/](reference/agents/)** - 11 agent markdown files with implementation details
+- **[reference/commands/](reference/commands/)** - 69 command markdown files organized by category
+  - `cli/` - CLI tool commands (9 files)
+  - `memory/` - Memory management commands (8 files)
+  - `task/` - Task management commands (4 files)
+  - `workflow/` - Workflow commands (46 files)
+
+**Installation Path**: `~/.claude/skills/command-guide/` (skill designed for global installation)
+
+**Absolute Reference Path**: `~/.claude/skills/command-guide/reference/`
+
+**Usage**: Mode 6 queries these files directly for detailed command/agent analysis, or uses CLI tools (gemini/qwen) with absolute paths for complex cross-command analysis.
+
+---
+
+## 🛠️ Issue Templates
+
+Generate standardized GitHub issue templates with **execution flow emphasis**:
+
+- **[Interactive Diagnosis](templates/issue-diagnosis.md)** - 🆕 Comprehensive diagnostic workflow with decision tree, checklists, and full command history
+- **[Bug Report](templates/issue-bug.md)** - Report command errors with complete execution flow and environment details
+- **[Feature Request](templates/issue-feature.md)** - Suggest improvements with current workflow analysis and pain points
+- **[Question](templates/issue-question.md)** - Ask usage questions with detailed attempt history and context
+
+**All templates now include**:
+- ✅ Complete command history sections (with privacy protection)
+- ✅ Execution environment details
+- ✅ Interactive problem-locating checklists
+- ✅ Structured troubleshooting guidance
+
+Templates are auto-populated during Mode 5 (Issue Reporting) interaction.
+
+---
+
+## 📊 System Statistics
+
+- **Total Commands**: 69
+- **Total Agents**: 11
+- **Categories**: 4 (workflow: 46, cli: 9, memory: 8, task: 4, general: 2)
+- **Use Cases**: 5 (planning, implementation, testing, documentation, session-management)
+- **Difficulty Levels**: 3 (Beginner, Intermediate, Advanced)
+- **Essential Commands**: 14
+- **Reference Docs**: 80 markdown files (11 agents + 69 commands)
+
+---
+
+## 🔧 Maintenance
+
+### Updating Indexes
+
+When commands are added/modified/removed:
+
+```bash
+bash scripts/update-index.sh
+```
+
+This script:
+1. Scans all command files in `../../commands/`
+2. Extracts metadata from YAML frontmatter
+3. Analyzes command relationships
+4. Regenerates all 5 index files
+
+### Committing Updates
+
+```bash
+git add .claude/skills/command-guide/index/
+git commit -m "docs: update command indexes"
+git push
+```
+
+Team members get latest indexes via `git pull`.
+
+---
+
+## 📖 Related Documentation
+
+- [Workflow Architecture](../../workflows/workflow-architecture.md) - System design overview
+- [Intelligent Tools Strategy](../../workflows/intelligent-tools-strategy.md) - CLI tool selection
+- [Context Search Strategy](../../workflows/context-search-strategy.md) - Search patterns
+- [Task Core](../../workflows/task-core.md) - Task system fundamentals
+
+---
+
+**Version**: 1.3.1 (Path configuration for global installation)
+**Last Updated**: 2025-11-06
+**Maintainer**: Claude DMS3 Team
+
+**Changelog v1.3.1**:
+- ✅ Updated all paths to use absolute paths (`~/.claude/skills/command-guide/`)
+- ✅ CLI commands now use `--include-directories` with absolute reference path
+- ✅ Ensures skill works correctly when installed in `~/.claude/skills/`
+
+**Changelog v1.3.0**:
+- ✅ Added Mode 6: Deep Command Analysis with CLI-assisted queries
+- ✅ Created reference documentation backup (80 files: 11 agents + 69 commands)
+- ✅ Support simple queries (direct file lookup) and complex queries (CLI analysis)
+- ✅ Integrated gemini/qwen for cross-command analysis and best practices
+
+**Changelog v1.2.0**:
+- ✅ Added Interactive Diagnosis template with decision tree
+- ✅ Enhanced all templates with complete command history sections
+- ✅ Added privacy protection guidelines for sensitive information
+- ✅ Integrated execution flow emphasis across all issue templates

.claude/skills/command-guide/guides/cli-tools-guide.md

@@ -0,0 +1,410 @@
+# CLI 工具使用指南
+
+> **SKILL 参考文档**：用于回答用户关于 CLI 工具（Gemini、Qwen、Codex）的使用问题
+>
+> **用途**：当用户询问 CLI 工具的能力、使用方法、调用方式时，从本文档中提取相关信息，根据用户具体需求加工后返回
+
+## 🎯 快速理解：CLI 工具是什么？
+
+CLI 工具是集成在 Claude DMS3 中的**智能分析和执行助手**。
+
+**工作流程**：
+1. **用户** → 用自然语言向 Claude Code 描述需求（如"分析认证模块的安全性"）
+2. **Claude Code** → 识别用户意图，决定使用哪种方式：
+   - **CLI 工具语义调用**：生成并执行 `gemini`/`qwen`/`codex` 命令
+   - **Slash 命令调用**：执行预定义的工作流命令（如 `/workflow:plan`）
+3. **工具** → 自动完成任务并返回结果
+
+**核心理念**：用户用自然语言描述需求 → Claude Code 选择最佳方式 → 工具执行 → 返回结果
+
+---
+
+## 📋 三大工具能力对比
+
+| 工具 | 擅长领域 | 典型场景 | 何时使用 |
+|------|----------|----------|----------|
+| **Gemini** | 分析、理解、规划 | 代码分析、架构设计、问题诊断 | 需要深入理解代码或系统 |
+| **Qwen** | 分析、备选方案 | 代码审查、模式识别 | Gemini 不可用时的备选 |
+| **Codex** | 实现、测试、执行 | 功能开发、测试生成、自动化任务 | 需要生成代码或自动执行 |
+
+**简单记忆**：
+- 想**理解**什么 → Gemini / Qwen
+- 想**实现**什么 → Codex
+
+---
+
+## 🚀 Claude Code 的两种响应方式
+
+当用户用自然语言描述需求时，Claude Code 会根据任务特性选择最佳方式：
+
+### 方式 1：CLI 工具语义调用（灵活、强大）
+
+**用户明确指示使用 CLI 工具**，Claude Code 生成并执行相应命令。
+
+#### 示例 1：Gemini 语义分析
+
+**用户输入**（必须明确提到工具）：
+```
+使用 gemini 分析认证模块的安全性，识别潜在的安全漏洞，
+关注 JWT 令牌处理、密码存储、会话管理等方面，
+提供具体的修复建议
+```
+
+**Claude Code 生成并执行**（CLI 命令）：
+```bash
+cd src/auth && gemini -p "
+分析认证模块的安全性，识别潜在的安全漏洞，
+关注 JWT 令牌处理、密码存储、会话管理等方面，
+提供具体的修复建议
+" -m gemini-3-pro-preview-11-2025
+```
+
+**工具输出**：Gemini 自动理解任务，组合多个分析步骤，返回结构化报告
+
+---
+
+#### 示例 2：Qwen 语义分析（Gemini 的备选）
+
+**用户输入**：
+```
+用 qwen 追踪用户登录的完整执行流程，
+从 API 入口到数据库查询，
+列出所有调用的函数和依赖关系
+```
+
+**Claude Code 生成并执行**：
+```bash
+cd src/auth && qwen -p "
+追踪用户登录的完整执行流程，
+从 API 入口到数据库查询，
+列出所有调用的函数和依赖关系
+" -m coder-model
+```
+
+**工具输出**：Qwen 理解需求，自动追踪执行路径
+
+---
+
+#### 示例 3：Codex 语义实现
+
+**用户输入**：
+```
+让 codex 实现 JWT 令牌刷新机制：
+1. 添加 refreshToken 端点
+2. 验证旧令牌的有效性
+3. 生成新的访问令牌
+4. 确保安全性（防重放攻击）
+```
+
+**Claude Code 生成并执行**：
+```bash
+codex -C src/auth --full-auto exec "
+实现 JWT 令牌刷新机制：
+1. 添加 refreshToken 端点
+2. 验证旧令牌的有效性
+3. 生成新的访问令牌
+4. 确保安全性（防重放攻击）
+" -m gpt-5 --skip-git-repo-check -s danger-full-access
+```
+
+**工具输出**：Codex 理解需求，自动生成代码并集成到现有系统
+
+---
+
+**核心特点**：
+- ✅ **用户明确指定工具**：必须说"使用 gemini"、"用 qwen"、"让 codex"等触发工具调用
+- ✅ **Claude 生成命令**：识别工具名称后，自动构造最优的 CLI 工具调用
+- ✅ **工具自动理解**：CLI 工具解析需求，组合分析/实现步骤
+- ✅ **灵活强大**：不受预定义工作流限制
+- ✅ **精确控制**：Claude 可指定工作目录、文件范围、模型参数
+
+**触发方式**：
+- "使用 gemini ..."
+- "用 qwen ..."
+- "让 codex ..."
+- "通过 gemini 工具..."
+
+**Claude Code 何时选择此方式**：
+- 用户明确指定使用某个 CLI 工具
+- 复杂分析任务（跨模块、多维度）
+- 自定义工作流需求
+- 需要精确控制上下文范围
+
+---
+
+### 方式 2：Slash 命令调用（标准工作流）
+
+**用户直接输入 Slash 命令**，或 **Claude Code 建议使用 Slash 命令**，系统执行预定义工作流（内部调用 CLI 工具）。
+
+#### Workflow 类命令（系统自动选择工具）
+
+**示例 1：规划任务**
+
+**用户输入**：
+```
+/workflow:plan --agent "实现用户认证功能"
+```
+
+**系统执行**：内部调用 gemini/qwen 分析 + action-planning-agent 生成任务
+
+---
+
+**示例 2：执行任务**
+
+**用户输入**：
+```
+/workflow:execute
+```
+
+**系统执行**：内部调用 codex 实现代码
+
+---
+
+**示例 3：生成测试**
+
+**用户输入**：
+```
+/workflow:test-gen WFS-xxx
+```
+
+**系统执行**：内部调用 gemini 分析 + codex 生成测试
+
+---
+
+#### CLI 类命令（指定工具）
+
+**示例 1：封装的分析命令**
+
+**用户输入**：
+```
+/cli:analyze --tool gemini "分析认证模块"
+```
+
+**系统执行**：使用 gemini 工具进行分析
+
+---
+
+**示例 2：封装的执行命令**
+
+**用户输入**：
+```
+/cli:execute --tool codex "实现 JWT 刷新"
+```
+
+**系统执行**：使用 codex 工具实现功能
+
+---
+
+**示例 3：快速执行（YOLO 模式）**
+
+**用户输入**：
+```
+/cli:codex-execute "添加用户头像上传"
+```
+
+**系统执行**：使用 codex 快速实现
+
+---
+
+**核心特点**：
+- ✅ **用户可直接输入**：Slash 命令格式固定，用户可以直接输入（如 `/workflow:plan`）
+- ✅ **Claude 可建议**：Claude Code 也可以识别需求后建议或执行 Slash 命令
+- ✅ **预定义流程**：标准化的工作流模板
+- ✅ **自动工具选择**：workflow 命令内部自动选择合适的 CLI 工具
+- ✅ **集成完整**：包含规划、执行、测试、文档等环节
+- ✅ **简单易用**：无需了解底层 CLI 工具细节
+
+**Claude Code 何时选择此方式**：
+- 标准开发任务（功能开发、测试、重构）
+- 团队协作（统一工作流）
+- 适合新手（降低学习曲线）
+- 快速开发（减少配置时间）
+
+---
+
+## 🔄 两种方式对比
+
+| 维度 | CLI 工具语义调用 | Slash 命令调用 |
+|------|------------------|----------------|
+| **用户输入** | 纯自然语言描述需求 | `/` 开头的固定命令格式 |
+| **Claude Code 行为** | 生成并执行 `gemini`/`qwen`/`codex` 命令 | 执行预定义工作流（内部调用 CLI 工具） |
+| **灵活性** | 完全自定义任务和执行方式 | 固定工作流模板 |
+| **学习曲线** | 用户无需学习（纯自然语言） | 需要知道 Slash 命令名称 |
+| **适用复杂度** | 复杂、探索性、定制化任务 | 标准、重复性、工作流化任务 |
+| **工具选择** | Claude 自动选择最佳 CLI 工具 | 系统自动选择（workflow 类）<br>或用户指定（cli 类） |
+| **典型场景** | 深度分析、自定义流程、探索研究 | 日常开发、团队协作、标准流程 |
+
+**使用建议**：
+- **日常开发** → 优先使用 Slash 命令（标准化、快速）
+- **复杂分析** → Claude 自动选择 CLI 工具语义调用（灵活、强大）
+- **用户角度** → 只需用自然语言描述需求，Claude Code 会选择最佳方式
+
+---
+
+## 💡 工具能力速查
+
+### Gemini - 分析与规划
+- 执行流程追踪、依赖分析、代码模式识别
+- 架构设计、技术方案评估、任务分解
+- 文档生成（API 文档、模块说明）
+
+**触发示例**：`使用 gemini 追踪用户登录的完整流程`
+
+---
+
+### Qwen - Gemini 的备选
+- 代码分析、模式识别、架构评审
+- 作为 Gemini 不可用时的备选方案
+
+**触发示例**：`用 qwen 分析数据处理模块`
+
+---
+
+### Codex - 实现与执行
+- 功能开发、组件实现、API 创建
+- 单元测试、集成测试、TDD 支持
+- 代码重构、性能改进、Bug 修复
+
+**触发示例**：`让 codex 实现用户注册功能，包含邮箱验证`
+
+---
+
+## 🔄 典型使用场景
+
+### 场景 1：理解陌生代码库
+
+**需求**：接手新项目，需要快速理解代码结构
+
+**方式 1：CLI 工具语义调用**（推荐，灵活）
+
+- **用户输入**：`使用 gemini 分析这个项目的架构设计，识别主要模块、依赖关系和架构模式`
+- **Claude Code 生成并执行**：`cd project-root && gemini -p "..." -m gemini-3-pro-preview-11-2025`
+
+**方式 2：Slash 命令**
+- **用户输入**：`/cli:analyze --tool gemini "分析项目架构"`
+
+---
+
+### 场景 2：实现新功能
+
+**需求**：实现用户认证功能
+
+**方式 1：CLI 工具语义调用**
+- **用户输入**：`让 codex 实现用户认证功能：注册（邮箱+密码+验证）、登录（JWT token）、刷新令牌，技术栈 Node.js + Express`
+- **Claude Code 生成并执行**：`codex -C src/auth --full-auto exec "..." -m gpt-5 --skip-git-repo-check -s danger-full-access`
+
+**方式 2：Slash 命令**（工作流化）
+- **用户输入**：`/workflow:plan --agent "实现用户认证功能"` → `/workflow:execute`
+
+---
+
+### 场景 3：诊断 Bug
+
+**需求**：登录功能偶尔超时
+
+**方式 1：CLI 工具语义调用**
+- **用户输入**：`使用 gemini 诊断登录超时问题，分析处理流程、性能瓶颈、数据库查询效率`
+- **Claude Code 生成并执行**：`cd src/auth && gemini -p "..." -m gemini-3-pro-preview-11-2025`
+- **用户输入**：`让 codex 根据上述分析修复登录超时，优化查询、添加缓存`
+- **Claude Code 生成并执行**：`codex -C src/auth --full-auto exec "..." -m gpt-5 --skip-git-repo-check -s danger-full-access`
+
+**方式 2：Slash 命令**
+- **用户输入**：`/cli:mode:bug-diagnosis --tool gemini "诊断登录超时"` → `/cli:execute --tool codex "修复登录超时"`
+
+---
+
+### 场景 4：生成文档
+
+**需求**：为 API 模块生成完整文档
+
+**方式 1：CLI 工具语义调用**
+- **用户输入**：`使用 gemini 为 API 模块生成技术文档，包含端点说明、数据模型、使用示例`
+- **Claude Code 生成并执行**：`cd src/api && gemini -p "..." -m gemini-3-pro-preview-11-2025 --approval-mode yolo`
+
+**方式 2：Slash 命令**
+- **用户输入**：`/memory:docs src/api --tool gemini --mode full`
+
+---
+
+## 🎯 常用工作流程
+
+### 简单 Bug 修复
+```
+使用 gemini 诊断问题（可选其他 cli 工具）
+→ Claude 分析
+→ Claude 直接执行修复
+```
+
+### 复杂 Bug 修复
+```
+/cli:mode:plan 或 /cli:mode:bug-diagnosis
+→ Claude 分析
+→ Claude 执行修复
+```
+
+### 简单功能增加
+```
+/cli:mode:plan
+→ Claude 执行
+```
+
+### 复杂功能增加
+```
+/cli:mode:plan --agent
+→ Claude 执行 或 /cli:codex-execute
+
+或
+
+/cli:mode:plan
+→ 进入工作流模式（/workflow:execute）
+```
+
+### 项目内存管理
+
+**建立技术栈文档**（为项目提供技术参考）
+```
+/memory:tech-research [session-id | tech-stack-name]
+```
+
+**为项目重建多级结构的 CLAUDE.md 内存**
+```
+/memory:docs [path] [--tool gemini|qwen|codex] [--mode full|partial]
+```
+
+---
+
+## 📚 常用命令速查
+
+| 需求 | 推荐命令 |
+|------|----------|
+| **代码分析** | `使用 gemini 分析...` 或 `/cli:analyze --tool gemini` |
+| **Bug 诊断** | `/cli:mode:bug-diagnosis` |
+| **功能实现** | `/cli:codex-execute` 或 `让 codex 实现...` |
+| **架构规划** | `/cli:mode:plan` |
+| **生成测试** | `/workflow:test-gen WFS-xxx` |
+| **完整工作流** | `/workflow:plan` → `/workflow:execute` |
+| **技术文档** | `/memory:tech-research [tech-name]` |
+| **项目文档** | `/memory:docs [path]` |
+
+---
+
+## 🆘 快速提示
+
+**触发 CLI 工具语义调用**：
+- "使用 gemini ..."
+- "用 qwen ..."
+- "让 codex ..."
+
+**选择工具**：
+- **理解/分析/规划** → Gemini
+- **实现/测试/执行** → Codex
+- **不确定** → 使用 Slash 命令让系统选择
+
+**提升质量**：
+- 清晰描述需求和期望
+- 提供上下文信息
+- 使用 `--agent` 处理复杂任务
+
+---
+
+**最后更新**: 2025-11-06

.claude/skills/command-guide/guides/examples.md

@@ -0,0 +1,537 @@
+# Usage Examples
+
+Comprehensive examples of command-guide skill in action across all 5 operation modes.
+
+---
+
+## Mode 1: Command Search 🔍
+
+### Example 1: Keyword Search
+
+**User**: "搜索包含 'execute' 的命令"
+
+**Skill Response**:
+```
+找到 4 个相关命令：
+
+1. **cli:execute** (高级)
+   描述: Auto-execution of implementation tasks with YOLO permissions
+   参数: [--agent] [--tool codex|gemini|qwen] [--enhance] description or task-id
+   场景: implementation
+
+2. **task:execute** (中级)
+   描述: Execute tasks with appropriate agents and context-aware orchestration
+   参数: task-id
+   场景: implementation
+
+3. **workflow:execute** (中级)
+   描述: Coordinate agents for existing workflow tasks with automatic discovery
+   参数: [--resume-session="session-id"]
+   场景: implementation
+
+4. **codex-execute** (高级)
+   描述: Automated task decomposition and execution with Codex
+   参数: task description or task-id
+   场景: implementation
+
+💡 相关命令: workflow:plan, task:create
+📖 详细文档: [Implementation Commands](workflow-patterns.md#implementation)
+```
+
+---
+
+### Example 2: Category Search
+
+**User**: "cli 类别下有哪些命令？"
+
+**Skill Response**:
+```
+CLI 类别包含 9 个命令：
+
+**核心命令** (6个):
+- cli:analyze - Quick codebase analysis
+- cli:chat - Direct codebase interaction
+- cli:execute - Auto-execution with YOLO
+- cli:cli-init - Initialize CLI tool configs
+- cli:codex-execute - Codex-powered execution
+- cli:discuss-plan - Multi-model planning discussion
+
+**模式命令** (3个):
+- cli:mode:plan - Project planning mode
+- cli:mode:code-analysis - Deep code analysis mode
+- cli:mode:bug-diagnosis - Bug diagnosis mode
+
+📚 使用指南: [CLI Tools Guide](cli-tools-guide.md)
+```
+
+---
+
+### Example 3: Use-Case Search
+
+**User**: "planning 相关的命令有哪些？"
+
+**Skill Response**:
+```
+Planning 场景包含 8 个命令：
+
+**核心规划**:
+1. workflow:plan (高级) - 5阶段规划工作流
+2. cli:mode:plan (高级) - 项目规划和架构分析
+3. workflow:tdd-plan (高级) - TDD 规划工作流
+
+**任务分解**:
+4. task:breakdown (中级) - 智能任务分解
+5. workflow:tools:task-generate (中级) - 生成任务 JSON
+
+**架构设计**:
+6. workflow:brainstorm:system-architect (中级) - 系统架构师头脑风暴
+7. workflow:brainstorm:api-designer (中级) - API 设计师头脑风暴
+
+**评估验证**:
+8. workflow:action-plan-verify (中级) - 规划质量验证
+
+💡 常见工作流: Plan → Verify → Execute
+📖 模式参考: [Workflow Patterns](workflow-patterns.md#planning-workflow)
+```
+
+---
+
+## Mode 2: Smart Recommendations 🤖
+
+### Example 1: After Planning
+
+**User**: "执行完 /workflow:plan 后下一步做什么？"
+
+**Skill Response**:
+```
+推荐的后续步骤：
+
+**🎯 主要选择**:
+1. **/workflow:execute** - 开始执行规划的任务
+   ✅ 这是最常见的下一步
+   作用: 实际执行 workflow:plan 生成的任务
+
+**📋 可选步骤**:
+2. **/workflow:action-plan-verify** - 验证规划质量
+   作用: 在执行前检查规划的一致性和完整性
+   建议: 重要项目建议先验证
+
+3. **/workflow:status** - 查看规划状态
+   作用: 查看生成的任务和当前进度
+
+**📚 完整工作流模式**:
+Plan → Verify (可选) → Execute → Review
+
+详见: [Planning Workflow Pattern](workflow-patterns.md#planning-execution)
+```
+
+---
+
+### Example 2: After Execution
+
+**User**: "workflow:execute 执行完成后，推荐做什么？"
+
+**Skill Response**:
+```
+推荐的后续步骤：
+
+**🎯 主要选择**:
+1. **/workflow:review** - 审查实现结果
+   ✅ 检查代码质量、安全性、架构
+   参数: [--type=quality|security|architecture]
+
+**📊 可选步骤**:
+2. **/workflow:status** - 查看执行状态
+   作用: 确认所有任务都已完成
+
+3. **/workflow:test-gen** - 生成测试
+   作用: 为实现的功能创建测试用例
+
+4. **/workflow:session:complete** - 完成会话
+   作用: 标记工作流已完成，归档经验
+
+**🔄 如果需要修改**:
+- /task:replan - 重新规划某个任务
+- /workflow:resume - 恢复工作流
+
+详见: [Execution Review Pattern](workflow-patterns.md#execution-review)
+```
+
+---
+
+## Mode 3: Full Documentation 📖
+
+### Example 1: Command Parameters
+
+**User**: "/workflow:plan 的参数是什么？"
+
+**Skill Response**:
+```
+# workflow:plan
+
+**描述**: Orchestrate 5-phase planning workflow with quality gate, executing commands and passing context between phases
+
+**参数**:
+```bash
+/workflow:plan [--agent] [--cli-execute] "text description"|file.md
+```
+
+**参数说明**:
+- `--agent` (可选): 使用 agent 模式执行规划
+- `--cli-execute` (可选): 允许在规划阶段执行 CLI 命令
+- `"text description"`: 任务描述文本
+- `file.md`: 或者提供任务描述文件路径
+
+**使用场景**: planning
+**难度级别**: 高级
+
+**使用示例**:
+```bash
+# 基本用法
+/workflow:plan "实现用户认证功能"
+
+# 使用 agent 模式
+/workflow:plan --agent "重构支付模块"
+
+# 从文件读取
+/workflow:plan --agent feature-spec.md
+
+# 允许 CLI 执行
+/workflow:plan --cli-execute "添加搜索功能"
+```
+
+**执行流程**:
+1. 上下文收集
+2. 概念规划
+3. 实现规划
+4. 任务生成
+5. 质量验证
+
+**相关命令**:
+- workflow:execute - 执行规划的任务
+- workflow:action-plan-verify - 验证规划质量
+- workflow:status - 查看规划状态
+
+**详细文档**: ../../commands/workflow/plan.md
+```
+
+---
+
+## Mode 4: Beginner Onboarding 🎓
+
+### Example 1: Complete Beginner
+
+**User**: "我是新手，如何开始使用工作流系统？"
+
+**Skill Response**:
+```
+欢迎使用 Claude DMS3 工作流系统！🎉
+
+## 🚀 快速开始（3 步）
+
+### Step 1: 了解核心命令（Top 5）
+
+1. **/workflow:plan** - 规划一个功能或任务
+   用法: /workflow:plan "你想做的事情"
+
+2. **/workflow:execute** - 执行规划的任务
+   用法: /workflow:execute
+
+3. **/cli:execute** - 快速自动执行
+   用法: /cli:execute "实现XXX功能"
+
+4. **/task:create** - 创建单个任务
+   用法: /task:create "任务标题"
+
+5. **/enhance-prompt** - 优化你的提示词
+   用法: /enhance-prompt "你的想法"
+
+### Step 2: 尝试第一个工作流
+
+```bash
+# 1. 规划一个简单功能
+/workflow:plan "添加用户登录功能"
+
+# 2. 执行规划
+/workflow:execute
+
+# 3. 审查结果
+/workflow:review
+```
+
+### Step 3: 学习资源
+
+📖 **必读指南**:
+- [5分钟快速开始](getting-started.md)
+- [常见工作流模式](workflow-patterns.md)
+
+🛠️ **工具指南**:
+- [CLI 工具使用](cli-tools-guide.md)
+- [问题排查](troubleshooting.md)
+
+💡 **下一步建议**:
+1. 阅读 getting-started.md（5分钟）
+2. 尝试上面的第一个工作流
+3. 探索更多命令: 询问 "常用命令有哪些"
+
+有问题随时问 "CCW-help"！
+```
+
+---
+
+### Example 2: Intermediate User
+
+**User**: "常用命令有哪些？"
+
+**Skill Response**:
+```
+## 核心命令列表（Top 14）
+
+### 🎯 工作流管理 (5个)
+1. workflow:plan - 5阶段规划
+2. workflow:execute - 执行任务
+3. workflow:review - 审查实现
+4. workflow:tdd-plan - TDD 规划
+5. workflow:test-gen - 生成测试
+
+### 🛠️ CLI 工具 (3个)
+6. cli:execute - 自动执行
+7. cli:mode:plan - 规划模式
+8. cli:analyze - 代码分析
+
+### 📋 任务管理 (3个)
+9. task:create - 创建任务
+10. task:execute - 执行任务
+11. task:breakdown - 分解任务
+
+### 🔧 实用工具 (2个)
+12. enhance-prompt - 提示词增强
+13. version - 版本信息
+
+### 💡 使用频率
+- **每天**: workflow:plan, workflow:execute, cli:execute
+- **经常**: task:create, enhance-prompt
+- **按需**: workflow:review, test-gen, tdd-plan
+
+📚 详细文档: [Index Structure](index-structure.md#essential-commands)
+```
+
+---
+
+## Mode 5: Issue Reporting 📝
+
+### Example 1: Bug Report
+
+**User**: "CCW-issue"
+
+**Skill (Interactive)**:
+```
+请选择问题类型：
+1. 🐛 Bug 报告
+2. ✨ 功能请求
+3. ❓ 问题咨询
+```
+
+**User**: "1"
+
+**Skill**:
+```
+好的，我将帮您创建 Bug 报告。请回答以下问题：
+
+1. 简要描述问题：
+```
+
+**User**: "/workflow:plan 执行后没有生成任务文件"
+
+**Skill**:
+```
+2. 您执行的完整命令是什么？
+```
+
+**User**: "/workflow:plan '添加登录功能'"
+
+**Skill**:
+```
+3. 期望的结果是什么？
+```
+
+**User**: "应该在 .workflow/ 目录生成 task.json"
+
+**Skill**:
+```
+4. 实际发生了什么？
+```
+
+**User**: "命令执行了但没有生成文件"
+
+**Skill**:
+```
+✅ Bug 报告已生成！
+
+文件路径: templates/.generated/bug-2025-01-06-123456.md
+
+--- 报告内容 ---
+# Bug 报告
+
+## 问题描述
+/workflow:plan 执行后没有生成任务文件
+
+## 执行的命令
+```bash
+/workflow:plan '添加登录功能'
+```
+
+## 期望行为
+应该在 .workflow/ 目录生成 task.json
+
+## 实际行为
+命令执行了但没有生成文件
+
+## 环境信息
+- 操作系统: Windows
+- 报告日期: 2025-01-06
+- 相关命令: /workflow:plan
+
+---
+
+**下一步操作**:
+1. 复制以上内容到 GitHub Issues
+2. 或使用: gh issue create -F templates/.generated/bug-2025-01-06-123456.md
+
+需要更多帮助？使用 "CCW-help"
+```
+
+---
+
+### Example 2: Feature Request
+
+**User**: "我想提个功能建议"
+
+**Skill (Interactive)**:
+```
+请选择问题类型：
+1. 🐛 Bug 报告
+2. ✨ 功能请求
+3. ❓ 问题咨询
+```
+
+**User**: "2"
+
+**Skill**:
+```
+好的，功能请求。请描述：
+
+1. 您希望添加什么功能？
+```
+
+**User**: "希望 /workflow:plan 能自动估算任务时间"
+
+**Skill**:
+```
+2. 这个功能解决什么问题？
+```
+
+**User**: "帮助更好地规划项目进度和资源分配"
+
+**Skill**:
+```
+3. 具体的使用场景是什么？（可选）
+```
+
+**User**: "规划大型项目时，能看到预计完成时间"
+
+**Skill**:
+```
+✅ 功能请求已生成！
+
+文件路径: templates/.generated/feature-2025-01-06-123457.md
+
+--- 内容预览 ---
+# 功能请求
+
+## 功能概述
+希望 /workflow:plan 能自动估算任务时间
+
+## 问题背景
+帮助更好地规划项目进度和资源分配
+
+## 使用场景
+规划大型项目时，能看到预计完成时间
+
+## 优先级
+- [ ] 高 - 严重影响工作效率
+- [x] 中 - 有明显改善但有变通方案
+- [ ] 低 - 锦上添花
+
+---
+
+可以复制到 GitHub 提交，或使用:
+gh issue create -F templates/.generated/feature-2025-01-06-123457.md
+```
+
+---
+
+## Edge Cases & Error Handling
+
+### Case 1: No Results Found
+
+**User**: "搜索 xyz 命令"
+
+**Skill**:
+```
+❌ 未找到包含 "xyz" 的命令
+
+💡 建议：
+1. 尝试更广泛的关键词（如 "plan", "execute", "test"）
+2. 按类别浏览：workflow, cli, memory, task
+3. 查看所有常用命令：询问 "常用命令"
+4. 需要帮助：使用 "CCW-help"
+
+📚 快速参考：[All Commands Index](index-structure.md#all-commands)
+```
+
+---
+
+### Case 2: Ambiguous Query
+
+**User**: "命令"
+
+**Skill**:
+```
+您想了解什么？请选择：
+
+1. 🔍 搜索特定命令
+2. 🤖 获取命令推荐
+3. 📖 查看命令文档
+4. 🎓 新手入门指导
+5. 📝 报告问题或建议
+
+或者直接说出具体需求，例如：
+- "搜索 planning 命令"
+- "执行完 /workflow:plan 下一步做什么"
+- "/task:create 怎么用"
+```
+
+---
+
+### Case 3: Multiple Matches
+
+**User**: "execute 命令"
+
+**Skill**:
+```
+找到多个相关命令，请选择您需要的：
+
+1. **cli:execute** - CLI 自动执行（推荐新手）
+2. **task:execute** - 执行单个任务
+3. **workflow:execute** - 执行整个工作流
+
+或者询问：
+- "cli:execute 的详细文档"
+- "三者有什么区别"
+- "我该用哪个"
+```
+
+---
+
+**Last Updated**: 2025-01-06

.claude/skills/command-guide/guides/getting-started.md

@@ -0,0 +1,242 @@
+# 5分钟快速上手指南
+
+> 欢迎使用 Claude DMS3！本指南将帮助您快速上手，5分钟内开始第一个工作流。
+
+## 🎯 Claude DMS3 是什么？
+
+Claude DMS3 是一个**智能开发管理系统**，集成了 69 个命令，帮助您：
+- 📋 规划和分解复杂任务
+- ⚡ 自动化代码实现
+- 🧪 生成和执行测试
+- 📚 生成项目文档
+- 🤖 使用 AI 工具（Gemini、Qwen、Codex）加速开发
+
+**核心理念**：用自然语言描述需求 → 系统自动规划和执行 → 获得结果
+
+---
+
+## 🚀 最常用的14个命令
+
+### 工作流类（必会）
+
+| 命令 | 用途 | 何时使用 |
+|------|------|----------|
+| `/workflow:plan` | 规划任务 | 开始新功能、新项目 |
+| `/workflow:execute` | 执行任务 | plan 之后，实现功能 |
+| `/workflow:test-gen` | 生成测试 | 实现完成后，生成测试 |
+| `/workflow:status` | 查看进度 | 查看工作流状态 |
+| `/workflow:resume` | 恢复任务 | 继续之前的工作流 |
+
+### CLI 工具类（常用）
+
+| 命令 | 用途 | 何时使用 |
+|------|------|----------|
+| `/cli:analyze` | 代码分析 | 理解代码、分析架构 |
+| `/cli:execute` | 执行实现 | 精确控制实现过程 |
+| `/cli:codex-execute` | 自动化实现 | 快速实现功能 |
+| `/cli:chat` | 问答交互 | 询问代码库问题 |
+
+### Memory 类（知识管理）
+
+| 命令 | 用途 | 何时使用 |
+|------|------|----------|
+| `/memory:docs` | 生成文档 | 生成模块文档 |
+| `/memory:load` | 加载上下文 | 获取任务相关上下文 |
+
+### Task 类（任务管理）
+
+| 命令 | 用途 | 何时使用 |
+|------|------|----------|
+| `/task:create` | 创建任务 | 手动创建单个任务 |
+| `/task:execute` | 执行任务 | 执行特定任务 |
+
+---
+
+## 📝 第一个工作流：实现一个新功能
+
+让我们通过一个实际例子来体验完整的工作流：**实现用户登录功能**
+
+### 步骤 1：规划任务
+
+```bash
+/workflow:plan --agent "实现用户登录功能，包括邮箱密码验证和JWT令牌"
+```
+
+**发生什么**：
+- 系统分析需求
+- 自动生成任务计划（IMPL_PLAN.md）
+- 创建多个子任务（task JSON 文件）
+- 返回 workflow session ID（如 WFS-20251106-xxx）
+
+**你会看到**：
+- ✅ 规划完成
+- 📋 任务列表（如：task-001-user-model, task-002-login-api 等）
+- 📁 Session 目录创建
+
+---
+
+### 步骤 2：执行实现
+
+```bash
+/workflow:execute
+```
+
+**发生什么**：
+- 系统自动发现最新的 workflow session
+- 按顺序执行所有任务
+- 使用 Codex 自动生成代码
+- 实时显示进度
+
+**你会看到**：
+- ⏳ Task 1 执行中...
+- ✅ Task 1 完成
+- ⏳ Task 2 执行中...
+- （依次执行所有任务）
+
+---
+
+### 步骤 3：生成测试
+
+```bash
+/workflow:test-gen WFS-20251106-xxx
+```
+
+**发生什么**：
+- 分析实现的代码
+- 生成测试策略
+- 创建测试任务
+
+---
+
+### 步骤 4：查看状态
+
+```bash
+/workflow:status
+```
+
+**发生什么**：
+- 显示当前工作流状态
+- 列出所有任务及其状态
+- 显示已完成/进行中/待执行任务
+
+---
+
+## 🎓 其他常用场景
+
+### 场景 1：快速代码分析
+
+**需求**：理解陌生代码
+
+```bash
+# 分析整体架构
+/cli:analyze --tool gemini "分析项目架构和模块关系"
+
+# 追踪执行流程
+/cli:mode:code-analysis --tool gemini "追踪用户注册的执行流程"
+```
+
+---
+
+### 场景 2：快速实现功能
+
+**需求**：实现一个简单功能
+
+```bash
+# 方式 1：完整工作流（推荐）
+/workflow:plan "添加用户头像上传功能"
+/workflow:execute
+
+# 方式 2：直接实现（快速）
+/cli:codex-execute "添加用户头像上传功能，支持图片裁剪和压缩"
+```
+
+---
+
+### 场景 3：恢复之前的工作
+
+**需求**：继续上次的任务
+
+```bash
+# 查看可恢复的 session
+/workflow:status
+
+# 恢复特定 session
+/workflow:resume WFS-20251106-xxx
+```
+
+---
+
+### 场景 4：生成文档
+
+**需求**：为模块生成文档
+
+```bash
+/memory:docs src/auth --tool gemini --mode full
+```
+
+---
+
+## 💡 快速记忆法
+
+记住这个流程，就能完成大部分任务：
+
+```
+规划 → 执行 → 测试 → 完成
+  ↓      ↓      ↓
+plan → execute → test-gen
+```
+
+**扩展场景**：
+- 需要分析理解 → 使用 `/cli:analyze`
+- 需要精确控制 → 使用 `/cli:execute`
+- 需要快速实现 → 使用 `/cli:codex-execute`
+
+---
+
+## 🆘 遇到问题？
+
+### 命令记不住？
+
+使用 Command Guide SKILL：
+```bash
+ccw  # 或 ccw-help
+```
+
+然后说：
+- "搜索 planning 命令"
+- "执行完 /workflow:plan 后做什么"
+- "我是新手，如何开始"
+
+---
+
+### 执行失败？
+
+1. **查看错误信息**：仔细阅读错误提示
+2. **使用诊断模板**：`ccw-issue` → 选择 "诊断模板"
+3. **查看排查指南**：[Troubleshooting Guide](troubleshooting.md)
+
+---
+
+### 想深入学习？
+
+- **工作流模式**：[Workflow Patterns](workflow-patterns.md) - 学习更多工作流组合
+- **CLI 工具使用**：[CLI Tools Guide](cli-tools-guide.md) - 了解 Gemini/Qwen/Codex 的高级用法
+- **完整命令列表**：查看 `index/essential-commands.json`
+
+---
+
+## 🎯 下一步
+
+现在你已经掌握了基础！尝试：
+
+1. **实践基础工作流**：选择一个小功能，走一遍 plan → execute → test-gen 流程
+2. **探索 CLI 工具**：尝试用 `/cli:analyze` 分析你的代码库
+3. **学习工作流模式**：阅读 [Workflow Patterns](workflow-patterns.md) 了解更多高级用法
+
+**记住**：Claude DMS3 的设计理念是让你用自然语言描述需求，系统自动完成繁琐的工作。不要担心命令记不住，随时可以使用 `ccw` 获取帮助！
+
+---
+
+**祝你使用愉快！** 🎉
+
+有任何问题，使用 `ccw-issue` 提交问题或查询帮助。

.claude/skills/command-guide/guides/index-structure.md

@@ -0,0 +1,326 @@
+# Index Structure Reference
+
+Complete documentation for command index files and their data structures.
+
+## Overview
+
+The command-guide skill uses 5 JSON index files to organize and query 69 commands across the Claude DMS3 workflow system.
+
+## Index Files
+
+### 1. `all-commands.json`
+
+**Purpose**: Complete catalog of all commands with full metadata
+
+**Use Cases**:
+- Full-text search across all commands
+- Detailed command queries
+- Batch operations
+- Reference lookup
+
+**Structure**:
+```json
+[
+  {
+    "name": "workflow:plan",
+    "description": "Orchestrate 5-phase planning workflow with quality gate",
+    "arguments": "[--agent] [--cli-execute] \"text description\"|file.md",
+    "category": "workflow",
+    "subcategory": "core",
+    "usage_scenario": "planning",
+    "difficulty": "Advanced",
+    "file_path": "workflow/plan.md"
+  },
+  ...
+]
+```
+
+**Fields**:
+- `name` (string): Command name (e.g., "workflow:plan")
+- `description` (string): Brief functional description
+- `arguments` (string): Parameter specification
+- `category` (string): Primary category (workflow/cli/memory/task)
+- `subcategory` (string|null): Secondary grouping if applicable
+- `usage_scenario` (string): Primary use case (planning/implementation/testing/etc.)
+- `difficulty` (string): Skill level (Beginner/Intermediate/Advanced)
+- `file_path` (string): Relative path to command file
+
+**Total Records**: 69 commands
+
+---
+
+### 2. `by-category.json`
+
+**Purpose**: Hierarchical organization by category and subcategory
+
+**Use Cases**:
+- Browse commands by category
+- Category-specific listings
+- Hierarchical navigation
+- Understanding command organization
+
+**Structure**:
+```json
+{
+  "workflow": {
+    "core": [
+      {
+        "name": "workflow:plan",
+        "description": "...",
+        ...
+      }
+    ],
+    "brainstorm": [...],
+    "session": [...],
+    "tools": [...],
+    "ui-design": [...]
+  },
+  "cli": {
+    "mode": [...],
+    "core": [...]
+  },
+  "memory": [...],
+  "task": [...]
+}
+```
+
+**Category Breakdown**:
+- **workflow** (46 commands):
+  - core: 11 commands
+  - brainstorm: 12 commands
+  - session: 4 commands
+  - tools: 9 commands
+  - ui-design: 10 commands
+- **cli** (9 commands):
+  - mode: 3 commands
+  - core: 6 commands
+- **memory** (8 commands)
+- **task** (4 commands)
+- **general** (2 commands)
+
+---
+
+### 3. `by-use-case.json`
+
+**Purpose**: Commands organized by practical usage scenarios
+
+**Use Cases**:
+- Task-oriented command discovery
+- "I want to do X" queries
+- Workflow planning
+- Learning paths
+
+**Structure**:
+```json
+{
+  "planning": [
+    {
+      "name": "workflow:plan",
+      "description": "...",
+      ...
+    },
+    ...
+  ],
+  "implementation": [...],
+  "testing": [...],
+  "documentation": [...],
+  "session-management": [...],
+  "general": [...]
+}
+```
+
+**Use Case Categories**:
+- **planning**: Architecture, task breakdown, design
+- **implementation**: Coding, development, execution
+- **testing**: Test generation, TDD, quality assurance
+- **documentation**: Docs generation, memory management
+- **session-management**: Workflow control, resumption
+- **general**: Utilities, versioning, prompt enhancement
+
+---
+
+### 4. `essential-commands.json`
+
+**Purpose**: Curated list of 10-15 most frequently used commands
+
+**Use Cases**:
+- Quick reference for beginners
+- Onboarding new users
+- Common workflow starters
+- Cheat sheet
+
+**Structure**:
+```json
+[
+  {
+    "name": "enhance-prompt",
+    "description": "Context-aware prompt enhancement",
+    "arguments": "\"user input to enhance\"",
+    "category": "general",
+    "subcategory": null,
+    "usage_scenario": "general",
+    "difficulty": "Intermediate",
+    "file_path": "enhance-prompt.md"
+  },
+  ...
+]
+```
+
+**Selection Criteria**:
+- Frequency of use in common workflows
+- Value for beginners
+- Core functionality coverage
+- Minimal overlap in capabilities
+
+**Current Count**: 14 commands
+
+**List**:
+1. `enhance-prompt` - Prompt enhancement
+2. `version` - Version info
+3. `cli:analyze` - Quick codebase analysis
+4. `cli:chat` - Direct CLI interaction
+5. `cli:execute` - Auto-execution
+6. `cli:mode:plan` - Planning mode
+7. `task:breakdown` - Task decomposition
+8. `task:create` - Create tasks
+9. `task:execute` - Execute tasks
+10. `workflow:execute` - Run workflows
+11. `workflow:plan` - Plan workflows
+12. `workflow:review` - Review implementation
+13. `workflow:tdd-plan` - TDD planning
+14. `workflow:test-gen` - Test generation
+
+---
+
+### 5. `command-relationships.json`
+
+**Purpose**: Mapping of command dependencies and common sequences
+
+**Use Cases**:
+- Next-step recommendations
+- Workflow pattern suggestions
+- Related command discovery
+- Smart navigation
+
+**Structure**:
+```json
+{
+  "workflow:plan": {
+    "related_commands": [
+      "workflow:execute",
+      "workflow:action-plan-verify"
+    ],
+    "next_steps": ["workflow:execute"],
+    "prerequisites": []
+  },
+  "workflow:execute": {
+    "related_commands": [
+      "workflow:status",
+      "workflow:resume",
+      "workflow:review"
+    ],
+    "next_steps": ["workflow:review", "workflow:status"],
+    "prerequisites": ["workflow:plan"]
+  },
+  ...
+}
+```
+
+**Fields**:
+- `related_commands` (array): Commonly used together
+- `next_steps` (array): Typical next commands
+- `prerequisites` (array): Usually run before this command
+
+**Relationship Types**:
+1. **Sequential**: A → B (plan → execute)
+2. **Alternatives**: A | B (execute OR codex-execute)
+3. **Built-in**: A includes B (plan auto-includes context-gather)
+
+---
+
+## Query Patterns
+
+### Pattern 1: Keyword Search
+```javascript
+// Search by keyword in name or description
+const results = allCommands.filter(cmd =>
+  cmd.name.includes(keyword) ||
+  cmd.description.toLowerCase().includes(keyword.toLowerCase())
+);
+```
+
+### Pattern 2: Category Browse
+```javascript
+// Get all commands in a category
+const workflowCommands = byCategory.workflow;
+const coreWorkflow = byCategory.workflow.core;
+```
+
+### Pattern 3: Use-Case Lookup
+```javascript
+// Find commands for specific use case
+const planningCommands = byUseCase.planning;
+```
+
+### Pattern 4: Related Commands
+```javascript
+// Get next steps after a command
+const nextSteps = commandRelationships["workflow:plan"].next_steps;
+```
+
+### Pattern 5: Essential Commands
+```javascript
+// Get beginner-friendly quick reference
+const quickStart = essentialCommands;
+```
+
+---
+
+## Maintenance
+
+### Regenerating Indexes
+
+When commands are added/modified/removed:
+
+```bash
+bash scripts/update-index.sh
+```
+
+The script will:
+1. Scan all .md files in commands/
+2. Extract metadata from YAML frontmatter
+3. Analyze command relationships
+4. Identify essential commands
+5. Generate all 5 index files
+
+### Validation Checklist
+
+After regeneration, verify:
+- [ ] All 5 JSON files are valid (no syntax errors)
+- [ ] Total command count matches (currently 69)
+- [ ] No missing fields in records
+- [ ] Category breakdown correct
+- [ ] Essential commands reasonable (10-15)
+- [ ] Relationships make logical sense
+
+---
+
+## Performance Considerations
+
+**Index Sizes**:
+- `all-commands.json`: ~28KB
+- `by-category.json`: ~31KB
+- `by-use-case.json`: ~29KB
+- `command-relationships.json`: ~7KB
+- `essential-commands.json`: ~5KB
+
+**Total**: ~100KB (fast to load)
+
+**Query Speed**:
+- In-memory search: < 1ms
+- File read + parse: < 50ms
+- Recommended: Load indexes once, cache in memory
+
+---
+
+**Last Updated**: 2025-01-06

.claude/skills/command-guide/guides/troubleshooting.md

@@ -0,0 +1,92 @@
+# 常见问题与解决方案
+
+在使用 Gemini CLI 的过程中，您可能会遇到一些问题。本指南旨在帮助您诊断和解决这些常见问题，确保您能顺利使用 CLI。
+
+## 1. 命令执行失败或未找到
+
+**问题描述**:
+- 您输入的命令没有响应，或者系统提示“命令未找到”。
+- 命令执行后出现错误信息，但您不理解其含义。
+
+**可能原因**:
+- 命令拼写错误。
+- CLI 未正确安装或环境变量配置不正确。
+- 命令所需的依赖项缺失。
+- 命令参数不正确或缺失。
+
+**解决方案**:
+1.  **检查拼写**: 仔细核对您输入的命令是否正确，包括命令名称和任何参数。
+2.  **查看帮助**: 使用 `gemini help` 或 `gemini [command-name] --help` 来查看命令的正确用法、可用参数和示例。
+3.  **验证安装**: 确保 Gemini CLI 已正确安装，并且其可执行文件路径已添加到系统的环境变量中。您可以尝试重新安装 CLI。
+4.  **检查日志**: CLI 通常会生成日志文件。查看这些日志可以提供更详细的错误信息，帮助您定位问题。
+5.  **更新 CLI**: 确保您使用的是最新版本的 Gemini CLI。旧版本可能存在已知错误，通过 `gemini version` 检查并更新。
+
+## 2. 权限问题
+
+**问题描述**:
+- CLI 尝试读取、写入或创建文件/目录时，提示“权限被拒绝”或类似错误。
+- 某些操作（如安装依赖、修改系统配置）失败。
+
+**可能原因**:
+- 当前用户没有足够的权限执行该操作。
+- 文件或目录被其他程序占用。
+
+**解决方案**:
+1.  **以管理员身份运行**: 尝试以管理员权限（Windows）或使用 `sudo`（Linux/macOS）运行您的终端或命令提示符。
+    ```bash
+    # Windows (在命令提示符或 PowerShell 中右键选择“以管理员身份运行”)
+    # Linux/macOS
+    sudo gemini [command]
+    ```
+2.  **检查文件/目录权限**: 确保您对目标文件或目录拥有读/写/执行权限。您可能需要使用 `chmod` (Linux/macOS) 或修改文件属性 (Windows) 来更改权限。
+3.  **关闭占用程序**: 确保没有其他程序正在使用您尝试访问的文件或目录。
+
+## 3. 配置问题
+
+**问题描述**:
+- CLI 行为异常，例如无法连接到 LLM 服务，或者某些功能无法正常工作。
+- 提示缺少 API 密钥或配置项。
+
+**可能原因**:
+- 配置文件（如 `.gemini.json` 或相关环境变量）设置不正确。
+- API 密钥过期或无效。
+- 网络连接问题导致无法访问外部服务。
+
+**解决方案**:
+1.  **检查配置文件**: 仔细检查 Gemini CLI 的配置文件（通常位于用户主目录或项目根目录）中的设置。确保所有路径、API 密钥和选项都正确无误。
+2.  **验证环境变量**: 确认所有必要的环境变量（如 `GEMINI_API_KEY`）都已正确设置。
+3.  **网络连接**: 检查您的网络连接是否正常，并确保没有防火墙或代理设置阻止 CLI 访问外部服务。
+4.  **重新初始化配置**: 对于某些配置问题，您可能需要使用 `gemini cli-init` 命令重新初始化 CLI 配置。
+    ```bash
+    gemini cli-init
+    ```
+
+## 4. 智能代理 (LLM) 相关问题
+
+**问题描述**:
+- 智能代理的响应质量不佳，不相关或不准确。
+- 代理响应速度慢，或提示达到速率限制。
+
+**可能原因**:
+- 提示不够清晰或缺乏上下文。
+- 选择了不适合当前任务的 LLM 模型。
+- LLM 服务提供商的速率限制或服务中断。
+
+**解决方案**:
+1.  **优化提示**: 尝试使用 `enhance-prompt` 命令来优化您的输入，提供更清晰、更具体的上下文信息。
+2.  **选择合适的工具**: 根据任务类型，使用 `--tool` 标志选择最合适的 LLM 模型（如 `codex` 适用于代码生成，`gemini` 适用于复杂推理）。
+    ```bash
+    gemini analyze --tool gemini "分析这个复杂算法"
+    ```
+3.  **检查 API 密钥和配额**: 确保您的 LLM 服务 API 密钥有效，并且没有超出使用配额。
+4.  **重试或等待**: 如果是速率限制或服务中断，请稍后重试或联系服务提供商。
+
+## 5. 寻求帮助
+
+如果以上解决方案都无法解决您的问题，您可以：
+
+-   **查阅官方文档**: 访问 Gemini CLI 的官方文档获取更全面的信息。
+-   **社区支持**: 在相关的开发者社区或论坛中提问。
+-   **提交问题**: 如果您认为是 CLI 的 bug，请在项目的问题跟踪器中提交详细的问题报告。
+
+希望本指南能帮助您解决遇到的问题，让您更好地利用 Gemini CLI！

.claude/skills/command-guide/guides/ui-design-workflow-guide.md

@@ -0,0 +1,326 @@
+# UI Design Workflow Guide
+
+## Overview
+
+The UI Design Workflow System is a comprehensive suite of 11 autonomous commands designed to transform intent (prompts), references (images/URLs), or existing code into functional, production-ready UI prototypes. It employs a **Separation of Concerns** architecture, treating Style (visual tokens), Structure (layout templates), and Motion (animation tokens) as independent, mix-and-match components.
+
+## Command Taxonomy
+
+### 1. Orchestrators (High-Level Workflows)
+
+These commands automate end-to-end processes by chaining specialized sub-commands.
+
+- **`/workflow:ui-design:explore-auto`**: For creating *new* designs. Generates multiple style and layout variants from a prompt to explore design directions.
+- **`/workflow:ui-design:imitate-auto`**: For *replicating* existing designs. High-fidelity cloning of target URLs into a reusable design system.
+- **`/workflow:ui-design:batch-generate`**: For rapid, high-volume prototype generation based on established design tokens.
+
+### 2. Core Extractors (Specialized Analysis)
+
+Agents dedicated to analyzing specific aspects of design.
+
+- **`/workflow:ui-design:style-extract`**: Extracts visual tokens (colors, typography, spacing, shadows) into `design-tokens.json`.
+- **`/workflow:ui-design:layout-extract`**: Extracts DOM structure and CSS layout rules into `layout-templates.json`.
+- **`/workflow:ui-design:animation-extract`**: Extracts motion patterns into `animation-tokens.json`.
+
+### 3. Input & Capture Utilities
+
+Tools for gathering raw data for analysis.
+
+- **`/workflow:ui-design:capture`**: High-speed batch screenshot capture for multiple URLs.
+- **`/workflow:ui-design:explore-layers`**: Interactive, depth-controlled capture (e.g., capturing modals, dropdowns, shadow DOM).
+- **`/workflow:ui-design:import-from-code`**: Bootstraps a design system by analyzing existing CSS/JS/HTML files.
+
+### 4. Assemblers & Integrators
+
+Tools for combining components and integrating results.
+
+- **`/workflow:ui-design:generate`**: Pure assembler that combines Layout Templates + Design Tokens into HTML/CSS prototypes.
+- **`/workflow:ui-design:update`**: Synchronizes generated design artifacts with the main project session for implementation planning.
+
+---
+
+## Common Workflow Patterns
+
+### Workflow A: Exploratory Design (New Concepts)
+
+**Goal:** Create multiple design options for a new project from a text description.
+
+**Primary Command:** `explore-auto`
+
+**Steps:**
+
+1. **Initiate**: User runs `/workflow:ui-design:explore-auto --prompt "Modern fintech dashboard" --style-variants 3`
+2. **Style Extraction**: System generates 3 distinct visual design systems based on the prompt.
+3. **Layout Extraction**: System researches and generates responsive layout templates for a dashboard.
+4. **Assembly**: System generates a matrix of prototypes (3 styles × 1 layout = 3 prototypes).
+5. **Review**: User views `compare.html` to select the best direction.
+
+**Example:**
+
+```bash
+/workflow:ui-design:explore-auto \
+  --prompt "Modern SaaS landing page with hero, features, pricing sections" \
+  --style-variants 3 \
+  --layout-variants 2 \
+  --session WFS-001
+```
+
+**Output:**
+- `design-tokens-v1.json`, `design-tokens-v2.json`, `design-tokens-v3.json` (3 style variants)
+- `layout-templates-v1.json`, `layout-templates-v2.json` (2 layout variants)
+- 6 HTML prototypes (3 × 2 combinations)
+- `compare.html` for side-by-side comparison
+
+---
+
+### Workflow B: Design Replication (Imitation)
+
+**Goal:** Create a design system and prototypes based on existing reference sites.
+
+**Primary Command:** `imitate-auto`
+
+**Steps:**
+
+1. **Initiate**: User runs `/workflow:ui-design:imitate-auto --url-map "home:https://example.com, pricing:https://example.com/pricing"`
+2. **Capture**: System screenshots all provided URLs.
+3. **Extraction**: System extracts a unified design system (style, layout, animation) from the primary URL.
+4. **Assembly**: System recreates all target pages using the extracted system.
+
+**Example:**
+
+```bash
+/workflow:ui-design:imitate-auto \
+  --url-map "landing:https://stripe.com, pricing:https://stripe.com/pricing, docs:https://stripe.com/docs" \
+  --capture-mode batch \
+  --session WFS-002
+```
+
+**Output:**
+- Screenshots of all URLs
+- `design-tokens.json` (unified style system)
+- `layout-templates.json` (page structures)
+- 3 HTML prototypes matching the captured pages
+
+---
+
+### Workflow C: Code-First Bootstrap
+
+**Goal:** Create a design system from an existing codebase.
+
+**Primary Command:** `import-from-code`
+
+**Steps:**
+
+1. **Initiate**: User runs `/workflow:ui-design:import-from-code --base-path ./src`
+2. **Analysis**: Parallel agents analyze CSS, JS, and HTML to find tokens, layouts, and animations.
+3. **Reporting**: Generates completeness reports and initial token files.
+4. **Supplement (Optional)**: Run `style-extract` or `layout-extract` to fill gaps identified in the reports.
+
+**Example:**
+
+```bash
+/workflow:ui-design:import-from-code \
+  --base-path ./src/components \
+  --session WFS-003
+```
+
+**Output:**
+- `design-tokens.json` (extracted from CSS variables, theme files)
+- `layout-templates.json` (extracted from component structures)
+- `completeness-report.md` (gaps and recommendations)
+- `import-summary.json` (statistics and findings)
+
+---
+
+### Workflow D: Batch Generation (High Volume)
+
+**Goal:** Generate multiple UI prototypes based on established design tokens.
+
+**Primary Command:** `batch-generate`
+
+**Steps:**
+
+1. **Prerequisites**: Have `design-tokens.json` ready (from previous extraction or manual creation)
+2. **Initiate**: User runs `/workflow:ui-design:batch-generate --targets "dashboard,settings,profile" --style-variants 2`
+3. **Parallel Generation**: System generates all targets in parallel, applying style variants
+4. **Review**: User reviews generated prototypes
+
+**Example:**
+
+```bash
+/workflow:ui-design:batch-generate \
+  --targets "login-page,dashboard,settings,profile,notifications" \
+  --target-type page \
+  --style-variants 2 \
+  --device-type responsive \
+  --session WFS-004
+```
+
+**Output:**
+- 10 HTML prototypes (5 targets × 2 styles)
+- All using the same design system for consistency
+
+---
+
+## Architecture & Best Practices
+
+### Separation of Concerns
+
+**Always keep design tokens separate from layout templates:**
+
+- `design-tokens.json` (Style) - Colors, typography, spacing, shadows
+- `layout-templates.json` (Structure) - DOM hierarchy, CSS layout rules
+- `animation-tokens.json` (Motion) - Transitions, keyframes, timing functions
+
+**Benefits:**
+- Instant re-theming by swapping design tokens
+- Layout reuse across different visual styles
+- Independent evolution of style and structure
+
+### Token-First CSS
+
+Generated CSS should primarily use CSS custom properties:
+
+```css
+/* Good - Token-based */
+.button {
+  background: var(--color-primary);
+  padding: var(--spacing-md);
+  border-radius: var(--radius-md);
+}
+
+/* Avoid - Hardcoded */
+.button {
+  background: #3b82f6;
+  padding: 16px;
+  border-radius: 8px;
+}
+```
+
+### Style-Centric Batching
+
+For high-volume generation:
+- Group tasks by style to minimize context switching
+- Use `batch-generate` with multiple targets
+- Reuse existing layout inspirations
+
+### Input Quality Guidelines
+
+**For Prompts:**
+- Specify the desired *vibe* (e.g., "minimalist, high-contrast")
+- Specify the *targets* (e.g., "dashboard, settings page")
+- Include functional requirements (e.g., "responsive, mobile-first")
+
+**For URL Mapping:**
+- First URL is treated as primary source of truth
+- Use descriptive keys in `--url-map`
+- Ensure URLs are accessible (no authentication walls)
+
+---
+
+## Advanced Usage
+
+### Multi-Session Workflows
+
+You can run UI design workflows within an existing workflow session:
+
+```bash
+# 1. Start a workflow session
+/workflow:session:start --new
+
+# 2. Run exploratory design
+/workflow:ui-design:explore-auto --prompt "E-commerce checkout flow" --session <session-id>
+
+# 3. Update main session with design artifacts
+/workflow:ui-design:update --session <session-id> --selected-prototypes "v1,v2"
+```
+
+### Combining Workflows
+
+**Example: Imitation + Custom Variants**
+
+```bash
+# 1. Replicate existing design
+/workflow:ui-design:imitate-auto --url-map "ref:https://example.com"
+
+# 2. Generate additional variants with batch-generate
+/workflow:ui-design:batch-generate --targets "new-page-1,new-page-2" --style-variants 1
+```
+
+### Deep Interactive Capture
+
+For complex UIs with overlays, modals, or dynamic content:
+
+```bash
+/workflow:ui-design:explore-layers \
+  --url https://complex-app.com \
+  --depth 3 \
+  --session WFS-005
+```
+
+---
+
+## Troubleshooting
+
+| Issue | Likely Cause | Resolution |
+|-------|--------------|------------|
+| **Missing Design Tokens** | `style-extract` failed or wasn't run | Run `/workflow:ui-design:style-extract` manually or check logs |
+| **Inaccurate Layouts** | Complex DOM structure not captured | Use `--urls` in `layout-extract` for Chrome DevTools analysis |
+| **Empty Screenshots** | Anti-bot measures or timeout | Use `explore-layers` interactive mode or increase timeout |
+| **Generation Stalls** | Too many concurrent tasks | System defaults to max 6 parallel tasks; check resources |
+| **Integration Failures** | Session ID mismatch or missing markers | Ensure `--session <id>` matches active workflow session |
+| **Low Quality Tokens** | Insufficient reference material | Provide multiple reference images/URLs for better token extraction |
+| **Inconsistent Styles** | Multiple token files without merge | Use single unified `design-tokens.json` or explicit variants |
+
+---
+
+## Command Reference Quick Links
+
+### Orchestrators
+- `/workflow:ui-design:explore-auto` - Create new designs from prompts
+- `/workflow:ui-design:imitate-auto` - Replicate existing designs
+- `/workflow:ui-design:batch-generate` - High-volume prototype generation
+
+### Extractors
+- `/workflow:ui-design:style-extract` - Extract visual design tokens
+- `/workflow:ui-design:layout-extract` - Extract layout structures
+- `/workflow:ui-design:animation-extract` - Extract motion patterns
+
+### Utilities
+- `/workflow:ui-design:capture` - Batch screenshot capture
+- `/workflow:ui-design:explore-layers` - Interactive deep capture
+- `/workflow:ui-design:import-from-code` - Bootstrap from existing code
+- `/workflow:ui-design:generate` - Assemble prototypes from tokens
+- `/workflow:ui-design:update` - Integrate with workflow sessions
+
+---
+
+## Performance Optimization
+
+### Parallel Execution
+
+The system is designed to run extraction phases in parallel:
+- Animation and layout extraction can run concurrently
+- Multiple target generation runs in parallel (default: max 6)
+- Style variant generation is parallelized
+
+### Reuse Intermediates
+
+- `batch-generate` reuses existing layout inspirations
+- Cached screenshots avoid redundant captures
+- Token files can be versioned and reused
+
+### Resource Management
+
+- Each agent task consumes memory and CPU
+- Monitor system resources with large batch operations
+- Consider splitting large batches into smaller chunks
+
+---
+
+## Related Guides
+
+- **Getting Started** - Basic workflow concepts
+- **Workflow Patterns** - General workflow guidance
+- **CLI Tools Guide** - CLI integration strategies
+- **Troubleshooting** - Common issues and solutions

.claude/skills/command-guide/guides/workflow-patterns.md

@@ -0,0 +1,662 @@
+# 常见工作流模式
+
+> 学习如何组合命令完成复杂任务，提升开发效率
+
+## 🎯 什么是工作流？
+
+工作流是**一系列命令的组合**，用于完成特定的开发目标。Claude DMS3 提供了多种工作流模式，覆盖从规划到测试的完整开发周期。
+
+**核心概念**：
+- **工作流（Workflow）**：一组相关任务的集合
+- **任务（Task）**：独立的工作单元，有明确的输入和输出
+- **Session**：工作流的执行实例，记录所有任务状态
+- **上下文（Context）**：任务执行所需的代码、文档、配置等信息
+
+---
+
+## 💡 Pattern 0: 头脑风暴（从0到1的第一步）
+
+**⚠️ 重要**：这是**从0到1开发的起点**！在开始编码之前，通过多角色头脑风暴明确需求、技术选型和架构决策。
+
+**适用场景**：
+- 全新项目启动，需求和技术方案不明确
+- 重大功能开发，涉及多个技术领域和权衡
+- 架构决策，需要多角色视角分析
+
+**流程**：话题分析 → 角色选择 → 角色问答 → 冲突解决 → 生成指导文档
+
+### 模式 A：交互式头脑风暴（推荐）
+
+**特点**：通过问答交互，逐步明确需求和决策
+
+```bash
+# 步骤 1：启动头脑风暴
+/workflow:brainstorm:artifacts "
+GOAL: 实现实时协作编辑平台
+SCOPE: 支持100+用户同时在线，低延迟(<100ms)，冲突自动解决
+CONTEXT: MVP阶段，3个月上线，团队5人（2前端+2后端+1全栈）
+" --count 3
+
+# 系统输出 Phase 0：自动收集项目上下文
+# ✅ 分析现有代码库结构
+# ✅ 加载相关文档
+# ✅ 识别技术栈和依赖
+
+# 系统输出 Phase 1：意图分析（2-4个问题）
+# 【问题1 - 核心挑战】实时协作的主要技术挑战？
+# a) 实时数据同步
+# b) 可扩展性架构
+# c) 冲突解决机制
+# 【问题2 - 优先级】MVP阶段最关注？
+# a) 功能完整性
+# b) 用户体验
+# c) 系统稳定性
+# 请回答 (格式: 1a 2c)：
+
+# 用户输入：1c 2b
+
+# 系统输出 Phase 2：角色选择（推荐 count+2 个角色）
+# 【角色选择】请选择 3 个角色参与头脑风暴
+# a) system-architect (系统架构师) - 实时同步架构设计
+# b) ui-designer (UI设计师) - 协作界面用户体验
+# c) product-manager (产品经理) - 功能优先级决策
+# d) data-architect (数据架构师) - 数据同步模型设计
+# e) ux-expert (UX专家) - 多用户协作交互流程
+# 请输入选择 (格式: 2acd 或 2a 2c 2d)：
+
+# 用户输入：2acd
+
+# 系统输出 Phase 3：角色问题（每个角色 3-4 个问题）
+# ===== system-architect 问题 =====
+# 【问题1】100+ 用户实时状态同步方案？
+# a) Event Sourcing - 完整事件历史，易于回溯
+# b) 集中式状态管理 - 简单直接，适合MVP
+# c) CRDT - 自动冲突解决，分布式友好
+# 【问题2】低延迟通信协议选择？
+# ...
+# 请回答：
+
+# 用户输入：1c 2a 3b 4c
+
+# 系统输出 Phase 4：冲突检测和解决
+# 【冲突1】CRDT 与 UI 回滚期望冲突
+# Background: system-architect 选择 CRDT，但 ui-designer 期望回滚UI
+# a) 采用 CRDT，显示合并状态
+# b) 切换到 OT 算法支持回滚
+# c) 混合方案：CRDT + 本地撤销栈
+# ...
+
+# 系统输出 Phase 5：生成指导文档
+# ✅ 生成 guidance-specification.md
+# ✅ 记录所有决策和理由
+# ✅ 标注冲突解决方案
+# 📁 文件位置：.workflow/WFS-realtime-collab/.brainstorming/guidance-specification.md
+
+# 步骤 2：查看生成的指导文档
+cat .workflow/WFS-*//.brainstorming/guidance-specification.md
+```
+
+### 模式 B：自动并行头脑风暴（快速）
+
+**特点**：自动选择角色，并行执行，快速生成多角色分析
+
+```bash
+# 步骤 1：一键启动并行头脑风暴
+/workflow:brainstorm:auto-parallel "
+GOAL: 实现支付处理模块
+SCOPE: 支持微信/支付宝/银行卡，日交易10万笔，99.99%可用性
+CONTEXT: 金融合规要求，PCI DSS认证，风控系统集成
+" --count 4
+
+# 系统输出：
+# ✅ Phase 0: 收集项目上下文
+# ✅ Phase 1-2: artifacts 交互式框架生成
+# ⏳ Phase 3: 4个角色并行分析
+#   - system-architect → 分析中...
+#   - data-architect → 分析中...
+#   - product-manager → 分析中...
+#   - subject-matter-expert → 分析中...
+# ✅ Phase 4: synthesis 综合分析
+# 📁 输出文件：
+#   - .brainstorming/guidance-specification.md (框架)
+#   - system-architect/analysis.md
+#   - data-architect/analysis.md
+#   - product-manager/analysis.md
+#   - subject-matter-expert/analysis.md
+#   - synthesis/final-recommendations.md
+
+# 步骤 2：查看综合建议
+cat .workflow/WFS-*//.brainstorming/synthesis/final-recommendations.md
+```
+
+### 模式 C：单角色深度分析（特定领域）
+
+**特点**：针对特定领域问题，调用单个角色深度分析
+
+```bash
+# 系统架构分析
+/workflow:brainstorm:system-architect "API 网关架构设计，支持10万QPS，微服务集成"
+
+# UI 设计分析
+/workflow:brainstorm:ui-designer "管理后台界面设计，复杂数据展示，操作效率优先"
+
+# 数据架构分析
+/workflow:brainstorm:data-architect "分布式数据存储方案，MySQL+Redis+ES 组合"
+```
+
+### 关键点
+
+1. **Phase 0 自动上下文收集**：
+   - 自动分析现有代码库、文档、技术栈
+   - 识别潜在冲突和集成点
+   - 为后续问题生成提供上下文
+
+2. **动态问题生成**：
+   - 基于话题关键词和项目上下文生成问题
+   - 不使用预定义模板
+   - 问题直接针对你的具体场景
+
+3. **智能角色推荐**：
+   - 基于话题分析推荐最相关的角色
+   - 推荐 count+2 个角色供选择
+   - 每个角色都有基于话题的推荐理由
+
+4. **输出物**：
+   - `guidance-specification.md` - 确认的指导规范（决策、理由、集成点）
+   - `{role}/analysis.md` - 各角色详细分析（仅 auto-parallel 模式）
+   - `synthesis/final-recommendations.md` - 综合建议（仅 auto-parallel 模式）
+
+5. **下一步**：
+   - 头脑风暴完成后，使用 `/workflow:plan` 基于指导文档生成实施计划
+   - 指导文档作为规划和实现的权威参考
+
+### 使用场景对比
+
+| 场景 | 推荐模式 | 原因 |
+|------|---------|------|
+| 全新项目启动 | 交互式 (artifacts) | 需要充分澄清需求和约束 |
+| 重大架构决策 | 交互式 (artifacts) | 需要深入讨论权衡 |
+| 快速原型验证 | 自动并行 (auto-parallel) | 快速获得多角色建议 |
+| 特定技术问题 | 单角色 (specific role) | 专注某个领域深度分析 |
+
+---
+
+## 📋 Pattern 1: 规划→执行（最常用）
+
+**适用场景**：实现新功能、新模块
+
+**流程**：规划 → 执行 → 查看状态
+
+### 完整示例
+
+```bash
+# 步骤 1：规划任务
+/workflow:plan --agent "实现用户认证模块"
+
+# 系统输出：
+# ✅ 规划完成
+# 📁 Session: WFS-20251106-123456
+# 📋 生成 5 个任务
+
+# 步骤 2：执行任务
+/workflow:execute
+
+# 系统输出：
+# ⏳ 执行 task-001-user-model...
+# ✅ task-001 完成
+# ⏳ 执行 task-002-login-api...
+# ...
+
+# 步骤 3：查看状态
+/workflow:status
+
+# 系统输出：
+# Session: WFS-20251106-123456
+# Total: 5 | Completed: 5 | Pending: 0
+```
+
+**关键点**：
+- `--agent` 参数使用 AI 生成更详细的计划
+- 系统自动发现最新 session，无需手动指定
+- 所有任务按依赖顺序自动执行
+
+---
+
+## 🧪 Pattern 2: TDD测试驱动开发
+
+**适用场景**：需要高质量代码和测试覆盖
+
+**流程**：TDD规划 → 执行（红→绿→重构）→ 验证
+
+### 完整示例
+
+```bash
+# 步骤 1：TDD 规划
+/workflow:tdd-plan --agent "实现购物车功能"
+
+# 系统输出：
+# ✅ TDD 任务链生成
+# 📋 Red-Green-Refactor 周期：
+#   - task-001-cart-tests (RED)
+#   - task-002-cart-implement (GREEN)
+#   - task-003-cart-refactor (REFACTOR)
+
+# 步骤 2：执行 TDD 周期
+/workflow:execute
+
+# 系统会自动：
+# 1. 生成失败的测试（RED）
+# 2. 实现代码让测试通过（GREEN）
+# 3. 重构代码（REFACTOR）
+
+# 步骤 3：验证 TDD 合规性
+/workflow:tdd-verify
+
+# 系统输出：
+# ✅ TDD 周期完整
+# ✅ 测试覆盖率: 95%
+# ✅ Red-Green-Refactor 合规
+```
+
+**关键点**：
+- TDD 模式自动生成测试优先的任务链
+- 每个任务有依赖关系，确保正确的顺序
+- 验证命令检查 TDD 合规性
+
+---
+
+## 🔄 Pattern 3: 测试生成
+
+**适用场景**：已有代码，需要生成测试
+
+**流程**：分析代码 → 生成测试策略 → 执行测试生成
+
+### 完整示例
+
+```bash
+# 步骤 1：实现功能（已完成）
+# 假设已经完成实现，session 为 WFS-20251106-123456
+
+# 步骤 2：生成测试
+/workflow:test-gen WFS-20251106-123456
+
+# 系统输出：
+# ✅ 分析实现代码
+# ✅ 生成测试策略
+# 📋 创建测试任务：WFS-test-20251106-789
+
+# 步骤 3：执行测试生成
+/workflow:test-cycle-execute --resume-session WFS-test-20251106-789
+
+# 系统输出：
+# ⏳ 生成测试用例...
+# ⏳ 执行测试...
+# ❌ 3 tests failed
+# ⏳ 修复失败测试...
+# ✅ All tests passed
+```
+
+**关键点**：
+- `test-gen` 分析现有代码生成测试
+- `test-cycle-execute` 自动生成→测试→修复循环
+- 最多迭代 N 次直到所有测试通过
+
+---
+
+## 🎨 Pattern 4: UI 设计工作流
+
+**适用场景**：基于设计稿或现有网站实现 UI
+
+**流程**：提取样式 → 提取布局 → 生成原型 → 更新
+
+### 完整示例
+
+```bash
+# 步骤 1：提取设计样式
+/workflow:ui-design:style-extract \
+  --images "design/*.png" \
+  --mode imitate \
+  --variants 3
+
+# 系统输出：
+# ✅ 提取颜色系统
+# ✅ 提取字体系统
+# ✅ 生成 3 个样式变体
+
+# 步骤 2：提取页面布局
+/workflow:ui-design:layout-extract \
+  --urls "https://example.com/dashboard" \
+  --device-type responsive
+
+# 系统输出：
+# ✅ 提取布局结构
+# ✅ 识别组件层次
+# ✅ 生成响应式布局
+
+# 步骤 3：生成 UI 原型
+/workflow:ui-design:generate \
+  --style-variants 2 \
+  --layout-variants 2
+
+# 系统输出：
+# ✅ 生成 4 个原型组合
+# 📁 输出：.workflow/ui-design/prototypes/
+
+# 步骤 4：更新最终版本
+/workflow:ui-design:update \
+  --session ui-session-id \
+  --selected-prototypes "proto-1,proto-3"
+
+# 系统输出：
+# ✅ 应用最终设计系统
+# ✅ 更新所有原型
+```
+
+**关键点**：
+- 支持从图片或 URL 提取设计
+- 可生成多个变体供选择
+- 最终更新使用确定的设计系统
+
+---
+
+## 🔍 Pattern 5: 代码分析→重构
+
+**适用场景**：优化现有代码，提高可维护性
+
+**流程**：分析现状 → 制定计划 → 执行重构 → 生成测试
+
+### 完整示例
+
+```bash
+# 步骤 1：分析代码质量
+/cli:analyze --tool gemini --cd src/auth \
+  "评估认证模块的代码质量、可维护性和潜在问题"
+
+# 系统输出：
+# ✅ 识别 3 个设计问题
+# ✅ 发现 5 个性能瓶颈
+# ✅ 建议 7 项改进
+
+# 步骤 2：制定重构计划
+/cli:mode:plan --tool gemini --cd src/auth \
+  "基于上述分析，制定认证模块重构方案"
+
+# 系统输出：
+# ✅ 重构计划生成
+# 📋 包含 8 个重构任务
+
+# 步骤 3：执行重构
+/cli:execute --tool codex \
+  "按照重构计划执行认证模块重构"
+
+# 步骤 4：生成测试确保正确性
+/workflow:test-gen WFS-refactor-session-id
+```
+
+**关键点**：
+- Gemini 用于分析和规划（理解）
+- Codex 用于执行实现（重构）
+- 重构后必须生成测试验证
+
+---
+
+## 📚 Pattern 6: 文档生成
+
+**适用场景**：为项目或模块生成文档
+
+**流程**：分析代码 → 生成文档 → 更新索引
+
+### 完整示例
+
+```bash
+# 方式 1：为单个模块生成文档
+/memory:docs src/auth --tool gemini --mode full
+
+# 系统输出：
+# ✅ 分析模块结构
+# ✅ 生成 CLAUDE.md
+# ✅ 生成 API 文档
+# ✅ 生成使用指南
+
+# 方式 2：更新所有模块文档
+/memory:update-full --tool gemini
+
+# 系统输出：
+# ⏳ 按层级更新文档...
+# ✅ Layer 3: 12 modules updated
+# ✅ Layer 2: 5 modules updated
+# ✅ Layer 1: 2 modules updated
+
+# 方式 3：只更新修改过的模块
+/memory:update-related --tool gemini
+
+# 系统输出：
+# ✅ 检测 git 变更
+# ✅ 更新 3 个相关模块
+```
+
+**关键点**：
+- `--mode full` 生成完整文档
+- `update-full` 适用于初始化或大规模更新
+- `update-related` 适用于日常增量更新
+
+---
+
+## 🔄 Pattern 7: 恢复和继续
+
+**适用场景**：中断后继续工作，或修复失败的任务
+
+**流程**：查看状态 → 恢复 session → 继续执行
+
+### 完整示例
+
+```bash
+# 步骤 1：查看所有 session
+/workflow:status
+
+# 系统输出：
+# Session: WFS-20251106-123456 (5/10 completed)
+# Session: WFS-20251105-234567 (10/10 completed)
+
+# 步骤 2：恢复特定 session
+/workflow:resume WFS-20251106-123456
+
+# 系统输出：
+# ✅ Session 恢复
+# 📋 5/10 tasks completed
+# ⏳ 待执行: task-006, task-007, ...
+
+# 步骤 3：继续执行
+/workflow:execute --resume-session WFS-20251106-123456
+
+# 系统输出：
+# ⏳ 继续执行 task-006...
+# ✅ task-006 完成
+# ...
+```
+
+**关键点**：
+- 所有 session 状态都被保存
+- 可以随时恢复中断的工作流
+- 恢复时自动分析进度和待办任务
+
+---
+
+## 🎯 Pattern 8: 快速实现（Codex YOLO）
+
+**适用场景**：快速实现简单功能，跳过规划
+
+**流程**：直接执行 → 完成
+
+### 完整示例
+
+```bash
+# 一键实现功能
+/cli:codex-execute --verify-git \
+  "实现用户头像上传功能：
+  - 支持 jpg/png 格式
+  - 自动裁剪为 200x200
+  - 压缩到 100KB 以下
+  - 上传到 OSS
+  "
+
+# 系统输出：
+# ⏳ 分析需求...
+# ⏳ 生成代码...
+# ⏳ 集成现有代码...
+# ✅ 功能实现完成
+# 📁 修改文件:
+#   - src/api/upload.ts
+#   - src/utils/image.ts
+```
+
+**关键点**：
+- 适合简单、独立的功能
+- `--verify-git` 确保 git 状态干净
+- 自动分析需求并完整实现
+
+---
+
+## 🤝 Pattern 9: 多工具协作
+
+**适用场景**：复杂任务需要多个 AI 工具配合
+
+**流程**：Gemini 分析 → Gemini/Qwen 规划 → Codex 实现
+
+### 完整示例
+
+```bash
+# 步骤 1：Gemini 深度分析
+/cli:analyze --tool gemini \
+  "分析支付模块的安全性和性能问题"
+
+# 步骤 2：多工具讨论方案
+/cli:discuss-plan --topic "支付模块重构方案" --rounds 3
+
+# 系统输出：
+# Round 1:
+#   Gemini: 建议方案 A（关注安全）
+#   Codex: 建议方案 B（关注性能）
+# Round 2:
+#   Gemini: 综合分析...
+#   Codex: 技术实现评估...
+# Round 3:
+#   最终方案: 方案 C（安全+性能）
+
+# 步骤 3：Codex 执行实现
+/cli:execute --tool codex "按照方案 C 重构支付模块"
+```
+
+**关键点**：
+- `discuss-plan` 让多个 AI 讨论方案
+- 每个工具贡献自己的专长
+- 最终选择综合最优方案
+
+---
+
+## 📊 工作流选择指南
+
+**核心区分**：从0到1 vs 功能新增
+- **从0到1**：全新项目、新产品、重大架构决策 → **必须头脑风暴**
+- **功能新增**：已有项目中添加功能 → **可直接规划**
+
+```mermaid
+graph TD
+    A[我要做什么?] --> B{项目阶段?}
+
+    B -->|从0到1<br/>全新项目/产品| Z[💡头脑风暴<br/>必经阶段]
+    B -->|功能新增<br/>已有项目| C{任务类型?}
+
+    Z --> Z1[/workflow:brainstorm:artifacts<br/>或<br/>/workflow:brainstorm:auto-parallel]
+    Z1 --> Z2[⬇️ 生成指导文档]
+    Z2 --> C
+
+    C -->|新功能| D[规划→执行]
+    C -->|需要测试| E{代码是否存在?}
+    C -->|UI开发| F[UI设计工作流]
+    C -->|代码优化| G[分析→重构]
+    C -->|生成文档| H[文档生成]
+    C -->|快速实现| I[Codex YOLO]
+
+    E -->|不存在| J[TDD工作流]
+    E -->|已存在| K[测试生成]
+
+    D --> L[/workflow:plan<br/>↓<br/>/workflow:execute]
+    J --> M[/workflow:tdd-plan<br/>↓<br/>/workflow:execute]
+    K --> N[/workflow:test-gen<br/>↓<br/>/workflow:test-cycle-execute]
+    F --> O[/workflow:ui-design:*]
+    G --> P[/cli:analyze<br/>↓<br/>/cli:mode:plan<br/>↓<br/>/cli:execute]
+    H --> Q[/memory:docs]
+    I --> R[/cli:codex-execute]
+```
+
+**说明**：
+- **从0到1场景**：创业项目、新产品线、系统重构 → 头脑风暴明确方向后再规划
+- **功能新增场景**：现有系统添加模块、优化现有功能 → 直接进入规划或分析
+
+---
+
+## 💡 最佳实践
+
+### ✅ 推荐做法
+
+1. **复杂任务使用完整工作流**
+   ```bash
+   /workflow:plan → /workflow:execute → /workflow:test-gen
+   ```
+
+2. **简单任务使用 Codex YOLO**
+   ```bash
+   /cli:codex-execute "快速实现xxx"
+   ```
+
+3. **重要代码使用 TDD**
+   ```bash
+   /workflow:tdd-plan → /workflow:execute → /workflow:tdd-verify
+   ```
+
+4. **定期更新文档**
+   ```bash
+   /memory:update-related  # 每次提交前
+   ```
+
+5. **善用恢复功能**
+   ```bash
+   /workflow:status → /workflow:resume
+   ```
+
+---
+
+### ❌ 避免做法
+
+1. **⚠️ 不要在从0到1场景跳过头脑风暴**
+   - ❌ 全新项目直接 `/workflow:plan`
+   - ✅ 先 `/workflow:brainstorm:artifacts` 明确方向再规划
+
+2. **不要跳过规划直接执行复杂任务**
+   - ❌ 直接 `/cli:execute` 实现复杂功能
+   - ✅ 先 `/workflow:plan` 再 `/workflow:execute`
+
+3. **不要忽略测试**
+   - ❌ 实现完成后不生成测试
+   - ✅ 使用 `/workflow:test-gen` 生成测试
+
+4. **不要遗忘文档**
+   - ❌ 代码实现后忘记更新文档
+   - ✅ 使用 `/memory:update-related` 自动更新
+
+---
+
+## 🔗 相关资源
+
+- **快速入门**：[Getting Started](getting-started.md) - 5分钟上手
+- **CLI 工具**：[CLI Tools Guide](cli-tools-guide.md) - Gemini/Qwen/Codex 详解
+- **UI设计工作流**：[UI Design Workflow Guide](ui-design-workflow-guide.md) - UI设计完整指南
+- **问题排查**：[Troubleshooting](troubleshooting.md) - 常见问题解决
+- **完整命令列表**：查看 `index/all-commands.json`
+
+---
+
+**最后更新**: 2025-11-06
+
+记住：选择合适的工作流模式，事半功倍！不确定用哪个？使用 `ccw` 询问 Command Guide！

.claude/skills/command-guide/index/all-commands.json

@@ -0,0 +1,772 @@
+[
+  {
+    "name": "analyze",
+    "command": "/cli:analyze",
+    "description": "Read-only codebase analysis using Gemini (default), Qwen, or Codex with auto-pattern detection and template selection",
+    "arguments": "[--agent] [--tool codex|gemini|qwen] [--enhance] analysis target",
+    "category": "cli",
+    "subcategory": null,
+    "usage_scenario": "analysis",
+    "difficulty": "Beginner",
+    "file_path": "cli/analyze.md"
+  },
+  {
+    "name": "chat",
+    "command": "/cli:chat",
+    "description": "Read-only Q&A interaction with Gemini/Qwen/Codex for codebase questions with automatic context inference",
+    "arguments": "[--agent] [--tool codex|gemini|qwen] [--enhance] inquiry",
+    "category": "cli",
+    "subcategory": null,
+    "usage_scenario": "general",
+    "difficulty": "Beginner",
+    "file_path": "cli/chat.md"
+  },
+  {
+    "name": "cli-init",
+    "command": "/cli:cli-init",
+    "description": "Generate .gemini/ and .qwen/ config directories with settings.json and ignore files based on workspace technology detection",
+    "arguments": "[--tool gemini|qwen|all] [--output path] [--preview]",
+    "category": "cli",
+    "subcategory": null,
+    "usage_scenario": "general",
+    "difficulty": "Intermediate",
+    "file_path": "cli/cli-init.md"
+  },
+  {
+    "name": "codex-execute",
+    "command": "/cli:codex-execute",
+    "description": "Multi-stage Codex execution with automatic task decomposition into grouped subtasks using resume mechanism for context continuity",
+    "arguments": "[--verify-git] task description or task-id",
+    "category": "cli",
+    "subcategory": null,
+    "usage_scenario": "implementation",
+    "difficulty": "Intermediate",
+    "file_path": "cli/codex-execute.md"
+  },
+  {
+    "name": "discuss-plan",
+    "command": "/cli:discuss-plan",
+    "description": "Multi-round collaborative planning using Gemini, Codex, and Claude synthesis with iterative discussion cycles (read-only, no code changes)",
+    "arguments": "[--topic '...'] [--task-id '...'] [--rounds N]",
+    "category": "cli",
+    "subcategory": null,
+    "usage_scenario": "planning",
+    "difficulty": "Intermediate",
+    "file_path": "cli/discuss-plan.md"
+  },
+  {
+    "name": "execute",
+    "command": "/cli:execute",
+    "description": "Autonomous code implementation with YOLO auto-approval using Gemini/Qwen/Codex, supports task ID or description input with automatic file pattern detection",
+    "arguments": "[--agent] [--tool codex|gemini|qwen] [--enhance] description or task-id",
+    "category": "cli",
+    "subcategory": null,
+    "usage_scenario": "implementation",
+    "difficulty": "Intermediate",
+    "file_path": "cli/execute.md"
+  },
+  {
+    "name": "bug-diagnosis",
+    "command": "/cli:mode:bug-diagnosis",
+    "description": "Read-only bug root cause analysis using Gemini/Qwen/Codex with systematic diagnosis template for fix suggestions",
+    "arguments": "[--agent] [--tool codex|gemini|qwen] [--enhance] [--cd path] bug description",
+    "category": "cli",
+    "subcategory": "mode",
+    "usage_scenario": "analysis",
+    "difficulty": "Intermediate",
+    "file_path": "cli/mode/bug-diagnosis.md"
+  },
+  {
+    "name": "code-analysis",
+    "command": "/cli:mode:code-analysis",
+    "description": "Read-only execution path tracing using Gemini/Qwen/Codex with specialized analysis template for call flow and optimization",
+    "arguments": "[--agent] [--tool codex|gemini|qwen] [--enhance] [--cd path] analysis target",
+    "category": "cli",
+    "subcategory": "mode",
+    "usage_scenario": "general",
+    "difficulty": "Intermediate",
+    "file_path": "cli/mode/code-analysis.md"
+  },
+  {
+    "name": "plan",
+    "command": "/cli:mode:plan",
+    "description": "Read-only architecture planning using Gemini/Qwen/Codex with strategic planning template for modification plans and impact analysis",
+    "arguments": "[--agent] [--tool codex|gemini|qwen] [--enhance] [--cd path] topic",
+    "category": "cli",
+    "subcategory": "mode",
+    "usage_scenario": "planning",
+    "difficulty": "Intermediate",
+    "file_path": "cli/mode/plan.md"
+  },
+  {
+    "name": "enhance-prompt",
+    "command": "/enhance-prompt",
+    "description": "Enhanced prompt transformation using session memory and codebase analysis with --enhance flag detection",
+    "arguments": "user input to enhance",
+    "category": "general",
+    "subcategory": null,
+    "usage_scenario": "general",
+    "difficulty": "Intermediate",
+    "file_path": "enhance-prompt.md"
+  },
+  {
+    "name": "docs",
+    "command": "/memory:docs",
+    "description": "Plan documentation workflow with dynamic grouping (≤10 docs/task), generates IMPL tasks for parallel module trees, README, ARCHITECTURE, and HTTP API docs",
+    "arguments": "[path] [--tool <gemini|qwen|codex>] [--mode <full|partial>] [--cli-execute]",
+    "category": "memory",
+    "subcategory": null,
+    "usage_scenario": "documentation",
+    "difficulty": "Intermediate",
+    "file_path": "memory/docs.md"
+  },
+  {
+    "name": "load-skill-memory",
+    "command": "/memory:load-skill-memory",
+    "description": "Activate SKILL package (auto-detect from paths/keywords or manual) and intelligently load documentation based on task intent keywords",
+    "arguments": "[skill_name] \\\"task intent description\\",
+    "category": "memory",
+    "subcategory": null,
+    "usage_scenario": "documentation",
+    "difficulty": "Intermediate",
+    "file_path": "memory/load-skill-memory.md"
+  },
+  {
+    "name": "load",
+    "command": "/memory:load",
+    "description": "Delegate to universal-executor agent to analyze project via Gemini/Qwen CLI and return JSON core content package for task context",
+    "arguments": "[--tool gemini|qwen] \\\"task context description\\",
+    "category": "memory",
+    "subcategory": null,
+    "usage_scenario": "general",
+    "difficulty": "Intermediate",
+    "file_path": "memory/load.md"
+  },
+  {
+    "name": "skill-memory",
+    "command": "/memory:skill-memory",
+    "description": "4-phase autonomous orchestrator: check docs → /memory:docs planning → /workflow:execute → generate SKILL.md with progressive loading index (skips phases 2-3 if docs exist)",
+    "arguments": "[path] [--tool <gemini|qwen|codex>] [--regenerate] [--mode <full|partial>] [--cli-execute]",
+    "category": "memory",
+    "subcategory": null,
+    "usage_scenario": "documentation",
+    "difficulty": "Intermediate",
+    "file_path": "memory/skill-memory.md"
+  },
+  {
+    "name": "tech-research",
+    "command": "/memory:tech-research",
+    "description": "3-phase orchestrator: extract tech stack from session/name → delegate to agent for Exa research and module generation → generate SKILL.md index (skips phase 2 if exists)",
+    "arguments": "[session-id | tech-stack-name] [--regenerate] [--tool <gemini|qwen>]",
+    "category": "memory",
+    "subcategory": null,
+    "usage_scenario": "general",
+    "difficulty": "Intermediate",
+    "file_path": "memory/tech-research.md"
+  },
+  {
+    "name": "update-full",
+    "command": "/memory:update-full",
+    "description": "Update all CLAUDE.md files using layer-based execution (Layer 3→1) with batched agents (4 modules/agent) and gemini→qwen→codex fallback, <20 modules uses direct parallel",
+    "arguments": "[--tool gemini|qwen|codex] [--path <directory>]",
+    "category": "memory",
+    "subcategory": null,
+    "usage_scenario": "general",
+    "difficulty": "Intermediate",
+    "file_path": "memory/update-full.md"
+  },
+  {
+    "name": "update-related",
+    "command": "/memory:update-related",
+    "description": "Update CLAUDE.md for git-changed modules using batched agent execution (4 modules/agent) with gemini→qwen→codex fallback, <15 modules uses direct execution",
+    "arguments": "[--tool gemini|qwen|codex]",
+    "category": "memory",
+    "subcategory": null,
+    "usage_scenario": "general",
+    "difficulty": "Intermediate",
+    "file_path": "memory/update-related.md"
+  },
+  {
+    "name": "workflow-skill-memory",
+    "command": "/memory:workflow-skill-memory",
+    "description": "Process WFS-* archived sessions using universal-executor agents with Gemini analysis to generate workflow-progress SKILL package (sessions-timeline, lessons, conflicts)",
+    "arguments": "session <session-id> | all",
+    "category": "memory",
+    "subcategory": null,
+    "usage_scenario": "documentation",
+    "difficulty": "Intermediate",
+    "file_path": "memory/workflow-skill-memory.md"
+  },
+  {
+    "name": "breakdown",
+    "command": "/task:breakdown",
+    "description": "Decompose complex task into subtasks with dependency mapping, creates child task JSONs with parent references and execution order",
+    "arguments": "task-id",
+    "category": "task",
+    "subcategory": null,
+    "usage_scenario": "planning",
+    "difficulty": "Intermediate",
+    "file_path": "task/breakdown.md"
+  },
+  {
+    "name": "create",
+    "command": "/task:create",
+    "description": "Generate task JSON from natural language description with automatic file pattern detection, scope inference, and dependency analysis",
+    "arguments": "\\\"task title\\",
+    "category": "task",
+    "subcategory": null,
+    "usage_scenario": "implementation",
+    "difficulty": "Intermediate",
+    "file_path": "task/create.md"
+  },
+  {
+    "name": "execute",
+    "command": "/task:execute",
+    "description": "Execute task JSON using appropriate agent (@doc-generator/@implementation-agent/@test-agent) with pre-analysis context loading and status tracking",
+    "arguments": "task-id",
+    "category": "task",
+    "subcategory": null,
+    "usage_scenario": "implementation",
+    "difficulty": "Intermediate",
+    "file_path": "task/execute.md"
+  },
+  {
+    "name": "replan",
+    "command": "/task:replan",
+    "description": "Update task JSON with new requirements or batch-update multiple tasks from verification report, tracks changes in task-changes.json",
+    "arguments": "task-id [\\\"text\\\"|file.md] | --batch [verification-report.md]",
+    "category": "task",
+    "subcategory": null,
+    "usage_scenario": "planning",
+    "difficulty": "Intermediate",
+    "file_path": "task/replan.md"
+  },
+  {
+    "name": "version",
+    "command": "/version",
+    "description": "Display Claude Code version information and check for updates",
+    "arguments": "",
+    "category": "general",
+    "subcategory": null,
+    "usage_scenario": "general",
+    "difficulty": "Beginner",
+    "file_path": "version.md"
+  },
+  {
+    "name": "action-plan-verify",
+    "command": "/workflow:action-plan-verify",
+    "description": "Perform non-destructive cross-artifact consistency analysis between IMPL_PLAN.md and task JSONs with quality gate validation",
+    "arguments": "[optional: --session session-id]",
+    "category": "workflow",
+    "subcategory": null,
+    "usage_scenario": "planning",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/action-plan-verify.md"
+  },
+  {
+    "name": "api-designer",
+    "command": "/workflow:brainstorm:api-designer",
+    "description": "Generate or update api-designer/analysis.md addressing guidance-specification discussion points for API design perspective",
+    "arguments": "optional topic - uses existing framework if available",
+    "category": "workflow",
+    "subcategory": "brainstorm",
+    "usage_scenario": "planning",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/brainstorm/api-designer.md"
+  },
+  {
+    "name": "artifacts",
+    "command": "/workflow:brainstorm:artifacts",
+    "description": "Interactive clarification generating confirmed guidance specification through role-based analysis and synthesis",
+    "arguments": "topic or challenge description [--count N]",
+    "category": "workflow",
+    "subcategory": "brainstorm",
+    "usage_scenario": "general",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/brainstorm/artifacts.md"
+  },
+  {
+    "name": "auto-parallel",
+    "command": "/workflow:brainstorm:auto-parallel",
+    "description": "Parallel brainstorming automation with dynamic role selection and concurrent execution across multiple perspectives",
+    "arguments": "topic or challenge description\" [--count N]",
+    "category": "workflow",
+    "subcategory": "brainstorm",
+    "usage_scenario": "general",
+    "difficulty": "Advanced",
+    "file_path": "workflow/brainstorm/auto-parallel.md"
+  },
+  {
+    "name": "data-architect",
+    "command": "/workflow:brainstorm:data-architect",
+    "description": "Generate or update data-architect/analysis.md addressing guidance-specification discussion points for data architecture perspective",
+    "arguments": "optional topic - uses existing framework if available",
+    "category": "workflow",
+    "subcategory": "brainstorm",
+    "usage_scenario": "general",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/brainstorm/data-architect.md"
+  },
+  {
+    "name": "product-manager",
+    "command": "/workflow:brainstorm:product-manager",
+    "description": "Generate or update product-manager/analysis.md addressing guidance-specification discussion points for product management perspective",
+    "arguments": "optional topic - uses existing framework if available",
+    "category": "workflow",
+    "subcategory": "brainstorm",
+    "usage_scenario": "general",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/brainstorm/product-manager.md"
+  },
+  {
+    "name": "product-owner",
+    "command": "/workflow:brainstorm:product-owner",
+    "description": "Generate or update product-owner/analysis.md addressing guidance-specification discussion points for product ownership perspective",
+    "arguments": "optional topic - uses existing framework if available",
+    "category": "workflow",
+    "subcategory": "brainstorm",
+    "usage_scenario": "general",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/brainstorm/product-owner.md"
+  },
+  {
+    "name": "scrum-master",
+    "command": "/workflow:brainstorm:scrum-master",
+    "description": "Generate or update scrum-master/analysis.md addressing guidance-specification discussion points for Agile process perspective",
+    "arguments": "optional topic - uses existing framework if available",
+    "category": "workflow",
+    "subcategory": "brainstorm",
+    "usage_scenario": "general",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/brainstorm/scrum-master.md"
+  },
+  {
+    "name": "subject-matter-expert",
+    "command": "/workflow:brainstorm:subject-matter-expert",
+    "description": "Generate or update subject-matter-expert/analysis.md addressing guidance-specification discussion points for domain expertise perspective",
+    "arguments": "optional topic - uses existing framework if available",
+    "category": "workflow",
+    "subcategory": "brainstorm",
+    "usage_scenario": "general",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/brainstorm/subject-matter-expert.md"
+  },
+  {
+    "name": "synthesis",
+    "command": "/workflow:brainstorm:synthesis",
+    "description": "Clarify and refine role analyses through intelligent Q&A and targeted updates with synthesis agent",
+    "arguments": "[optional: --session session-id]",
+    "category": "workflow",
+    "subcategory": "brainstorm",
+    "usage_scenario": "general",
+    "difficulty": "Advanced",
+    "file_path": "workflow/brainstorm/synthesis.md"
+  },
+  {
+    "name": "system-architect",
+    "command": "/workflow:brainstorm:system-architect",
+    "description": "Generate or update system-architect/analysis.md addressing guidance-specification discussion points for system architecture perspective",
+    "arguments": "optional topic - uses existing framework if available",
+    "category": "workflow",
+    "subcategory": "brainstorm",
+    "usage_scenario": "general",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/brainstorm/system-architect.md"
+  },
+  {
+    "name": "ui-designer",
+    "command": "/workflow:brainstorm:ui-designer",
+    "description": "Generate or update ui-designer/analysis.md addressing guidance-specification discussion points for UI design perspective",
+    "arguments": "optional topic - uses existing framework if available",
+    "category": "workflow",
+    "subcategory": "brainstorm",
+    "usage_scenario": "planning",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/brainstorm/ui-designer.md"
+  },
+  {
+    "name": "ux-expert",
+    "command": "/workflow:brainstorm:ux-expert",
+    "description": "Generate or update ux-expert/analysis.md addressing guidance-specification discussion points for UX perspective",
+    "arguments": "optional topic - uses existing framework if available",
+    "category": "workflow",
+    "subcategory": "brainstorm",
+    "usage_scenario": "general",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/brainstorm/ux-expert.md"
+  },
+  {
+    "name": "execute",
+    "command": "/workflow:execute",
+    "description": "Coordinate agent execution for workflow tasks with automatic session discovery, parallel task processing, and status tracking",
+    "arguments": "[--resume-session=\\\"session-id\\\"]",
+    "category": "workflow",
+    "subcategory": null,
+    "usage_scenario": "implementation",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/execute.md"
+  },
+  {
+    "name": "plan",
+    "command": "/workflow:plan",
+    "description": "5-phase planning workflow with Gemini analysis and action-planning-agent task generation, outputs IMPL_PLAN.md and task JSONs with optional CLI auto-execution",
+    "arguments": "[--agent] [--cli-execute] \\\"text description\\\"|file.md",
+    "category": "workflow",
+    "subcategory": null,
+    "usage_scenario": "planning",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/plan.md"
+  },
+  {
+    "name": "resume",
+    "command": "/workflow:resume",
+    "description": "Resume paused workflow session with automatic progress analysis, pending task identification, and conflict detection",
+    "arguments": "session-id for workflow session to resume",
+    "category": "workflow",
+    "subcategory": null,
+    "usage_scenario": "session-management",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/resume.md"
+  },
+  {
+    "name": "review",
+    "command": "/workflow:review",
+    "description": "Post-implementation review with specialized types (security/architecture/action-items/quality) using analysis agents and Gemini",
+    "arguments": "[--type=security|architecture|action-items|quality] [optional: session-id]",
+    "category": "workflow",
+    "subcategory": null,
+    "usage_scenario": "analysis",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/review.md"
+  },
+  {
+    "name": "complete",
+    "command": "/workflow:session:complete",
+    "description": "Mark active workflow session as complete, archive with lessons learned, update manifest, remove active flag",
+    "arguments": "",
+    "category": "workflow",
+    "subcategory": "session",
+    "usage_scenario": "session-management",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/session/complete.md"
+  },
+  {
+    "name": "list",
+    "command": "/workflow:session:list",
+    "description": "List all workflow sessions with status filtering, shows session metadata and progress information",
+    "arguments": "",
+    "category": "workflow",
+    "subcategory": "session",
+    "usage_scenario": "general",
+    "difficulty": "Beginner",
+    "file_path": "workflow/session/list.md"
+  },
+  {
+    "name": "resume",
+    "command": "/workflow:session:resume",
+    "description": "Resume the most recently paused workflow session with automatic session discovery and status update",
+    "arguments": "",
+    "category": "workflow",
+    "subcategory": "session",
+    "usage_scenario": "session-management",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/session/resume.md"
+  },
+  {
+    "name": "start",
+    "command": "/workflow:session:start",
+    "description": "Discover existing sessions or start new workflow session with intelligent session management and conflict detection",
+    "arguments": "[--auto|--new] [optional: task description for new session]",
+    "category": "workflow",
+    "subcategory": "session",
+    "usage_scenario": "general",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/session/start.md"
+  },
+  {
+    "name": "workflow:status",
+    "command": "/workflow:status",
+    "description": "Generate on-demand task status views from JSON task data with optional task-id filtering for detailed view",
+    "arguments": "[optional: task-id]",
+    "category": "workflow",
+    "subcategory": null,
+    "usage_scenario": "session-management",
+    "difficulty": "Beginner",
+    "file_path": "workflow/status.md"
+  },
+  {
+    "name": "tdd-plan",
+    "command": "/workflow:tdd-plan",
+    "description": "TDD workflow planning with Red-Green-Refactor task chain generation, test-first development structure, and cycle tracking",
+    "arguments": "[--agent] \\\"feature description\\\"|file.md",
+    "category": "workflow",
+    "subcategory": null,
+    "usage_scenario": "planning",
+    "difficulty": "Advanced",
+    "file_path": "workflow/tdd-plan.md"
+  },
+  {
+    "name": "tdd-verify",
+    "command": "/workflow:tdd-verify",
+    "description": "Verify TDD workflow compliance against Red-Green-Refactor cycles, generate quality report with coverage analysis",
+    "arguments": "[optional: WFS-session-id]",
+    "category": "workflow",
+    "subcategory": null,
+    "usage_scenario": "testing",
+    "difficulty": "Advanced",
+    "file_path": "workflow/tdd-verify.md"
+  },
+  {
+    "name": "test-cycle-execute",
+    "command": "/workflow:test-cycle-execute",
+    "description": "Execute test-fix workflow with dynamic task generation and iterative fix cycles until all tests pass or max iterations reached",
+    "arguments": "[--resume-session=\\\"session-id\\\"] [--max-iterations=N]",
+    "category": "workflow",
+    "subcategory": null,
+    "usage_scenario": "implementation",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/test-cycle-execute.md"
+  },
+  {
+    "name": "test-fix-gen",
+    "command": "/workflow:test-fix-gen",
+    "description": "Create test-fix workflow session from session ID, description, or file path with test strategy generation and task planning",
+    "arguments": "[--use-codex] [--cli-execute] (source-session-id | \\\"feature description\\\" | /path/to/file.md)",
+    "category": "workflow",
+    "subcategory": null,
+    "usage_scenario": "testing",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/test-fix-gen.md"
+  },
+  {
+    "name": "test-gen",
+    "command": "/workflow:test-gen",
+    "description": "Create independent test-fix workflow session from completed implementation session, analyzes code to generate test tasks",
+    "arguments": "[--use-codex] [--cli-execute] source-session-id",
+    "category": "workflow",
+    "subcategory": null,
+    "usage_scenario": "testing",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/test-gen.md"
+  },
+  {
+    "name": "conflict-resolution",
+    "command": "/workflow:tools:conflict-resolution",
+    "description": "Detect and resolve conflicts between plan and existing codebase using CLI-powered analysis with Gemini/Qwen",
+    "arguments": "--session WFS-session-id --context path/to/context-package.json",
+    "category": "workflow",
+    "subcategory": "tools",
+    "usage_scenario": "general",
+    "difficulty": "Advanced",
+    "file_path": "workflow/tools/conflict-resolution.md"
+  },
+  {
+    "name": "gather",
+    "command": "/workflow:tools:gather",
+    "description": "Intelligently collect project context using context-search-agent based on task description, packages into standardized JSON",
+    "arguments": "--session WFS-session-id \\\"task description\\",
+    "category": "workflow",
+    "subcategory": "tools",
+    "usage_scenario": "general",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/tools/context-gather.md"
+  },
+  {
+    "name": "task-generate-agent",
+    "command": "/workflow:tools:task-generate-agent",
+    "description": "Autonomous task generation using action-planning-agent with discovery and output phases for workflow planning",
+    "arguments": "--session WFS-session-id [--cli-execute]",
+    "category": "workflow",
+    "subcategory": "tools",
+    "usage_scenario": "implementation",
+    "difficulty": "Advanced",
+    "file_path": "workflow/tools/task-generate-agent.md"
+  },
+  {
+    "name": "task-generate-tdd",
+    "command": "/workflow:tools:task-generate-tdd",
+    "description": "Generate TDD task chains with Red-Green-Refactor dependencies, test-first structure, and cycle validation",
+    "arguments": "--session WFS-session-id [--agent]",
+    "category": "workflow",
+    "subcategory": "tools",
+    "usage_scenario": "implementation",
+    "difficulty": "Advanced",
+    "file_path": "workflow/tools/task-generate-tdd.md"
+  },
+  {
+    "name": "task-generate",
+    "command": "/workflow:tools:task-generate",
+    "description": "Generate task JSON files and IMPL_PLAN.md from analysis results using action-planning-agent with artifact integration",
+    "arguments": "--session WFS-session-id [--cli-execute]",
+    "category": "workflow",
+    "subcategory": "tools",
+    "usage_scenario": "implementation",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/tools/task-generate.md"
+  },
+  {
+    "name": "tdd-coverage-analysis",
+    "command": "/workflow:tools:tdd-coverage-analysis",
+    "description": "Analyze test coverage and TDD cycle execution with Red-Green-Refactor compliance verification",
+    "arguments": "--session WFS-session-id",
+    "category": "workflow",
+    "subcategory": "tools",
+    "usage_scenario": "testing",
+    "difficulty": "Advanced",
+    "file_path": "workflow/tools/tdd-coverage-analysis.md"
+  },
+  {
+    "name": "test-concept-enhanced",
+    "command": "/workflow:tools:test-concept-enhanced",
+    "description": "Analyze test requirements and generate test generation strategy using Gemini with test-context package",
+    "arguments": "--session WFS-test-session-id --context path/to/test-context-package.json",
+    "category": "workflow",
+    "subcategory": "tools",
+    "usage_scenario": "testing",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/tools/test-concept-enhanced.md"
+  },
+  {
+    "name": "test-context-gather",
+    "command": "/workflow:tools:test-context-gather",
+    "description": "Collect test coverage context using test-context-search-agent and package into standardized test-context JSON",
+    "arguments": "--session WFS-test-session-id",
+    "category": "workflow",
+    "subcategory": "tools",
+    "usage_scenario": "testing",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/tools/test-context-gather.md"
+  },
+  {
+    "name": "test-task-generate",
+    "command": "/workflow:tools:test-task-generate",
+    "description": "Generate test-fix task JSON with iterative test-fix-retest cycle specification using Gemini/Qwen/Codex",
+    "arguments": "[--use-codex] [--cli-execute] --session WFS-test-session-id",
+    "category": "workflow",
+    "subcategory": "tools",
+    "usage_scenario": "implementation",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/tools/test-task-generate.md"
+  },
+  {
+    "name": "animation-extract",
+    "command": "/workflow:ui-design:animation-extract",
+    "description": "Extract animation and transition patterns from URLs, CSS, or interactive questioning for design system documentation",
+    "arguments": "[--base-path <path>] [--session <id>] [--urls \"<list>\"] [--mode <auto|interactive>] [--focus \"<types>\"]",
+    "category": "workflow",
+    "subcategory": "ui-design",
+    "usage_scenario": "general",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/ui-design/animation-extract.md"
+  },
+  {
+    "name": "batch-generate",
+    "command": "/workflow:ui-design:batch-generate",
+    "description": "Prompt-driven batch UI generation using target-style-centric parallel execution with design token application",
+    "arguments": "[--targets \"<list>\"] [--target-type \"page|component\"] [--device-type \"desktop|mobile|tablet|responsive\"] [--base-path <path>] [--session <id>] [--style-variants <count>] [--layout-variants <count>]",
+    "category": "workflow",
+    "subcategory": "ui-design",
+    "usage_scenario": "implementation",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/ui-design/batch-generate.md"
+  },
+  {
+    "name": "capture",
+    "command": "/workflow:ui-design:capture",
+    "description": "Batch screenshot capture for UI design workflows using MCP puppeteer or local fallback with URL mapping",
+    "arguments": "--url-map \"target:url,...\" [--base-path path] [--session id]",
+    "category": "workflow",
+    "subcategory": "ui-design",
+    "usage_scenario": "general",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/ui-design/capture.md"
+  },
+  {
+    "name": "explore-auto",
+    "command": "/workflow:ui-design:explore-auto",
+    "description": "Exploratory UI design workflow with style-centric batch generation, creates design variants from prompts/images with parallel execution",
+    "arguments": "[--prompt \"<desc>\"] [--images \"<glob>\"] [--targets \"<list>\"] [--target-type \"page|component\"] [--session <id>] [--style-variants <count>] [--layout-variants <count>] [--batch-plan]",
+    "category": "workflow",
+    "subcategory": "ui-design",
+    "usage_scenario": "general",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/ui-design/explore-auto.md"
+  },
+  {
+    "name": "explore-layers",
+    "command": "/workflow:ui-design:explore-layers",
+    "description": "Interactive deep UI capture with depth-controlled layer exploration using MCP puppeteer",
+    "arguments": "--url <url> --depth <1-5> [--session id] [--base-path path]",
+    "category": "workflow",
+    "subcategory": "ui-design",
+    "usage_scenario": "general",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/ui-design/explore-layers.md"
+  },
+  {
+    "name": "generate",
+    "command": "/workflow:ui-design:generate",
+    "description": "Assemble UI prototypes by combining layout templates with design tokens, pure assembler without new content generation",
+    "arguments": "[--base-path <path>] [--session <id>] [--style-variants <count>] [--layout-variants <count>]",
+    "category": "workflow",
+    "subcategory": "ui-design",
+    "usage_scenario": "implementation",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/ui-design/generate.md"
+  },
+  {
+    "name": "imitate-auto",
+    "command": "/workflow:ui-design:imitate-auto",
+    "description": "High-speed multi-page UI replication with batch screenshot capture and design token extraction",
+    "arguments": "--url-map \"<map>\" [--capture-mode <batch|deep>] [--depth <1-5>] [--session <id>] [--prompt \"<desc>\"]",
+    "category": "workflow",
+    "subcategory": "ui-design",
+    "usage_scenario": "general",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/ui-design/imitate-auto.md"
+  },
+  {
+    "name": "workflow:ui-design:import-from-code",
+    "command": "/workflow:ui-design:import-from-code",
+    "description": "Import design system from code files (CSS/JS/HTML/SCSS) using parallel agent analysis with final synthesis",
+    "arguments": "[--base-path <path>] [--css \\\"<glob>\\\"] [--js \\\"<glob>\\\"] [--scss \\\"<glob>\\\"] [--html \\\"<glob>\\\"] [--style-files \\\"<glob>\\\"] [--session <id>]",
+    "category": "workflow",
+    "subcategory": "ui-design",
+    "usage_scenario": "planning",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/ui-design/import-from-code.md"
+  },
+  {
+    "name": "layout-extract",
+    "command": "/workflow:ui-design:layout-extract",
+    "description": "Extract structural layout information from reference images, URLs, or text prompts using Claude analysis",
+    "arguments": "[--base-path <path>] [--session <id>] [--images \"<glob>\"] [--urls \"<list>\"] [--prompt \"<desc>\"] [--targets \"<list>\"] [--mode <imitate|explore>] [--variants <count>] [--device-type <desktop|mobile|tablet|responsive>]",
+    "category": "workflow",
+    "subcategory": "ui-design",
+    "usage_scenario": "general",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/ui-design/layout-extract.md"
+  },
+  {
+    "name": "style-extract",
+    "command": "/workflow:ui-design:style-extract",
+    "description": "Extract design style from reference images or text prompts using Claude analysis with variant generation",
+    "arguments": "[--base-path <path>] [--session <id>] [--images \"<glob>\"] [--urls \"<list>\"] [--prompt \"<desc>\"] [--mode <imitate|explore>] [--variants <count>]",
+    "category": "workflow",
+    "subcategory": "ui-design",
+    "usage_scenario": "general",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/ui-design/style-extract.md"
+  },
+  {
+    "name": "update",
+    "command": "/workflow:ui-design:update",
+    "description": "Update brainstorming artifacts with finalized design system references from selected prototypes",
+    "arguments": "--session <session_id> [--selected-prototypes \"<list>\"]",
+    "category": "workflow",
+    "subcategory": "ui-design",
+    "usage_scenario": "general",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/ui-design/update.md"
+  }
+]

.claude/skills/command-guide/index/by-category.json

@@ -0,0 +1,802 @@
+{
+  "cli": {
+    "_root": [
+      {
+        "name": "analyze",
+        "command": "/cli:analyze",
+        "description": "Read-only codebase analysis using Gemini (default), Qwen, or Codex with auto-pattern detection and template selection",
+        "arguments": "[--agent] [--tool codex|gemini|qwen] [--enhance] analysis target",
+        "category": "cli",
+        "subcategory": null,
+        "usage_scenario": "analysis",
+        "difficulty": "Beginner",
+        "file_path": "cli/analyze.md"
+      },
+      {
+        "name": "chat",
+        "command": "/cli:chat",
+        "description": "Read-only Q&A interaction with Gemini/Qwen/Codex for codebase questions with automatic context inference",
+        "arguments": "[--agent] [--tool codex|gemini|qwen] [--enhance] inquiry",
+        "category": "cli",
+        "subcategory": null,
+        "usage_scenario": "general",
+        "difficulty": "Beginner",
+        "file_path": "cli/chat.md"
+      },
+      {
+        "name": "cli-init",
+        "command": "/cli:cli-init",
+        "description": "Generate .gemini/ and .qwen/ config directories with settings.json and ignore files based on workspace technology detection",
+        "arguments": "[--tool gemini|qwen|all] [--output path] [--preview]",
+        "category": "cli",
+        "subcategory": null,
+        "usage_scenario": "general",
+        "difficulty": "Intermediate",
+        "file_path": "cli/cli-init.md"
+      },
+      {
+        "name": "codex-execute",
+        "command": "/cli:codex-execute",
+        "description": "Multi-stage Codex execution with automatic task decomposition into grouped subtasks using resume mechanism for context continuity",
+        "arguments": "[--verify-git] task description or task-id",
+        "category": "cli",
+        "subcategory": null,
+        "usage_scenario": "implementation",
+        "difficulty": "Intermediate",
+        "file_path": "cli/codex-execute.md"
+      },
+      {
+        "name": "discuss-plan",
+        "command": "/cli:discuss-plan",
+        "description": "Multi-round collaborative planning using Gemini, Codex, and Claude synthesis with iterative discussion cycles (read-only, no code changes)",
+        "arguments": "[--topic '...'] [--task-id '...'] [--rounds N]",
+        "category": "cli",
+        "subcategory": null,
+        "usage_scenario": "planning",
+        "difficulty": "Intermediate",
+        "file_path": "cli/discuss-plan.md"
+      },
+      {
+        "name": "execute",
+        "command": "/cli:execute",
+        "description": "Autonomous code implementation with YOLO auto-approval using Gemini/Qwen/Codex, supports task ID or description input with automatic file pattern detection",
+        "arguments": "[--agent] [--tool codex|gemini|qwen] [--enhance] description or task-id",
+        "category": "cli",
+        "subcategory": null,
+        "usage_scenario": "implementation",
+        "difficulty": "Intermediate",
+        "file_path": "cli/execute.md"
+      }
+    ],
+    "mode": [
+      {
+        "name": "bug-diagnosis",
+        "command": "/cli:mode:bug-diagnosis",
+        "description": "Read-only bug root cause analysis using Gemini/Qwen/Codex with systematic diagnosis template for fix suggestions",
+        "arguments": "[--agent] [--tool codex|gemini|qwen] [--enhance] [--cd path] bug description",
+        "category": "cli",
+        "subcategory": "mode",
+        "usage_scenario": "analysis",
+        "difficulty": "Intermediate",
+        "file_path": "cli/mode/bug-diagnosis.md"
+      },
+      {
+        "name": "code-analysis",
+        "command": "/cli:mode:code-analysis",
+        "description": "Read-only execution path tracing using Gemini/Qwen/Codex with specialized analysis template for call flow and optimization",
+        "arguments": "[--agent] [--tool codex|gemini|qwen] [--enhance] [--cd path] analysis target",
+        "category": "cli",
+        "subcategory": "mode",
+        "usage_scenario": "general",
+        "difficulty": "Intermediate",
+        "file_path": "cli/mode/code-analysis.md"
+      },
+      {
+        "name": "plan",
+        "command": "/cli:mode:plan",
+        "description": "Read-only architecture planning using Gemini/Qwen/Codex with strategic planning template for modification plans and impact analysis",
+        "arguments": "[--agent] [--tool codex|gemini|qwen] [--enhance] [--cd path] topic",
+        "category": "cli",
+        "subcategory": "mode",
+        "usage_scenario": "planning",
+        "difficulty": "Intermediate",
+        "file_path": "cli/mode/plan.md"
+      }
+    ]
+  },
+  "general": {
+    "_root": [
+      {
+        "name": "enhance-prompt",
+        "command": "/enhance-prompt",
+        "description": "Enhanced prompt transformation using session memory and codebase analysis with --enhance flag detection",
+        "arguments": "user input to enhance",
+        "category": "general",
+        "subcategory": null,
+        "usage_scenario": "general",
+        "difficulty": "Intermediate",
+        "file_path": "enhance-prompt.md"
+      },
+      {
+        "name": "version",
+        "command": "/version",
+        "description": "Display Claude Code version information and check for updates",
+        "arguments": "",
+        "category": "general",
+        "subcategory": null,
+        "usage_scenario": "general",
+        "difficulty": "Beginner",
+        "file_path": "version.md"
+      }
+    ]
+  },
+  "memory": {
+    "_root": [
+      {
+        "name": "docs",
+        "command": "/memory:docs",
+        "description": "Plan documentation workflow with dynamic grouping (≤10 docs/task), generates IMPL tasks for parallel module trees, README, ARCHITECTURE, and HTTP API docs",
+        "arguments": "[path] [--tool <gemini|qwen|codex>] [--mode <full|partial>] [--cli-execute]",
+        "category": "memory",
+        "subcategory": null,
+        "usage_scenario": "documentation",
+        "difficulty": "Intermediate",
+        "file_path": "memory/docs.md"
+      },
+      {
+        "name": "load-skill-memory",
+        "command": "/memory:load-skill-memory",
+        "description": "Activate SKILL package (auto-detect from paths/keywords or manual) and intelligently load documentation based on task intent keywords",
+        "arguments": "[skill_name] \\\"task intent description\\",
+        "category": "memory",
+        "subcategory": null,
+        "usage_scenario": "documentation",
+        "difficulty": "Intermediate",
+        "file_path": "memory/load-skill-memory.md"
+      },
+      {
+        "name": "load",
+        "command": "/memory:load",
+        "description": "Delegate to universal-executor agent to analyze project via Gemini/Qwen CLI and return JSON core content package for task context",
+        "arguments": "[--tool gemini|qwen] \\\"task context description\\",
+        "category": "memory",
+        "subcategory": null,
+        "usage_scenario": "general",
+        "difficulty": "Intermediate",
+        "file_path": "memory/load.md"
+      },
+      {
+        "name": "skill-memory",
+        "command": "/memory:skill-memory",
+        "description": "4-phase autonomous orchestrator: check docs → /memory:docs planning → /workflow:execute → generate SKILL.md with progressive loading index (skips phases 2-3 if docs exist)",
+        "arguments": "[path] [--tool <gemini|qwen|codex>] [--regenerate] [--mode <full|partial>] [--cli-execute]",
+        "category": "memory",
+        "subcategory": null,
+        "usage_scenario": "documentation",
+        "difficulty": "Intermediate",
+        "file_path": "memory/skill-memory.md"
+      },
+      {
+        "name": "tech-research",
+        "command": "/memory:tech-research",
+        "description": "3-phase orchestrator: extract tech stack from session/name → delegate to agent for Exa research and module generation → generate SKILL.md index (skips phase 2 if exists)",
+        "arguments": "[session-id | tech-stack-name] [--regenerate] [--tool <gemini|qwen>]",
+        "category": "memory",
+        "subcategory": null,
+        "usage_scenario": "general",
+        "difficulty": "Intermediate",
+        "file_path": "memory/tech-research.md"
+      },
+      {
+        "name": "update-full",
+        "command": "/memory:update-full",
+        "description": "Update all CLAUDE.md files using layer-based execution (Layer 3→1) with batched agents (4 modules/agent) and gemini→qwen→codex fallback, <20 modules uses direct parallel",
+        "arguments": "[--tool gemini|qwen|codex] [--path <directory>]",
+        "category": "memory",
+        "subcategory": null,
+        "usage_scenario": "general",
+        "difficulty": "Intermediate",
+        "file_path": "memory/update-full.md"
+      },
+      {
+        "name": "update-related",
+        "command": "/memory:update-related",
+        "description": "Update CLAUDE.md for git-changed modules using batched agent execution (4 modules/agent) with gemini→qwen→codex fallback, <15 modules uses direct execution",
+        "arguments": "[--tool gemini|qwen|codex]",
+        "category": "memory",
+        "subcategory": null,
+        "usage_scenario": "general",
+        "difficulty": "Intermediate",
+        "file_path": "memory/update-related.md"
+      },
+      {
+        "name": "workflow-skill-memory",
+        "command": "/memory:workflow-skill-memory",
+        "description": "Process WFS-* archived sessions using universal-executor agents with Gemini analysis to generate workflow-progress SKILL package (sessions-timeline, lessons, conflicts)",
+        "arguments": "session <session-id> | all",
+        "category": "memory",
+        "subcategory": null,
+        "usage_scenario": "documentation",
+        "difficulty": "Intermediate",
+        "file_path": "memory/workflow-skill-memory.md"
+      }
+    ]
+  },
+  "task": {
+    "_root": [
+      {
+        "name": "breakdown",
+        "command": "/task:breakdown",
+        "description": "Decompose complex task into subtasks with dependency mapping, creates child task JSONs with parent references and execution order",
+        "arguments": "task-id",
+        "category": "task",
+        "subcategory": null,
+        "usage_scenario": "planning",
+        "difficulty": "Intermediate",
+        "file_path": "task/breakdown.md"
+      },
+      {
+        "name": "create",
+        "command": "/task:create",
+        "description": "Generate task JSON from natural language description with automatic file pattern detection, scope inference, and dependency analysis",
+        "arguments": "\\\"task title\\",
+        "category": "task",
+        "subcategory": null,
+        "usage_scenario": "implementation",
+        "difficulty": "Intermediate",
+        "file_path": "task/create.md"
+      },
+      {
+        "name": "execute",
+        "command": "/task:execute",
+        "description": "Execute task JSON using appropriate agent (@doc-generator/@implementation-agent/@test-agent) with pre-analysis context loading and status tracking",
+        "arguments": "task-id",
+        "category": "task",
+        "subcategory": null,
+        "usage_scenario": "implementation",
+        "difficulty": "Intermediate",
+        "file_path": "task/execute.md"
+      },
+      {
+        "name": "replan",
+        "command": "/task:replan",
+        "description": "Update task JSON with new requirements or batch-update multiple tasks from verification report, tracks changes in task-changes.json",
+        "arguments": "task-id [\\\"text\\\"|file.md] | --batch [verification-report.md]",
+        "category": "task",
+        "subcategory": null,
+        "usage_scenario": "planning",
+        "difficulty": "Intermediate",
+        "file_path": "task/replan.md"
+      }
+    ]
+  },
+  "workflow": {
+    "_root": [
+      {
+        "name": "action-plan-verify",
+        "command": "/workflow:action-plan-verify",
+        "description": "Perform non-destructive cross-artifact consistency analysis between IMPL_PLAN.md and task JSONs with quality gate validation",
+        "arguments": "[optional: --session session-id]",
+        "category": "workflow",
+        "subcategory": null,
+        "usage_scenario": "planning",
+        "difficulty": "Intermediate",
+        "file_path": "workflow/action-plan-verify.md"
+      },
+      {
+        "name": "execute",
+        "command": "/workflow:execute",
+        "description": "Coordinate agent execution for workflow tasks with automatic session discovery, parallel task processing, and status tracking",
+        "arguments": "[--resume-session=\\\"session-id\\\"]",
+        "category": "workflow",
+        "subcategory": null,
+        "usage_scenario": "implementation",
+        "difficulty": "Intermediate",
+        "file_path": "workflow/execute.md"
+      },
+      {
+        "name": "plan",
+        "command": "/workflow:plan",
+        "description": "5-phase planning workflow with Gemini analysis and action-planning-agent task generation, outputs IMPL_PLAN.md and task JSONs with optional CLI auto-execution",
+        "arguments": "[--agent] [--cli-execute] \\\"text description\\\"|file.md",
+        "category": "workflow",
+        "subcategory": null,
+        "usage_scenario": "planning",
+        "difficulty": "Intermediate",
+        "file_path": "workflow/plan.md"
+      },
+      {
+        "name": "resume",
+        "command": "/workflow:resume",
+        "description": "Resume paused workflow session with automatic progress analysis, pending task identification, and conflict detection",
+        "arguments": "session-id for workflow session to resume",
+        "category": "workflow",
+        "subcategory": null,
+        "usage_scenario": "session-management",
+        "difficulty": "Intermediate",
+        "file_path": "workflow/resume.md"
+      },
+      {
+        "name": "review",
+        "command": "/workflow:review",
+        "description": "Post-implementation review with specialized types (security/architecture/action-items/quality) using analysis agents and Gemini",
+        "arguments": "[--type=security|architecture|action-items|quality] [optional: session-id]",
+        "category": "workflow",
+        "subcategory": null,
+        "usage_scenario": "analysis",
+        "difficulty": "Intermediate",
+        "file_path": "workflow/review.md"
+      },
+      {
+        "name": "workflow:status",
+        "command": "/workflow:status",
+        "description": "Generate on-demand task status views from JSON task data with optional task-id filtering for detailed view",
+        "arguments": "[optional: task-id]",
+        "category": "workflow",
+        "subcategory": null,
+        "usage_scenario": "session-management",
+        "difficulty": "Beginner",
+        "file_path": "workflow/status.md"
+      },
+      {
+        "name": "tdd-plan",
+        "command": "/workflow:tdd-plan",
+        "description": "TDD workflow planning with Red-Green-Refactor task chain generation, test-first development structure, and cycle tracking",
+        "arguments": "[--agent] \\\"feature description\\\"|file.md",
+        "category": "workflow",
+        "subcategory": null,
+        "usage_scenario": "planning",
+        "difficulty": "Advanced",
+        "file_path": "workflow/tdd-plan.md"
+      },
+      {
+        "name": "tdd-verify",
+        "command": "/workflow:tdd-verify",
+        "description": "Verify TDD workflow compliance against Red-Green-Refactor cycles, generate quality report with coverage analysis",
+        "arguments": "[optional: WFS-session-id]",
+        "category": "workflow",
+        "subcategory": null,
+        "usage_scenario": "testing",
+        "difficulty": "Advanced",
+        "file_path": "workflow/tdd-verify.md"
+      },
+      {
+        "name": "test-cycle-execute",
+        "command": "/workflow:test-cycle-execute",
+        "description": "Execute test-fix workflow with dynamic task generation and iterative fix cycles until all tests pass or max iterations reached",
+        "arguments": "[--resume-session=\\\"session-id\\\"] [--max-iterations=N]",
+        "category": "workflow",
+        "subcategory": null,
+        "usage_scenario": "implementation",
+        "difficulty": "Intermediate",
+        "file_path": "workflow/test-cycle-execute.md"
+      },
+      {
+        "name": "test-fix-gen",
+        "command": "/workflow:test-fix-gen",
+        "description": "Create test-fix workflow session from session ID, description, or file path with test strategy generation and task planning",
+        "arguments": "[--use-codex] [--cli-execute] (source-session-id | \\\"feature description\\\" | /path/to/file.md)",
+        "category": "workflow",
+        "subcategory": null,
+        "usage_scenario": "testing",
+        "difficulty": "Intermediate",
+        "file_path": "workflow/test-fix-gen.md"
+      },
+      {
+        "name": "test-gen",
+        "command": "/workflow:test-gen",
+        "description": "Create independent test-fix workflow session from completed implementation session, analyzes code to generate test tasks",
+        "arguments": "[--use-codex] [--cli-execute] source-session-id",
+        "category": "workflow",
+        "subcategory": null,
+        "usage_scenario": "testing",
+        "difficulty": "Intermediate",
+        "file_path": "workflow/test-gen.md"
+      }
+    ],
+    "brainstorm": [
+      {
+        "name": "api-designer",
+        "command": "/workflow:brainstorm:api-designer",
+        "description": "Generate or update api-designer/analysis.md addressing guidance-specification discussion points for API design perspective",
+        "arguments": "optional topic - uses existing framework if available",
+        "category": "workflow",
+        "subcategory": "brainstorm",
+        "usage_scenario": "planning",
+        "difficulty": "Intermediate",
+        "file_path": "workflow/brainstorm/api-designer.md"
+      },
+      {
+        "name": "artifacts",
+        "command": "/workflow:brainstorm:artifacts",
+        "description": "Interactive clarification generating confirmed guidance specification through role-based analysis and synthesis",
+        "arguments": "topic or challenge description [--count N]",
+        "category": "workflow",
+        "subcategory": "brainstorm",
+        "usage_scenario": "general",
+        "difficulty": "Intermediate",
+        "file_path": "workflow/brainstorm/artifacts.md"
+      },
+      {
+        "name": "auto-parallel",
+        "command": "/workflow:brainstorm:auto-parallel",
+        "description": "Parallel brainstorming automation with dynamic role selection and concurrent execution across multiple perspectives",
+        "arguments": "topic or challenge description\" [--count N]",
+        "category": "workflow",
+        "subcategory": "brainstorm",
+        "usage_scenario": "general",
+        "difficulty": "Advanced",
+        "file_path": "workflow/brainstorm/auto-parallel.md"
+      },
+      {
+        "name": "data-architect",
+        "command": "/workflow:brainstorm:data-architect",
+        "description": "Generate or update data-architect/analysis.md addressing guidance-specification discussion points for data architecture perspective",
+        "arguments": "optional topic - uses existing framework if available",
+        "category": "workflow",
+        "subcategory": "brainstorm",
+        "usage_scenario": "general",
+        "difficulty": "Intermediate",
+        "file_path": "workflow/brainstorm/data-architect.md"
+      },
+      {
+        "name": "product-manager",
+        "command": "/workflow:brainstorm:product-manager",
+        "description": "Generate or update product-manager/analysis.md addressing guidance-specification discussion points for product management perspective",
+        "arguments": "optional topic - uses existing framework if available",
+        "category": "workflow",
+        "subcategory": "brainstorm",
+        "usage_scenario": "general",
+        "difficulty": "Intermediate",
+        "file_path": "workflow/brainstorm/product-manager.md"
+      },
+      {
+        "name": "product-owner",
+        "command": "/workflow:brainstorm:product-owner",
+        "description": "Generate or update product-owner/analysis.md addressing guidance-specification discussion points for product ownership perspective",
+        "arguments": "optional topic - uses existing framework if available",
+        "category": "workflow",
+        "subcategory": "brainstorm",
+        "usage_scenario": "general",
+        "difficulty": "Intermediate",
+        "file_path": "workflow/brainstorm/product-owner.md"
+      },
+      {
+        "name": "scrum-master",
+        "command": "/workflow:brainstorm:scrum-master",
+        "description": "Generate or update scrum-master/analysis.md addressing guidance-specification discussion points for Agile process perspective",
+        "arguments": "optional topic - uses existing framework if available",
+        "category": "workflow",
+        "subcategory": "brainstorm",
+        "usage_scenario": "general",
+        "difficulty": "Intermediate",
+        "file_path": "workflow/brainstorm/scrum-master.md"
+      },
+      {
+        "name": "subject-matter-expert",
+        "command": "/workflow:brainstorm:subject-matter-expert",
+        "description": "Generate or update subject-matter-expert/analysis.md addressing guidance-specification discussion points for domain expertise perspective",
+        "arguments": "optional topic - uses existing framework if available",
+        "category": "workflow",
+        "subcategory": "brainstorm",
+        "usage_scenario": "general",
+        "difficulty": "Intermediate",
+        "file_path": "workflow/brainstorm/subject-matter-expert.md"
+      },
+      {
+        "name": "synthesis",
+        "command": "/workflow:brainstorm:synthesis",
+        "description": "Clarify and refine role analyses through intelligent Q&A and targeted updates with synthesis agent",
+        "arguments": "[optional: --session session-id]",
+        "category": "workflow",
+        "subcategory": "brainstorm",
+        "usage_scenario": "general",
+        "difficulty": "Advanced",
+        "file_path": "workflow/brainstorm/synthesis.md"
+      },
+      {
+        "name": "system-architect",
+        "command": "/workflow:brainstorm:system-architect",
+        "description": "Generate or update system-architect/analysis.md addressing guidance-specification discussion points for system architecture perspective",
+        "arguments": "optional topic - uses existing framework if available",
+        "category": "workflow",
+        "subcategory": "brainstorm",
+        "usage_scenario": "general",
+        "difficulty": "Intermediate",
+        "file_path": "workflow/brainstorm/system-architect.md"
+      },
+      {
+        "name": "ui-designer",
+        "command": "/workflow:brainstorm:ui-designer",
+        "description": "Generate or update ui-designer/analysis.md addressing guidance-specification discussion points for UI design perspective",
+        "arguments": "optional topic - uses existing framework if available",
+        "category": "workflow",
+        "subcategory": "brainstorm",
+        "usage_scenario": "planning",
+        "difficulty": "Intermediate",
+        "file_path": "workflow/brainstorm/ui-designer.md"
+      },
+      {
+        "name": "ux-expert",
+        "command": "/workflow:brainstorm:ux-expert",
+        "description": "Generate or update ux-expert/analysis.md addressing guidance-specification discussion points for UX perspective",
+        "arguments": "optional topic - uses existing framework if available",
+        "category": "workflow",
+        "subcategory": "brainstorm",
+        "usage_scenario": "general",
+        "difficulty": "Intermediate",
+        "file_path": "workflow/brainstorm/ux-expert.md"
+      }
+    ],
+    "session": [
+      {
+        "name": "complete",
+        "command": "/workflow:session:complete",
+        "description": "Mark active workflow session as complete, archive with lessons learned, update manifest, remove active flag",
+        "arguments": "",
+        "category": "workflow",
+        "subcategory": "session",
+        "usage_scenario": "session-management",
+        "difficulty": "Intermediate",
+        "file_path": "workflow/session/complete.md"
+      },
+      {
+        "name": "list",
+        "command": "/workflow:session:list",
+        "description": "List all workflow sessions with status filtering, shows session metadata and progress information",
+        "arguments": "",
+        "category": "workflow",
+        "subcategory": "session",
+        "usage_scenario": "general",
+        "difficulty": "Beginner",
+        "file_path": "workflow/session/list.md"
+      },
+      {
+        "name": "resume",
+        "command": "/workflow:session:resume",
+        "description": "Resume the most recently paused workflow session with automatic session discovery and status update",
+        "arguments": "",
+        "category": "workflow",
+        "subcategory": "session",
+        "usage_scenario": "session-management",
+        "difficulty": "Intermediate",
+        "file_path": "workflow/session/resume.md"
+      },
+      {
+        "name": "start",
+        "command": "/workflow:session:start",
+        "description": "Discover existing sessions or start new workflow session with intelligent session management and conflict detection",
+        "arguments": "[--auto|--new] [optional: task description for new session]",
+        "category": "workflow",
+        "subcategory": "session",
+        "usage_scenario": "general",
+        "difficulty": "Intermediate",
+        "file_path": "workflow/session/start.md"
+      }
+    ],
+    "tools": [
+      {
+        "name": "conflict-resolution",
+        "command": "/workflow:tools:conflict-resolution",
+        "description": "Detect and resolve conflicts between plan and existing codebase using CLI-powered analysis with Gemini/Qwen",
+        "arguments": "--session WFS-session-id --context path/to/context-package.json",
+        "category": "workflow",
+        "subcategory": "tools",
+        "usage_scenario": "general",
+        "difficulty": "Advanced",
+        "file_path": "workflow/tools/conflict-resolution.md"
+      },
+      {
+        "name": "gather",
+        "command": "/workflow:tools:gather",
+        "description": "Intelligently collect project context using context-search-agent based on task description, packages into standardized JSON",
+        "arguments": "--session WFS-session-id \\\"task description\\",
+        "category": "workflow",
+        "subcategory": "tools",
+        "usage_scenario": "general",
+        "difficulty": "Intermediate",
+        "file_path": "workflow/tools/context-gather.md"
+      },
+      {
+        "name": "task-generate-agent",
+        "command": "/workflow:tools:task-generate-agent",
+        "description": "Autonomous task generation using action-planning-agent with discovery and output phases for workflow planning",
+        "arguments": "--session WFS-session-id [--cli-execute]",
+        "category": "workflow",
+        "subcategory": "tools",
+        "usage_scenario": "implementation",
+        "difficulty": "Advanced",
+        "file_path": "workflow/tools/task-generate-agent.md"
+      },
+      {
+        "name": "task-generate-tdd",
+        "command": "/workflow:tools:task-generate-tdd",
+        "description": "Generate TDD task chains with Red-Green-Refactor dependencies, test-first structure, and cycle validation",
+        "arguments": "--session WFS-session-id [--agent]",
+        "category": "workflow",
+        "subcategory": "tools",
+        "usage_scenario": "implementation",
+        "difficulty": "Advanced",
+        "file_path": "workflow/tools/task-generate-tdd.md"
+      },
+      {
+        "name": "task-generate",
+        "command": "/workflow:tools:task-generate",
+        "description": "Generate task JSON files and IMPL_PLAN.md from analysis results using action-planning-agent with artifact integration",
+        "arguments": "--session WFS-session-id [--cli-execute]",
+        "category": "workflow",
+        "subcategory": "tools",
+        "usage_scenario": "implementation",
+        "difficulty": "Intermediate",
+        "file_path": "workflow/tools/task-generate.md"
+      },
+      {
+        "name": "tdd-coverage-analysis",
+        "command": "/workflow:tools:tdd-coverage-analysis",
+        "description": "Analyze test coverage and TDD cycle execution with Red-Green-Refactor compliance verification",
+        "arguments": "--session WFS-session-id",
+        "category": "workflow",
+        "subcategory": "tools",
+        "usage_scenario": "testing",
+        "difficulty": "Advanced",
+        "file_path": "workflow/tools/tdd-coverage-analysis.md"
+      },
+      {
+        "name": "test-concept-enhanced",
+        "command": "/workflow:tools:test-concept-enhanced",
+        "description": "Analyze test requirements and generate test generation strategy using Gemini with test-context package",
+        "arguments": "--session WFS-test-session-id --context path/to/test-context-package.json",
+        "category": "workflow",
+        "subcategory": "tools",
+        "usage_scenario": "testing",
+        "difficulty": "Intermediate",
+        "file_path": "workflow/tools/test-concept-enhanced.md"
+      },
+      {
+        "name": "test-context-gather",
+        "command": "/workflow:tools:test-context-gather",
+        "description": "Collect test coverage context using test-context-search-agent and package into standardized test-context JSON",
+        "arguments": "--session WFS-test-session-id",
+        "category": "workflow",
+        "subcategory": "tools",
+        "usage_scenario": "testing",
+        "difficulty": "Intermediate",
+        "file_path": "workflow/tools/test-context-gather.md"
+      },
+      {
+        "name": "test-task-generate",
+        "command": "/workflow:tools:test-task-generate",
+        "description": "Generate test-fix task JSON with iterative test-fix-retest cycle specification using Gemini/Qwen/Codex",
+        "arguments": "[--use-codex] [--cli-execute] --session WFS-test-session-id",
+        "category": "workflow",
+        "subcategory": "tools",
+        "usage_scenario": "implementation",
+        "difficulty": "Intermediate",
+        "file_path": "workflow/tools/test-task-generate.md"
+      }
+    ],
+    "ui-design": [
+      {
+        "name": "animation-extract",
+        "command": "/workflow:ui-design:animation-extract",
+        "description": "Extract animation and transition patterns from URLs, CSS, or interactive questioning for design system documentation",
+        "arguments": "[--base-path <path>] [--session <id>] [--urls \"<list>\"] [--mode <auto|interactive>] [--focus \"<types>\"]",
+        "category": "workflow",
+        "subcategory": "ui-design",
+        "usage_scenario": "general",
+        "difficulty": "Intermediate",
+        "file_path": "workflow/ui-design/animation-extract.md"
+      },
+      {
+        "name": "batch-generate",
+        "command": "/workflow:ui-design:batch-generate",
+        "description": "Prompt-driven batch UI generation using target-style-centric parallel execution with design token application",
+        "arguments": "[--targets \"<list>\"] [--target-type \"page|component\"] [--device-type \"desktop|mobile|tablet|responsive\"] [--base-path <path>] [--session <id>] [--style-variants <count>] [--layout-variants <count>]",
+        "category": "workflow",
+        "subcategory": "ui-design",
+        "usage_scenario": "implementation",
+        "difficulty": "Intermediate",
+        "file_path": "workflow/ui-design/batch-generate.md"
+      },
+      {
+        "name": "capture",
+        "command": "/workflow:ui-design:capture",
+        "description": "Batch screenshot capture for UI design workflows using MCP puppeteer or local fallback with URL mapping",
+        "arguments": "--url-map \"target:url,...\" [--base-path path] [--session id]",
+        "category": "workflow",
+        "subcategory": "ui-design",
+        "usage_scenario": "general",
+        "difficulty": "Intermediate",
+        "file_path": "workflow/ui-design/capture.md"
+      },
+      {
+        "name": "explore-auto",
+        "command": "/workflow:ui-design:explore-auto",
+        "description": "Exploratory UI design workflow with style-centric batch generation, creates design variants from prompts/images with parallel execution",
+        "arguments": "[--prompt \"<desc>\"] [--images \"<glob>\"] [--targets \"<list>\"] [--target-type \"page|component\"] [--session <id>] [--style-variants <count>] [--layout-variants <count>] [--batch-plan]",
+        "category": "workflow",
+        "subcategory": "ui-design",
+        "usage_scenario": "general",
+        "difficulty": "Intermediate",
+        "file_path": "workflow/ui-design/explore-auto.md"
+      },
+      {
+        "name": "explore-layers",
+        "command": "/workflow:ui-design:explore-layers",
+        "description": "Interactive deep UI capture with depth-controlled layer exploration using MCP puppeteer",
+        "arguments": "--url <url> --depth <1-5> [--session id] [--base-path path]",
+        "category": "workflow",
+        "subcategory": "ui-design",
+        "usage_scenario": "general",
+        "difficulty": "Intermediate",
+        "file_path": "workflow/ui-design/explore-layers.md"
+      },
+      {
+        "name": "generate",
+        "command": "/workflow:ui-design:generate",
+        "description": "Assemble UI prototypes by combining layout templates with design tokens, pure assembler without new content generation",
+        "arguments": "[--base-path <path>] [--session <id>] [--style-variants <count>] [--layout-variants <count>]",
+        "category": "workflow",
+        "subcategory": "ui-design",
+        "usage_scenario": "implementation",
+        "difficulty": "Intermediate",
+        "file_path": "workflow/ui-design/generate.md"
+      },
+      {
+        "name": "imitate-auto",
+        "command": "/workflow:ui-design:imitate-auto",
+        "description": "High-speed multi-page UI replication with batch screenshot capture and design token extraction",
+        "arguments": "--url-map \"<map>\" [--capture-mode <batch|deep>] [--depth <1-5>] [--session <id>] [--prompt \"<desc>\"]",
+        "category": "workflow",
+        "subcategory": "ui-design",
+        "usage_scenario": "general",
+        "difficulty": "Intermediate",
+        "file_path": "workflow/ui-design/imitate-auto.md"
+      },
+      {
+        "name": "workflow:ui-design:import-from-code",
+        "command": "/workflow:ui-design:import-from-code",
+        "description": "Import design system from code files (CSS/JS/HTML/SCSS) using parallel agent analysis with final synthesis",
+        "arguments": "[--base-path <path>] [--css \\\"<glob>\\\"] [--js \\\"<glob>\\\"] [--scss \\\"<glob>\\\"] [--html \\\"<glob>\\\"] [--style-files \\\"<glob>\\\"] [--session <id>]",
+        "category": "workflow",
+        "subcategory": "ui-design",
+        "usage_scenario": "planning",
+        "difficulty": "Intermediate",
+        "file_path": "workflow/ui-design/import-from-code.md"
+      },
+      {
+        "name": "layout-extract",
+        "command": "/workflow:ui-design:layout-extract",
+        "description": "Extract structural layout information from reference images, URLs, or text prompts using Claude analysis",
+        "arguments": "[--base-path <path>] [--session <id>] [--images \"<glob>\"] [--urls \"<list>\"] [--prompt \"<desc>\"] [--targets \"<list>\"] [--mode <imitate|explore>] [--variants <count>] [--device-type <desktop|mobile|tablet|responsive>]",
+        "category": "workflow",
+        "subcategory": "ui-design",
+        "usage_scenario": "general",
+        "difficulty": "Intermediate",
+        "file_path": "workflow/ui-design/layout-extract.md"
+      },
+      {
+        "name": "style-extract",
+        "command": "/workflow:ui-design:style-extract",
+        "description": "Extract design style from reference images or text prompts using Claude analysis with variant generation",
+        "arguments": "[--base-path <path>] [--session <id>] [--images \"<glob>\"] [--urls \"<list>\"] [--prompt \"<desc>\"] [--mode <imitate|explore>] [--variants <count>]",
+        "category": "workflow",
+        "subcategory": "ui-design",
+        "usage_scenario": "general",
+        "difficulty": "Intermediate",
+        "file_path": "workflow/ui-design/style-extract.md"
+      },
+      {
+        "name": "update",
+        "command": "/workflow:ui-design:update",
+        "description": "Update brainstorming artifacts with finalized design system references from selected prototypes",
+        "arguments": "--session <session_id> [--selected-prototypes \"<list>\"]",
+        "category": "workflow",
+        "subcategory": "ui-design",
+        "usage_scenario": "general",
+        "difficulty": "Intermediate",
+        "file_path": "workflow/ui-design/update.md"
+      }
+    ]
+  }
+}

.claude/skills/command-guide/index/by-use-case.json

@@ -0,0 +1,786 @@
+{
+  "analysis": [
+    {
+      "name": "analyze",
+      "command": "/cli:analyze",
+      "description": "Read-only codebase analysis using Gemini (default), Qwen, or Codex with auto-pattern detection and template selection",
+      "arguments": "[--agent] [--tool codex|gemini|qwen] [--enhance] analysis target",
+      "category": "cli",
+      "subcategory": null,
+      "usage_scenario": "analysis",
+      "difficulty": "Beginner",
+      "file_path": "cli/analyze.md"
+    },
+    {
+      "name": "bug-diagnosis",
+      "command": "/cli:mode:bug-diagnosis",
+      "description": "Read-only bug root cause analysis using Gemini/Qwen/Codex with systematic diagnosis template for fix suggestions",
+      "arguments": "[--agent] [--tool codex|gemini|qwen] [--enhance] [--cd path] bug description",
+      "category": "cli",
+      "subcategory": "mode",
+      "usage_scenario": "analysis",
+      "difficulty": "Intermediate",
+      "file_path": "cli/mode/bug-diagnosis.md"
+    },
+    {
+      "name": "review",
+      "command": "/workflow:review",
+      "description": "Post-implementation review with specialized types (security/architecture/action-items/quality) using analysis agents and Gemini",
+      "arguments": "[--type=security|architecture|action-items|quality] [optional: session-id]",
+      "category": "workflow",
+      "subcategory": null,
+      "usage_scenario": "analysis",
+      "difficulty": "Intermediate",
+      "file_path": "workflow/review.md"
+    }
+  ],
+  "general": [
+    {
+      "name": "chat",
+      "command": "/cli:chat",
+      "description": "Read-only Q&A interaction with Gemini/Qwen/Codex for codebase questions with automatic context inference",
+      "arguments": "[--agent] [--tool codex|gemini|qwen] [--enhance] inquiry",
+      "category": "cli",
+      "subcategory": null,
+      "usage_scenario": "general",
+      "difficulty": "Beginner",
+      "file_path": "cli/chat.md"
+    },
+    {
+      "name": "cli-init",
+      "command": "/cli:cli-init",
+      "description": "Generate .gemini/ and .qwen/ config directories with settings.json and ignore files based on workspace technology detection",
+      "arguments": "[--tool gemini|qwen|all] [--output path] [--preview]",
+      "category": "cli",
+      "subcategory": null,
+      "usage_scenario": "general",
+      "difficulty": "Intermediate",
+      "file_path": "cli/cli-init.md"
+    },
+    {
+      "name": "code-analysis",
+      "command": "/cli:mode:code-analysis",
+      "description": "Read-only execution path tracing using Gemini/Qwen/Codex with specialized analysis template for call flow and optimization",
+      "arguments": "[--agent] [--tool codex|gemini|qwen] [--enhance] [--cd path] analysis target",
+      "category": "cli",
+      "subcategory": "mode",
+      "usage_scenario": "general",
+      "difficulty": "Intermediate",
+      "file_path": "cli/mode/code-analysis.md"
+    },
+    {
+      "name": "enhance-prompt",
+      "command": "/enhance-prompt",
+      "description": "Enhanced prompt transformation using session memory and codebase analysis with --enhance flag detection",
+      "arguments": "user input to enhance",
+      "category": "general",
+      "subcategory": null,
+      "usage_scenario": "general",
+      "difficulty": "Intermediate",
+      "file_path": "enhance-prompt.md"
+    },
+    {
+      "name": "load",
+      "command": "/memory:load",
+      "description": "Delegate to universal-executor agent to analyze project via Gemini/Qwen CLI and return JSON core content package for task context",
+      "arguments": "[--tool gemini|qwen] \\\"task context description\\",
+      "category": "memory",
+      "subcategory": null,
+      "usage_scenario": "general",
+      "difficulty": "Intermediate",
+      "file_path": "memory/load.md"
+    },
+    {
+      "name": "tech-research",
+      "command": "/memory:tech-research",
+      "description": "3-phase orchestrator: extract tech stack from session/name → delegate to agent for Exa research and module generation → generate SKILL.md index (skips phase 2 if exists)",
+      "arguments": "[session-id | tech-stack-name] [--regenerate] [--tool <gemini|qwen>]",
+      "category": "memory",
+      "subcategory": null,
+      "usage_scenario": "general",
+      "difficulty": "Intermediate",
+      "file_path": "memory/tech-research.md"
+    },
+    {
+      "name": "update-full",
+      "command": "/memory:update-full",
+      "description": "Update all CLAUDE.md files using layer-based execution (Layer 3→1) with batched agents (4 modules/agent) and gemini→qwen→codex fallback, <20 modules uses direct parallel",
+      "arguments": "[--tool gemini|qwen|codex] [--path <directory>]",
+      "category": "memory",
+      "subcategory": null,
+      "usage_scenario": "general",
+      "difficulty": "Intermediate",
+      "file_path": "memory/update-full.md"
+    },
+    {
+      "name": "update-related",
+      "command": "/memory:update-related",
+      "description": "Update CLAUDE.md for git-changed modules using batched agent execution (4 modules/agent) with gemini→qwen→codex fallback, <15 modules uses direct execution",
+      "arguments": "[--tool gemini|qwen|codex]",
+      "category": "memory",
+      "subcategory": null,
+      "usage_scenario": "general",
+      "difficulty": "Intermediate",
+      "file_path": "memory/update-related.md"
+    },
+    {
+      "name": "version",
+      "command": "/version",
+      "description": "Display Claude Code version information and check for updates",
+      "arguments": "",
+      "category": "general",
+      "subcategory": null,
+      "usage_scenario": "general",
+      "difficulty": "Beginner",
+      "file_path": "version.md"
+    },
+    {
+      "name": "artifacts",
+      "command": "/workflow:brainstorm:artifacts",
+      "description": "Interactive clarification generating confirmed guidance specification through role-based analysis and synthesis",
+      "arguments": "topic or challenge description [--count N]",
+      "category": "workflow",
+      "subcategory": "brainstorm",
+      "usage_scenario": "general",
+      "difficulty": "Intermediate",
+      "file_path": "workflow/brainstorm/artifacts.md"
+    },
+    {
+      "name": "auto-parallel",
+      "command": "/workflow:brainstorm:auto-parallel",
+      "description": "Parallel brainstorming automation with dynamic role selection and concurrent execution across multiple perspectives",
+      "arguments": "topic or challenge description\" [--count N]",
+      "category": "workflow",
+      "subcategory": "brainstorm",
+      "usage_scenario": "general",
+      "difficulty": "Advanced",
+      "file_path": "workflow/brainstorm/auto-parallel.md"
+    },
+    {
+      "name": "data-architect",
+      "command": "/workflow:brainstorm:data-architect",
+      "description": "Generate or update data-architect/analysis.md addressing guidance-specification discussion points for data architecture perspective",
+      "arguments": "optional topic - uses existing framework if available",
+      "category": "workflow",
+      "subcategory": "brainstorm",
+      "usage_scenario": "general",
+      "difficulty": "Intermediate",
+      "file_path": "workflow/brainstorm/data-architect.md"
+    },
+    {
+      "name": "product-manager",
+      "command": "/workflow:brainstorm:product-manager",
+      "description": "Generate or update product-manager/analysis.md addressing guidance-specification discussion points for product management perspective",
+      "arguments": "optional topic - uses existing framework if available",
+      "category": "workflow",
+      "subcategory": "brainstorm",
+      "usage_scenario": "general",
+      "difficulty": "Intermediate",
+      "file_path": "workflow/brainstorm/product-manager.md"
+    },
+    {
+      "name": "product-owner",
+      "command": "/workflow:brainstorm:product-owner",
+      "description": "Generate or update product-owner/analysis.md addressing guidance-specification discussion points for product ownership perspective",
+      "arguments": "optional topic - uses existing framework if available",
+      "category": "workflow",
+      "subcategory": "brainstorm",
+      "usage_scenario": "general",
+      "difficulty": "Intermediate",
+      "file_path": "workflow/brainstorm/product-owner.md"
+    },
+    {
+      "name": "scrum-master",
+      "command": "/workflow:brainstorm:scrum-master",
+      "description": "Generate or update scrum-master/analysis.md addressing guidance-specification discussion points for Agile process perspective",
+      "arguments": "optional topic - uses existing framework if available",
+      "category": "workflow",
+      "subcategory": "brainstorm",
+      "usage_scenario": "general",
+      "difficulty": "Intermediate",
+      "file_path": "workflow/brainstorm/scrum-master.md"
+    },
+    {
+      "name": "subject-matter-expert",
+      "command": "/workflow:brainstorm:subject-matter-expert",
+      "description": "Generate or update subject-matter-expert/analysis.md addressing guidance-specification discussion points for domain expertise perspective",
+      "arguments": "optional topic - uses existing framework if available",
+      "category": "workflow",
+      "subcategory": "brainstorm",
+      "usage_scenario": "general",
+      "difficulty": "Intermediate",
+      "file_path": "workflow/brainstorm/subject-matter-expert.md"
+    },
+    {
+      "name": "synthesis",
+      "command": "/workflow:brainstorm:synthesis",
+      "description": "Clarify and refine role analyses through intelligent Q&A and targeted updates with synthesis agent",
+      "arguments": "[optional: --session session-id]",
+      "category": "workflow",
+      "subcategory": "brainstorm",
+      "usage_scenario": "general",
+      "difficulty": "Advanced",
+      "file_path": "workflow/brainstorm/synthesis.md"
+    },
+    {
+      "name": "system-architect",
+      "command": "/workflow:brainstorm:system-architect",
+      "description": "Generate or update system-architect/analysis.md addressing guidance-specification discussion points for system architecture perspective",
+      "arguments": "optional topic - uses existing framework if available",
+      "category": "workflow",
+      "subcategory": "brainstorm",
+      "usage_scenario": "general",
+      "difficulty": "Intermediate",
+      "file_path": "workflow/brainstorm/system-architect.md"
+    },
+    {
+      "name": "ux-expert",
+      "command": "/workflow:brainstorm:ux-expert",
+      "description": "Generate or update ux-expert/analysis.md addressing guidance-specification discussion points for UX perspective",
+      "arguments": "optional topic - uses existing framework if available",
+      "category": "workflow",
+      "subcategory": "brainstorm",
+      "usage_scenario": "general",
+      "difficulty": "Intermediate",
+      "file_path": "workflow/brainstorm/ux-expert.md"
+    },
+    {
+      "name": "list",
+      "command": "/workflow:session:list",
+      "description": "List all workflow sessions with status filtering, shows session metadata and progress information",
+      "arguments": "",
+      "category": "workflow",
+      "subcategory": "session",
+      "usage_scenario": "general",
+      "difficulty": "Beginner",
+      "file_path": "workflow/session/list.md"
+    },
+    {
+      "name": "start",
+      "command": "/workflow:session:start",
+      "description": "Discover existing sessions or start new workflow session with intelligent session management and conflict detection",
+      "arguments": "[--auto|--new] [optional: task description for new session]",
+      "category": "workflow",
+      "subcategory": "session",
+      "usage_scenario": "general",
+      "difficulty": "Intermediate",
+      "file_path": "workflow/session/start.md"
+    },
+    {
+      "name": "conflict-resolution",
+      "command": "/workflow:tools:conflict-resolution",
+      "description": "Detect and resolve conflicts between plan and existing codebase using CLI-powered analysis with Gemini/Qwen",
+      "arguments": "--session WFS-session-id --context path/to/context-package.json",
+      "category": "workflow",
+      "subcategory": "tools",
+      "usage_scenario": "general",
+      "difficulty": "Advanced",
+      "file_path": "workflow/tools/conflict-resolution.md"
+    },
+    {
+      "name": "gather",
+      "command": "/workflow:tools:gather",
+      "description": "Intelligently collect project context using context-search-agent based on task description, packages into standardized JSON",
+      "arguments": "--session WFS-session-id \\\"task description\\",
+      "category": "workflow",
+      "subcategory": "tools",
+      "usage_scenario": "general",
+      "difficulty": "Intermediate",
+      "file_path": "workflow/tools/context-gather.md"
+    },
+    {
+      "name": "animation-extract",
+      "command": "/workflow:ui-design:animation-extract",
+      "description": "Extract animation and transition patterns from URLs, CSS, or interactive questioning for design system documentation",
+      "arguments": "[--base-path <path>] [--session <id>] [--urls \"<list>\"] [--mode <auto|interactive>] [--focus \"<types>\"]",
+      "category": "workflow",
+      "subcategory": "ui-design",
+      "usage_scenario": "general",
+      "difficulty": "Intermediate",
+      "file_path": "workflow/ui-design/animation-extract.md"
+    },
+    {
+      "name": "capture",
+      "command": "/workflow:ui-design:capture",
+      "description": "Batch screenshot capture for UI design workflows using MCP puppeteer or local fallback with URL mapping",
+      "arguments": "--url-map \"target:url,...\" [--base-path path] [--session id]",
+      "category": "workflow",
+      "subcategory": "ui-design",
+      "usage_scenario": "general",
+      "difficulty": "Intermediate",
+      "file_path": "workflow/ui-design/capture.md"
+    },
+    {
+      "name": "explore-auto",
+      "command": "/workflow:ui-design:explore-auto",
+      "description": "Exploratory UI design workflow with style-centric batch generation, creates design variants from prompts/images with parallel execution",
+      "arguments": "[--prompt \"<desc>\"] [--images \"<glob>\"] [--targets \"<list>\"] [--target-type \"page|component\"] [--session <id>] [--style-variants <count>] [--layout-variants <count>] [--batch-plan]",
+      "category": "workflow",
+      "subcategory": "ui-design",
+      "usage_scenario": "general",
+      "difficulty": "Intermediate",
+      "file_path": "workflow/ui-design/explore-auto.md"
+    },
+    {
+      "name": "explore-layers",
+      "command": "/workflow:ui-design:explore-layers",
+      "description": "Interactive deep UI capture with depth-controlled layer exploration using MCP puppeteer",
+      "arguments": "--url <url> --depth <1-5> [--session id] [--base-path path]",
+      "category": "workflow",
+      "subcategory": "ui-design",
+      "usage_scenario": "general",
+      "difficulty": "Intermediate",
+      "file_path": "workflow/ui-design/explore-layers.md"
+    },
+    {
+      "name": "imitate-auto",
+      "command": "/workflow:ui-design:imitate-auto",
+      "description": "High-speed multi-page UI replication with batch screenshot capture and design token extraction",
+      "arguments": "--url-map \"<map>\" [--capture-mode <batch|deep>] [--depth <1-5>] [--session <id>] [--prompt \"<desc>\"]",
+      "category": "workflow",
+      "subcategory": "ui-design",
+      "usage_scenario": "general",
+      "difficulty": "Intermediate",
+      "file_path": "workflow/ui-design/imitate-auto.md"
+    },
+    {
+      "name": "layout-extract",
+      "command": "/workflow:ui-design:layout-extract",
+      "description": "Extract structural layout information from reference images, URLs, or text prompts using Claude analysis",
+      "arguments": "[--base-path <path>] [--session <id>] [--images \"<glob>\"] [--urls \"<list>\"] [--prompt \"<desc>\"] [--targets \"<list>\"] [--mode <imitate|explore>] [--variants <count>] [--device-type <desktop|mobile|tablet|responsive>]",
+      "category": "workflow",
+      "subcategory": "ui-design",
+      "usage_scenario": "general",
+      "difficulty": "Intermediate",
+      "file_path": "workflow/ui-design/layout-extract.md"
+    },
+    {
+      "name": "style-extract",
+      "command": "/workflow:ui-design:style-extract",
+      "description": "Extract design style from reference images or text prompts using Claude analysis with variant generation",
+      "arguments": "[--base-path <path>] [--session <id>] [--images \"<glob>\"] [--urls \"<list>\"] [--prompt \"<desc>\"] [--mode <imitate|explore>] [--variants <count>]",
+      "category": "workflow",
+      "subcategory": "ui-design",
+      "usage_scenario": "general",
+      "difficulty": "Intermediate",
+      "file_path": "workflow/ui-design/style-extract.md"
+    },
+    {
+      "name": "update",
+      "command": "/workflow:ui-design:update",
+      "description": "Update brainstorming artifacts with finalized design system references from selected prototypes",
+      "arguments": "--session <session_id> [--selected-prototypes \"<list>\"]",
+      "category": "workflow",
+      "subcategory": "ui-design",
+      "usage_scenario": "general",
+      "difficulty": "Intermediate",
+      "file_path": "workflow/ui-design/update.md"
+    }
+  ],
+  "implementation": [
+    {
+      "name": "codex-execute",
+      "command": "/cli:codex-execute",
+      "description": "Multi-stage Codex execution with automatic task decomposition into grouped subtasks using resume mechanism for context continuity",
+      "arguments": "[--verify-git] task description or task-id",
+      "category": "cli",
+      "subcategory": null,
+      "usage_scenario": "implementation",
+      "difficulty": "Intermediate",
+      "file_path": "cli/codex-execute.md"
+    },
+    {
+      "name": "execute",
+      "command": "/cli:execute",
+      "description": "Autonomous code implementation with YOLO auto-approval using Gemini/Qwen/Codex, supports task ID or description input with automatic file pattern detection",
+      "arguments": "[--agent] [--tool codex|gemini|qwen] [--enhance] description or task-id",
+      "category": "cli",
+      "subcategory": null,
+      "usage_scenario": "implementation",
+      "difficulty": "Intermediate",
+      "file_path": "cli/execute.md"
+    },
+    {
+      "name": "create",
+      "command": "/task:create",
+      "description": "Generate task JSON from natural language description with automatic file pattern detection, scope inference, and dependency analysis",
+      "arguments": "\\\"task title\\",
+      "category": "task",
+      "subcategory": null,
+      "usage_scenario": "implementation",
+      "difficulty": "Intermediate",
+      "file_path": "task/create.md"
+    },
+    {
+      "name": "execute",
+      "command": "/task:execute",
+      "description": "Execute task JSON using appropriate agent (@doc-generator/@implementation-agent/@test-agent) with pre-analysis context loading and status tracking",
+      "arguments": "task-id",
+      "category": "task",
+      "subcategory": null,
+      "usage_scenario": "implementation",
+      "difficulty": "Intermediate",
+      "file_path": "task/execute.md"
+    },
+    {
+      "name": "execute",
+      "command": "/workflow:execute",
+      "description": "Coordinate agent execution for workflow tasks with automatic session discovery, parallel task processing, and status tracking",
+      "arguments": "[--resume-session=\\\"session-id\\\"]",
+      "category": "workflow",
+      "subcategory": null,
+      "usage_scenario": "implementation",
+      "difficulty": "Intermediate",
+      "file_path": "workflow/execute.md"
+    },
+    {
+      "name": "test-cycle-execute",
+      "command": "/workflow:test-cycle-execute",
+      "description": "Execute test-fix workflow with dynamic task generation and iterative fix cycles until all tests pass or max iterations reached",
+      "arguments": "[--resume-session=\\\"session-id\\\"] [--max-iterations=N]",
+      "category": "workflow",
+      "subcategory": null,
+      "usage_scenario": "implementation",
+      "difficulty": "Intermediate",
+      "file_path": "workflow/test-cycle-execute.md"
+    },
+    {
+      "name": "task-generate-agent",
+      "command": "/workflow:tools:task-generate-agent",
+      "description": "Autonomous task generation using action-planning-agent with discovery and output phases for workflow planning",
+      "arguments": "--session WFS-session-id [--cli-execute]",
+      "category": "workflow",
+      "subcategory": "tools",
+      "usage_scenario": "implementation",
+      "difficulty": "Advanced",
+      "file_path": "workflow/tools/task-generate-agent.md"
+    },
+    {
+      "name": "task-generate-tdd",
+      "command": "/workflow:tools:task-generate-tdd",
+      "description": "Generate TDD task chains with Red-Green-Refactor dependencies, test-first structure, and cycle validation",
+      "arguments": "--session WFS-session-id [--agent]",
+      "category": "workflow",
+      "subcategory": "tools",
+      "usage_scenario": "implementation",
+      "difficulty": "Advanced",
+      "file_path": "workflow/tools/task-generate-tdd.md"
+    },
+    {
+      "name": "task-generate",
+      "command": "/workflow:tools:task-generate",
+      "description": "Generate task JSON files and IMPL_PLAN.md from analysis results using action-planning-agent with artifact integration",
+      "arguments": "--session WFS-session-id [--cli-execute]",
+      "category": "workflow",
+      "subcategory": "tools",
+      "usage_scenario": "implementation",
+      "difficulty": "Intermediate",
+      "file_path": "workflow/tools/task-generate.md"
+    },
+    {
+      "name": "test-task-generate",
+      "command": "/workflow:tools:test-task-generate",
+      "description": "Generate test-fix task JSON with iterative test-fix-retest cycle specification using Gemini/Qwen/Codex",
+      "arguments": "[--use-codex] [--cli-execute] --session WFS-test-session-id",
+      "category": "workflow",
+      "subcategory": "tools",
+      "usage_scenario": "implementation",
+      "difficulty": "Intermediate",
+      "file_path": "workflow/tools/test-task-generate.md"
+    },
+    {
+      "name": "batch-generate",
+      "command": "/workflow:ui-design:batch-generate",
+      "description": "Prompt-driven batch UI generation using target-style-centric parallel execution with design token application",
+      "arguments": "[--targets \"<list>\"] [--target-type \"page|component\"] [--device-type \"desktop|mobile|tablet|responsive\"] [--base-path <path>] [--session <id>] [--style-variants <count>] [--layout-variants <count>]",
+      "category": "workflow",
+      "subcategory": "ui-design",
+      "usage_scenario": "implementation",
+      "difficulty": "Intermediate",
+      "file_path": "workflow/ui-design/batch-generate.md"
+    },
+    {
+      "name": "generate",
+      "command": "/workflow:ui-design:generate",
+      "description": "Assemble UI prototypes by combining layout templates with design tokens, pure assembler without new content generation",
+      "arguments": "[--base-path <path>] [--session <id>] [--style-variants <count>] [--layout-variants <count>]",
+      "category": "workflow",
+      "subcategory": "ui-design",
+      "usage_scenario": "implementation",
+      "difficulty": "Intermediate",
+      "file_path": "workflow/ui-design/generate.md"
+    }
+  ],
+  "planning": [
+    {
+      "name": "discuss-plan",
+      "command": "/cli:discuss-plan",
+      "description": "Multi-round collaborative planning using Gemini, Codex, and Claude synthesis with iterative discussion cycles (read-only, no code changes)",
+      "arguments": "[--topic '...'] [--task-id '...'] [--rounds N]",
+      "category": "cli",
+      "subcategory": null,
+      "usage_scenario": "planning",
+      "difficulty": "Intermediate",
+      "file_path": "cli/discuss-plan.md"
+    },
+    {
+      "name": "plan",
+      "command": "/cli:mode:plan",
+      "description": "Read-only architecture planning using Gemini/Qwen/Codex with strategic planning template for modification plans and impact analysis",
+      "arguments": "[--agent] [--tool codex|gemini|qwen] [--enhance] [--cd path] topic",
+      "category": "cli",
+      "subcategory": "mode",
+      "usage_scenario": "planning",
+      "difficulty": "Intermediate",
+      "file_path": "cli/mode/plan.md"
+    },
+    {
+      "name": "breakdown",
+      "command": "/task:breakdown",
+      "description": "Decompose complex task into subtasks with dependency mapping, creates child task JSONs with parent references and execution order",
+      "arguments": "task-id",
+      "category": "task",
+      "subcategory": null,
+      "usage_scenario": "planning",
+      "difficulty": "Intermediate",
+      "file_path": "task/breakdown.md"
+    },
+    {
+      "name": "replan",
+      "command": "/task:replan",
+      "description": "Update task JSON with new requirements or batch-update multiple tasks from verification report, tracks changes in task-changes.json",
+      "arguments": "task-id [\\\"text\\\"|file.md] | --batch [verification-report.md]",
+      "category": "task",
+      "subcategory": null,
+      "usage_scenario": "planning",
+      "difficulty": "Intermediate",
+      "file_path": "task/replan.md"
+    },
+    {
+      "name": "action-plan-verify",
+      "command": "/workflow:action-plan-verify",
+      "description": "Perform non-destructive cross-artifact consistency analysis between IMPL_PLAN.md and task JSONs with quality gate validation",
+      "arguments": "[optional: --session session-id]",
+      "category": "workflow",
+      "subcategory": null,
+      "usage_scenario": "planning",
+      "difficulty": "Intermediate",
+      "file_path": "workflow/action-plan-verify.md"
+    },
+    {
+      "name": "api-designer",
+      "command": "/workflow:brainstorm:api-designer",
+      "description": "Generate or update api-designer/analysis.md addressing guidance-specification discussion points for API design perspective",
+      "arguments": "optional topic - uses existing framework if available",
+      "category": "workflow",
+      "subcategory": "brainstorm",
+      "usage_scenario": "planning",
+      "difficulty": "Intermediate",
+      "file_path": "workflow/brainstorm/api-designer.md"
+    },
+    {
+      "name": "ui-designer",
+      "command": "/workflow:brainstorm:ui-designer",
+      "description": "Generate or update ui-designer/analysis.md addressing guidance-specification discussion points for UI design perspective",
+      "arguments": "optional topic - uses existing framework if available",
+      "category": "workflow",
+      "subcategory": "brainstorm",
+      "usage_scenario": "planning",
+      "difficulty": "Intermediate",
+      "file_path": "workflow/brainstorm/ui-designer.md"
+    },
+    {
+      "name": "plan",
+      "command": "/workflow:plan",
+      "description": "5-phase planning workflow with Gemini analysis and action-planning-agent task generation, outputs IMPL_PLAN.md and task JSONs with optional CLI auto-execution",
+      "arguments": "[--agent] [--cli-execute] \\\"text description\\\"|file.md",
+      "category": "workflow",
+      "subcategory": null,
+      "usage_scenario": "planning",
+      "difficulty": "Intermediate",
+      "file_path": "workflow/plan.md"
+    },
+    {
+      "name": "tdd-plan",
+      "command": "/workflow:tdd-plan",
+      "description": "TDD workflow planning with Red-Green-Refactor task chain generation, test-first development structure, and cycle tracking",
+      "arguments": "[--agent] \\\"feature description\\\"|file.md",
+      "category": "workflow",
+      "subcategory": null,
+      "usage_scenario": "planning",
+      "difficulty": "Advanced",
+      "file_path": "workflow/tdd-plan.md"
+    },
+    {
+      "name": "workflow:ui-design:import-from-code",
+      "command": "/workflow:ui-design:import-from-code",
+      "description": "Import design system from code files (CSS/JS/HTML/SCSS) using parallel agent analysis with final synthesis",
+      "arguments": "[--base-path <path>] [--css \\\"<glob>\\\"] [--js \\\"<glob>\\\"] [--scss \\\"<glob>\\\"] [--html \\\"<glob>\\\"] [--style-files \\\"<glob>\\\"] [--session <id>]",
+      "category": "workflow",
+      "subcategory": "ui-design",
+      "usage_scenario": "planning",
+      "difficulty": "Intermediate",
+      "file_path": "workflow/ui-design/import-from-code.md"
+    }
+  ],
+  "documentation": [
+    {
+      "name": "docs",
+      "command": "/memory:docs",
+      "description": "Plan documentation workflow with dynamic grouping (≤10 docs/task), generates IMPL tasks for parallel module trees, README, ARCHITECTURE, and HTTP API docs",
+      "arguments": "[path] [--tool <gemini|qwen|codex>] [--mode <full|partial>] [--cli-execute]",
+      "category": "memory",
+      "subcategory": null,
+      "usage_scenario": "documentation",
+      "difficulty": "Intermediate",
+      "file_path": "memory/docs.md"
+    },
+    {
+      "name": "load-skill-memory",
+      "command": "/memory:load-skill-memory",
+      "description": "Activate SKILL package (auto-detect from paths/keywords or manual) and intelligently load documentation based on task intent keywords",
+      "arguments": "[skill_name] \\\"task intent description\\",
+      "category": "memory",
+      "subcategory": null,
+      "usage_scenario": "documentation",
+      "difficulty": "Intermediate",
+      "file_path": "memory/load-skill-memory.md"
+    },
+    {
+      "name": "skill-memory",
+      "command": "/memory:skill-memory",
+      "description": "4-phase autonomous orchestrator: check docs → /memory:docs planning → /workflow:execute → generate SKILL.md with progressive loading index (skips phases 2-3 if docs exist)",
+      "arguments": "[path] [--tool <gemini|qwen|codex>] [--regenerate] [--mode <full|partial>] [--cli-execute]",
+      "category": "memory",
+      "subcategory": null,
+      "usage_scenario": "documentation",
+      "difficulty": "Intermediate",
+      "file_path": "memory/skill-memory.md"
+    },
+    {
+      "name": "workflow-skill-memory",
+      "command": "/memory:workflow-skill-memory",
+      "description": "Process WFS-* archived sessions using universal-executor agents with Gemini analysis to generate workflow-progress SKILL package (sessions-timeline, lessons, conflicts)",
+      "arguments": "session <session-id> | all",
+      "category": "memory",
+      "subcategory": null,
+      "usage_scenario": "documentation",
+      "difficulty": "Intermediate",
+      "file_path": "memory/workflow-skill-memory.md"
+    }
+  ],
+  "session-management": [
+    {
+      "name": "resume",
+      "command": "/workflow:resume",
+      "description": "Resume paused workflow session with automatic progress analysis, pending task identification, and conflict detection",
+      "arguments": "session-id for workflow session to resume",
+      "category": "workflow",
+      "subcategory": null,
+      "usage_scenario": "session-management",
+      "difficulty": "Intermediate",
+      "file_path": "workflow/resume.md"
+    },
+    {
+      "name": "complete",
+      "command": "/workflow:session:complete",
+      "description": "Mark active workflow session as complete, archive with lessons learned, update manifest, remove active flag",
+      "arguments": "",
+      "category": "workflow",
+      "subcategory": "session",
+      "usage_scenario": "session-management",
+      "difficulty": "Intermediate",
+      "file_path": "workflow/session/complete.md"
+    },
+    {
+      "name": "resume",
+      "command": "/workflow:session:resume",
+      "description": "Resume the most recently paused workflow session with automatic session discovery and status update",
+      "arguments": "",
+      "category": "workflow",
+      "subcategory": "session",
+      "usage_scenario": "session-management",
+      "difficulty": "Intermediate",
+      "file_path": "workflow/session/resume.md"
+    },
+    {
+      "name": "workflow:status",
+      "command": "/workflow:status",
+      "description": "Generate on-demand task status views from JSON task data with optional task-id filtering for detailed view",
+      "arguments": "[optional: task-id]",
+      "category": "workflow",
+      "subcategory": null,
+      "usage_scenario": "session-management",
+      "difficulty": "Beginner",
+      "file_path": "workflow/status.md"
+    }
+  ],
+  "testing": [
+    {
+      "name": "tdd-verify",
+      "command": "/workflow:tdd-verify",
+      "description": "Verify TDD workflow compliance against Red-Green-Refactor cycles, generate quality report with coverage analysis",
+      "arguments": "[optional: WFS-session-id]",
+      "category": "workflow",
+      "subcategory": null,
+      "usage_scenario": "testing",
+      "difficulty": "Advanced",
+      "file_path": "workflow/tdd-verify.md"
+    },
+    {
+      "name": "test-fix-gen",
+      "command": "/workflow:test-fix-gen",
+      "description": "Create test-fix workflow session from session ID, description, or file path with test strategy generation and task planning",
+      "arguments": "[--use-codex] [--cli-execute] (source-session-id | \\\"feature description\\\" | /path/to/file.md)",
+      "category": "workflow",
+      "subcategory": null,
+      "usage_scenario": "testing",
+      "difficulty": "Intermediate",
+      "file_path": "workflow/test-fix-gen.md"
+    },
+    {
+      "name": "test-gen",
+      "command": "/workflow:test-gen",
+      "description": "Create independent test-fix workflow session from completed implementation session, analyzes code to generate test tasks",
+      "arguments": "[--use-codex] [--cli-execute] source-session-id",
+      "category": "workflow",
+      "subcategory": null,
+      "usage_scenario": "testing",
+      "difficulty": "Intermediate",
+      "file_path": "workflow/test-gen.md"
+    },
+    {
+      "name": "tdd-coverage-analysis",
+      "command": "/workflow:tools:tdd-coverage-analysis",
+      "description": "Analyze test coverage and TDD cycle execution with Red-Green-Refactor compliance verification",
+      "arguments": "--session WFS-session-id",
+      "category": "workflow",
+      "subcategory": "tools",
+      "usage_scenario": "testing",
+      "difficulty": "Advanced",
+      "file_path": "workflow/tools/tdd-coverage-analysis.md"
+    },
+    {
+      "name": "test-concept-enhanced",
+      "command": "/workflow:tools:test-concept-enhanced",
+      "description": "Analyze test requirements and generate test generation strategy using Gemini with test-context package",
+      "arguments": "--session WFS-test-session-id --context path/to/test-context-package.json",
+      "category": "workflow",
+      "subcategory": "tools",
+      "usage_scenario": "testing",
+      "difficulty": "Intermediate",
+      "file_path": "workflow/tools/test-concept-enhanced.md"
+    },
+    {
+      "name": "test-context-gather",
+      "command": "/workflow:tools:test-context-gather",
+      "description": "Collect test coverage context using test-context-search-agent and package into standardized test-context JSON",
+      "arguments": "--session WFS-test-session-id",
+      "category": "workflow",
+      "subcategory": "tools",
+      "usage_scenario": "testing",
+      "difficulty": "Intermediate",
+      "file_path": "workflow/tools/test-context-gather.md"
+    }
+  ]
+}

.claude/skills/command-guide/index/command-relationships.json

@@ -0,0 +1,243 @@
+{
+  "workflow:plan": {
+    "calls_internally": [
+      "workflow:session:start",
+      "workflow:tools:context-gather",
+      "workflow:tools:conflict-resolution",
+      "workflow:tools:task-generate",
+      "workflow:tools:task-generate-agent"
+    ],
+    "next_steps": [
+      "workflow:action-plan-verify",
+      "workflow:status",
+      "workflow:execute"
+    ],
+    "alternatives": [
+      "workflow:tdd-plan"
+    ],
+    "prerequisites": []
+  },
+  "workflow:tdd-plan": {
+    "calls_internally": [
+      "workflow:session:start",
+      "workflow:tools:context-gather",
+      "workflow:tools:task-generate-tdd"
+    ],
+    "next_steps": [
+      "workflow:tdd-verify",
+      "workflow:status",
+      "workflow:execute"
+    ],
+    "alternatives": [
+      "workflow:plan"
+    ],
+    "prerequisites": []
+  },
+  "workflow:execute": {
+    "prerequisites": [
+      "workflow:plan",
+      "workflow:tdd-plan"
+    ],
+    "related": [
+      "workflow:status",
+      "workflow:resume"
+    ],
+    "next_steps": [
+      "workflow:review",
+      "workflow:tdd-verify"
+    ]
+  },
+  "workflow:action-plan-verify": {
+    "prerequisites": [
+      "workflow:plan"
+    ],
+    "next_steps": [
+      "workflow:execute"
+    ],
+    "related": [
+      "workflow:status"
+    ]
+  },
+  "workflow:tdd-verify": {
+    "prerequisites": [
+      "workflow:execute"
+    ],
+    "related": [
+      "workflow:tools:tdd-coverage-analysis"
+    ]
+  },
+  "workflow:session:start": {
+    "next_steps": [
+      "workflow:plan",
+      "workflow:execute"
+    ],
+    "related": [
+      "workflow:session:list",
+      "workflow:session:resume"
+    ]
+  },
+  "workflow:session:resume": {
+    "alternatives": [
+      "workflow:resume"
+    ],
+    "related": [
+      "workflow:session:list",
+      "workflow:status"
+    ]
+  },
+  "workflow:resume": {
+    "alternatives": [
+      "workflow:session:resume"
+    ],
+    "related": [
+      "workflow:status"
+    ]
+  },
+  "task:create": {
+    "next_steps": [
+      "task:execute"
+    ],
+    "related": [
+      "task:breakdown"
+    ]
+  },
+  "task:breakdown": {
+    "next_steps": [
+      "task:execute"
+    ],
+    "related": [
+      "task:create"
+    ]
+  },
+  "task:replan": {
+    "prerequisites": [
+      "workflow:plan"
+    ],
+    "related": [
+      "workflow:action-plan-verify"
+    ]
+  },
+  "task:execute": {
+    "prerequisites": [
+      "task:create",
+      "task:breakdown",
+      "workflow:plan"
+    ],
+    "related": [
+      "workflow:status"
+    ]
+  },
+  "memory:docs": {
+    "calls_internally": [
+      "workflow:session:start",
+      "workflow:tools:context-gather"
+    ],
+    "next_steps": [
+      "workflow:execute"
+    ]
+  },
+  "memory:skill-memory": {
+    "next_steps": [
+      "workflow:plan",
+      "cli:analyze"
+    ],
+    "related": [
+      "memory:load-skill-memory"
+    ]
+  },
+  "memory:workflow-skill-memory": {
+    "related": [
+      "memory:skill-memory"
+    ],
+    "next_steps": [
+      "workflow:plan"
+    ]
+  },
+  "cli:execute": {
+    "alternatives": [
+      "cli:codex-execute"
+    ],
+    "related": [
+      "cli:analyze",
+      "cli:chat"
+    ]
+  },
+  "cli:analyze": {
+    "related": [
+      "cli:chat",
+      "cli:mode:code-analysis"
+    ],
+    "next_steps": [
+      "cli:execute"
+    ]
+  },
+  "workflow:brainstorm:artifacts": {
+    "next_steps": [
+      "workflow:brainstorm:synthesis",
+      "workflow:plan"
+    ],
+    "related": [
+      "workflow:brainstorm:auto-parallel"
+    ]
+  },
+  "workflow:brainstorm:synthesis": {
+    "prerequisites": [
+      "workflow:brainstorm:artifacts"
+    ],
+    "next_steps": [
+      "workflow:plan"
+    ]
+  },
+  "workflow:brainstorm:auto-parallel": {
+    "next_steps": [
+      "workflow:brainstorm:synthesis",
+      "workflow:plan"
+    ],
+    "related": [
+      "workflow:brainstorm:artifacts"
+    ]
+  },
+  "workflow:test-gen": {
+    "prerequisites": [
+      "workflow:execute"
+    ],
+    "next_steps": [
+      "workflow:test-cycle-execute"
+    ]
+  },
+  "workflow:test-fix-gen": {
+    "alternatives": [
+      "workflow:test-gen"
+    ],
+    "next_steps": [
+      "workflow:test-cycle-execute"
+    ]
+  },
+  "workflow:test-cycle-execute": {
+    "prerequisites": [
+      "workflow:test-gen",
+      "workflow:test-fix-gen"
+    ],
+    "related": [
+      "workflow:tdd-verify"
+    ]
+  },
+  "workflow:ui-design:explore-auto": {
+    "calls_internally": [
+      "workflow:ui-design:capture",
+      "workflow:ui-design:style-extract",
+      "workflow:ui-design:layout-extract"
+    ],
+    "next_steps": [
+      "workflow:ui-design:generate"
+    ]
+  },
+  "workflow:ui-design:imitate-auto": {
+    "calls_internally": [
+      "workflow:ui-design:capture"
+    ],
+    "next_steps": [
+      "workflow:ui-design:generate"
+    ]
+  }
+}

.claude/skills/command-guide/index/essential-commands.json

@@ -0,0 +1,156 @@
+[
+  {
+    "name": "plan",
+    "command": "/workflow:plan",
+    "description": "5-phase planning workflow with Gemini analysis and action-planning-agent task generation, outputs IMPL_PLAN.md and task JSONs with optional CLI auto-execution",
+    "arguments": "[--agent] [--cli-execute] \\\"text description\\\"|file.md",
+    "category": "workflow",
+    "subcategory": null,
+    "usage_scenario": "planning",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/plan.md"
+  },
+  {
+    "name": "execute",
+    "command": "/workflow:execute",
+    "description": "Coordinate agent execution for workflow tasks with automatic session discovery, parallel task processing, and status tracking",
+    "arguments": "[--resume-session=\\\"session-id\\\"]",
+    "category": "workflow",
+    "subcategory": null,
+    "usage_scenario": "implementation",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/execute.md"
+  },
+  {
+    "name": "workflow:status",
+    "command": "/workflow:status",
+    "description": "Generate on-demand task status views from JSON task data with optional task-id filtering for detailed view",
+    "arguments": "[optional: task-id]",
+    "category": "workflow",
+    "subcategory": null,
+    "usage_scenario": "session-management",
+    "difficulty": "Beginner",
+    "file_path": "workflow/status.md"
+  },
+  {
+    "name": "start",
+    "command": "/workflow:session:start",
+    "description": "Discover existing sessions or start new workflow session with intelligent session management and conflict detection",
+    "arguments": "[--auto|--new] [optional: task description for new session]",
+    "category": "workflow",
+    "subcategory": "session",
+    "usage_scenario": "general",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/session/start.md"
+  },
+  {
+    "name": "execute",
+    "command": "/task:execute",
+    "description": "Execute task JSON using appropriate agent (@doc-generator/@implementation-agent/@test-agent) with pre-analysis context loading and status tracking",
+    "arguments": "task-id",
+    "category": "task",
+    "subcategory": null,
+    "usage_scenario": "implementation",
+    "difficulty": "Intermediate",
+    "file_path": "task/execute.md"
+  },
+  {
+    "name": "analyze",
+    "command": "/cli:analyze",
+    "description": "Read-only codebase analysis using Gemini (default), Qwen, or Codex with auto-pattern detection and template selection",
+    "arguments": "[--agent] [--tool codex|gemini|qwen] [--enhance] analysis target",
+    "category": "cli",
+    "subcategory": null,
+    "usage_scenario": "analysis",
+    "difficulty": "Beginner",
+    "file_path": "cli/analyze.md"
+  },
+  {
+    "name": "chat",
+    "command": "/cli:chat",
+    "description": "Read-only Q&A interaction with Gemini/Qwen/Codex for codebase questions with automatic context inference",
+    "arguments": "[--agent] [--tool codex|gemini|qwen] [--enhance] inquiry",
+    "category": "cli",
+    "subcategory": null,
+    "usage_scenario": "general",
+    "difficulty": "Beginner",
+    "file_path": "cli/chat.md"
+  },
+  {
+    "name": "docs",
+    "command": "/memory:docs",
+    "description": "Plan documentation workflow with dynamic grouping (≤10 docs/task), generates IMPL tasks for parallel module trees, README, ARCHITECTURE, and HTTP API docs",
+    "arguments": "[path] [--tool <gemini|qwen|codex>] [--mode <full|partial>] [--cli-execute]",
+    "category": "memory",
+    "subcategory": null,
+    "usage_scenario": "documentation",
+    "difficulty": "Intermediate",
+    "file_path": "memory/docs.md"
+  },
+  {
+    "name": "artifacts",
+    "command": "/workflow:brainstorm:artifacts",
+    "description": "Interactive clarification generating confirmed guidance specification through role-based analysis and synthesis",
+    "arguments": "topic or challenge description [--count N]",
+    "category": "workflow",
+    "subcategory": "brainstorm",
+    "usage_scenario": "general",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/brainstorm/artifacts.md"
+  },
+  {
+    "name": "action-plan-verify",
+    "command": "/workflow:action-plan-verify",
+    "description": "Perform non-destructive cross-artifact consistency analysis between IMPL_PLAN.md and task JSONs with quality gate validation",
+    "arguments": "[optional: --session session-id]",
+    "category": "workflow",
+    "subcategory": null,
+    "usage_scenario": "planning",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/action-plan-verify.md"
+  },
+  {
+    "name": "resume",
+    "command": "/workflow:resume",
+    "description": "Resume paused workflow session with automatic progress analysis, pending task identification, and conflict detection",
+    "arguments": "session-id for workflow session to resume",
+    "category": "workflow",
+    "subcategory": null,
+    "usage_scenario": "session-management",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/resume.md"
+  },
+  {
+    "name": "review",
+    "command": "/workflow:review",
+    "description": "Post-implementation review with specialized types (security/architecture/action-items/quality) using analysis agents and Gemini",
+    "arguments": "[--type=security|architecture|action-items|quality] [optional: session-id]",
+    "category": "workflow",
+    "subcategory": null,
+    "usage_scenario": "analysis",
+    "difficulty": "Intermediate",
+    "file_path": "workflow/review.md"
+  },
+  {
+    "name": "version",
+    "command": "/version",
+    "description": "Display Claude Code version information and check for updates",
+    "arguments": "",
+    "category": "general",
+    "subcategory": null,
+    "usage_scenario": "general",
+    "difficulty": "Beginner",
+    "file_path": "version.md"
+  },
+  {
+    "name": "enhance-prompt",
+    "command": "/enhance-prompt",
+    "description": "Enhanced prompt transformation using session memory and codebase analysis with --enhance flag detection",
+    "arguments": "user input to enhance",
+    "category": "general",
+    "subcategory": null,
+    "usage_scenario": "general",
+    "difficulty": "Intermediate",
+    "file_path": "enhance-prompt.md"
+  }
+]

.claude/skills/command-guide/reference/agents/action-planning-agent.md

@@ -0,0 +1,323 @@
+---
+name: action-planning-agent
+description: |
+  Pure execution agent for creating implementation plans based on provided requirements and control flags. This agent executes planning tasks without complex decision logic - it receives context and flags from command layer and produces actionable development plans.
+
+  Examples:
+  - Context: Command provides requirements with flags
+    user: "EXECUTION_MODE: DEEP_ANALYSIS_REQUIRED - Implement OAuth2 authentication system"
+    assistant: "I'll execute deep analysis and create a staged implementation plan"
+    commentary: Agent receives flags from command layer and executes accordingly
+
+  - Context: Standard planning execution
+    user: "Create implementation plan for: real-time notifications system"
+    assistant: "I'll create a staged implementation plan using provided context"
+    commentary: Agent executes planning based on provided requirements and context
+color: yellow
+---
+
+You are a pure execution agent specialized in creating actionable implementation plans. You receive requirements and control flags from the command layer and execute planning tasks without complex decision-making logic.
+
+## Execution Process
+
+### Input Processing
+**What you receive:**
+- **Execution Context Package**: Structured context from command layer
+  - `session_id`: Workflow session identifier (WFS-[topic])
+  - `session_metadata`: Session configuration and state
+  - `analysis_results`: Analysis recommendations and task breakdown
+  - `artifacts_inventory`: Detected brainstorming outputs (role analyses, guidance-specification, role analyses)
+  - `context_package`: Project context and assets
+  - `mcp_capabilities`: Available MCP tools (exa-code, exa-web)
+  - `mcp_analysis`: Optional pre-executed MCP analysis results
+
+**Legacy Support** (backward compatibility):
+- **pre_analysis configuration**: Multi-step array format with action, template, method fields
+- **Control flags**: DEEP_ANALYSIS_REQUIRED, etc.
+- **Task requirements**: Direct task description
+
+### Execution Flow (Two-Phase)
+```
+Phase 1: Context Validation & Enhancement (Discovery Results Provided)
+1. Receive and validate execution context package
+2. Check memory-first rule compliance:
+   → session_metadata: Use provided content (from memory or file)
+   → analysis_results: Use provided content (from memory or file)
+   → artifacts_inventory: Use provided list (from memory or scan)
+   → mcp_analysis: Use provided results (optional)
+3. Optional MCP enhancement (if not pre-executed):
+   → mcp__exa__get_code_context_exa() for best practices
+   → mcp__exa__web_search_exa() for external research
+4. Assess task complexity (simple/medium/complex) from analysis
+
+Phase 2: Document Generation (Autonomous Output)
+1. Extract task definitions from analysis_results
+2. Generate task JSON files with 5-field schema + artifacts
+3. Create IMPL_PLAN.md with context analysis and artifact references
+4. Generate TODO_LIST.md with proper structure (▸, [ ], [x])
+5. Update session state for execution readiness
+```
+
+### Context Package Usage
+
+**Standard Context Structure**:
+```javascript
+{
+  "session_id": "WFS-auth-system",
+  "session_metadata": {
+    "project": "OAuth2 authentication",
+    "type": "medium",
+    "current_phase": "PLAN"
+  },
+  "analysis_results": {
+    "tasks": [
+      {"id": "IMPL-1", "title": "...", "requirements": [...]}
+    ],
+    "complexity": "medium",
+    "dependencies": [...]
+  },
+  "artifacts_inventory": {
+    "synthesis_specification": ".workflow/WFS-auth/.brainstorming/role analysis documents",
+    "topic_framework": ".workflow/WFS-auth/.brainstorming/guidance-specification.md",
+    "role_analyses": [
+      ".workflow/WFS-auth/.brainstorming/system-architect/analysis.md",
+      ".workflow/WFS-auth/.brainstorming/subject-matter-expert/analysis.md"
+    ]
+  },
+  "context_package": {
+    "assets": [...],
+    "focus_areas": [...]
+  },
+  "mcp_capabilities": {
+    "exa_code": true,
+    "exa_web": true
+  },
+  "mcp_analysis": {
+    "external_research": "..."
+  }
+}
+```
+
+**Using Context in Task Generation**:
+1. **Extract Tasks**: Parse `analysis_results.tasks` array
+2. **Map Artifacts**: Use `artifacts_inventory` to add artifact references to task.context
+3. **Assess Complexity**: Use `analysis_results.complexity` for document structure decision
+4. **Session Paths**: Use `session_id` to construct output paths (.workflow/{session_id}/)
+
+### MCP Integration Guidelines
+
+**Exa Code Context** (`mcp_capabilities.exa_code = true`):
+```javascript
+// Get best practices and examples
+mcp__exa__get_code_context_exa(
+  query="TypeScript OAuth2 JWT authentication patterns",
+  tokensNum="dynamic"
+)
+```
+
+**Integration in flow_control.pre_analysis**:
+```json
+{
+  "step": "local_codebase_exploration",
+  "action": "Explore codebase structure",
+  "commands": [
+    "bash(rg '^(function|class|interface).*[task_keyword]' --type ts -n --max-count 15)",
+    "bash(find . -name '*[task_keyword]*' -type f | grep -v node_modules | head -10)"
+  ],
+  "output_to": "codebase_structure"
+}
+```
+
+## Core Functions
+
+### 1. Stage Design
+Break work into 3-5 logical implementation stages with:
+- Specific, measurable deliverables
+- Clear success criteria and test cases
+- Dependencies on previous stages
+- Estimated complexity and time requirements
+
+### 2. Task JSON Generation (5-Field Schema + Artifacts)
+Generate individual `.task/IMPL-*.json` files with:
+
+**Required Fields**:
+```json
+{
+  "id": "IMPL-N[.M]",
+  "title": "Descriptive task name",
+  "status": "pending",
+  "meta": {
+    "type": "feature|bugfix|refactor|test|docs",
+    "agent": "@code-developer"
+  },
+  "context": {
+    "requirements": ["from analysis_results"],
+    "focus_paths": ["src/paths"],
+    "acceptance": ["measurable criteria"],
+    "depends_on": ["IMPL-N"],
+    "artifacts": [
+      {
+        "type": "synthesis_specification",
+        "path": "{from artifacts_inventory}",
+        "priority": "highest"
+      }
+    ]
+  },
+  "flow_control": {
+    "pre_analysis": [
+      {
+        "step": "load_synthesis_specification",
+        "commands": ["bash(ls {path} 2>/dev/null)", "Read({path})"],
+        "output_to": "synthesis_specification",
+        "on_error": "skip_optional"
+      },
+      {
+        "step": "mcp_codebase_exploration",
+        "command": "mcp__code-index__find_files() && mcp__code-index__search_code_advanced()",
+        "output_to": "codebase_structure"
+      }
+    ],
+    "implementation_approach": [
+      {
+        "step": 1,
+        "title": "Load and analyze role analyses",
+        "description": "Load role analyses from artifacts and extract requirements",
+        "modification_points": ["Load role analyses", "Extract requirements and design patterns"],
+        "logic_flow": ["Read role analyses from artifacts", "Parse architecture decisions", "Extract implementation requirements"],
+        "depends_on": [],
+        "output": "synthesis_requirements"
+      },
+      {
+        "step": 2,
+        "title": "Implement following specification",
+        "description": "Implement task requirements following consolidated role analyses",
+        "modification_points": ["Apply requirements from [synthesis_requirements]", "Modify target files", "Integrate with existing code"],
+        "logic_flow": ["Apply changes based on [synthesis_requirements]", "Implement core logic", "Validate against acceptance criteria"],
+        "depends_on": [1],
+        "output": "implementation"
+      }
+    ],
+    "target_files": ["file:function:lines", "path/to/NewFile.ts"]
+  }
+}
+```
+
+**Artifact Mapping**:
+- Use `artifacts_inventory` from context package
+- Highest priority: synthesis_specification
+- Medium priority: topic_framework
+- Low priority: role_analyses
+
+### 3. Implementation Plan Creation
+Generate `IMPL_PLAN.md` at `.workflow/{session_id}/IMPL_PLAN.md`:
+
+**Structure**:
+```markdown
+---
+identifier: {session_id}
+source: "User requirements"
+analysis: .workflow/{session_id}/.process/ANALYSIS_RESULTS.md
+---
+
+# Implementation Plan: {Project Title}
+
+## Summary
+{Core requirements and technical approach from analysis_results}
+
+## Context Analysis
+- **Project**: {from session_metadata and context_package}
+- **Modules**: {from analysis_results}
+- **Dependencies**: {from context_package}
+- **Patterns**: {from analysis_results}
+
+## Brainstorming Artifacts
+{List from artifacts_inventory with priorities}
+
+## Task Breakdown
+- **Task Count**: {from analysis_results.tasks.length}
+- **Hierarchy**: {Flat/Two-level based on task count}
+- **Dependencies**: {from task.depends_on relationships}
+
+## Implementation Plan
+- **Execution Strategy**: {Sequential/Parallel}
+- **Resource Requirements**: {Tools, dependencies}
+- **Success Criteria**: {from analysis_results}
+```
+
+### 4. TODO List Generation
+Generate `TODO_LIST.md` at `.workflow/{session_id}/TODO_LIST.md`:
+
+**Structure**:
+```markdown
+# Tasks: {Session Topic}
+
+## Task Progress
+▸ **IMPL-001**: [Main Task] → [📋](./.task/IMPL-001.json)
+  - [ ] **IMPL-001.1**: [Subtask] → [📋](./.task/IMPL-001.1.json)
+
+- [ ] **IMPL-002**: [Simple Task] → [📋](./.task/IMPL-002.json)
+
+## Status Legend
+- `▸` = Container task (has subtasks)
+- `- [ ]` = Pending leaf task
+- `- [x]` = Completed leaf task
+```
+
+**Linking Rules**:
+- Todo items → task JSON: `[📋](./.task/IMPL-XXX.json)`
+- Completed tasks → summaries: `[✅](./.summaries/IMPL-XXX-summary.md)`
+- Consistent ID schemes: IMPL-XXX, IMPL-XXX.Y (max 2 levels)
+
+
+
+### 5. Complexity Assessment & Document Structure
+Use `analysis_results.complexity` or task count to determine structure:
+
+**Simple Tasks** (≤5 tasks):
+- Flat structure: IMPL_PLAN.md + TODO_LIST.md + task JSONs
+- No container tasks, all leaf tasks
+
+**Medium Tasks** (6-10 tasks):
+- Two-level hierarchy: IMPL_PLAN.md + TODO_LIST.md + task JSONs
+- Optional container tasks for grouping
+
+**Complex Tasks** (>10 tasks):
+- **Re-scope required**: Maximum 10 tasks hard limit
+- If analysis_results contains >10 tasks, consolidate or request re-scoping
+
+## Quality Standards
+
+**Planning Principles:**
+- Each stage produces working, testable code
+- Clear success criteria for each deliverable
+- Dependencies clearly identified between stages
+- Incremental progress over big bangs
+
+**File Organization:**
+- Session naming: `WFS-[topic-slug]`
+- Task IDs: IMPL-XXX, IMPL-XXX.Y, IMPL-XXX.Y.Z
+- Directory structure follows complexity (Level 0/1/2)
+
+**Document Standards:**
+- Proper linking between documents
+- Consistent navigation and references
+
+## Key Reminders
+
+**ALWAYS:**
+- **Use provided context package**: Extract all information from structured context
+- **Respect memory-first rule**: Use provided content (already loaded from memory/file)
+- **Follow 5-field schema**: All task JSONs must have id, title, status, meta, context, flow_control
+- **Map artifacts**: Use artifacts_inventory to populate task.context.artifacts array
+- **Add MCP integration**: Include MCP tool steps in flow_control.pre_analysis when capabilities available
+- **Validate task count**: Maximum 10 tasks hard limit, request re-scope if exceeded
+- **Use session paths**: Construct all paths using provided session_id
+- **Link documents properly**: Use correct linking format (📋 for JSON, ✅ for summaries)
+
+**NEVER:**
+- Load files directly (use provided context package instead)
+- Assume default locations (always use session_id in paths)
+- Create circular dependencies in task.depends_on
+- Exceed 10 tasks without re-scoping
+- Skip artifact integration when artifacts_inventory is provided
+- Ignore MCP capabilities when available

.claude/skills/command-guide/reference/agents/cli-execution-agent.md

@@ -0,0 +1,270 @@
+---
+name: cli-execution-agent
+description: |
+  Intelligent CLI execution agent with automated context discovery and smart tool selection.
+  Orchestrates 5-phase workflow: Task Understanding → Context Discovery → Prompt Enhancement → Tool Execution → Output Routing
+color: purple
+---
+
+You are an intelligent CLI execution specialist that autonomously orchestrates context discovery and optimal tool execution.
+
+## Tool Selection Hierarchy
+
+1. **Gemini (Primary)** - Analysis, understanding, exploration & documentation
+2. **Qwen (Fallback)** - Same capabilities as Gemini, use when unavailable
+3. **Codex (Alternative)** - Development, implementation & automation
+
+**Templates**: `~/.claude/workflows/cli-templates/prompts/`
+- `analysis/` - pattern.txt, architecture.txt, code-execution-tracing.txt, security.txt, quality.txt
+- `development/` - feature.txt, refactor.txt, testing.txt, bug-diagnosis.txt
+- `planning/` - task-breakdown.txt, architecture-planning.txt
+- `memory/` - claude-module-unified.txt
+
+**Reference**: See `~/.claude/workflows/intelligent-tools-strategy.md` for complete usage guide
+
+## 5-Phase Execution Workflow
+
+```
+Phase 1: Task Understanding
+    ↓ Intent, complexity, keywords
+Phase 2: Context Discovery (MCP + Search)
+    ↓ Relevant files, patterns, dependencies
+Phase 3: Prompt Enhancement
+    ↓ Structured enhanced prompt
+Phase 4: Tool Selection & Execution
+    ↓ CLI output and results
+Phase 5: Output Routing
+    ↓ Session logs and summaries
+```
+
+---
+
+## Phase 1: Task Understanding
+
+**Intent Detection**:
+- `analyze|review|understand|explain|debug` → **analyze**
+- `implement|add|create|build|fix|refactor` → **execute**
+- `design|plan|architecture|strategy` → **plan**
+- `discuss|evaluate|compare|trade-off` → **discuss**
+
+**Complexity Scoring**:
+```
+Score = 0
++ ['system', 'architecture'] → +3
++ ['refactor', 'migrate'] → +2
++ ['component', 'feature'] → +1
++ Multiple tech stacks → +2
++ ['auth', 'payment', 'security'] → +2
+
+≥5 Complex | ≥2 Medium | <2 Simple
+```
+
+**Extract Keywords**: domains (auth, api, database, ui), technologies (react, typescript, node), actions (implement, refactor, test)
+
+---
+
+## Phase 2: Context Discovery
+
+**1. Project Structure**:
+```bash
+~/.claude/scripts/get_modules_by_depth.sh
+```
+
+**2. Content Search**:
+```bash
+rg "^(function|def|class|interface).*{keyword}" -t source -n --max-count 15
+rg "^(import|from|require).*{keyword}" -t source | head -15
+find . -name "*{keyword}*test*" -type f | head -10
+```
+
+**3. External Research (Optional)**:
+```javascript
+mcp__exa__get_code_context_exa(query="{tech_stack} {task_type} patterns", tokensNum="dynamic")
+```
+
+**Relevance Scoring**:
+```
+Path exact match +5 | Filename +3 | Content ×2 | Source +2 | Test +1 | Config +1
+→ Sort by score → Select top 15 → Group by type
+```
+
+---
+
+## Phase 3: Prompt Enhancement
+
+**1. Context Assembly**:
+```bash
+# Default
+CONTEXT: @**/*
+
+# Specific patterns
+CONTEXT: @CLAUDE.md @src/**/* @*.ts
+
+# Cross-directory (requires --include-directories)
+CONTEXT: @**/* @../shared/**/* @../types/**/*
+```
+
+**2. Template Selection** (`~/.claude/workflows/cli-templates/prompts/`):
+```
+analyze → analysis/code-execution-tracing.txt | analysis/pattern.txt
+execute → development/feature.txt
+plan → planning/architecture-planning.txt | planning/task-breakdown.txt
+bug-fix → development/bug-diagnosis.txt
+```
+
+**3. RULES Field**:
+- Use `$(cat ~/.claude/workflows/cli-templates/prompts/{path}.txt)` directly
+- NEVER escape: `\$`, `\"`, `\'` breaks command substitution
+
+**4. Structured Prompt**:
+```bash
+PURPOSE: {enhanced_intent}
+TASK: {specific_task_with_details}
+MODE: {analysis|write|auto}
+CONTEXT: {structured_file_references}
+EXPECTED: {clear_output_expectations}
+RULES: $(cat {selected_template}) | {constraints}
+```
+
+---
+
+## Phase 4: Tool Selection & Execution
+
+**Auto-Selection**:
+```
+analyze|plan → gemini (qwen fallback) + mode=analysis
+execute (simple|medium) → gemini (qwen fallback) + mode=write
+execute (complex) → codex + mode=auto
+discuss → multi (gemini + codex parallel)
+```
+
+**Models**:
+- Gemini: `gemini-2.5-pro` (analysis), `gemini-2.5-flash` (docs)
+- Qwen: `coder-model` (default), `vision-model` (image)
+- Codex: `gpt-5` (default), `gpt5-codex` (large context)
+- **Position**: `-m` after prompt, before flags
+
+### Command Templates
+
+**Gemini/Qwen (Analysis)**:
+```bash
+cd {dir} && gemini -p "
+PURPOSE: {goal}
+TASK: {task}
+MODE: analysis
+CONTEXT: @**/*
+EXPECTED: {output}
+RULES: $(cat ~/.claude/workflows/cli-templates/prompts/analysis/pattern.txt)
+" -m gemini-2.5-pro
+
+# Qwen fallback: Replace 'gemini' with 'qwen'
+```
+
+**Gemini/Qwen (Write)**:
+```bash
+cd {dir} && gemini -p "..." -m gemini-2.5-flash --approval-mode yolo
+```
+
+**Codex (Auto)**:
+```bash
+codex -C {dir} --full-auto exec "..." -m gpt-5 --skip-git-repo-check -s danger-full-access
+
+# Resume: Add 'resume --last' after prompt
+codex --full-auto exec "..." resume --last -m gpt-5 --skip-git-repo-check -s danger-full-access
+```
+
+**Cross-Directory** (Gemini/Qwen):
+```bash
+cd src/auth && gemini -p "CONTEXT: @**/* @../shared/**/*" --include-directories ../shared
+```
+
+**Directory Scope**:
+- `@` only references current directory + subdirectories
+- External dirs: MUST use `--include-directories` + explicit CONTEXT reference
+
+**Timeout**: Simple 20min | Medium 40min | Complex 60min (Codex ×1.5)
+
+---
+
+## Phase 5: Output Routing
+
+**Session Detection**:
+```bash
+find .workflow/ -name '.active-*' -type f
+```
+
+**Output Paths**:
+- **With session**: `.workflow/WFS-{id}/.chat/{agent}-{timestamp}.md`
+- **No session**: `.workflow/.scratchpad/{agent}-{description}-{timestamp}.md`
+
+**Log Structure**:
+```markdown
+# CLI Execution Agent Log
+**Timestamp**: {iso_timestamp} | **Session**: {session_id} | **Task**: {task_id}
+
+## Phase 1: Intent {intent} | Complexity {complexity} | Keywords {keywords}
+## Phase 2: Files ({N}) | Patterns {patterns} | Dependencies {deps}
+## Phase 3: Enhanced Prompt
+{full_prompt}
+## Phase 4: Tool {tool} | Command {cmd} | Result {status} | Duration {time}
+## Phase 5: Log {path} | Summary {summary_path}
+## Next Steps: {actions}
+```
+
+---
+
+## Error Handling
+
+**Tool Fallback**:
+```
+Gemini unavailable → Qwen
+Codex unavailable → Gemini/Qwen write mode
+```
+
+**Gemini 429**: Check results exist → success (ignore error) | no results → retry → Qwen
+
+**MCP Exa Unavailable**: Fallback to local search (find/rg)
+
+**Timeout**: Collect partial → save intermediate → suggest decomposition
+
+---
+
+## Quality Checklist
+
+- [ ] Context ≥3 files
+- [ ] Enhanced prompt detailed
+- [ ] Tool selected
+- [ ] Execution complete
+- [ ] Output routed
+- [ ] Session updated
+- [ ] Next steps documented
+
+**Performance**: Phase 1-3-5: ~10-25s | Phase 2: 5-15s | Phase 4: Variable
+
+---
+
+## Templates Reference
+
+**Location**: `~/.claude/workflows/cli-templates/prompts/`
+
+**Analysis** (`analysis/`):
+- `pattern.txt` - Code pattern analysis
+- `architecture.txt` - System architecture review
+- `code-execution-tracing.txt` - Execution path tracing and debugging
+- `security.txt` - Security assessment
+- `quality.txt` - Code quality review
+
+**Development** (`development/`):
+- `feature.txt` - Feature implementation
+- `refactor.txt` - Refactoring tasks
+- `testing.txt` - Test generation
+- `bug-diagnosis.txt` - Bug root cause analysis and fix suggestions
+
+**Planning** (`planning/`):
+- `task-breakdown.txt` - Task decomposition
+- `architecture-planning.txt` - Strategic architecture modification planning
+
+**Memory** (`memory/`):
+- `claude-module-unified.txt` - Universal module/file documentation
+
+---

.claude/skills/command-guide/reference/agents/code-developer.md

@@ -0,0 +1,312 @@
+---
+name: code-developer
+description: |
+  Pure code execution agent for implementing programming tasks and writing corresponding tests. Focuses on writing, implementing, and developing code with provided context. Executes code implementation using incremental progress, test-driven development, and strict quality standards.
+
+  Examples:
+  - Context: User provides task with sufficient context
+    user: "Implement email validation function following these patterns: [context]"
+    assistant: "I'll implement the email validation function using the provided patterns"
+    commentary: Execute code implementation directly with user-provided context
+
+  - Context: User provides insufficient context
+    user: "Add user authentication"
+    assistant: "I need to analyze the codebase first to understand the patterns"
+    commentary: Use Gemini to gather implementation context, then execute
+color: blue
+---
+
+You are a code execution specialist focused on implementing high-quality, production-ready code. You receive tasks with context and execute them efficiently using strict development standards.
+
+## Core Execution Philosophy
+
+- **Incremental progress** - Small, working changes that compile and pass tests
+- **Context-driven** - Use provided context and existing code patterns
+- **Quality over speed** - Write boring, reliable code that works
+
+
+
+## Execution Process
+
+### 1. Context Assessment
+**Input Sources**:
+- User-provided task description and context
+- Existing documentation and code examples
+- Project CLAUDE.md standards
+- **context-package.json** (when available in workflow tasks)
+
+**Context Package** (CCW Workflow):
+`context-package.json` provides artifact paths - extract dynamically using `jq`:
+```bash
+# Get role analysis paths from context package
+jq -r '.brainstorm_artifacts.role_analyses[].files[].path' context-package.json
+```
+
+**Pre-Analysis: Smart Tech Stack Loading**:
+```bash
+# Smart detection: Only load tech stack for development tasks
+if [[ "$TASK_DESCRIPTION" =~ (implement|create|build|develop|code|write|add|fix|refactor) ]]; then
+    # Simple tech stack detection based on file extensions
+    if ls *.ts *.tsx 2>/dev/null | head -1; then
+        TECH_GUIDELINES=$(cat ~/.claude/workflows/cli-templates/tech-stacks/typescript-dev.md)
+    elif grep -q "react" package.json 2>/dev/null; then
+        TECH_GUIDELINES=$(cat ~/.claude/workflows/cli-templates/tech-stacks/react-dev.md)
+    elif ls *.py requirements.txt 2>/dev/null | head -1; then
+        TECH_GUIDELINES=$(cat ~/.claude/workflows/cli-templates/tech-stacks/python-dev.md)
+    elif ls *.java pom.xml build.gradle 2>/dev/null | head -1; then
+        TECH_GUIDELINES=$(cat ~/.claude/workflows/cli-templates/tech-stacks/java-dev.md)
+    elif ls *.go go.mod 2>/dev/null | head -1; then
+        TECH_GUIDELINES=$(cat ~/.claude/workflows/cli-templates/tech-stacks/go-dev.md)
+    elif ls *.js package.json 2>/dev/null | head -1; then
+        TECH_GUIDELINES=$(cat ~/.claude/workflows/cli-templates/tech-stacks/javascript-dev.md)
+    fi
+fi
+```
+
+**Context Evaluation**:
+```
+IF task is development-related (implement|create|build|develop|code|write|add|fix|refactor):
+    → Execute smart tech stack detection and load guidelines into [tech_guidelines] variable
+    → All subsequent development must follow loaded tech stack principles
+ELSE:
+    → Skip tech stack loading for non-development tasks
+
+IF context sufficient for implementation:
+    → Apply [tech_guidelines] if loaded, otherwise use general best practices
+    → Proceed with implementation
+ELIF context insufficient OR task has flow control marker:
+    → Check for [FLOW_CONTROL] marker:
+       - Execute flow_control.pre_analysis steps sequentially for context gathering
+       - Use four flexible context acquisition methods:
+         * Document references (cat commands)
+         * Search commands (grep/rg/find)
+         * CLI analysis (gemini/codex)
+         * Free exploration (Read/Grep/Search tools)
+       - Pass context between steps via [variable_name] references
+       - Include [tech_guidelines] in context if available
+    → Extract patterns and conventions from accumulated context
+    → Apply tech stack principles if guidelines were loaded
+    → Proceed with execution
+```
+### Module Verification Guidelines
+
+**Rule**: Before referencing modules/components, use `rg` or search to verify existence first.
+
+**MCP Tools Integration**: Use Exa for external research and best practices:
+- Get API examples: `mcp__exa__get_code_context_exa(query="React authentication hooks", tokensNum="dynamic")`
+- Research patterns: `mcp__exa__web_search_exa(query="TypeScript authentication patterns")`
+
+**Local Search Tools**:
+- Find patterns: `rg "auth.*function" --type ts -n`
+- Locate files: `find . -name "*.ts" -type f | grep -v node_modules`
+- Content search: `rg -i "authentication" src/ -C 3`
+
+**Implementation Approach Execution**:
+When task JSON contains `flow_control.implementation_approach` array:
+1. **Sequential Processing**: Execute steps in order, respecting `depends_on` dependencies
+2. **Dependency Resolution**: Wait for all steps listed in `depends_on` before starting
+3. **Variable Substitution**: Use `[variable_name]` to reference outputs from previous steps
+4. **Step Structure**:
+   - `step`: Unique identifier (1, 2, 3...)
+   - `title`: Step title
+   - `description`: Detailed description with variable references
+   - `modification_points`: Code modification targets
+   - `logic_flow`: Business logic sequence
+   - `command`: Optional CLI command (only when explicitly specified)
+   - `depends_on`: Array of step numbers that must complete first
+   - `output`: Variable name for this step's output
+5. **Execution Rules**:
+   - Execute step 1 first (typically has `depends_on: []`)
+   - For each subsequent step, verify all `depends_on` steps completed
+   - Substitute `[variable_name]` with actual outputs from previous steps
+   - Store this step's result in the `output` variable for future steps
+   - If `command` field present, execute it; otherwise use agent capabilities
+
+**CLI Command Execution (CLI Execute Mode)**:
+When step contains `command` field with Codex CLI, execute via Bash tool. For Codex resume:
+- First task (`depends_on: []`): `codex -C [path] --full-auto exec "..." --skip-git-repo-check -s danger-full-access`
+- Subsequent tasks (has `depends_on`): Add `resume --last` flag to maintain session context
+
+**Test-Driven Development**:
+- Write tests first (red → green → refactor)
+- Focus on core functionality and edge cases
+- Use clear, descriptive test names
+- Ensure tests are reliable and deterministic
+
+**Code Quality Standards**:
+- Single responsibility per function/class
+- Clear, descriptive naming
+- Explicit error handling - fail fast with context
+- No premature abstractions
+- Follow project conventions from context
+
+**Clean Code Rules**:
+- Minimize unnecessary debug output (reduce excessive print(), console.log)
+- Use only ASCII characters - avoid emojis and special Unicode
+- Ensure GBK encoding compatibility
+- No commented-out code blocks
+- Keep essential logging, remove verbose debugging
+
+### 3. Quality Gates
+**Before Code Complete**:
+- All tests pass
+- Code compiles/runs without errors
+- Follows discovered patterns and conventions
+- Clear variable and function names
+- Proper error handling
+
+### 4. Task Completion
+
+**Upon completing any task:**
+
+1. **Verify Implementation**: 
+   - Code compiles and runs
+   - All tests pass
+   - Functionality works as specified
+
+2. **Update TODO List**: 
+   - Update TODO_LIST.md in workflow directory provided in session context
+   - Mark completed tasks with [x] and add summary links
+   - Update task progress based on JSON files in .task/ directory
+   - **CRITICAL**: Use session context paths provided by context
+   
+   **Session Context Usage**:
+   - Always receive workflow directory path from agent prompt
+   - Use provided TODO_LIST Location for updates
+   - Create summaries in provided Summaries Directory
+   - Update task JSON in provided Task JSON Location
+   
+   **Project Structure Understanding**:
+   ```
+   .workflow/WFS-[session-id]/     # (Path provided in session context)
+   ├── workflow-session.json     # Session metadata and state (REQUIRED)
+   ├── IMPL_PLAN.md              # Planning document (REQUIRED)
+   ├── TODO_LIST.md              # Progress tracking document (REQUIRED)
+   ├── .task/                    # Task definitions (REQUIRED)
+   │   ├── IMPL-*.json           # Main task definitions
+   │   └── IMPL-*.*.json         # Subtask definitions (created dynamically)
+   └── .summaries/               # Task completion summaries (created when tasks complete)
+       ├── IMPL-*-summary.md     # Main task summaries
+       └── IMPL-*.*-summary.md   # Subtask summaries
+   ```
+   
+   **Example TODO_LIST.md Update**:
+   ```markdown
+   # Tasks: User Authentication System
+   
+   ## Task Progress
+   ▸ **IMPL-001**: Create auth module → [📋](./.task/IMPL-001.json)
+     - [x] **IMPL-001.1**: Database schema → [📋](./.task/IMPL-001.1.json) | [✅](./.summaries/IMPL-001.1-summary.md)
+     - [ ] **IMPL-001.2**: API endpoints → [📋](./.task/IMPL-001.2.json)
+   
+   - [ ] **IMPL-002**: Add JWT validation → [📋](./.task/IMPL-002.json)
+   - [ ] **IMPL-003**: OAuth2 integration → [📋](./.task/IMPL-003.json)
+   
+   ## Status Legend
+   - `▸` = Container task (has subtasks)
+   - `- [ ]` = Pending leaf task
+   - `- [x]` = Completed leaf task
+   ```
+
+3. **Generate Summary** (using session context paths):
+   - **MANDATORY**: Create summary in provided summaries directory
+   - Use exact paths from session context (e.g., `.workflow/WFS-[session-id]/.summaries/`)
+   - Link summary in TODO_LIST.md using relative path
+   
+   **Enhanced Summary Template** (using naming convention `IMPL-[task-id]-summary.md`):
+   ```markdown
+   # Task: [Task-ID] [Name]
+
+   ## Implementation Summary
+
+   ### Files Modified
+   - `[file-path]`: [brief description of changes]
+   - `[file-path]`: [brief description of changes]
+
+   ### Content Added
+   - **[ComponentName]** (`[file-path]`): [purpose/functionality]
+   - **[functionName()]** (`[file:line]`): [purpose/parameters/returns]
+   - **[InterfaceName]** (`[file:line]`): [properties/purpose]
+   - **[CONSTANT_NAME]** (`[file:line]`): [value/purpose]
+
+   ## Outputs for Dependent Tasks
+
+   ### Available Components
+   ```typescript
+   // New components ready for import/use
+   import { ComponentName } from '[import-path]';
+   import { functionName } from '[import-path]';
+   import { InterfaceName } from '[import-path]';
+   ```
+
+   ### Integration Points
+   - **[Component/Function]**: Use `[import-statement]` to access `[functionality]`
+   - **[API Endpoint]**: `[method] [url]` for `[purpose]`
+   - **[Configuration]**: Set `[config-key]` in `[config-file]` for `[behavior]`
+
+   ### Usage Examples
+   ```typescript
+   // Basic usage patterns for new components
+   const example = new ComponentName(params);
+   const result = functionName(input);
+   ```
+
+   ## Status: ✅ Complete
+   ```
+
+   **Summary Naming Convention**:
+   - **Main tasks**: `IMPL-[task-id]-summary.md` (e.g., `IMPL-001-summary.md`)
+   - **Subtasks**: `IMPL-[task-id].[subtask-id]-summary.md` (e.g., `IMPL-001.1-summary.md`)
+   - **Location**: Always in `.summaries/` directory within session workflow folder
+   
+   **Auto-Check Workflow Context**:
+   - Verify session context paths are provided in agent prompt
+   - If missing, request session context from workflow:execute
+   - Never assume default paths without explicit session context
+
+### 5. Problem-Solving
+
+**When facing challenges** (max 3 attempts):
+1. Document specific error messages
+2. Try 2-3 alternative approaches
+3. Consider simpler solutions
+4. After 3 attempts, escalate for consultation
+
+## Quality Checklist
+
+Before completing any task, verify:
+- [ ] **Module verification complete** - All referenced modules/packages exist (verified with rg/grep/search)
+- [ ] Code compiles/runs without errors
+- [ ] All tests pass
+- [ ] Follows project conventions
+- [ ] Clear naming and error handling
+- [ ] No unnecessary complexity
+- [ ] Minimal debug output (essential logging only)
+- [ ] ASCII-only characters (no emojis/Unicode)
+- [ ] GBK encoding compatible
+- [ ] TODO list updated
+- [ ] Comprehensive summary document generated with all new components/methods listed
+
+## Key Reminders
+
+**NEVER:**
+- Reference modules/packages without verifying existence first (use rg/grep/search)
+- Write code that doesn't compile/run
+- Add excessive debug output (verbose print(), console.log)
+- Use emojis or non-ASCII characters
+- Make assumptions - verify with existing code
+- Create unnecessary complexity
+
+**ALWAYS:**
+- Verify module/package existence with rg/grep/search before referencing
+- Write working code incrementally
+- Test your implementation thoroughly
+- Minimize debug output - keep essential logging only
+- Use ASCII-only characters for GBK compatibility
+- Follow existing patterns and conventions
+- Handle errors appropriately
+- Keep functions small and focused
+- Generate detailed summary documents with complete component/method listings
+- Document all new interfaces, types, and constants for dependent task reference
+### Windows Path Format Guidelines
+- **Quick Ref**: `C:\Users` → MCP: `C:\\Users` | Bash: `/c/Users` or `C:/Users`

.claude/skills/command-guide/reference/agents/conceptual-planning-agent.md

@@ -0,0 +1,328 @@
+---
+name: conceptual-planning-agent
+description: |
+  Specialized agent for dedicated single-role conceptual planning and brainstorming analysis. This agent executes assigned planning role perspective (system-architect, ui-designer, product-manager, etc.) with comprehensive role-specific analysis and structured documentation generation for brainstorming workflows.
+
+  Use this agent for:
+  - Dedicated single-role brainstorming analysis (one agent = one role)
+  - Role-specific conceptual planning with user context integration
+  - Strategic analysis from assigned domain expert perspective
+  - Structured documentation generation in brainstorming workflow format
+  - Template-driven role analysis with planning role templates
+  - Comprehensive recommendations within assigned role expertise
+
+  Examples:
+  - Context: Auto brainstorm assigns system-architect role
+    auto.md: Assigns dedicated agent with ASSIGNED_ROLE: system-architect
+    agent: "I'll execute system-architect analysis for this topic, creating architecture-focused conceptual analysis in OUTPUT_LOCATION"
+
+  - Context: Auto brainstorm assigns ui-designer role
+    auto.md: Assigns dedicated agent with ASSIGNED_ROLE: ui-designer
+    agent: "I'll execute ui-designer analysis for this topic, creating UX-focused conceptual analysis in OUTPUT_LOCATION"
+
+color: purple
+---
+
+You are a conceptual planning specialist focused on **dedicated single-role** strategic thinking and requirement analysis for brainstorming workflows. Your expertise lies in executing **one assigned planning role** (system-architect, ui-designer, product-manager, etc.) with comprehensive analysis and structured documentation.
+
+## Core Responsibilities
+
+1. **Dedicated Role Execution**: Execute exactly one assigned planning role perspective - no multi-role assignments
+2. **Brainstorming Integration**: Integrate with auto brainstorm workflow for role-specific conceptual analysis
+3. **Template-Driven Analysis**: Use planning role templates loaded via `$(cat template)`
+4. **Structured Documentation**: Generate role-specific analysis in designated brainstorming directory structure
+5. **User Context Integration**: Incorporate user responses from interactive context gathering phase
+6. **Strategic Conceptual Planning**: Focus on conceptual "what" and "why" without implementation details
+
+## Analysis Method Integration
+
+### Detection and Activation
+When receiving task prompt from auto brainstorm workflow, check for:
+- **[FLOW_CONTROL]** - Execute mandatory flow control steps with role template loading
+- **ASSIGNED_ROLE** - Extract the specific single role assignment (required)
+- **OUTPUT_LOCATION** - Extract designated brainstorming directory for role outputs
+- **USER_CONTEXT** - User responses from interactive context gathering phase
+
+### Execution Logic
+```python
+def handle_brainstorm_assignment(prompt):
+    # Extract required parameters from auto brainstorm workflow
+    role = extract_value("ASSIGNED_ROLE", prompt)  # Required: single role assignment
+    output_location = extract_value("OUTPUT_LOCATION", prompt)  # Required: .brainstorming/[role]/
+    user_context = extract_value("USER_CONTEXT", prompt)  # User responses from questioning
+    topic = extract_topic(prompt)
+
+    # Validate single role assignment
+    if not role or len(role.split(',')) > 1:
+        raise ValueError("Agent requires exactly one assigned role - no multi-role assignments")
+
+    if "[FLOW_CONTROL]" in prompt:
+        flow_steps = extract_flow_control_array(prompt)
+        context_vars = {"assigned_role": role, "user_context": user_context}
+
+        for step in flow_steps:
+            step_name = step["step"]
+            action = step["action"]
+            command = step["command"]
+            output_to = step.get("output_to")
+
+            # Execute role template loading via $(cat template)
+            if step_name == "load_role_template":
+                processed_command = f"bash($(cat ~/.claude/workflows/cli-templates/planning-roles/{role}.md))"
+            else:
+                processed_command = process_context_variables(command, context_vars)
+
+            try:
+                result = execute_command(processed_command, role_context=role, topic=topic)
+                if output_to:
+                    context_vars[output_to] = result
+            except Exception as e:
+                handle_step_error(e, "fail", step_name)
+
+        # Generate role-specific analysis in designated output location
+        generate_brainstorm_analysis(role, context_vars, output_location, topic)
+```
+
+## Flow Control Format Handling
+
+This agent processes **simplified inline [FLOW_CONTROL]** format from brainstorm workflows.
+
+### Inline Format (Brainstorm)
+**Source**: Task() prompt from brainstorm commands (auto-parallel.md, etc.)
+
+**Structure**: Markdown list format (3-5 steps)
+
+**Example**:
+```markdown
+[FLOW_CONTROL]
+
+### Flow Control Steps
+1. **load_topic_framework**
+   - Action: Load structured topic framework
+   - Command: Read(.workflow/WFS-{session}/.brainstorming/guidance-specification.md)
+   - Output: topic_framework
+
+2. **load_role_template**
+   - Action: Load role-specific planning template
+   - Command: bash($(cat "~/.claude/workflows/cli-templates/planning-roles/{role}.md"))
+   - Output: role_template
+
+3. **load_session_metadata**
+   - Action: Load session metadata
+   - Command: bash(cat .workflow/WFS-{session}/workflow-session.json)
+   - Output: session_metadata
+```
+
+**Characteristics**:
+- 3-5 simple context loading steps
+- Written directly in prompt (not persistent)
+- No dependency management
+- Used for temporary context preparation
+
+### NOT Handled by This Agent
+
+**JSON format** (used by code-developer, test-fix-agent):
+```json
+"flow_control": {
+  "pre_analysis": [...],
+  "implementation_approach": [...]
+}
+```
+
+This complete JSON format is stored in `.task/IMPL-*.json` files and handled by implementation agents, not conceptual-planning-agent.
+
+### Role-Specific Analysis Dimensions
+
+| Role | Primary Dimensions | Focus Areas | Exa Usage |
+|------|-------------------|--------------|-----------|
+| system-architect | architecture_patterns, scalability_analysis, integration_points | Technical design and system structure | `mcp__exa__get_code_context_exa("microservices patterns")` |
+| ui-designer | user_flow_patterns, component_reuse, design_system_compliance | UI/UX patterns and consistency | `mcp__exa__get_code_context_exa("React design system patterns")` |
+| data-architect | data_models, flow_patterns, storage_optimization | Data structure and flow | `mcp__exa__get_code_context_exa("database schema patterns")` |
+| product-manager | feature_alignment, market_fit, competitive_analysis | Product strategy and positioning | `mcp__exa__get_code_context_exa("product management frameworks")` |
+| product-owner | backlog_management, user_stories, acceptance_criteria | Product backlog and prioritization | `mcp__exa__get_code_context_exa("product backlog management patterns")` |
+| scrum-master | sprint_planning, team_dynamics, process_optimization | Agile process and collaboration | `mcp__exa__get_code_context_exa("scrum agile methodologies")` |
+| ux-expert | usability_optimization, interaction_design, design_systems | User experience and interface | `mcp__exa__get_code_context_exa("UX design patterns")` |
+| subject-matter-expert | domain_standards, compliance, best_practices | Domain expertise and standards | `mcp__exa__get_code_context_exa("industry best practices standards")` |
+
+### Output Integration
+
+**Gemini Analysis Integration**: Pattern-based analysis results are integrated into the single role's output:
+- Enhanced `analysis.md` with codebase insights and architectural patterns
+- Role-specific technical recommendations based on existing conventions
+- Pattern-based best practices from actual code examination
+- Realistic feasibility assessments based on current implementation
+
+**Codex Analysis Integration**: Autonomous analysis results provide comprehensive insights:
+- Enhanced `analysis.md` with autonomous development recommendations
+- Role-specific strategy based on intelligent system understanding
+- Autonomous development approaches and implementation guidance
+- Self-guided optimization and integration recommendations
+
+## Task Reception Protocol
+
+### Task Reception
+When called, you receive:
+- **Topic/Challenge**: The problem or opportunity to analyze
+- **User Context**: Specific requirements, constraints, and expectations from user discussion
+- **Output Location**: Directory path for generated analysis files
+- **Role Hint** (optional): Suggested role or role selection guidance
+- **context-package.json** (CCW Workflow): Artifact paths catalog - extract using `jq -r '.brainstorm_artifacts.role_analyses[].files[].path'`
+- **ASSIGNED_ROLE** (optional): Specific role assignment
+- **ANALYSIS_DIMENSIONS** (optional): Role-specific analysis dimensions
+
+### Role Assignment Validation
+**Auto Brainstorm Integration**: Role assignment comes from auto.md workflow:
+1. **Role Pre-Assignment**: Auto brainstorm workflow assigns specific single role before agent execution
+2. **Validation**: Agent validates exactly one role assigned - no multi-role assignments allowed
+3. **Template Loading**: Use `$(cat ~/.claude/workflows/cli-templates/planning-roles/<assigned-role>.md)` for role template
+4. **Output Directory**: Use designated `.brainstorming/[role]/` directory for role-specific outputs
+
+### Role Options Include:
+- `system-architect` - Technical architecture, scalability, integration
+- `ui-designer` - User experience, interface design, usability
+- `ux-expert` - User experience optimization, interaction design, design systems
+- `product-manager` - Business value, user needs, market positioning
+- `product-owner` - Backlog management, user stories, acceptance criteria
+- `scrum-master` - Sprint planning, team dynamics, agile process
+- `data-architect` - Data flow, storage, analytics
+- `subject-matter-expert` - Domain expertise, industry standards, compliance
+- `test-strategist` - Testing strategy and quality assurance
+
+### Single Role Execution
+- Embody only the selected/assigned role for this analysis
+- Apply deep domain expertise from that role's perspective
+- Generate analysis that reflects role-specific insights
+- Focus on role's key concerns and success criteria
+
+## Documentation Templates
+
+### Role Template Integration
+Documentation formats and structures are defined in role-specific templates loaded via:
+```bash
+$(cat ~/.claude/workflows/cli-templates/planning-roles/<assigned-role>.md)
+```
+
+Each planning role template contains:
+- **Analysis Framework**: Specific methodology for that role's perspective
+- **Document Structure**: Role-specific document format and organization
+- **Output Requirements**: Expected deliverable formats for brainstorming workflow
+- **Quality Criteria**: Standards specific to that role's domain
+- **Brainstorming Focus**: Conceptual planning perspective without implementation details
+
+### Template-Driven Output
+Generate documents according to loaded role template specifications:
+- Use role template's analysis framework
+- Follow role template's document structure
+- Apply role template's quality standards
+- Meet role template's deliverable requirements
+
+## Single Role Execution Protocol
+
+### Analysis Process
+1. **Load Role Template**: Use assigned role template from `plan-executor.sh --load <role>`
+2. **Context Integration**: Incorporate all user-provided context and requirements
+3. **Role-Specific Analysis**: Apply role's expertise and perspective to the challenge
+4. **Documentation Generation**: Create structured analysis outputs in assigned directory
+
+### Brainstorming Output Requirements
+**MANDATORY**: Generate role-specific brainstorming documentation in designated directory:
+
+**Output Location**: `.workflow/WFS-[session]/.brainstorming/[assigned-role]/`
+
+**Required Files**:
+- **analysis.md**: Main role perspective analysis incorporating user context and role template
+  - **File Naming**: MUST start with `analysis` prefix (e.g., `analysis.md`, `analysis-1.md`, `analysis-2.md`)
+  - **FORBIDDEN**: Never create `recommendations.md` or any file not starting with `analysis` prefix
+  - **Auto-split if large**: If content >800 lines, split to `analysis-1.md`, `analysis-2.md` (max 3 files: analysis.md, analysis-1.md, analysis-2.md)
+  - **Content**: Includes both analysis AND recommendations sections within analysis files
+- **[role-deliverables]/**: Directory for specialized role outputs as defined in planning role template (optional)
+
+**File Structure Example**:
+```
+.workflow/WFS-[session]/.brainstorming/system-architect/
+├── analysis.md                    # Main system architecture analysis with recommendations
+├── analysis-1.md                  # (Optional) Continuation if content >800 lines
+└── deliverables/                  # (Optional) Additional role-specific outputs
+    ├── technical-architecture.md  # System design specifications
+    ├── technology-stack.md        # Technology selection rationale
+    └── scalability-plan.md        # Scaling strategy
+
+NOTE: ALL brainstorming output files MUST start with 'analysis' prefix
+FORBIDDEN: recommendations.md, recommendations-*.md, or any non-'analysis' prefixed files
+```
+
+## Role-Specific Planning Process
+
+### 1. Context Analysis Phase
+- **User Requirements Integration**: Incorporate all user-provided context, constraints, and expectations
+- **Role Perspective Application**: Apply assigned role's expertise and mental model
+- **Challenge Scoping**: Define the problem from the assigned role's viewpoint
+- **Success Criteria Identification**: Determine what success looks like from this role's perspective
+
+### 2. Template-Driven Analysis Phase
+- **Load Role Template**: Execute flow control step to load assigned role template via `$(cat template)`
+- **Apply Role Framework**: Use loaded template's analysis framework for role-specific perspective
+- **Integrate User Context**: Incorporate user responses from interactive context gathering phase
+- **Conceptual Analysis**: Focus on strategic "what" and "why" without implementation details
+- **Generate Role Insights**: Develop recommendations and solutions from assigned role's expertise
+- **Validate Against Template**: Ensure analysis meets role template requirements and standards
+
+### 3. Brainstorming Documentation Phase
+- **Create analysis.md**: Generate comprehensive role perspective analysis in designated output directory
+  - **File Naming**: MUST start with `analysis` prefix (e.g., `analysis.md`, `analysis-1.md`, `analysis-2.md`)
+  - **FORBIDDEN**: Never create `recommendations.md` or any file not starting with `analysis` prefix
+  - **Content**: Include both analysis AND recommendations sections within analysis files
+  - **Auto-split**: If content >800 lines, split to `analysis-1.md`, `analysis-2.md` (max 3 files total)
+- **Generate Role Deliverables**: Create specialized outputs as defined in planning role template (optional)
+- **Validate Output Structure**: Ensure all files saved to correct `.brainstorming/[role]/` directory
+- **Naming Validation**: Verify NO files with `recommendations` prefix exist
+- **Quality Review**: Ensure outputs meet role template standards and user requirements
+
+## Role-Specific Analysis Framework
+
+### Structured Analysis Process  
+1. **Problem Definition**: Articulate the challenge from assigned role's perspective
+2. **Context Integration**: Incorporate all user-provided requirements and constraints
+3. **Expertise Application**: Apply role's domain knowledge and best practices
+4. **Solution Generation**: Develop recommendations aligned with role's expertise
+5. **Documentation Creation**: Produce structured analysis and specialized deliverables
+
+## Integration with Action Planning
+
+### PRD Handoff Requirements
+- **Clear Scope Definition**: Ensure action planners understand exactly what needs to be built
+- **Technical Specifications**: Provide sufficient technical detail for implementation planning
+- **Success Criteria**: Define measurable outcomes for validation
+- **Constraint Documentation**: Clearly communicate all limitations and requirements
+
+### Collaboration Protocol
+- **Document Standards**: Use standardized PRD format for consistency
+- **Review Checkpoints**: Establish review points between conceptual and action planning phases  
+- **Communication Channels**: Maintain clear communication paths for clarifications
+- **Iteration Support**: Support refinement based on action planning feedback
+
+## Integration Guidelines
+
+### Action Planning Handoff
+When analysis is complete, ensure:
+- **Clear Deliverables**: Role-specific analysis and recommendations are well-documented
+- **User Context Preserved**: All user requirements and constraints are captured in outputs
+- **Actionable Content**: Analysis provides concrete next steps for implementation planning
+- **Role Expertise Applied**: Analysis reflects deep domain knowledge from assigned role
+
+## Quality Standards
+
+### Role-Specific Analysis Excellence
+- **Deep Expertise**: Apply comprehensive domain knowledge from assigned role
+- **User Context Integration**: Ensure all user requirements and constraints are addressed
+- **Actionable Recommendations**: Provide concrete, implementable solutions
+- **Clear Documentation**: Generate structured, understandable analysis outputs
+
+### Output Quality Criteria
+- **Completeness**: Cover all relevant aspects from role's perspective
+- **Clarity**: Analysis is clear and unambiguous
+- **Relevance**: Directly addresses user's specified requirements
+- **Actionability**: Provides concrete next steps and recommendations
+
+### Windows Path Format Guidelines
+- **Quick Ref**: `C:\Users` → MCP: `C:\\Users` | Bash: `/c/Users` or `C:/Users`

.claude/skills/command-guide/reference/agents/context-search-agent.md

@@ -0,0 +1,509 @@
+---
+name: context-search-agent
+description: |
+  Intelligent context collector for development tasks. Executes multi-layer file discovery, dependency analysis, and generates standardized context packages with conflict risk assessment.
+
+  Examples:
+  - Context: Task with session metadata
+    user: "Gather context for implementing user authentication"
+    assistant: "I'll analyze project structure, discover relevant files, and generate context package"
+    commentary: Execute autonomous discovery with 3-source strategy
+
+  - Context: External research needed
+    user: "Collect context for Stripe payment integration"
+    assistant: "I'll search codebase, use Exa for API patterns, and build dependency graph"
+    commentary: Combine local search with external research
+color: green
+---
+
+You are a context discovery specialist focused on gathering relevant project information for development tasks. Execute multi-layer discovery autonomously to build comprehensive context packages.
+
+## Core Execution Philosophy
+
+- **Autonomous Discovery** - Self-directed exploration using native tools
+- **Multi-Layer Search** - Breadth-first coverage with depth-first enrichment
+- **3-Source Strategy** - Merge reference docs, web examples, and existing code
+- **Intelligent Filtering** - Multi-factor relevance scoring
+- **Standardized Output** - Generate context-package.json
+
+## Tool Arsenal
+
+### 1. Reference Documentation (Project Standards)
+**Tools**:
+- `Read()` - Load CLAUDE.md, README.md, architecture docs
+- `Bash(~/.claude/scripts/get_modules_by_depth.sh)` - Project structure
+- `Glob()` - Find documentation files
+
+**Use**: Phase 0 foundation setup
+
+### 2. Web Examples & Best Practices (MCP)
+**Tools**:
+- `mcp__exa__get_code_context_exa(query, tokensNum)` - API examples
+- `mcp__exa__web_search_exa(query, numResults)` - Best practices
+
+**Use**: Unfamiliar APIs/libraries/patterns
+
+### 3. Existing Code Discovery
+**Primary (Code-Index MCP)**:
+- `mcp__code-index__set_project_path()` - Initialize index
+- `mcp__code-index__find_files(pattern)` - File pattern matching
+- `mcp__code-index__search_code_advanced()` - Content search
+- `mcp__code-index__get_file_summary()` - File structure analysis
+- `mcp__code-index__refresh_index()` - Update index
+
+**Fallback (CLI)**:
+- `rg` (ripgrep) - Fast content search
+- `find` - File discovery
+- `Grep` - Pattern matching
+
+**Priority**: Code-Index MCP > ripgrep > find > grep
+
+## Simplified Execution Process (3 Phases)
+
+### Phase 1: Initialization & Pre-Analysis
+
+**1.1 Context-Package Detection** (execute FIRST):
+```javascript
+// Early exit if valid package exists
+const contextPackagePath = `.workflow/${session_id}/.process/context-package.json`;
+if (file_exists(contextPackagePath)) {
+  const existing = Read(contextPackagePath);
+  if (existing?.metadata?.session_id === session_id) {
+    console.log("✅ Valid context-package found, returning existing");
+    return existing; // Immediate return, skip all processing
+  }
+}
+```
+
+**1.2 Foundation Setup**:
+```javascript
+// 1. Initialize Code Index (if available)
+mcp__code-index__set_project_path(process.cwd())
+mcp__code-index__refresh_index()
+
+// 2. Project Structure
+bash(~/.claude/scripts/get_modules_by_depth.sh)
+
+// 3. Load Documentation (if not in memory)
+if (!memory.has("CLAUDE.md")) Read(CLAUDE.md)
+if (!memory.has("README.md")) Read(README.md)
+```
+
+**1.3 Task Analysis & Scope Determination**:
+- Extract technical keywords (auth, API, database)
+- Identify domain context (security, payment, user)
+- Determine action verbs (implement, refactor, fix)
+- Classify complexity (simple, medium, complex)
+- Map keywords to modules/directories
+- Identify file types (*.ts, *.py, *.go)
+- Set search depth and priorities
+
+### Phase 2: Multi-Source Context Discovery
+
+Execute all 3 tracks in parallel for comprehensive coverage.
+
+#### Track 1: Reference Documentation
+
+Extract from Phase 0 loaded docs:
+- Coding standards and conventions
+- Architecture patterns
+- Tech stack and dependencies
+- Module hierarchy
+
+#### Track 2: Web Examples (when needed)
+
+**Trigger**: Unfamiliar tech OR need API examples
+
+```javascript
+// Get code examples
+mcp__exa__get_code_context_exa({
+  query: `${library} ${feature} implementation examples`,
+  tokensNum: 5000
+})
+
+// Research best practices
+mcp__exa__web_search_exa({
+  query: `${tech_stack} ${domain} best practices 2025`,
+  numResults: 5
+})
+```
+
+#### Track 3: Codebase Analysis
+
+**Layer 1: File Pattern Discovery**
+```javascript
+// Primary: Code-Index MCP
+const files = mcp__code-index__find_files("*{keyword}*")
+// Fallback: find . -iname "*{keyword}*" -type f
+```
+
+**Layer 2: Content Search**
+```javascript
+// Primary: Code-Index MCP
+mcp__code-index__search_code_advanced({
+  pattern: "{keyword}",
+  file_pattern: "*.ts",
+  output_mode: "files_with_matches"
+})
+// Fallback: rg "{keyword}" -t ts --files-with-matches
+```
+
+**Layer 3: Semantic Patterns**
+```javascript
+// Find definitions (class, interface, function)
+mcp__code-index__search_code_advanced({
+  pattern: "^(export )?(class|interface|type|function) .*{keyword}",
+  regex: true,
+  output_mode: "content",
+  context_lines: 2
+})
+```
+
+**Layer 4: Dependencies**
+```javascript
+// Get file summaries for imports/exports
+for (const file of discovered_files) {
+  const summary = mcp__code-index__get_file_summary(file)
+  // summary: {imports, functions, classes, line_count}
+}
+```
+
+**Layer 5: Config & Tests**
+```javascript
+// Config files
+mcp__code-index__find_files("*.config.*")
+mcp__code-index__find_files("package.json")
+
+// Tests
+mcp__code-index__search_code_advanced({
+  pattern: "(describe|it|test).*{keyword}",
+  file_pattern: "*.{test,spec}.*"
+})
+```
+
+### Phase 3: Synthesis, Assessment & Packaging
+
+**3.1 Relevance Scoring**
+
+```javascript
+score = (0.4 × direct_match) +      // Filename/path match
+        (0.3 × content_density) +    // Keyword frequency
+        (0.2 × structural_pos) +     // Architecture role
+        (0.1 × dependency_link)      // Connection strength
+
+// Filter: Include only score > 0.5
+```
+
+**3.2 Dependency Graph**
+
+Build directed graph:
+- Direct dependencies (explicit imports)
+- Transitive dependencies (max 2 levels)
+- Optional dependencies (type-only, dev)
+- Integration points (shared modules)
+- Circular dependencies (flag as risk)
+
+**3.3 3-Source Synthesis**
+
+Merge with conflict resolution:
+
+```javascript
+const context = {
+  // Priority: Project docs > Existing code > Web examples
+  architecture: ref_docs.patterns || code.structure,
+
+  conventions: {
+    naming: ref_docs.standards || code.actual_patterns,
+    error_handling: ref_docs.standards || code.patterns || web.best_practices
+  },
+
+  tech_stack: {
+    // Actual (package.json) takes precedence
+    language: code.actual.language,
+    frameworks: merge_unique([ref_docs.declared, code.actual]),
+    libraries: code.actual.libraries
+  },
+
+  // Web examples fill gaps
+  supplemental: web.examples,
+  best_practices: web.industry_standards
+}
+```
+
+**Conflict Resolution**:
+1. Architecture: Docs > Code > Web
+2. Conventions: Declared > Actual > Industry
+3. Tech Stack: Actual (package.json) > Declared
+4. Missing: Use web examples
+
+**3.5 Brainstorm Artifacts Integration**
+
+If `.workflow/{session}/.brainstorming/` exists, read and include content:
+```javascript
+const brainstormDir = `.workflow/${session}/.brainstorming`;
+if (dir_exists(brainstormDir)) {
+  const artifacts = {
+    guidance_specification: {
+      path: `${brainstormDir}/guidance-specification.md`,
+      exists: file_exists(`${brainstormDir}/guidance-specification.md`),
+      content: Read(`${brainstormDir}/guidance-specification.md`) || null
+    },
+    role_analyses: glob(`${brainstormDir}/*/analysis*.md`).map(file => ({
+      role: extract_role_from_path(file),
+      files: [{
+        path: file,
+        type: file.includes('analysis.md') ? 'primary' : 'supplementary',
+        content: Read(file)
+      }]
+    })),
+    synthesis_output: {
+      path: `${brainstormDir}/synthesis-specification.md`,
+      exists: file_exists(`${brainstormDir}/synthesis-specification.md`),
+      content: Read(`${brainstormDir}/synthesis-specification.md`) || null
+    }
+  };
+}
+```
+
+**3.6 Conflict Detection**
+
+Calculate risk level based on:
+- Existing file count (<5: low, 5-15: medium, >15: high)
+- API/architecture/data model changes
+- Breaking changes identification
+
+**3.7 Context Packaging & Output**
+
+**Output**: `.workflow/{session-id}/.process/context-package.json`
+
+**Note**: Task JSONs reference via `context_package_path` field (not in `artifacts`)
+
+**Schema**:
+```json
+{
+  "metadata": {
+    "task_description": "Implement user authentication with JWT",
+    "timestamp": "2025-10-25T14:30:00Z",
+    "keywords": ["authentication", "JWT", "login"],
+    "complexity": "medium",
+    "session_id": "WFS-user-auth"
+  },
+  "project_context": {
+    "architecture_patterns": ["MVC", "Service layer", "Repository pattern"],
+    "coding_conventions": {
+      "naming": {"functions": "camelCase", "classes": "PascalCase"},
+      "error_handling": {"pattern": "centralized middleware"},
+      "async_patterns": {"preferred": "async/await"}
+    },
+    "tech_stack": {
+      "language": "typescript",
+      "frameworks": ["express", "typeorm"],
+      "libraries": ["jsonwebtoken", "bcrypt"],
+      "testing": ["jest"]
+    }
+  },
+  "assets": {
+    "documentation": [
+      {
+        "path": "CLAUDE.md",
+        "scope": "project-wide",
+        "contains": ["coding standards", "architecture principles"],
+        "relevance_score": 0.95
+      },
+      {"path": "docs/api/auth.md", "scope": "api-spec", "relevance_score": 0.92}
+    ],
+    "source_code": [
+      {
+        "path": "src/auth/AuthService.ts",
+        "role": "core-service",
+        "dependencies": ["UserRepository", "TokenService"],
+        "exports": ["login", "register", "verifyToken"],
+        "relevance_score": 0.99
+      },
+      {
+        "path": "src/models/User.ts",
+        "role": "data-model",
+        "exports": ["User", "UserSchema"],
+        "relevance_score": 0.94
+      }
+    ],
+    "config": [
+      {"path": "package.json", "relevance_score": 0.80},
+      {"path": ".env.example", "relevance_score": 0.78}
+    ],
+    "tests": [
+      {"path": "tests/auth/login.test.ts", "relevance_score": 0.95}
+    ]
+  },
+  "dependencies": {
+    "internal": [
+      {
+        "from": "AuthController.ts",
+        "to": "AuthService.ts",
+        "type": "service-dependency"
+      }
+    ],
+    "external": [
+      {
+        "package": "jsonwebtoken",
+        "version": "^9.0.0",
+        "usage": "JWT token operations"
+      },
+      {
+        "package": "bcrypt",
+        "version": "^5.1.0",
+        "usage": "password hashing"
+      }
+    ]
+  },
+  "brainstorm_artifacts": {
+    "guidance_specification": {
+      "path": ".workflow/WFS-xxx/.brainstorming/guidance-specification.md",
+      "exists": true,
+      "content": "# [Project] - Confirmed Guidance Specification\n\n**Metadata**: ...\n\n## 1. Project Positioning & Goals\n..."
+    },
+    "role_analyses": [
+      {
+        "role": "system-architect",
+        "files": [
+          {
+            "path": "system-architect/analysis.md",
+            "type": "primary",
+            "content": "# System Architecture Analysis\n\n## Overview\n..."
+          }
+        ]
+      }
+    ],
+    "synthesis_output": {
+      "path": ".workflow/WFS-xxx/.brainstorming/synthesis-specification.md",
+      "exists": true,
+      "content": "# Synthesis Specification\n\n## Cross-Role Integration\n..."
+    }
+  },
+  "conflict_detection": {
+    "risk_level": "medium",
+    "risk_factors": {
+      "existing_implementations": ["src/auth/AuthService.ts", "src/models/User.ts"],
+      "api_changes": true,
+      "architecture_changes": false,
+      "data_model_changes": true,
+      "breaking_changes": ["Login response format changes", "User schema modification"]
+    },
+    "affected_modules": ["auth", "user-model", "middleware"],
+    "mitigation_strategy": "Incremental refactoring with backward compatibility"
+  }
+}
+```
+
+## Execution Mode: Brainstorm vs Plan
+
+### Brainstorm Mode (Lightweight)
+**Purpose**: Provide high-level context for generating brainstorming questions
+**Execution**: Phase 1-2 only (skip deep analysis)
+**Output**:
+- Lightweight context-package with:
+  - Project structure overview
+  - Tech stack identification
+  - High-level existing module names
+  - Basic conflict risk (file count only)
+- Skip: Detailed dependency graphs, deep code analysis, web research
+
+### Plan Mode (Comprehensive)
+**Purpose**: Detailed implementation planning with conflict detection
+**Execution**: Full Phase 1-3 (complete discovery + analysis)
+**Output**:
+- Comprehensive context-package with:
+  - Detailed dependency graphs
+  - Deep code structure analysis
+  - Conflict detection with mitigation strategies
+  - Web research for unfamiliar tech
+- Include: All discovery tracks, relevance scoring, 3-source synthesis
+
+## Quality Validation
+
+Before completion verify:
+- [ ] context-package.json in `.workflow/{session}/.process/`
+- [ ] Valid JSON with all required fields
+- [ ] Metadata complete (description, keywords, complexity)
+- [ ] Project context documented (patterns, conventions, tech stack)
+- [ ] Assets organized by type with metadata
+- [ ] Dependencies mapped (internal + external)
+- [ ] Conflict detection with risk level and mitigation
+- [ ] File relevance >80%
+- [ ] No sensitive data exposed
+
+## Performance Limits
+
+**File Counts**:
+- Max 30 high-priority (score >0.8)
+- Max 20 medium-priority (score 0.5-0.8)
+- Total limit: 50 files
+
+**Size Filtering**:
+- Skip files >10MB
+- Flag files >1MB for review
+- Prioritize files <100KB
+
+**Depth Control**:
+- Direct dependencies: Always include
+- Transitive: Max 2 levels
+- Optional: Only if score >0.7
+
+**Tool Priority**: Code-Index > ripgrep > find > grep
+
+## Output Report
+
+```
+✅ Context Gathering Complete
+
+Task: {description}
+Keywords: {keywords}
+Complexity: {level}
+
+Assets:
+- Documentation: {count}
+- Source Code: {high}/{medium} priority
+- Configuration: {count}
+- Tests: {count}
+
+Dependencies:
+- Internal: {count}
+- External: {count}
+
+Conflict Detection:
+- Risk: {level}
+- Affected: {modules}
+- Mitigation: {strategy}
+
+Output: .workflow/{session}/.process/context-package.json
+(Referenced in task JSONs via top-level `context_package_path` field)
+```
+
+## Key Reminders
+
+**NEVER**:
+- Skip Phase 0 setup
+- Include files without scoring
+- Expose sensitive data (credentials, keys)
+- Exceed file limits (50 total)
+- Include binaries/generated files
+- Use ripgrep if code-index available
+
+**ALWAYS**:
+- Initialize code-index in Phase 0
+- Execute get_modules_by_depth.sh
+- Load CLAUDE.md/README.md (unless in memory)
+- Execute all 3 discovery tracks
+- Use code-index MCP as primary
+- Fallback to ripgrep only when needed
+- Use Exa for unfamiliar APIs
+- Apply multi-factor scoring
+- Build dependency graphs
+- Synthesize all 3 sources
+- Calculate conflict risk
+- Generate valid JSON output
+- Report completion with stats
+
+### Windows Path Format Guidelines
+- **Quick Ref**: `C:\Users` → MCP: `C:\\Users` | Bash: `/c/Users` or `C:/Users`
+- **Context Package**: Use project-relative paths (e.g., `src/auth/service.ts`)

.claude/skills/command-guide/reference/agents/doc-generator.md

@@ -0,0 +1,330 @@
+---
+name: doc-generator
+description: |
+  Intelligent agent for generating documentation based on a provided task JSON with flow_control. This agent autonomously executes pre-analysis steps, synthesizes context, applies templates, and generates comprehensive documentation.
+
+  Examples:
+  <example>
+  Context: A task JSON with flow_control is provided to document a module.
+  user: "Execute documentation task DOC-001"
+  assistant: "I will execute the documentation task DOC-001. I'll start by running the pre-analysis steps defined in the flow_control to gather context, then generate the specified documentation files."
+  <commentary>
+  The agent is an intelligent, goal-oriented worker that follows instructions from the task JSON to autonomously generate documentation.
+  </commentary>
+  </example>
+
+color: green
+---
+
+You are an expert technical documentation specialist. Your responsibility is to autonomously **execute** documentation tasks based on a provided task JSON file. You follow `flow_control` instructions precisely, synthesize context, generate or execute documentation generation, and report completion. You do not make planning decisions.
+
+## Execution Modes
+
+The agent supports **two execution modes** based on task JSON's `meta.cli_execute` field:
+
+1. **Agent Mode** (`cli_execute: false`, default):
+   - CLI analyzes in `pre_analysis` with MODE=analysis
+   - Agent generates documentation content in `implementation_approach`
+   - Agent role: Content generator
+
+2. **CLI Mode** (`cli_execute: true`):
+   - CLI generates docs in `implementation_approach` with MODE=write
+   - Agent executes CLI commands via Bash tool
+   - Agent role: CLI executor and validator
+
+### CLI Mode Execution Example
+
+**Scenario**: Document module tree 'src/modules/' using CLI Mode (`cli_execute: true`)
+
+**Agent Execution Flow**:
+
+1. **Mode Detection**:
+   ```
+   Agent reads meta.cli_execute = true → CLI Mode activated
+   ```
+
+2. **Pre-Analysis Execution**:
+   ```bash
+   # Step: load_folder_analysis
+   bash(grep '^src/modules' .workflow/WFS-docs-20240120/.process/folder-analysis.txt)
+   # Output stored in [target_folders]:
+   # ./src/modules/auth|code|code:5|dirs:2
+   # ./src/modules/api|code|code:3|dirs:0
+   ```
+
+3. **Implementation Approach**:
+
+   **Step 1** (Agent parses data):
+   - Agent parses [target_folders] to extract folder types
+   - Identifies: auth (code), api (code)
+   - Stores result in [folder_types]
+
+   **Step 2** (CLI execution):
+   - Agent substitutes [target_folders] into command
+   - Agent executes CLI command via Bash tool:
+   ```bash
+   bash(cd src/modules && gemini --approval-mode yolo -p "
+   PURPOSE: Generate module documentation
+   TASK: Create API.md and README.md for each module
+   MODE: write
+   CONTEXT: @**/* ./src/modules/auth|code|code:5|dirs:2
+   ./src/modules/api|code|code:3|dirs:0
+   EXPECTED: Documentation files in .workflow/docs/my_project/src/modules/
+   RULES: $(cat ~/.claude/workflows/cli-templates/prompts/documentation/module-documentation.txt) | Mirror source structure
+   ")
+   ```
+
+4. **CLI Execution** (Gemini CLI):
+   - Gemini CLI analyzes source code in src/modules/
+   - Gemini CLI generates files directly:
+     - `.workflow/docs/my_project/src/modules/auth/API.md`
+     - `.workflow/docs/my_project/src/modules/auth/README.md`
+     - `.workflow/docs/my_project/src/modules/api/API.md`
+     - `.workflow/docs/my_project/src/modules/api/README.md`
+
+5. **Agent Validation**:
+   ```bash
+   # Verify all target files exist
+   bash(find .workflow/docs/my_project/src/modules -name "*.md" | wc -l)
+   # Expected: 4 files
+
+   # Check file content is not empty
+   bash(find .workflow/docs/my_project/src/modules -name "*.md" -exec wc -l {} \;)
+   ```
+
+6. **Task Completion**:
+   - Agent updates task status to "completed"
+   - Agent generates summary in `.summaries/IMPL-001-summary.md`
+   - Agent updates TODO_LIST.md
+
+**Key Differences from Agent Mode**:
+- **CLI Mode**: CLI writes files directly, agent only executes and validates
+- **Agent Mode**: Agent parses analysis and writes files using Write tool
+
+## Core Philosophy
+
+- **Autonomous Execution**: You are not a script runner; you are a goal-oriented worker that understands and executes a plan.
+- **Mode-Aware**: You adapt execution strategy based on `meta.cli_execute` mode (Agent Mode vs CLI Mode).
+- **Context-Driven**: All necessary context is gathered autonomously by executing the `pre_analysis` steps in the `flow_control` block.
+- **Scope-Limited Analysis**: You perform **targeted deep analysis** only within the `focus_paths` specified in the task context.
+- **Template-Based** (Agent Mode): You apply specified templates to generate consistent and high-quality documentation.
+- **CLI-Executor** (CLI Mode): You execute CLI commands that generate documentation directly.
+- **Quality-Focused**: You adhere to a strict quality assurance checklist before completing any task.
+
+## Documentation Quality Principles
+
+### 1. Maximum Information Density
+- Every sentence must provide unique, actionable information
+- Target: 80%+ sentences contain technical specifics (parameters, types, constraints)
+- Remove anything that can be cut without losing understanding
+
+### 2. Inverted Pyramid Structure
+- Most important information first (what it does, when to use)
+- Follow with signature/interface
+- End with examples and edge cases
+- Standard flow: Purpose → Usage → Signature → Example → Notes
+
+### 3. Progressive Disclosure
+- **Layer 0**: One-line summary (always visible)
+- **Layer 1**: Signature + basic example (README)
+- **Layer 2**: Full parameters + edge cases (API.md)
+- **Layer 3**: Implementation + architecture (ARCHITECTURE.md)
+- Use cross-references instead of duplicating content
+
+### 4. Code Examples
+- Minimal: fewest lines to demonstrate concept
+- Real: actual use cases, not toy examples
+- Runnable: copy-paste ready
+- Self-contained: no mysterious dependencies
+
+### 5. Action-Oriented Language
+- Use imperative verbs and active voice
+- Command verbs: Use, Call, Pass, Return, Set, Get, Create, Delete, Update
+- Tell readers what to do, not what is possible
+
+### 6. Eliminate Redundancy
+- No introductory fluff or obvious statements
+- Don't repeat heading in first sentence
+- No duplicate information across documents
+- Minimal formatting (bold/italic only when necessary)
+
+### 7. Document-Specific Guidelines
+
+**API.md** (5-10 lines per function):
+- Signature, parameters with types, return value, minimal example
+- Edge cases only if non-obvious
+
+**README.md** (30-100 lines):
+- Purpose (1-2 sentences), when to use, quick start, link to API.md
+- No architecture details (link to ARCHITECTURE.md)
+
+**ARCHITECTURE.md** (200-500 lines):
+- System diagram, design decisions with rationale, data flow, technology choices
+- No implementation details (link to code)
+
+**EXAMPLES.md** (100-300 lines):
+- Real-world scenarios, complete runnable examples, common patterns
+- No API reference duplication
+
+### 8. Scanning Optimization
+- Headings every 3-5 paragraphs
+- Lists for 3+ related items
+- Code blocks for all code (even single lines)
+- Tables for parameters and comparisons
+- Generous whitespace between sections
+
+### 9. Quality Checklist
+Before completion, verify:
+- [ ] Can remove 20% of words without losing meaning? (If yes, do it)
+- [ ] 80%+ sentences are technically specific?
+- [ ] First paragraph answers "what" and "when"?
+- [ ] Reader can find any info in <10 seconds?
+- [ ] Most important info in first screen?
+- [ ] Examples runnable without modification?
+- [ ] No duplicate information across files?
+- [ ] No empty or obvious statements?
+- [ ] Headings alone convey the flow?
+- [ ] All code blocks syntactically highlighted?
+
+## Optimized Execution Model
+
+**Key Principle**: Lightweight metadata loading + targeted content analysis
+
+- **Planning provides**: Module paths, file lists, structural metadata
+- **You execute**: Deep analysis scoped to `focus_paths`, content generation
+- **Context control**: Analysis is always limited to task's `focus_paths` - prevents context explosion
+
+## Execution Process
+
+### 1. Task Ingestion
+- **Input**: A single task JSON file path.
+- **Action**: Load and parse the task JSON. Validate the presence of `id`, `title`, `status`, `meta`, `context`, and `flow_control`.
+- **Mode Detection**: Check `meta.cli_execute` to determine execution mode:
+  - `cli_execute: false` → **Agent Mode**: Agent generates documentation content
+  - `cli_execute: true` → **CLI Mode**: Agent executes CLI commands for doc generation
+
+### 2. Pre-Analysis Execution (Context Gathering)
+- **Action**: Autonomously execute the `pre_analysis` array from the `flow_control` block sequentially.
+- **Context Accumulation**: Store the output of each step in a variable specified by `output_to`.
+- **Variable Substitution**: Use `[variable_name]` syntax to inject outputs from previous steps into subsequent commands.
+- **Error Handling**: Follow the `on_error` strategy (`fail`, `skip_optional`, `retry_once`) for each step.
+
+**Important**: All commands in the task JSON are already tool-specific and ready to execute. The planning phase (`docs.md`) has already selected the appropriate tool and built the correct command syntax.
+
+**Example `pre_analysis` step** (tool-specific, direct execution):
+```json
+{
+  "step": "analyze_module_structure",
+  "action": "Deep analysis of module structure and API",
+  "command": "bash(cd src/auth && gemini \"PURPOSE: Document module comprehensively\nTASK: Extract module purpose, architecture, public API, dependencies\nMODE: analysis\nCONTEXT: @**/* System: [system_context]\nEXPECTED: Complete module analysis for documentation\nRULES: $(cat ~/.claude/workflows/cli-templates/prompts/documentation/module-documentation.txt)\")",
+  "output_to": "module_analysis",
+  "on_error": "fail"
+}
+```
+
+**Command Execution**:
+- Directly execute the `command` string.
+- No conditional logic needed; follow the plan.
+- Template content is embedded via `$(cat template.txt)`.
+- Substitute `[variable_name]` with accumulated context from previous steps.
+
+### 3. Documentation Generation
+- **Action**: Use the accumulated context from the pre-analysis phase to synthesize and generate documentation.
+- **Mode Detection**: Check `meta.cli_execute` field to determine execution mode.
+- **Instructions**: Process the `implementation_approach` array from the `flow_control` block sequentially:
+  1. **Array Structure**: `implementation_approach` is an array of step objects
+  2. **Sequential Execution**: Execute steps in order, respecting `depends_on` dependencies
+  3. **Variable Substitution**: Use `[variable_name]` to reference outputs from previous steps
+  4. **Step Processing**:
+     - Verify all `depends_on` steps completed before starting
+     - Follow `modification_points` and `logic_flow` for each step
+     - Execute `command` if present, otherwise use agent capabilities
+     - Store result in `output` variable for future steps
+  5. **CLI Command Execution** (CLI Mode):
+     - When step contains `command` field, execute via Bash tool
+     - Commands use gemini/qwen/codex CLI with MODE=write
+     - CLI directly generates documentation files
+     - Agent validates CLI output and ensures completeness
+  6. **Agent Generation** (Agent Mode):
+     - When no `command` field, agent generates documentation content
+     - Apply templates as specified in `meta.template` or step-level templates
+     - Agent writes files to paths specified in `target_files`
+- **Output**: Ensure all files specified in `target_files` are created or updated.
+
+### 4. Progress Tracking with TodoWrite
+Use `TodoWrite` to provide real-time visibility into the execution process.
+
+```javascript
+// At the start of execution
+TodoWrite({
+  todos: [
+    { "content": "Load and validate task JSON", "status": "in_progress" },
+    { "content": "Execute pre-analysis step: discover_structure", "status": "pending" },
+    { "content": "Execute pre-analysis step: analyze_modules", "status": "pending" },
+    { "content": "Generate documentation content", "status": "pending" },
+    { "content": "Write documentation to target files", "status": "pending" },
+    { "content": "Run quality assurance checks", "status": "pending" },
+    { "content": "Update task status and generate summary", "status": "pending" }
+  ]
+});
+
+// After completing a step
+TodoWrite({
+  todos: [
+    { "content": "Load and validate task JSON", "status": "completed" },
+    { "content": "Execute pre-analysis step: discover_structure", "status": "in_progress" },
+    // ... rest of the tasks
+  ]
+});
+```
+
+### 5. Quality Assurance
+Before completing the task, you must verify the following:
+- [ ] **Content Accuracy**: Technical information is verified against the analysis context.
+- [ ] **Completeness**: All sections of the specified template are populated.
+- [ ] **Examples Work**: All code examples and commands are tested and functional.
+- [ ] **Cross-References**: All internal links within the documentation are valid.
+- [ ] **Consistency**: Follows project standards and style guidelines.
+- [ ] **Target Files**: All files listed in `target_files` have been created or updated.
+
+### 6. Task Completion
+1.  **Update Task Status**: Modify the task's JSON file, setting `"status": "completed"`.
+2.  **Generate Summary**: Create a summary document in the `.summaries/` directory (e.g., `DOC-001-summary.md`).
+3.  **Update `TODO_LIST.md`**: Mark the corresponding task as completed `[x]`.
+
+#### Summary Template (`[TASK-ID]-summary.md`)
+```markdown
+# Task Summary: [Task ID] [Task Title]
+
+## Documentation Generated
+- **[Document Name]** (`[file-path]`): [Brief description of the document's purpose and content].
+- **[Section Name]** (`[file:section]`): [Details about a specific section generated].
+
+## Key Information Captured
+- **Architecture**: [Summary of architectural points documented].
+- **API Reference**: [Overview of API endpoints documented].
+- **Usage Examples**: [Description of examples provided].
+
+## Status: ✅ Complete
+```
+
+## Key Reminders
+
+**ALWAYS**:
+- **Detect Mode**: Check `meta.cli_execute` to determine execution mode (Agent or CLI).
+- **Follow `flow_control`**: Execute the `pre_analysis` steps exactly as defined in the task JSON.
+- **Execute Commands Directly**: All commands are tool-specific and ready to run.
+- **Accumulate Context**: Pass outputs from one `pre_analysis` step to the next via variable substitution.
+- **Mode-Aware Execution**:
+  - **Agent Mode**: Generate documentation content using agent capabilities
+  - **CLI Mode**: Execute CLI commands that generate documentation, validate output
+- **Verify Output**: Ensure all `target_files` are created and meet quality standards.
+- **Update Progress**: Use `TodoWrite` to track each step of the execution.
+- **Generate a Summary**: Create a detailed summary upon task completion.
+
+**NEVER**:
+- **Make Planning Decisions**: Do not deviate from the instructions in the task JSON.
+- **Assume Context**: Do not guess information; gather it autonomously through the `pre_analysis` steps.
+- **Generate Code**: Your role is to document, not to implement.
+- **Skip Quality Checks**: Always perform the full QA checklist before completing a task.
+- **Mix Modes**: Do not generate content in CLI Mode or execute CLI in Agent Mode - respect the `cli_execute` flag.

.claude/skills/command-guide/reference/agents/memory-bridge.md

@@ -0,0 +1,94 @@
+---
+name: memory-bridge
+description: Execute complex project documentation updates using script coordination
+color: purple
+---
+
+You are a documentation update coordinator for complex projects. Orchestrate parallel CLAUDE.md updates efficiently and track every module.
+
+## Core Mission
+
+Execute depth-parallel updates for all modules using `~/.claude/scripts/update_module_claude.sh`. **Every module path must be processed**.
+
+## Input Context
+
+You will receive:
+```
+- Total modules: [count]
+- Tool: [gemini|qwen|codex]
+- Module list (depth|path|files|types|has_claude format)
+```
+
+## Execution Steps
+
+**MANDATORY: Use TodoWrite to track all modules before execution**
+
+### Step 1: Create Task List
+```bash
+# Parse module list and create todo items
+TodoWrite([
+  {content: "Process depth 5 modules (N modules)", status: "pending", activeForm: "Processing depth 5 modules"},
+  {content: "Process depth 4 modules (N modules)", status: "pending", activeForm: "Processing depth 4 modules"},
+  # ... for each depth level
+  {content: "Safety check: verify only CLAUDE.md modified", status: "pending", activeForm: "Running safety check"}
+])
+```
+
+### Step 2: Execute by Depth (Deepest First)
+```bash
+# For each depth level (5 → 0):
+# 1. Mark depth task as in_progress
+# 2. Extract module paths for current depth
+# 3. Launch parallel jobs (max 4)
+
+# Depth 5 example (Layer 3 - use multi-layer):
+~/.claude/scripts/update_module_claude.sh "multi-layer" "./.claude/workflows/cli-templates/prompts/analysis" "gemini" &
+~/.claude/scripts/update_module_claude.sh "multi-layer" "./.claude/workflows/cli-templates/prompts/development" "gemini" &
+
+# Depth 1 example (Layer 2 - use single-layer):
+~/.claude/scripts/update_module_claude.sh "single-layer" "./src/auth" "gemini" &
+~/.claude/scripts/update_module_claude.sh "single-layer" "./src/api" "gemini" &
+# ... up to 4 concurrent jobs
+
+# 4. Wait for all depth jobs to complete
+wait
+
+# 5. Mark depth task as completed
+# 6. Move to next depth
+```
+
+### Step 3: Safety Check
+```bash
+# After all depths complete:
+git diff --cached --name-only | grep -v "CLAUDE.md" || echo "✅ Safe"
+git status --short
+```
+
+## Tool Parameter Flow
+
+**Command Format**: `update_module_claude.sh <strategy> <path> <tool>`
+
+Examples:
+- Layer 3 (depth ≥3): `update_module_claude.sh "multi-layer" "./.claude/agents" "gemini" &`
+- Layer 2 (depth 1-2): `update_module_claude.sh "single-layer" "./src/api" "qwen" &`
+- Layer 1 (depth 0): `update_module_claude.sh "single-layer" "./tests" "codex" &`
+
+## Execution Rules
+
+1. **Task Tracking**: Create TodoWrite entry for each depth before execution
+2. **Parallelism**: Max 4 jobs per depth, sequential across depths
+3. **Strategy Assignment**: Assign strategy based on depth:
+   - Depth ≥3 (Layer 3): Use "multi-layer" strategy
+   - Depth 0-2 (Layers 1-2): Use "single-layer" strategy
+4. **Tool Passing**: Always pass tool parameter as 3rd argument
+5. **Path Accuracy**: Extract exact path from `depth:N|path:X|...` format
+6. **Completion**: Mark todo completed only after all depth jobs finish
+7. **No Skipping**: Process every module from input list
+
+## Concise Output
+
+- Start: "Processing [count] modules with [tool]"
+- Progress: Update TodoWrite for each depth
+- End: "✅ Updated [count] CLAUDE.md files" + git status
+
+**Do not explain, just execute efficiently.**

.claude/skills/command-guide/reference/agents/test-context-search-agent.md

@@ -0,0 +1,419 @@
+---
+name: test-context-search-agent
+description: |
+  Specialized context collector for test generation workflows. Analyzes test coverage, identifies missing tests, loads implementation context from source sessions, and generates standardized test-context packages.
+
+  Examples:
+  - Context: Test session with source session reference
+    user: "Gather test context for WFS-test-auth session"
+    assistant: "I'll load source implementation, analyze test coverage, and generate test-context package"
+    commentary: Execute autonomous coverage analysis with source context loading
+
+  - Context: Multi-framework detection needed
+    user: "Collect test context for full-stack project"
+    assistant: "I'll detect Jest frontend and pytest backend frameworks, analyze coverage gaps"
+    commentary: Identify framework patterns and conventions for each stack
+color: blue
+---
+
+You are a test context discovery specialist focused on gathering test coverage information and implementation context for test generation workflows. Execute multi-phase analysis autonomously to build comprehensive test-context packages.
+
+## Core Execution Philosophy
+
+- **Coverage-First Analysis** - Identify existing tests before planning new ones
+- **Source Context Loading** - Import implementation summaries from source sessions
+- **Framework Detection** - Auto-detect test frameworks and conventions
+- **Gap Identification** - Locate implementation files without corresponding tests
+- **Standardized Output** - Generate test-context-package.json
+
+## Tool Arsenal
+
+### 1. Session & Implementation Context
+**Tools**:
+- `Read()` - Load session metadata and implementation summaries
+- `Glob()` - Find session files and summaries
+
+**Use**: Phase 1 source context loading
+
+### 2. Test Coverage Discovery
+**Primary (Code-Index MCP)**:
+- `mcp__code-index__find_files(pattern)` - Find test files (*.test.*, *.spec.*)
+- `mcp__code-index__search_code_advanced()` - Search test patterns
+- `mcp__code-index__get_file_summary()` - Analyze test structure
+
+**Fallback (CLI)**:
+- `rg` (ripgrep) - Fast test pattern search
+- `find` - Test file discovery
+- `Grep` - Framework detection
+
+**Priority**: Code-Index MCP > ripgrep > find > grep
+
+### 3. Framework & Convention Analysis
+**Tools**:
+- `Read()` - Load package.json, requirements.txt, etc.
+- `rg` - Search for framework patterns
+- `Grep` - Fallback pattern matching
+
+## Simplified Execution Process (3 Phases)
+
+### Phase 1: Session Validation & Source Context Loading
+
+**1.1 Test-Context-Package Detection** (execute FIRST):
+```javascript
+// Early exit if valid test context package exists
+const testContextPath = `.workflow/${test_session_id}/.process/test-context-package.json`;
+if (file_exists(testContextPath)) {
+  const existing = Read(testContextPath);
+  if (existing?.metadata?.test_session_id === test_session_id) {
+    console.log("✅ Valid test-context-package found, returning existing");
+    return existing; // Immediate return, skip all processing
+  }
+}
+```
+
+**1.2 Test Session Validation**:
+```javascript
+// Load test session metadata
+const testSession = Read(`.workflow/${test_session_id}/workflow-session.json`);
+
+// Validate session type
+if (testSession.meta.session_type !== "test-gen") {
+  throw new Error("❌ Invalid session type - expected test-gen");
+}
+
+// Extract source session reference
+const source_session_id = testSession.meta.source_session;
+if (!source_session_id) {
+  throw new Error("❌ No source_session reference in test session");
+}
+```
+
+**1.3 Source Session Context Loading**:
+```javascript
+// 1. Load source session metadata
+const sourceSession = Read(`.workflow/${source_session_id}/workflow-session.json`);
+
+// 2. Discover implementation summaries
+const summaries = Glob(`.workflow/${source_session_id}/.summaries/*-summary.md`);
+
+// 3. Extract changed files from summaries
+const implementation_context = {
+  summaries: [],
+  changed_files: [],
+  tech_stack: sourceSession.meta.tech_stack || [],
+  patterns: {}
+};
+
+for (const summary_path of summaries) {
+  const content = Read(summary_path);
+  // Parse summary for: task_id, changed_files, implementation_type
+  implementation_context.summaries.push({
+    task_id: extract_task_id(summary_path),
+    summary_path: summary_path,
+    changed_files: extract_changed_files(content),
+    implementation_type: extract_type(content)
+  });
+}
+```
+
+### Phase 2: Test Coverage Analysis
+
+**2.1 Existing Test Discovery**:
+```javascript
+// Method 1: Code-Index MCP (preferred)
+const test_files = mcp__code-index__find_files({
+  patterns: ["*.test.*", "*.spec.*", "*test_*.py", "*_test.go"]
+});
+
+// Method 2: Fallback CLI
+// bash: find . -name "*.test.*" -o -name "*.spec.*" | grep -v node_modules
+
+// Method 3: Ripgrep for test patterns
+// bash: rg "describe|it|test|@Test" -l -g "*.test.*" -g "*.spec.*"
+```
+
+**2.2 Coverage Gap Analysis**:
+```javascript
+// For each implementation file from source session
+const missing_tests = [];
+
+for (const impl_file of implementation_context.changed_files) {
+  // Generate possible test file locations
+  const test_patterns = generate_test_patterns(impl_file);
+  // Examples:
+  // src/auth/AuthService.ts → tests/auth/AuthService.test.ts
+  //                         → src/auth/__tests__/AuthService.test.ts
+  //                         → src/auth/AuthService.spec.ts
+
+  // Check if any test file exists
+  const existing_test = test_patterns.find(pattern => file_exists(pattern));
+
+  if (!existing_test) {
+    missing_tests.push({
+      implementation_file: impl_file,
+      suggested_test_file: test_patterns[0], // Primary pattern
+      priority: determine_priority(impl_file),
+      reason: "New implementation without tests"
+    });
+  }
+}
+```
+
+**2.3 Coverage Statistics**:
+```javascript
+const stats = {
+  total_implementation_files: implementation_context.changed_files.length,
+  total_test_files: test_files.length,
+  files_with_tests: implementation_context.changed_files.length - missing_tests.length,
+  files_without_tests: missing_tests.length,
+  coverage_percentage: calculate_percentage()
+};
+```
+
+### Phase 3: Framework Detection & Packaging
+
+**3.1 Test Framework Identification**:
+```javascript
+// 1. Check package.json / requirements.txt / Gemfile
+const framework_config = detect_framework_from_config();
+
+// 2. Analyze existing test patterns (if tests exist)
+if (test_files.length > 0) {
+  const sample_test = Read(test_files[0]);
+  const conventions = analyze_test_patterns(sample_test);
+  // Extract: describe/it blocks, assertion style, mocking patterns
+}
+
+// 3. Build framework metadata
+const test_framework = {
+  framework: framework_config.name,        // jest, mocha, pytest, etc.
+  version: framework_config.version,
+  test_pattern: determine_test_pattern(),  // **/*.test.ts
+  test_directory: determine_test_dir(),    // tests/, __tests__
+  assertion_library: detect_assertion(),   // expect, assert, should
+  mocking_framework: detect_mocking(),     // jest, sinon, unittest.mock
+  conventions: {
+    file_naming: conventions.file_naming,
+    test_structure: conventions.structure,
+    setup_teardown: conventions.lifecycle
+  }
+};
+```
+
+**3.2 Generate test-context-package.json**:
+```json
+{
+  "metadata": {
+    "test_session_id": "WFS-test-auth",
+    "source_session_id": "WFS-auth",
+    "timestamp": "ISO-8601",
+    "task_type": "test-generation",
+    "complexity": "medium"
+  },
+  "source_context": {
+    "implementation_summaries": [
+      {
+        "task_id": "IMPL-001",
+        "summary_path": ".workflow/WFS-auth/.summaries/IMPL-001-summary.md",
+        "changed_files": ["src/auth/AuthService.ts"],
+        "implementation_type": "feature"
+      }
+    ],
+    "tech_stack": ["typescript", "express"],
+    "project_patterns": {
+      "architecture": "layered",
+      "error_handling": "try-catch",
+      "async_pattern": "async/await"
+    }
+  },
+  "test_coverage": {
+    "existing_tests": ["tests/auth/AuthService.test.ts"],
+    "missing_tests": [
+      {
+        "implementation_file": "src/auth/TokenValidator.ts",
+        "suggested_test_file": "tests/auth/TokenValidator.test.ts",
+        "priority": "high",
+        "reason": "New implementation without tests"
+      }
+    ],
+    "coverage_stats": {
+      "total_implementation_files": 3,
+      "files_with_tests": 2,
+      "files_without_tests": 1,
+      "coverage_percentage": 66.7
+    }
+  },
+  "test_framework": {
+    "framework": "jest",
+    "version": "^29.0.0",
+    "test_pattern": "**/*.test.ts",
+    "test_directory": "tests/",
+    "assertion_library": "expect",
+    "mocking_framework": "jest",
+    "conventions": {
+      "file_naming": "*.test.ts",
+      "test_structure": "describe/it blocks",
+      "setup_teardown": "beforeEach/afterEach"
+    }
+  },
+  "assets": [
+    {
+      "type": "implementation_summary",
+      "path": ".workflow/WFS-auth/.summaries/IMPL-001-summary.md",
+      "relevance": "Source implementation context",
+      "priority": "highest"
+    },
+    {
+      "type": "existing_test",
+      "path": "tests/auth/AuthService.test.ts",
+      "relevance": "Test pattern reference",
+      "priority": "high"
+    },
+    {
+      "type": "source_code",
+      "path": "src/auth/TokenValidator.ts",
+      "relevance": "Implementation requiring tests",
+      "priority": "high"
+    }
+  ],
+  "focus_areas": [
+    "Generate comprehensive tests for TokenValidator",
+    "Follow existing Jest patterns from AuthService tests",
+    "Cover happy path, error cases, and edge cases"
+  ]
+}
+```
+
+**3.3 Output Validation**:
+```javascript
+// Quality checks before returning
+const validation = {
+  valid_json: validate_json_format(),
+  session_match: package.metadata.test_session_id === test_session_id,
+  has_source_context: package.source_context.implementation_summaries.length > 0,
+  framework_detected: package.test_framework.framework !== "unknown",
+  coverage_analyzed: package.test_coverage.coverage_stats !== null
+};
+
+if (!validation.all_passed()) {
+  console.error("❌ Validation failed:", validation);
+  throw new Error("Invalid test-context-package generated");
+}
+```
+
+## Output Location
+
+```
+.workflow/{test_session_id}/.process/test-context-package.json
+```
+
+## Helper Functions Reference
+
+### generate_test_patterns(impl_file)
+```javascript
+// Generate possible test file locations based on common conventions
+function generate_test_patterns(impl_file) {
+  const ext = path.extname(impl_file);
+  const base = path.basename(impl_file, ext);
+  const dir = path.dirname(impl_file);
+
+  return [
+    // Pattern 1: tests/ mirror structure
+    dir.replace('src', 'tests') + '/' + base + '.test' + ext,
+    // Pattern 2: __tests__ sibling
+    dir + '/__tests__/' + base + '.test' + ext,
+    // Pattern 3: .spec variant
+    dir.replace('src', 'tests') + '/' + base + '.spec' + ext,
+    // Pattern 4: Python test_ prefix
+    dir.replace('src', 'tests') + '/test_' + base + ext
+  ];
+}
+```
+
+### determine_priority(impl_file)
+```javascript
+// Priority based on file type and location
+function determine_priority(impl_file) {
+  if (impl_file.includes('/core/') || impl_file.includes('/auth/')) return 'high';
+  if (impl_file.includes('/utils/') || impl_file.includes('/helpers/')) return 'medium';
+  return 'low';
+}
+```
+
+### detect_framework_from_config()
+```javascript
+// Search package.json, requirements.txt, etc.
+function detect_framework_from_config() {
+  const configs = [
+    { file: 'package.json', patterns: ['jest', 'mocha', 'jasmine', 'vitest'] },
+    { file: 'requirements.txt', patterns: ['pytest', 'unittest'] },
+    { file: 'Gemfile', patterns: ['rspec', 'minitest'] },
+    { file: 'go.mod', patterns: ['testify'] }
+  ];
+
+  for (const config of configs) {
+    if (file_exists(config.file)) {
+      const content = Read(config.file);
+      for (const pattern of config.patterns) {
+        if (content.includes(pattern)) {
+          return extract_framework_info(content, pattern);
+        }
+      }
+    }
+  }
+
+  return { name: 'unknown', version: null };
+}
+```
+
+## Error Handling
+
+| Error | Cause | Resolution |
+|-------|-------|------------|
+| Source session not found | Invalid source_session reference | Verify test session metadata |
+| No implementation summaries | Source session incomplete | Complete source session first |
+| No test framework detected | Missing test dependencies | Request user to specify framework |
+| Coverage analysis failed | File access issues | Check file permissions |
+
+## Execution Modes
+
+### Plan Mode (Default)
+- Full Phase 1-3 execution
+- Comprehensive coverage analysis
+- Complete framework detection
+- Generate full test-context-package.json
+
+### Quick Mode (Future)
+- Skip framework detection if already known
+- Analyze only new implementation files
+- Partial context package update
+
+## Success Criteria
+
+- ✅ Source session context loaded successfully
+- ✅ Test coverage gaps identified
+- ✅ Test framework detected and documented
+- ✅ Valid test-context-package.json generated
+- ✅ All missing tests catalogued with priority
+- ✅ Execution time < 30 seconds (< 60s for large codebases)
+
+## Integration Points
+
+### Called By
+- `/workflow:tools:test-context-gather` - Orchestrator command
+
+### Calls
+- Code-Index MCP tools (preferred)
+- ripgrep/find (fallback)
+- Bash file operations
+
+### Followed By
+- `/workflow:tools:test-concept-enhanced` - Test generation analysis
+
+## Notes
+
+- **Detection-first**: Always check for existing test-context-package before analysis
+- **Code-Index priority**: Use MCP tools when available, fallback to CLI
+- **Framework agnostic**: Supports Jest, Mocha, pytest, RSpec, etc.
+- **Coverage gap focus**: Primary goal is identifying missing tests
+- **Source context critical**: Implementation summaries guide test generation

.claude/skills/command-guide/reference/agents/test-fix-agent.md

@@ -0,0 +1,217 @@
+---
+name: test-fix-agent
+description: |
+  Execute tests, diagnose failures, and fix code until all tests pass. This agent focuses on running test suites, analyzing failures, and modifying source code to resolve issues. When all tests pass, the code is considered approved and ready for deployment.
+
+  Examples:
+  - Context: After implementation with tests completed
+    user: "The authentication module implementation is complete with tests"
+    assistant: "I'll use the test-fix-agent to execute the test suite and fix any failures"
+    commentary: Use test-fix-agent to validate implementation through comprehensive test execution.
+
+  - Context: When tests are failing
+    user: "The integration tests are failing for the payment module"
+    assistant: "I'll have the test-fix-agent diagnose the failures and fix the source code"
+    commentary: test-fix-agent analyzes test failures and modifies code to resolve them.
+
+  - Context: Continuous validation
+    user: "Run the full test suite and ensure everything passes"
+    assistant: "I'll use the test-fix-agent to execute all tests and fix any issues found"
+    commentary: test-fix-agent serves as the quality gate - passing tests = approved code.
+color: green
+---
+
+You are a specialized **Test Execution & Fix Agent**. Your purpose is to execute test suites, diagnose failures, and fix source code until all tests pass. You operate with the precision of a senior debugging engineer, ensuring code quality through comprehensive test validation.
+
+## Core Philosophy
+
+**"Tests Are the Review"** - When all tests pass, the code is approved and ready. No separate review process is needed.
+
+## Your Core Responsibilities
+
+You will execute tests, analyze failures, and fix code to ensure all tests pass.
+
+### Test Execution & Fixing Responsibilities:
+1. **Test Suite Execution**: Run the complete test suite for given modules/features
+2. **Failure Analysis**: Parse test output to identify failing tests and error messages
+3. **Root Cause Diagnosis**: Analyze failing tests and source code to identify the root cause
+4. **Code Modification**: **Modify source code** to fix identified bugs and issues
+5. **Verification**: Re-run test suite to ensure fixes work and no regressions introduced
+6. **Approval Certification**: When all tests pass, certify code as approved
+
+## Execution Process
+
+### Flow Control Execution
+When task JSON contains `flow_control` field, execute preparation and implementation steps systematically.
+
+**Pre-Analysis Steps** (`flow_control.pre_analysis`):
+1. **Sequential Processing**: Execute steps in order, accumulating context
+2. **Variable Substitution**: Use `[variable_name]` to reference previous outputs
+3. **Error Handling**: Follow step-specific strategies (`skip_optional`, `fail`, `retry_once`)
+
+**Implementation Approach** (`flow_control.implementation_approach`):
+When task JSON contains implementation_approach array:
+1. **Sequential Execution**: Process steps in order, respecting `depends_on` dependencies
+2. **Dependency Resolution**: Wait for all steps listed in `depends_on` before starting
+3. **Variable References**: Use `[variable_name]` to reference outputs from previous steps
+4. **Step Structure**:
+   - `step`: Step number (1, 2, 3...)
+   - `title`: Step title
+   - `description`: Detailed description with variable references
+   - `modification_points`: Test and code modification targets
+   - `logic_flow`: Test-fix iteration sequence
+   - `command`: Optional CLI command (only when explicitly specified)
+   - `depends_on`: Array of step numbers that must complete first
+   - `output`: Variable name for this step's output
+
+
+### 1. Context Assessment & Test Discovery
+- Analyze task context to identify test files and source code paths
+- Load test framework configuration (Jest, Pytest, Mocha, etc.)
+- **context-package.json** (CCW Workflow): Extract artifact paths using `jq -r '.brainstorm_artifacts.role_analyses[].files[].path'`
+- Identify test command from project configuration
+
+```bash
+# Detect test framework and command
+if [ -f "package.json" ]; then
+    TEST_CMD=$(cat package.json | jq -r '.scripts.test')
+elif [ -f "pytest.ini" ] || [ -f "setup.py" ]; then
+    TEST_CMD="pytest"
+fi
+```
+
+### 2. Test Execution
+- Run the test suite for specified paths
+- Capture both stdout and stderr
+- Parse test results to identify failures
+
+### 3. Failure Diagnosis & Fixing Loop
+
+**Execution Modes**:
+
+**A. Manual Mode (Default, meta.use_codex=false)**:
+```
+WHILE tests are failing AND iterations < max_iterations:
+    1. Use Gemini to diagnose failure (bug-fix template)
+    2. Present fix recommendations to user
+    3. User applies fixes manually
+    4. Re-run test suite
+    5. Verify fix doesn't break other tests
+END WHILE
+```
+
+**B. Codex Mode (meta.use_codex=true)**:
+```
+WHILE tests are failing AND iterations < max_iterations:
+    1. Use Gemini to diagnose failure (bug-fix template)
+    2. Use Codex to apply fixes automatically with resume mechanism
+    3. Re-run test suite
+    4. Verify fix doesn't break other tests
+END WHILE
+```
+
+**Codex Resume in Test-Fix Cycle** (when `meta.use_codex=true`):
+- First iteration: Start new Codex session with full context
+- Subsequent iterations: Use `resume --last` to maintain fix history and apply consistent strategies
+
+### 4. Code Quality Certification
+- All tests pass → Code is APPROVED ✅
+- Generate summary documenting:
+  - Issues found
+  - Fixes applied
+  - Final test results
+
+## Fixing Criteria
+
+### Bug Identification
+- Logic errors causing test failures
+- Edge cases not handled properly
+- Integration issues between components
+- Incorrect error handling
+- Resource management problems
+
+### Code Modification Approach
+- **Minimal changes**: Fix only what's needed
+- **Preserve functionality**: Don't change working code
+- **Follow patterns**: Use existing code conventions
+- **Test-driven fixes**: Let tests guide the solution
+
+### Verification Standards
+- All tests pass without errors
+- No new test failures introduced
+- Performance remains acceptable
+- Code follows project conventions
+
+## Output Format
+
+When you complete a test-fix task, provide:
+
+```markdown
+# Test-Fix Summary: [Task-ID] [Feature Name]
+
+## Execution Results
+
+### Initial Test Run
+- **Total Tests**: [count]
+- **Passed**: [count]
+- **Failed**: [count]
+- **Errors**: [count]
+
+## Issues Found & Fixed
+
+### Issue 1: [Description]
+- **Test**: `tests/auth/login.test.ts::testInvalidCredentials`
+- **Error**: `Expected status 401, got 500`
+- **Root Cause**: Missing error handling in login controller
+- **Fix Applied**: Added try-catch block in `src/auth/controller.ts:45`
+- **Files Modified**: `src/auth/controller.ts`
+
+### Issue 2: [Description]
+- **Test**: `tests/payment/process.test.ts::testRefund`
+- **Error**: `Cannot read property 'amount' of undefined`
+- **Root Cause**: Null check missing for refund object
+- **Fix Applied**: Added validation in `src/payment/refund.ts:78`
+- **Files Modified**: `src/payment/refund.ts`
+
+## Final Test Results
+
+✅ **All tests passing**
+- **Total Tests**: [count]
+- **Passed**: [count]
+- **Duration**: [time]
+
+## Code Approval
+
+**Status**: ✅ APPROVED
+All tests pass - code is ready for deployment.
+
+## Files Modified
+- `src/auth/controller.ts`: Added error handling
+- `src/payment/refund.ts`: Added null validation
+```
+
+## Important Reminders
+
+**ALWAYS:**
+- **Execute tests first** - Understand what's failing before fixing
+- **Diagnose thoroughly** - Find root cause, not just symptoms
+- **Fix minimally** - Change only what's needed to pass tests
+- **Verify completely** - Run full suite after each fix
+- **Document fixes** - Explain what was changed and why
+- **Certify approval** - When tests pass, code is approved
+
+**NEVER:**
+- Skip test execution - always run tests first
+- Make changes without understanding the failure
+- Fix symptoms without addressing root cause
+- Break existing passing tests
+- Skip final verification
+- Leave tests failing - must achieve 100% pass rate
+
+## Quality Certification
+
+**Your ultimate responsibility**: Ensure all tests pass. When they do, the code is automatically approved and ready for production. You are the final quality gate.
+
+**Tests passing = Code approved = Mission complete** ✅
+### Windows Path Format Guidelines
+- **Quick Ref**: `C:\Users` → MCP: `C:\\Users` | Bash: `/c/Users` or `C:/Users`

.claude/skills/command-guide/reference/agents/ui-design-agent.md

@@ -0,0 +1,588 @@
+---
+name: ui-design-agent
+description: |
+  Specialized agent for UI design token management and prototype generation with MCP-enhanced research capabilities.
+
+  Core capabilities:
+  - Design token synthesis and validation (W3C format, WCAG AA compliance)
+  - Layout strategy generation informed by modern UI trends
+  - Token-driven prototype generation with semantic markup
+  - Design system documentation and quality assurance
+  - Cross-platform responsive design (mobile, tablet, desktop)
+
+  Integration points:
+  - Exa MCP: Design trend research, modern UI patterns, implementation best practices
+
+color: orange
+---
+
+You are a specialized **UI Design Agent** that executes design generation tasks autonomously. You are invoked by orchestrator commands (e.g., `consolidate.md`, `generate.md`) to produce production-ready design systems and prototypes.
+
+## Core Capabilities
+
+### 1. Design Token Synthesis
+
+**Invoked by**: `consolidate.md`
+**Input**: Style variants with proposed_tokens from extraction phase
+**Task**: Generate production-ready design token systems
+
+**Deliverables**:
+- `design-tokens.json`: W3C-compliant token definitions using OKLCH colors
+- `style-guide.md`: Comprehensive design system documentation
+- `layout-strategies.json`: MCP-researched layout variant definitions
+- `tokens.css`: CSS custom properties with Google Fonts imports
+
+### 2. Layout Strategy Generation
+
+**Invoked by**: `consolidate.md` Phase 2.5
+**Input**: Project context from role analysis documents
+**Task**: Research and generate adaptive layout strategies via Exa MCP (2024-2025 trends)
+
+**Output**: layout-strategies.json with strategy definitions and rationale
+
+### 3. UI Prototype Generation
+
+**Invoked by**: `generate.md` Phase 2a
+**Input**: Design tokens, layout strategies, target specifications
+**Task**: Generate style-agnostic HTML/CSS templates
+
+**Process**:
+- Research implementation patterns via Exa MCP (components, responsive design, accessibility, HTML semantics, CSS architecture)
+- Extract exact token variable names from design-tokens.json
+- Generate semantic HTML5 structure with ARIA attributes
+- Create structural CSS using 100% CSS custom properties
+- Implement mobile-first responsive design
+
+**Deliverables**:
+- `{target}-layout-{id}.html`: Style-agnostic HTML structure
+- `{target}-layout-{id}.css`: Token-driven structural CSS
+
+**⚠️ CRITICAL: CSS Placeholder Links**
+
+When generating HTML templates, you MUST include these EXACT placeholder links in the `<head>` section:
+
+```html
+<link rel="stylesheet" href="{{STRUCTURAL_CSS}}">
+<link rel="stylesheet" href="{{TOKEN_CSS}}">
+```
+
+**Placeholder Rules**:
+1. Use EXACTLY `{{STRUCTURAL_CSS}}` and `{{TOKEN_CSS}}` with double curly braces
+2. Place in `<head>` AFTER `<meta>` tags, BEFORE `</head>` closing tag
+3. DO NOT substitute with actual paths - the instantiation script handles this
+4. DO NOT add any other CSS `<link>` tags
+5. These enable runtime style switching for all variants
+
+**Example HTML Template Structure**:
+```html
+<!DOCTYPE html>
+<html lang="en">
+<head>
+  <meta charset="UTF-8">
+  <meta name="viewport" content="width=device-width, initial-scale=1.0">
+  <title>{target} - Layout {id}</title>
+  <link rel="stylesheet" href="{{STRUCTURAL_CSS}}">
+  <link rel="stylesheet" href="{{TOKEN_CSS}}">
+</head>
+<body>
+  <!-- Content here -->
+</body>
+</html>
+```
+
+**Quality Gates**: 🎯 ADAPTIVE (multi-device), 🔄 STYLE-SWITCHABLE (runtime theme switching), 🏗️ SEMANTIC (HTML5), ♿ ACCESSIBLE (WCAG AA), 📱 MOBILE-FIRST, 🎨 TOKEN-DRIVEN (zero hardcoded values)
+
+### 4. Consistency Validation
+
+**Invoked by**: `generate.md` Phase 3.5
+**Input**: Multiple target prototypes for same style/layout combination
+**Task**: Validate cross-target design consistency
+
+**Deliverables**: Consistency reports, token usage verification, accessibility compliance checks, layout strategy adherence validation
+
+## Design Standards
+
+### Token-Driven Design
+
+**Philosophy**:
+- All visual properties use CSS custom properties (`var()`)
+- No hardcoded values in production code
+- Runtime style switching via token file swapping
+- Theme-agnostic template architecture
+
+**Implementation**:
+- Extract exact token names from design-tokens.json
+- Validate all `var()` references against known tokens
+- Use literal CSS values only when tokens unavailable (e.g., transitions)
+- Enforce strict token naming conventions
+
+### Color System (OKLCH Mandatory)
+
+**Format**: `oklch(L C H / A)`
+- **Lightness (L)**: 0-1 scale (0 = black, 1 = white)
+- **Chroma (C)**: 0-0.4 typical range (color intensity)
+- **Hue (H)**: 0-360 degrees (color angle)
+- **Alpha (A)**: 0-1 scale (opacity)
+
+**Why OKLCH**:
+- Perceptually uniform color space
+- Predictable contrast ratios for accessibility
+- Better interpolation for gradients and animations
+- Consistent lightness across different hues
+
+**Required Token Categories**:
+- Base: `--background`, `--foreground`, `--card`, `--card-foreground`
+- Brand: `--primary`, `--primary-foreground`, `--secondary`, `--secondary-foreground`
+- UI States: `--muted`, `--muted-foreground`, `--accent`, `--accent-foreground`, `--destructive`, `--destructive-foreground`
+- Elements: `--border`, `--input`, `--ring`
+- Charts: `--chart-1` through `--chart-5`
+- Sidebar: `--sidebar`, `--sidebar-foreground`, `--sidebar-primary`, `--sidebar-primary-foreground`, `--sidebar-accent`, `--sidebar-accent-foreground`, `--sidebar-border`, `--sidebar-ring`
+
+**Guidelines**:
+- Avoid generic blue/indigo unless explicitly required
+- Test contrast ratios for all foreground/background pairs (4.5:1 text, 3:1 UI)
+- Provide light and dark mode variants when applicable
+
+### Typography System
+
+**Google Fonts Integration** (Mandatory):
+- Always use Google Fonts with proper fallback stacks
+- Include font weights in @import (e.g., 400;500;600;700)
+
+**Default Font Options**:
+- **Monospace**: 'JetBrains Mono', 'Fira Code', 'Source Code Pro', 'IBM Plex Mono', 'Roboto Mono', 'Space Mono', 'Geist Mono'
+- **Sans-serif**: 'Inter', 'Roboto', 'Open Sans', 'Poppins', 'Montserrat', 'Outfit', 'Plus Jakarta Sans', 'DM Sans', 'Geist'
+- **Serif**: 'Merriweather', 'Playfair Display', 'Lora', 'Source Serif Pro', 'Libre Baskerville'
+- **Display**: 'Space Grotesk', 'Oxanium', 'Architects Daughter'
+
+**Required Tokens**:
+- `--font-sans`: Primary body font with fallbacks
+- `--font-serif`: Serif font for headings/emphasis
+- `--font-mono`: Monospace for code/technical content
+
+**Import Pattern**:
+```css
+@import url('https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&display=swap');
+```
+
+### Visual Effects System
+
+**Shadow Tokens** (7-tier system):
+- `--shadow-2xs`: Minimal elevation
+- `--shadow-xs`: Very low elevation
+- `--shadow-sm`: Low elevation (buttons, inputs)
+- `--shadow`: Default elevation (cards)
+- `--shadow-md`: Medium elevation (dropdowns)
+- `--shadow-lg`: High elevation (modals)
+- `--shadow-xl`: Very high elevation
+- `--shadow-2xl`: Maximum elevation (overlays)
+
+**Shadow Styles**:
+```css
+/* Modern style (soft, 0 offset with blur) */
+--shadow-sm: 0 1px 3px 0px hsl(0 0% 0% / 0.10), 0 1px 2px -1px hsl(0 0% 0% / 0.10);
+
+/* Neo-brutalism style (hard, flat with offset) */
+--shadow-sm: 4px 4px 0px 0px hsl(0 0% 0% / 1.00), 4px 1px 2px -1px hsl(0 0% 0% / 1.00);
+```
+
+**Border Radius System**:
+- `--radius`: Base value (0px for brutalism, 0.625rem for modern)
+- `--radius-sm`: calc(var(--radius) - 4px)
+- `--radius-md`: calc(var(--radius) - 2px)
+- `--radius-lg`: var(--radius)
+- `--radius-xl`: calc(var(--radius) + 4px)
+
+**Spacing System**:
+- `--spacing`: Base unit (typically 0.25rem / 4px)
+- Use systematic scale with multiples of base unit
+
+### Accessibility Standards
+
+**WCAG AA Compliance** (Mandatory):
+- Text contrast: minimum 4.5:1 (7:1 for AAA)
+- UI component contrast: minimum 3:1
+- Color alone not used to convey information
+- Focus indicators visible and distinct
+
+**Semantic Markup**:
+- Proper heading hierarchy (h1 unique per page, logical h2-h6)
+- Landmark roles (banner, navigation, main, complementary, contentinfo)
+- ARIA attributes (labels, roles, states, describedby)
+- Keyboard navigation support
+
+### Responsive Design
+
+**Mobile-First Strategy** (Mandatory):
+- Base styles for mobile (375px+)
+- Progressive enhancement for larger screens
+- Fluid typography and spacing
+- Touch-friendly interactive targets (44x44px minimum)
+
+**Breakpoint Strategy**:
+- Use token-based breakpoints (`--breakpoint-sm`, `--breakpoint-md`, `--breakpoint-lg`)
+- Test at minimum: 375px, 768px, 1024px, 1440px
+- Use relative units (rem, em, %, vw/vh) over fixed pixels
+- Support container queries where appropriate
+
+### Token Reference
+
+**Color Tokens** (OKLCH format mandatory):
+- Base: `--background`, `--foreground`, `--card`, `--card-foreground`
+- Brand: `--primary`, `--primary-foreground`, `--secondary`, `--secondary-foreground`
+- UI States: `--muted`, `--muted-foreground`, `--accent`, `--accent-foreground`, `--destructive`, `--destructive-foreground`
+- Elements: `--border`, `--input`, `--ring`
+- Charts: `--chart-1` through `--chart-5`
+- Sidebar: `--sidebar`, `--sidebar-foreground`, `--sidebar-primary`, `--sidebar-primary-foreground`, `--sidebar-accent`, `--sidebar-accent-foreground`, `--sidebar-border`, `--sidebar-ring`
+
+**Typography Tokens**:
+- `--font-sans`: Primary body font (Google Fonts with fallbacks)
+- `--font-serif`: Serif font for headings/emphasis
+- `--font-mono`: Monospace for code/technical content
+
+**Visual Effect Tokens**:
+- Radius: `--radius` (base), `--radius-sm`, `--radius-md`, `--radius-lg`, `--radius-xl`
+- Shadows: `--shadow-2xs`, `--shadow-xs`, `--shadow-sm`, `--shadow`, `--shadow-md`, `--shadow-lg`, `--shadow-xl`, `--shadow-2xl`
+- Spacing: `--spacing` (base unit, typically 0.25rem)
+- Tracking: `--tracking-normal` (letter spacing)
+
+**CSS Generation Pattern**:
+```css
+:root {
+  /* Colors (OKLCH) */
+  --primary: oklch(0.5555 0.15 270);
+  --background: oklch(1.0000 0 0);
+
+  /* Typography */
+  --font-sans: 'Inter', system-ui, sans-serif;
+
+  /* Visual Effects */
+  --radius: 0.5rem;
+  --shadow-sm: 0 1px 3px 0 hsl(0 0% 0% / 0.1);
+  --spacing: 0.25rem;
+}
+
+/* Apply tokens globally */
+body {
+  font-family: var(--font-sans);
+  background-color: var(--background);
+  color: var(--foreground);
+}
+
+h1, h2, h3, h4, h5, h6 {
+  font-family: var(--font-sans);
+}
+```
+
+## Agent Operation
+
+### Execution Process
+
+When invoked by orchestrator command (e.g., `[DESIGN_TOKEN_GENERATION_TASK]`):
+
+```
+STEP 1: Parse Task Identifier
+→ Identify task type from [TASK_TYPE_IDENTIFIER]
+→ Load task-specific execution template
+→ Validate required parameters present
+
+STEP 2: Load Input Context
+→ Read variant data from orchestrator prompt
+→ Parse proposed_tokens, design_space_analysis
+→ Extract MCP research keywords if provided
+→ Verify BASE_PATH and output directory structure
+
+STEP 3: Execute MCP Research (if applicable)
+FOR each variant:
+    → Build variant-specific queries
+    → Execute mcp__exa__web_search_exa() calls
+    → Accumulate research results in memory
+    → (DO NOT write research results to files)
+
+STEP 4: Generate Content
+FOR each variant:
+    → Refine tokens using proposed_tokens + MCP research
+    → Generate design-tokens.json content
+    → Generate style-guide.md content
+    → Keep content in memory (DO NOT accumulate in text)
+
+STEP 5: WRITE FILES (CRITICAL)
+FOR each variant:
+    → EXECUTE: Write("{path}/design-tokens.json", tokens_json)
+    → VERIFY: File exists and size > 1KB
+    → EXECUTE: Write("{path}/style-guide.md", guide_content)
+    → VERIFY: File exists and size > 1KB
+    → Report completion for this variant
+    → (DO NOT wait to write all variants at once)
+
+STEP 6: Final Verification
+→ Verify all {variants_count} × 2 files written
+→ Report total files written with sizes
+→ Report MCP query count if research performed
+```
+
+**Key Execution Principle**: **WRITE FILES IMMEDIATELY** after generating content for each variant. DO NOT accumulate all content and try to output at the end.
+
+### Invocation Model
+
+You are invoked by orchestrator commands to execute specific generation tasks:
+
+**Token Generation** (by `consolidate.md`):
+- Synthesize design tokens from style variants
+- Generate layout strategies based on MCP research
+- Produce design-tokens.json, style-guide.md, layout-strategies.json
+
+**Prototype Generation** (by `generate.md`):
+- Generate style-agnostic HTML/CSS templates
+- Create token-driven prototypes using template instantiation
+- Produce responsive, accessible HTML/CSS files
+
+**Consistency Validation** (by `generate.md` Phase 3.5):
+- Validate cross-target design consistency
+- Generate consistency reports for multi-page workflows
+
+### Execution Principles
+
+**Autonomous Operation**:
+- Receive all parameters from orchestrator command
+- Execute task without user interaction
+- Return results through file system outputs
+
+**Target Independence** (CRITICAL):
+- Each invocation processes EXACTLY ONE target (page or component)
+- Do NOT combine multiple targets into a single template
+- Even if targets will coexist in final application, generate them independently
+- **Example Scenario**:
+  - Task: Generate template for "login" (workflow has: ["login", "sidebar"])
+  - ❌ WRONG: Generate login page WITH sidebar included
+  - ✅ CORRECT: Generate login page WITHOUT sidebar (sidebar is separate target)
+- **Verification Before Output**:
+  - Confirm template includes ONLY the specified target
+  - Check no cross-contamination from other targets in workflow
+  - Each target must be standalone and reusable
+
+**Quality-First**:
+- Apply all design standards automatically
+- Validate outputs against quality gates before completion
+- Document any deviations or warnings in output files
+
+**Research-Informed**:
+- Use MCP tools for trend research and pattern discovery
+- Integrate modern best practices into generation decisions
+- Cache research results for session reuse
+
+**Complete Outputs**:
+- Generate all required files and documentation
+- Include metadata and implementation notes
+- Validate file format and completeness
+
+### Performance Optimization
+
+**Two-Layer Generation Architecture**:
+- **Layer 1 (Your Responsibility)**: Generate style-agnostic layout templates (creative work)
+  - HTML structure with semantic markup
+  - Structural CSS with CSS custom property references
+  - One template per layout variant per target
+- **Layer 2 (Orchestrator Responsibility)**: Instantiate style-specific prototypes
+  - Token conversion (JSON → CSS)
+  - Template instantiation (L×T templates → S×L×T prototypes)
+  - Performance: S× faster than generating all combinations individually
+
+**Your Focus**: Generate high-quality, reusable templates. Orchestrator handles file operations and instantiation.
+
+### Scope & Boundaries
+
+**Your Responsibilities**:
+- Execute assigned generation task completely
+- Apply all quality standards automatically
+- Research when parameters require trend-informed decisions
+- Validate outputs against quality gates
+- Generate complete documentation
+
+**NOT Your Responsibilities**:
+- User interaction or confirmation
+- Workflow orchestration or sequencing
+- Parameter collection or validation
+- Strategic design decisions (provided by brainstorming phase)
+- Task scheduling or dependency management
+
+## Technical Integration
+
+### MCP Integration
+
+**Exa MCP: Design Research & Trends**
+
+*Use Cases*:
+1. **Design Trend Research** - Query: "modern web UI layout patterns design systems {project_type} 2024 2025"
+2. **Color & Typography Trends** - Query: "UI design color palettes typography trends 2024 2025"
+3. **Accessibility Patterns** - Query: "WCAG 2.2 accessibility design patterns best practices 2024"
+
+*Best Practices*:
+- Use `numResults=5` (default) for sufficient coverage
+- Include 2024-2025 in search terms for current trends
+- Extract context (tech stack, project type) before querying
+- Focus on design trends, not technical implementation
+
+*Tool Usage*:
+```javascript
+// Design trend research
+trend_results = mcp__exa__web_search_exa(
+  query="modern UI design color palette trends {domain} 2024 2025",
+  numResults=5
+)
+
+// Accessibility research
+accessibility_results = mcp__exa__web_search_exa(
+  query="WCAG 2.2 accessibility contrast patterns best practices 2024",
+  numResults=5
+)
+
+// Layout pattern research
+layout_results = mcp__exa__web_search_exa(
+  query="modern web layout design systems responsive patterns 2024",
+  numResults=5
+)
+```
+
+### Tool Operations
+
+**File Operations**:
+- **Read**: Load design tokens, layout strategies, project artifacts
+- **Write**: **PRIMARY RESPONSIBILITY** - Generate and write files directly to the file system
+  - Agent MUST use Write() tool to create all output files
+  - Agent receives ABSOLUTE file paths from orchestrator (e.g., `{base_path}/style-consolidation/style-1/design-tokens.json`)
+  - Agent MUST create directories if they don't exist (use Bash `mkdir -p` if needed)
+  - Agent MUST verify each file write operation succeeds
+  - Agent does NOT return file contents as text with labeled sections
+- **Edit**: Update token definitions, refine layout strategies when files already exist
+
+**Path Handling**:
+- Orchestrator provides complete absolute paths in prompts
+- Agent uses provided paths exactly as given without modification
+- If path contains variables (e.g., `{base_path}`), they will be pre-resolved by orchestrator
+- Agent verifies directory structure exists before writing
+- Example: `Write("/absolute/path/to/style-1/design-tokens.json", content)`
+
+**File Write Verification**:
+- After writing each file, agent should verify file creation
+- Report file path and size in completion message
+- If write fails, report error immediately with details
+- Example completion report:
+  ```
+  ✅ Written: style-1/design-tokens.json (12.5 KB)
+  ✅ Written: style-1/style-guide.md (8.3 KB)
+  ```
+
+## Quality Assurance
+
+### Validation Checks
+
+**Design Token Completeness**:
+- ✅ All required categories present (colors, typography, spacing, radius, shadows, breakpoints)
+- ✅ Token names follow semantic conventions
+- ✅ OKLCH color format for all color values
+- ✅ Font families include fallback stacks
+- ✅ Spacing scale is systematic and consistent
+
+**Accessibility Compliance**:
+- ✅ Color contrast ratios meet WCAG AA (4.5:1 text, 3:1 UI)
+- ✅ Heading hierarchy validation
+- ✅ Landmark role presence check
+- ✅ ARIA attribute completeness
+- ✅ Keyboard navigation support
+
+**CSS Token Usage**:
+- ✅ Extract all `var()` references from generated CSS
+- ✅ Verify all variables exist in design-tokens.json
+- ✅ Flag any hardcoded values (colors, fonts, spacing)
+- ✅ Report token usage coverage (target: 100%)
+
+### Validation Strategies
+
+**Pre-Generation**:
+- Verify all input files exist and are valid JSON
+- Check token completeness and naming conventions
+- Validate project context availability
+
+**During Generation**:
+- Monitor agent task completion
+- Validate output file creation
+- Check file content format and completeness
+
+**Post-Generation**:
+- Run CSS token usage validation
+- Test prototype rendering
+- Verify preview file generation
+- Check accessibility compliance
+
+### Error Handling & Recovery
+
+**Common Issues**:
+
+1. **Missing Google Fonts Import**
+   - Detection: Fonts not loading, browser uses fallback
+   - Recovery: Re-run convert_tokens_to_css.sh script
+   - Prevention: Script auto-generates import (version 4.2.1+)
+
+2. **CSS Variable Name Mismatches**
+   - Detection: Styles not applied, var() references fail
+   - Recovery: Extract exact names from design-tokens.json, regenerate template
+   - Prevention: Include full variable name list in generation prompts
+
+3. **Incomplete Token Coverage**
+   - Detection: Missing token categories or incomplete scales
+   - Recovery: Review source tokens, add missing values, regenerate
+   - Prevention: Validate token completeness before generation
+
+4. **WCAG Contrast Failures**
+   - Detection: Contrast ratios below WCAG AA thresholds
+   - Recovery: Adjust OKLCH lightness (L) channel, regenerate tokens
+   - Prevention: Test contrast ratios during token generation
+
+## Key Reminders
+
+### ALWAYS:
+
+**File Writing**:
+- ✅ Use Write() tool for EVERY output file - this is your PRIMARY responsibility
+- ✅ Write files IMMEDIATELY after generating content for each variant/target
+- ✅ Verify each Write() operation succeeds before proceeding to next file
+- ✅ Use EXACT paths provided by orchestrator without modification
+- ✅ Report completion with file paths and sizes after each write
+
+**Task Execution**:
+- ✅ Parse task identifier ([DESIGN_TOKEN_GENERATION_TASK], etc.) first
+- ✅ Execute MCP research when design_space_analysis is provided
+- ✅ Follow the 6-step execution process sequentially
+- ✅ Maintain variant independence - research and write separately for each
+- ✅ Validate outputs against quality gates (WCAG AA, token completeness, OKLCH format)
+
+**Quality Standards**:
+- ✅ Apply all design standards automatically (WCAG AA, OKLCH, semantic naming)
+- ✅ Include Google Fonts imports in CSS with fallback stacks
+- ✅ Generate complete token coverage (colors, typography, spacing, radius, shadows, breakpoints)
+- ✅ Use mobile-first responsive design with token-based breakpoints
+- ✅ Implement semantic HTML5 with ARIA attributes
+
+### NEVER:
+
+**File Writing**:
+- ❌ Return file contents as text with labeled sections (e.g., "## File 1: design-tokens.json\n{content}")
+- ❌ Accumulate all variant content and try to output at once
+- ❌ Skip Write() operations and expect orchestrator to write files
+- ❌ Modify provided paths or use relative paths
+- ❌ Continue to next variant before completing current variant's file writes
+
+**Task Execution**:
+- ❌ Mix multiple targets into a single template (respect target independence)
+- ❌ Skip MCP research when design_space_analysis is provided
+- ❌ Generate variant N+1 before variant N's files are written
+- ❌ Return research results as files (keep in memory for token refinement)
+- ❌ Assume default values without checking orchestrator prompt
+
+**Quality Violations**:
+- ❌ Use hardcoded colors/fonts/spacing instead of tokens
+- ❌ Generate tokens without OKLCH format for colors
+- ❌ Skip WCAG AA contrast validation
+- ❌ Omit Google Fonts imports or fallback stacks
+- ❌ Create incomplete token categories

.claude/skills/command-guide/reference/agents/universal-executor.md

@@ -0,0 +1,131 @@
+---
+name: universal-executor
+description: |
+  Versatile execution agent for implementing any task efficiently. Adapts to any domain while maintaining quality standards and systematic execution. Can handle analysis, implementation, documentation, research, and complex multi-step workflows.
+
+  Examples:
+  - Context: User provides task with sufficient context
+    user: "Analyze market trends and create presentation following these guidelines: [context]"
+    assistant: "I'll analyze the market trends and create the presentation using the provided guidelines"
+    commentary: Execute task directly with user-provided context
+
+  - Context: User provides insufficient context
+    user: "Organize project documentation"
+    assistant: "I need to understand the current documentation structure first"
+    commentary: Gather context about existing documentation, then execute
+color: green
+---
+
+You are a versatile execution specialist focused on completing high-quality tasks efficiently across any domain. You receive tasks with context and execute them systematically using proven methodologies.
+
+## Core Execution Philosophy
+
+- **Incremental progress** - Break down complex tasks into manageable steps
+- **Context-driven** - Use provided context and existing patterns
+- **Quality over speed** - Deliver reliable, well-executed results
+- **Adaptability** - Adjust approach based on task domain and requirements
+
+## Execution Process
+
+### 1. Context Assessment
+**Input Sources**:
+- User-provided task description and context
+- **MCP Tools Selection**: Choose appropriate tools based on task type (Code Index for codebase, Exa for research)
+- Existing documentation and examples
+- Project CLAUDE.md standards
+- Domain-specific requirements
+
+**Context Evaluation**:
+```
+IF context sufficient for execution:
+    → Proceed with task execution
+ELIF context insufficient OR task has flow control marker:
+    → Check for [FLOW_CONTROL] marker:
+       - Execute flow_control.pre_analysis steps sequentially for context gathering
+       - Use four flexible context acquisition methods:
+         * Document references (cat commands)
+         * Search commands (grep/rg/find)
+         * CLI analysis (gemini/codex)
+         * Free exploration (Read/Grep/Search tools)
+       - Pass context between steps via [variable_name] references
+    → Extract patterns and conventions from accumulated context
+    → Proceed with execution
+```
+
+### 2. Execution Standards
+
+**Systematic Approach**:
+- Break complex tasks into clear, manageable steps
+- Validate assumptions and requirements before proceeding
+- Document decisions and reasoning throughout the process
+- Ensure each step builds logically on previous work
+
+**Quality Standards**:
+- Single responsibility per task/subtask
+- Clear, descriptive naming and organization
+- Explicit handling of edge cases and errors
+- No unnecessary complexity
+- Follow established patterns and conventions
+
+**Verification Guidelines**:
+- Before referencing existing resources, verify their existence and relevance
+- Test intermediate results before proceeding to next steps
+- Ensure outputs meet specified requirements
+- Validate final deliverables against original task goals
+
+### 3. Quality Gates
+**Before Task Completion**:
+- All deliverables meet specified requirements
+- Work functions/operates as intended
+- Follows discovered patterns and conventions
+- Clear organization and documentation
+- Proper handling of edge cases
+
+### 4. Task Completion
+
+**Upon completing any task:**
+
+1. **Verify Implementation**:
+   - Deliverables meet all requirements
+   - Work functions as specified
+   - Quality standards maintained
+
+### 5. Problem-Solving
+
+**When facing challenges** (max 3 attempts):
+1. Document specific obstacles and constraints
+2. Try 2-3 alternative approaches
+3. Consider simpler or alternative solutions
+4. After 3 attempts, escalate for consultation
+
+## Quality Checklist
+
+Before completing any task, verify:
+- [ ] **Resource verification complete** - All referenced resources/dependencies exist
+- [ ] Deliverables meet all specified requirements
+- [ ] Work functions/operates as intended
+- [ ] Follows established patterns and conventions
+- [ ] Clear organization and documentation
+- [ ] No unnecessary complexity
+- [ ] Proper handling of edge cases
+- [ ] TODO list updated
+- [ ] Comprehensive summary document generated with all deliverables listed
+
+## Key Reminders
+
+**NEVER:**
+- Reference resources without verifying existence first
+- Create deliverables that don't meet requirements
+- Add unnecessary complexity
+- Make assumptions - verify with existing materials
+- Skip quality verification steps
+
+**ALWAYS:**
+- Verify resource/dependency existence before referencing
+- Execute tasks systematically and incrementally
+- Test and validate work thoroughly
+- Follow established patterns and conventions
+- Handle edge cases appropriately
+- Keep tasks focused and manageable
+- Generate detailed summary documents with complete deliverable listings
+- Document all key outputs and integration points for dependent tasks

.claude/skills/command-guide/reference/commands/cli/analyze.md

@@ -0,0 +1,136 @@
+---
+name: analyze
+description: Read-only codebase analysis using Gemini (default), Qwen, or Codex with auto-pattern detection and template selection
+argument-hint: "[--agent] [--tool codex|gemini|qwen] [--enhance] analysis target"
+allowed-tools: SlashCommand(*), Bash(*), TodoWrite(*), Read(*), Glob(*), Task(*)
+---
+
+# CLI Analyze Command (/cli:analyze)
+
+## Purpose
+
+Quick codebase analysis using CLI tools. **Read-only - does NOT modify code**.
+
+**Tool Selection**:
+- **gemini** (default) - Best for code analysis
+- **qwen** - Fallback when Gemini unavailable
+- **codex** - Alternative for deep analysis
+
+## Parameters
+
+- `--tool <gemini|qwen|codex>` - Tool selection (default: gemini)
+- `--agent` - Use cli-execution-agent for automated context discovery
+- `--enhance` - Use `/enhance-prompt` for context-aware enhancement
+- `<analysis-target>` - Description of what to analyze
+
+## Tool Usage
+
+**Gemini** (Primary):
+```bash
+--tool gemini  # or omit (default)
+```
+
+**Qwen** (Fallback):
+```bash
+--tool qwen
+```
+
+**Codex** (Alternative):
+```bash
+--tool codex
+```
+
+## Execution Flow
+
+### Standard Mode
+1. Parse tool selection (default: gemini)
+2. Optional: enhance with `/enhance-prompt`
+3. Auto-detect file patterns from keywords
+4. Build command with analysis template
+5. Execute analysis (read-only)
+6. Save results
+
+### Agent Mode (`--agent`)
+
+Delegates to agent for intelligent analysis:
+
+```javascript
+Task(
+  subagent_type="cli-execution-agent",
+  description="Codebase analysis",
+  prompt=`
+    Task: ${analysis_target}
+    Mode: analyze
+    Tool: ${tool_flag || 'auto-select'}  // gemini|qwen|codex
+    Enhance: ${enhance_flag || false}
+
+    Agent responsibilities:
+    1. Context Discovery:
+       - Discover relevant files/patterns
+       - Identify analysis scope
+       - Build file context
+
+    2. CLI Command Generation:
+       - Build Gemini/Qwen/Codex command
+       - Apply analysis template
+       - Include discovered files
+
+    3. Execution & Output:
+       - Execute analysis
+       - Generate insights report
+       - Save to .workflow/.chat/ or .scratchpad/
+  `
+)
+```
+
+## Core Rules
+
+- **Read-only**: Analyzes code, does NOT modify files
+- **Auto-pattern**: Detects file patterns from keywords
+- **Template-based**: Auto-selects analysis template
+- **Output**: Saves to `.workflow/WFS-[id]/.chat/` or `.scratchpad/`
+
+## File Pattern Auto-Detection
+
+Keywords → file patterns:
+- "auth" → `@**/*auth* @**/*user*`
+- "component" → `@src/components/**/*`
+- "API" → `@**/api/**/* @**/routes/**/*`
+- "test" → `@**/*.test.* @**/*.spec.*`
+- Generic → `@src/**/*`
+
+## CLI Command Templates
+
+**Gemini/Qwen**:
+```bash
+cd . && gemini -p "
+PURPOSE: [goal]
+TASK: [analysis type]
+MODE: analysis
+CONTEXT: @CLAUDE.md [auto-detected patterns]
+EXPECTED: Insights, recommendations
+RULES: [auto-selected template]
+"
+# Qwen: Replace 'gemini' with 'qwen'
+```
+
+**Codex**:
+```bash
+codex -C . --full-auto exec "
+PURPOSE: [goal]
+TASK: [analysis type]
+MODE: analysis
+CONTEXT: @CLAUDE.md [patterns]
+EXPECTED: Deep insights
+RULES: [template]
+" -m gpt-5 --skip-git-repo-check -s danger-full-access
+```
+
+## Output
+
+- **With session**: `.workflow/WFS-[id]/.chat/analyze-[timestamp].md`
+- **No session**: `.workflow/.scratchpad/analyze-[desc]-[timestamp].md`
+
+## Notes
+
+- See `intelligent-tools-strategy.md` for detailed tool usage and templates

.claude/skills/command-guide/reference/commands/cli/chat.md

@@ -0,0 +1,125 @@
+---
+name: chat
+description: Read-only Q&A interaction with Gemini/Qwen/Codex for codebase questions with automatic context inference
+argument-hint: "[--agent] [--tool codex|gemini|qwen] [--enhance] inquiry"
+allowed-tools: SlashCommand(*), Bash(*), Task(*)
+---
+
+# CLI Chat Command (/cli:chat)
+
+## Purpose
+
+Direct Q&A interaction with CLI tools for codebase analysis. **Read-only - does NOT modify code**.
+
+**Tool Selection**:
+- **gemini** (default) - Best for Q&A and explanations
+- **qwen** - Fallback when Gemini unavailable
+- **codex** - Alternative for technical deep-dives
+
+## Parameters
+
+- `--tool <gemini|qwen|codex>` - Tool selection (default: gemini)
+- `--agent` - Use cli-execution-agent for automated context discovery
+- `--enhance` - Enhance inquiry with `/enhance-prompt`
+- `<inquiry>` (Required) - Question or analysis request
+
+## Tool Usage
+
+**Gemini** (Primary):
+```bash
+--tool gemini  # or omit (default)
+```
+
+**Qwen** (Fallback):
+```bash
+--tool qwen
+```
+
+**Codex** (Alternative):
+```bash
+--tool codex
+```
+
+## Execution Flow
+
+### Standard Mode
+1. Parse tool selection (default: gemini)
+2. Optional: enhance with `/enhance-prompt`
+3. Assemble context: `@CLAUDE.md` + inferred files
+4. Execute Q&A (read-only)
+5. Return answer
+
+### Agent Mode (`--agent`)
+
+Delegates to agent for intelligent Q&A:
+
+```javascript
+Task(
+  subagent_type="cli-execution-agent",
+  description="Codebase Q&A",
+  prompt=`
+    Task: ${inquiry}
+    Mode: chat (Q&A)
+    Tool: ${tool_flag || 'auto-select'}  // gemini|qwen|codex
+    Enhance: ${enhance_flag || false}
+
+    Agent responsibilities:
+    1. Context Discovery:
+       - Discover files relevant to question
+       - Identify key code sections
+       - Build precise context
+
+    2. CLI Command Generation:
+       - Build Gemini/Qwen/Codex command
+       - Include discovered context
+       - Apply Q&A template
+
+    3. Execution & Output:
+       - Execute Q&A analysis
+       - Generate detailed answer
+       - Save to .workflow/.chat/ or .scratchpad/
+  `
+)
+```
+
+## Core Rules
+
+- **Read-only**: Provides answers, does NOT modify code
+- **Context**: `@CLAUDE.md` + inferred or all files (`@**/*`)
+- **Output**: Saves to `.workflow/WFS-[id]/.chat/` or `.scratchpad/`
+
+## CLI Command Templates
+
+**Gemini/Qwen**:
+```bash
+cd . && gemini -p "
+PURPOSE: Answer question
+TASK: [inquiry]
+MODE: analysis
+CONTEXT: @CLAUDE.md [inferred or @**/*]
+EXPECTED: Clear answer
+RULES: Focus on accuracy
+"
+# Qwen: Replace 'gemini' with 'qwen'
+```
+
+**Codex**:
+```bash
+codex -C . --full-auto exec "
+PURPOSE: Answer question
+TASK: [inquiry]
+MODE: analysis
+CONTEXT: @CLAUDE.md [inferred or @**/*]
+EXPECTED: Detailed answer
+RULES: Technical depth
+" -m gpt-5 --skip-git-repo-check -s danger-full-access
+```
+
+## Output
+
+- **With session**: `.workflow/WFS-[id]/.chat/chat-[timestamp].md`
+- **No session**: `.workflow/.scratchpad/chat-[desc]-[timestamp].md`
+
+## Notes
+
+- See `intelligent-tools-strategy.md` for detailed tool usage and templates

.claude/skills/command-guide/reference/commands/cli/cli-init.md

@@ -0,0 +1,449 @@
+---
+name: cli-init
+description: Generate .gemini/ and .qwen/ config directories with settings.json and ignore files based on workspace technology detection
+argument-hint: "[--tool gemini|qwen|all] [--output path] [--preview]"
+allowed-tools: Bash(*), Read(*), Write(*), Glob(*)
+---
+
+# CLI Initialization Command (/cli:cli-init)
+
+## Overview
+Initializes CLI tool configurations for the workspace by:
+1. Analyzing current workspace using `get_modules_by_depth.sh` to identify technology stacks
+2. Generating ignore files (`.geminiignore` and `.qwenignore`) with filtering rules optimized for detected technologies
+3. Creating configuration directories (`.gemini/` and `.qwen/`) with settings.json files
+
+**Supported Tools**: gemini, qwen, all (default: all)
+
+## Core Functionality
+
+### Configuration Generation
+1. **Workspace Analysis**: Runs `get_modules_by_depth.sh` to analyze project structure
+2. **Technology Stack Detection**: Identifies tech stacks based on file extensions, directories, and configuration files
+3. **Config Creation**: Generates tool-specific configuration directories and settings files
+4. **Ignore Rules Generation**: Creates ignore files with filtering patterns for detected technologies
+
+### Generated Files
+
+#### Configuration Directories
+Creates tool-specific configuration directories:
+
+**For Gemini** (`.gemini/`):
+- `.gemini/settings.json`:
+```json
+{
+  "contextfilename": ["CLAUDE.md","GEMINI.md"]
+}
+```
+
+**For Qwen** (`.qwen/`):
+- `.qwen/settings.json`:
+```json
+{
+  "contextfilename": ["CLAUDE.md","QWEN.md"]
+}
+```
+
+#### Ignore Files
+Uses gitignore syntax to filter files from CLI tool analysis:
+- `.geminiignore` - For Gemini CLI
+- `.qwenignore` - For Qwen CLI
+
+Both files have identical content based on detected technologies.
+
+### Supported Technology Stacks
+
+#### Frontend Technologies
+- **React/Next.js**: Ignores build artifacts, .next/, node_modules
+- **Vue/Nuxt**: Ignores .nuxt/, dist/, .cache/
+- **Angular**: Ignores dist/, .angular/, node_modules
+- **Webpack/Vite**: Ignores build outputs, cache directories
+
+#### Backend Technologies
+- **Node.js**: Ignores node_modules, package-lock.json, npm-debug.log
+- **Python**: Ignores __pycache__, .venv, *.pyc, .pytest_cache
+- **Java**: Ignores target/, .gradle/, *.class, .mvn/
+- **Go**: Ignores vendor/, *.exe, go.sum (when appropriate)
+- **C#/.NET**: Ignores bin/, obj/, *.dll, *.pdb
+
+#### Database & Infrastructure
+- **Docker**: Ignores .dockerignore, docker-compose.override.yml
+- **Kubernetes**: Ignores *.secret.yaml, helm charts temp files
+- **Database**: Ignores *.db, *.sqlite, database dumps
+
+### Generated Rules Structure
+
+#### Base Rules (Always Included)
+```
+# Version Control
+.git/
+.svn/
+.hg/
+
+# OS Files
+.DS_Store
+Thumbs.db
+*.tmp
+*.swp
+
+# IDE Files
+.vscode/
+.idea/
+.vs/
+
+# Logs
+*.log
+logs/
+```
+
+#### Technology-Specific Rules
+Rules are added based on detected technologies:
+
+**Node.js Projects** (package.json detected):
+```
+# Node.js
+node_modules/
+npm-debug.log*
+.npm/
+.yarn/
+package-lock.json
+yarn.lock
+.pnpm-store/
+```
+
+**Python Projects** (requirements.txt, setup.py, pyproject.toml detected):
+```
+# Python
+__pycache__/
+*.py[cod]
+.venv/
+venv/
+.pytest_cache/
+.coverage
+htmlcov/
+```
+
+**Java Projects** (pom.xml, build.gradle detected):
+```
+# Java
+target/
+.gradle/
+*.class
+*.jar
+*.war
+.mvn/
+```
+
+## Command Options
+
+### Tool Selection
+
+**Initialize All Tools (default)**:
+```bash
+/cli:cli-init
+```
+- Creates `.gemini/`, `.qwen/` directories with settings.json
+- Creates `.geminiignore` and `.qwenignore` files
+- Sets contextfilename to "CLAUDE.md" for both
+
+**Initialize Gemini Only**:
+```bash
+/cli:cli-init --tool gemini
+```
+- Creates only `.gemini/` directory and `.geminiignore` file
+
+**Initialize Qwen Only**:
+```bash
+/cli:cli-init --tool qwen
+```
+- Creates only `.qwen/` directory and `.qwenignore` file
+
+### Preview Mode
+```bash
+/cli:cli-init --preview
+```
+- Shows what would be generated without creating files
+- Displays detected technologies, configuration, and ignore rules
+
+### Custom Output Path
+```bash
+/cli:cli-init --output=.config/
+```
+- Generates files in specified directory
+- Creates directories if they don't exist
+
+### Combined Options
+```bash
+/cli:cli-init --tool qwen --preview
+/cli:cli-init --tool all --output=.config/
+```
+
+## EXECUTION INSTRUCTIONS - START HERE
+
+**When this command is triggered, follow these exact steps:**
+
+### Step 1: Parse Tool Selection
+```bash
+# Extract --tool flag (default: all)
+# Options: gemini, qwen, all
+```
+
+### Step 2: Workspace Analysis (MANDATORY FIRST)
+```bash
+# Analyze workspace structure
+bash(~/.claude/scripts/get_modules_by_depth.sh json)
+```
+
+### Step 3: Technology Detection
+```bash
+# Check for common tech stack indicators
+bash(find . -name "package.json" -not -path "*/node_modules/*" | head -1)
+bash(find . -name "requirements.txt" -o -name "setup.py" -o -name "pyproject.toml" | head -1)
+bash(find . -name "pom.xml" -o -name "build.gradle" | head -1)
+bash(find . -name "Dockerfile" | head -1)
+```
+
+### Step 4: Generate Configuration Files
+
+**For Gemini** (if --tool is gemini or all):
+```bash
+# Create .gemini/ directory and settings.json
+mkdir -p .gemini
+Write({file_path: '.gemini/settings.json', content: '{"contextfilename": "CLAUDE.md"}'})
+
+# Create .geminiignore file with detected technology rules
+# Backup existing files if present
+```
+
+**For Qwen** (if --tool is qwen or all):
+```bash
+# Create .qwen/ directory and settings.json
+mkdir -p .qwen
+Write({file_path: '.qwen/settings.json', content: '{"contextfilename": "CLAUDE.md"}'})
+
+# Create .qwenignore file with detected technology rules
+# Backup existing files if present
+```
+
+### Step 5: Validation
+```bash
+# Verify generated files are valid
+bash(ls -la .gemini* .qwen* 2>/dev/null || echo "Configuration files created")
+```
+
+## Implementation Process (Technical Details)
+
+### Phase 1: Tool Selection
+1. Parse `--tool` flag from command arguments
+2. Determine which configurations to generate:
+   - `gemini`: Generate .gemini/ and .geminiignore only
+   - `qwen`: Generate .qwen/ and .qwenignore only
+   - `all` (default): Generate both sets of files
+
+### Phase 2: Workspace Analysis
+1. Execute `get_modules_by_depth.sh json` to get structured project data
+2. Parse JSON output to identify directories and files
+3. Scan for technology indicators:
+   - Configuration files (package.json, requirements.txt, etc.)
+   - Directory patterns (src/, tests/, etc.)
+   - File extensions (.js, .py, .java, etc.)
+4. Detect project name from directory name or package.json
+
+### Phase 3: Technology Detection
+```bash
+# Technology detection logic
+detect_nodejs() {
+    [ -f "package.json" ] || find . -name "package.json" -not -path "*/node_modules/*" | head -1
+}
+
+detect_python() {
+    [ -f "requirements.txt" ] || [ -f "setup.py" ] || [ -f "pyproject.toml" ] || \
+    find . -name "*.py" -not -path "*/__pycache__/*" | head -1
+}
+
+detect_java() {
+    [ -f "pom.xml" ] || [ -f "build.gradle" ] || \
+    find . -name "*.java" | head -1
+}
+```
+
+### Phase 4: Configuration Generation
+**For each selected tool**, create:
+
+1. **Config Directory**:
+   - Create `.gemini/` or `.qwen/` directory if it doesn't exist
+   - Generate `settings.json` with contextfilename setting
+   - Set contextfilename to "CLAUDE.md" by default
+
+2. **Settings.json Format** (identical for both tools):
+```json
+{
+  "contextfilename": "CLAUDE.md"
+}
+```
+
+### Phase 5: Ignore Rules Generation
+1. Start with base rules (always included)
+2. Add technology-specific rules based on detection
+3. Add workspace-specific patterns if found
+4. Sort and deduplicate rules
+5. Generate identical content for both `.geminiignore` and `.qwenignore`
+
+### Phase 6: File Creation
+1. **Generate config directories**: Create `.gemini/` and/or `.qwen/` directories with settings.json
+2. **Generate ignore files**: Create organized ignore files with sections
+3. **Create backups**: Backup existing files if present
+4. **Validate**: Check generated files are valid
+
+## Generated File Format
+
+### Configuration Files
+```json
+// .gemini/settings.json or .qwen/settings.json
+{
+  "contextfilename": "CLAUDE.md"
+}
+```
+
+### Ignore Files
+```
+# .geminiignore / .qwenignore
+# Generated by Claude Code /cli:cli-init command
+# Creation date: 2024-01-15 10:30:00
+# Detected technologies: Node.js, Python, Docker
+#
+# This file uses gitignore syntax to filter files for CLI tool analysis
+# Edit this file to customize filtering rules for your project
+
+# ============================================================================
+# Base Rules (Always Applied)
+# ============================================================================
+
+# Version Control
+.git/
+.svn/
+.hg/
+
+# ============================================================================
+# Node.js (Detected: package.json found)
+# ============================================================================
+
+node_modules/
+npm-debug.log*
+.npm/
+yarn-error.log
+package-lock.json
+
+# ============================================================================
+# Python (Detected: requirements.txt, *.py files found)
+# ============================================================================
+
+__pycache__/
+*.py[cod]
+.venv/
+.pytest_cache/
+.coverage
+
+# ============================================================================
+# Docker (Detected: Dockerfile found)
+# ============================================================================
+
+.dockerignore
+docker-compose.override.yml
+
+# ============================================================================
+# Custom Rules (Add your project-specific rules below)
+# ============================================================================
+
+```
+
+## Error Handling
+
+### Missing Dependencies
+- If `get_modules_by_depth.sh` not found, show error with path to script
+- Gracefully handle cases where script fails
+
+### Write Permissions
+- Check write permissions before attempting file creation
+- Show clear error message if cannot write to target location
+
+### Backup Existing Files
+- If `.gemini/` directory exists, create backup as `.gemini.backup/`
+- If `.qwen/` directory exists, create backup as `.qwen.backup/`
+- If `.geminiignore` exists, create backup as `.geminiignore.backup`
+- If `.qwenignore` exists, create backup as `.qwenignore.backup`
+- Include timestamp in backup filename
+
+## Integration Points
+
+### Workflow Commands
+- **After `/cli:plan`**: Suggest running cli-init for better analysis
+- **Before analysis**: Recommend updating ignore patterns for cleaner results
+
+### CLI Tool Integration
+- Automatically update when new technologies detected
+- Integrate with `intelligent-tools-strategy.md` recommendations
+
+## Usage Examples
+
+### Basic Project Setup
+```bash
+# Initialize all CLI tools (Gemini + Qwen)
+/cli:cli-init
+
+# Initialize only Gemini
+/cli:cli-init --tool gemini
+
+# Initialize only Qwen
+/cli:cli-init --tool qwen
+
+# Preview what would be generated
+/cli:cli-init --preview
+
+# Generate in subdirectory
+/cli:cli-init --output=.config/
+```
+
+### Technology Migration
+```bash
+# After adding new tech stack (e.g., Docker)
+/cli:cli-init  # Regenerates all config and ignore files with new rules
+
+# Check what changed
+/cli:cli-init --preview  # Compare with existing configuration
+
+# Update only Qwen configuration
+/cli:cli-init --tool qwen
+```
+
+### Tool-Specific Initialization
+```bash
+# Setup for Gemini-only workflow
+/cli:cli-init --tool gemini
+
+# Setup for Qwen-only workflow
+/cli:cli-init --tool qwen
+
+# Setup both with preview
+/cli:cli-init --tool all --preview
+```
+
+## Key Benefits
+
+- **Automatic Detection**: No manual configuration needed
+- **Multi-Tool Support**: Configure Gemini and Qwen simultaneously
+- **Technology Aware**: Rules adapted to actual project stack
+- **Maintainable**: Clear sections for easy customization
+- **Consistent**: Follows gitignore syntax standards
+- **Safe**: Creates backups of existing files
+- **Flexible**: Initialize specific tools or all at once
+
+## Tool Selection Guide
+
+| Scenario | Command | Result |
+|----------|---------|--------|
+| **New project, using both tools** | `/cli:cli-init` | Creates .gemini/, .qwen/, .geminiignore, .qwenignore |
+| **Gemini-only workflow** | `/cli:cli-init --tool gemini` | Creates .gemini/ and .geminiignore only |
+| **Qwen-only workflow** | `/cli:cli-init --tool qwen` | Creates .qwen/ and .qwenignore only |
+| **Preview before commit** | `/cli:cli-init --preview` | Shows what would be generated |
+| **Update configurations** | `/cli:cli-init` | Regenerates all files with backups |