claude-code-workflow 7.2.10 → 7.2.11

package/.claude/agents/cli-planning-agent.md

@@ -31,6 +31,9 @@ If the prompt contains a `<files_to_read>` block, you MUST use the `Read` tool
 to load every file listed there before performing any other actions. This is your
 primary context.
 
+**Load Project Context** (from spec system):
+- Run: `ccw spec load --category test` for test framework context, coverage targets, and conventions
+
 **Core responsibilities:**
 - **FIRST: Execute CLI analysis** with appropriate templates and context
 - Parse structured results (fix strategies, root causes, modification points)

package/.claude/agents/debug-explore-agent.md

@@ -36,6 +36,7 @@ Phase 5: Fix & Verification
 ## Phase 1: Bug Analysis
 
 **Load Project Context** (from spec system):
+- Load debug specs using: `ccw spec load --category debug` for known issues, workarounds, and root-cause notes
 - Load exploration specs using: `ccw spec load --category exploration` for tech stack context and coding constraints
 
 **Session Setup**:

package/.claude/agents/tdd-developer.md

@@ -383,6 +383,7 @@ Bash(
 ### Context Loading (Inherited from code-developer)
 
 **Standard Context Sources**:
+- Test specs: Run `ccw spec load --category test` for test framework context, conventions, and coverage targets
 - Task JSON: `description`, `convergence.criteria`, `focus_paths`
 - Context Package: `context_package_path` → brainstorm artifacts, exploration results
 - Tech Stack: `meta.shared_context.tech_stack` (skip auto-detection if present)

package/.claude/agents/team-worker.md

@@ -99,8 +99,8 @@ Execute on every loop iteration:
    - Subject starts with this role's `prefix` + `-` (e.g., `DRAFT-`, `IMPL-`)
    - Status is `pending`
    - `blockedBy` list is empty (all dependencies resolved)
-   - **Owner matches** `agent_name` from prompt (e.g., task owner "explorer-1" matches agent_name "explorer-1"). This prevents parallel workers from claiming each other's tasks.
    - If role has `additional_prefixes` (e.g., reviewer handles REVIEW-* + QUALITY-* + IMPROVE-*), check all prefixes
+   - **NOTE**: Do NOT filter by owner name. The system appends numeric suffixes to agent names (e.g., `profiler` → `profiler-4`), making exact owner matching unreliable. Prefix-based filtering is sufficient to prevent cross-role task claiming.
 3. **No matching tasks?**
    - If first iteration → report idle, SendMessage "No tasks found for [role]", STOP
    - If inner loop continuation → proceed to Phase 5-F (all done)

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

@@ -52,6 +52,9 @@ Read("d:\Claude_dms3\.claude\agents\action-planning-agent.md")
 ```
 <!-- TODO: verify mandatory read path -->
 
+**Load Project Context** (from spec system):
+- Run: `ccw spec load --category test` for test framework, coverage targets, and conventions
+
 </role>
 
 <test_specification_reference>

package/.claude/agents/test-context-search-agent.md

@@ -25,6 +25,7 @@ You are a test context discovery specialist focused on gathering test coverage i
 **Mandatory Initial Read:**
 - Project `CLAUDE.md` for coding standards and conventions
 - Test session metadata (`workflow-session.json`) for session context
+- Run: `ccw spec load --category test` for test framework, coverage targets, and conventions
 
 **Core Responsibilities:**
 - Coverage-first analysis of existing tests

package/.claude/agents/test-fix-agent.md

@@ -34,6 +34,9 @@ If the prompt contains a `<files_to_read>` block, you MUST use the `Read` tool
 to load every file listed there before performing any other actions. This is your
 primary context.
 
+**Load Project Context** (from spec system):
+- Run: `ccw spec load --category test` for test framework, coverage targets, and conventions
+
 ## Core Philosophy
 
 **"Tests Are the Review"** - When all tests pass across all layers, the code is approved and ready. No separate review process is needed.

package/.claude/skills/review-code/SKILL.md

@@ -40,6 +40,8 @@ Multi-dimensional code review skill that analyzes code across 6 key dimensions a
 └─────────────────────────────────────────────────────────────────┘
 ```
 
+**Project Context**: Run `ccw spec load --category review` for review standards, checklists, and approval gates.
+
 ## Key Design Principles
 
 1. **多维度审查**: 覆盖正确性、可读性、性能、安全性、测试覆盖、架构一致性六大维度

package/.claude/skills/review-cycle/SKILL.md

@@ -98,6 +98,10 @@ Skill(skill="review-cycle", args="-y src/auth/**")
 | module | [phases/review-module.md](phases/review-module.md) | review-module-cycle.md | Module-based review: path patterns → 7-dimension parallel analysis → aggregation → deep-dive → completion |
 | fix | [phases/review-fix.md](phases/review-fix.md) | review-cycle-fix.md | Automated fix: export file → intelligent batching → parallel planning → execution → completion |
 
+## Project Context
+
+Run `ccw spec load --category review` for review standards, checklists, and approval gates.
+
 ## Core Rules
 
 1. **Mode Detection First**: Parse input to determine session/module/fix mode before anything else

package/.claude/skills/skill-simplify/phases/02-optimize.md

@@ -9,6 +9,10 @@ Apply simplification rules from analysisResult to produce optimized content. Wri
 - Fix pseudo-code format issues
 - Write optimized content back to target file
 
+## Pre-Step: Load Context
+
+Run `ccw spec load --category validation` for verification rules and acceptance criteria to validate optimization preserves functional integrity.
+
 ## Execution
 
 ### Step 2.1: Apply Operations in Order

package/.claude/skills/spec-generator/phases/05-epics-stories.md

@@ -19,6 +19,10 @@ Decompose the specification into executable Epics and Stories with dependency ma
 
 ## Execution Steps
 
+### Step 0: Load Validation Context
+
+Run `ccw spec load --category validation` for verification rules and acceptance criteria to validate epic decomposition.
+
 ### Step 1: Load Phase 2-4 Context
 
 ```javascript

package/.claude/skills/team-arch-opt/specs/team-config.json

@@ -23,7 +23,7 @@
       "name": "analyzer",
       "type": "orchestration",
       "description": "Analyzes architecture: dependency graphs, coupling/cohesion, layering violations, God Classes, dead code",
-      "role_spec": "role-specs/analyzer.md",
+      "role_spec": "roles/analyzer/role.md",
       "inner_loop": false,
       "frontmatter": {
         "prefix": "ANALYZE",
@@ -43,7 +43,7 @@
       "name": "designer",
       "type": "orchestration",
       "description": "Designs refactoring strategies from architecture analysis, produces prioritized refactoring plan with discrete REFACTOR-IDs",
-      "role_spec": "role-specs/designer.md",
+      "role_spec": "roles/designer/role.md",
       "inner_loop": false,
       "frontmatter": {
         "prefix": "DESIGN",
@@ -63,7 +63,7 @@
       "name": "refactorer",
       "type": "code_generation",
       "description": "Implements architecture refactoring changes following the design plan",
-      "role_spec": "role-specs/refactorer.md",
+      "role_spec": "roles/refactorer/role.md",
       "inner_loop": true,
       "frontmatter": {
         "prefix": "REFACTOR",
@@ -84,7 +84,7 @@
       "name": "validator",
       "type": "validation",
       "description": "Validates refactoring: build checks, test suites, dependency metrics, API compatibility",
-      "role_spec": "role-specs/validator.md",
+      "role_spec": "roles/validator/role.md",
       "inner_loop": false,
       "frontmatter": {
         "prefix": "VALIDATE",
@@ -105,7 +105,7 @@
       "name": "reviewer",
       "type": "read_only_analysis",
       "description": "Reviews refactoring code for correctness, pattern consistency, completeness, migration safety, and best practices",
-      "role_spec": "role-specs/reviewer.md",
+      "role_spec": "roles/reviewer/role.md",
       "inner_loop": false,
       "frontmatter": {
         "prefix": "REVIEW",

package/.claude/skills/team-frontend-debug/roles/analyzer/role.md

@@ -31,8 +31,9 @@ Root cause analysis from debug evidence.
 
 ## Phase 2: Load Evidence
 
-1. Read upstream artifacts via team_msg(operation="get_state", role="reproducer")
-2. Extract evidence paths from reproducer's state_update ref
+1. Load debug specs: Run `ccw spec load --category debug` for known issues, workarounds, and root-cause notes
+2. Read upstream artifacts via team_msg(operation="get_state", role="reproducer")
+3. Extract evidence paths from reproducer's state_update ref
 3. Load evidence-summary.json from session evidence/
 4. Load all evidence files:
    - Read screenshot files (visual inspection)

package/.claude/skills/team-perf-opt/roles/coordinator/commands/monitor.md

@@ -73,7 +73,7 @@ Agent({
   run_in_background: true,
   prompt: `## Role Assignment
 role: <role>
-role_spec: ~  or <project>/.claude/skills/team-perf-opt/role-specs/<role>.md
+role_spec: ~  or <project>/.claude/skills/team-perf-opt/roles/<role>/role.md
 session: <session-folder>
 session_id: <session-id>
 team_name: perf-opt

package/.claude/skills/team-perf-opt/specs/team-config.json

@@ -24,7 +24,7 @@
       "name": "profiler",
       "type": "orchestration",
       "description": "Profiles application performance, identifies CPU/memory/IO/network/rendering bottlenecks",
-      "role_spec": "role-specs/profiler.md",
+      "role_spec": "roles/profiler/role.md",
       "inner_loop": false,
       "frontmatter": {
         "prefix": "PROFILE",
@@ -44,7 +44,7 @@
       "name": "strategist",
       "type": "orchestration",
       "description": "Analyzes bottleneck reports, designs prioritized optimization plans with concrete strategies",
-      "role_spec": "role-specs/strategist.md",
+      "role_spec": "roles/strategist/role.md",
       "inner_loop": false,
       "frontmatter": {
         "prefix": "STRATEGY",
@@ -64,7 +64,7 @@
       "name": "optimizer",
       "type": "code_generation",
       "description": "Implements optimization changes following the strategy plan",
-      "role_spec": "role-specs/optimizer.md",
+      "role_spec": "roles/optimizer/role.md",
       "inner_loop": true,
       "frontmatter": {
         "prefix": "IMPL",
@@ -85,7 +85,7 @@
       "name": "benchmarker",
       "type": "validation",
       "description": "Runs benchmarks, compares before/after metrics, validates performance improvements",
-      "role_spec": "role-specs/benchmarker.md",
+      "role_spec": "roles/benchmarker/role.md",
       "inner_loop": false,
       "frontmatter": {
         "prefix": "BENCH",
@@ -106,7 +106,7 @@
       "name": "reviewer",
       "type": "read_only_analysis",
       "description": "Reviews optimization code for correctness, side effects, and regression risks",
-      "role_spec": "role-specs/reviewer.md",
+      "role_spec": "roles/reviewer/role.md",
       "inner_loop": false,
       "frontmatter": {
         "prefix": "REVIEW",

package/.claude/skills/team-quality-assurance/roles/executor/role.md

@@ -26,7 +26,8 @@ Run test suites, collect coverage data, and perform automatic fix cycles when te
 | Target layer | task description `layer: L1/L2/L3` | Yes |
 
 1. Extract session path and target layer from task description
-2. Read .msg/meta.json for strategy and generated test file list
+2. Load validation specs: Run `ccw spec load --category validation` for verification rules and acceptance criteria
+3. Read .msg/meta.json for strategy and generated test file list
 3. Detect test command by framework:
 
 | Framework | Command |

package/.claude/skills/team-review/roles/reviewer/role.md

@@ -21,7 +21,8 @@ Deep analysis on scan findings: triage, root cause / impact / optimization enric
 | .msg/meta.json | <session>/.msg/meta.json | No |
 
 1. Extract session path, input path, dimensions from task description
-2. Load scan results. If missing or empty -> report clean, complete immediately
+2. Load review specs: Run `ccw spec load --category review` for review standards, checklists, and approval gates
+3. Load scan results. If missing or empty -> report clean, complete immediately
 3. Load wisdom files from `<session>/wisdom/`
 4. Triage findings into two buckets:
 

package/.claude/skills/team-tech-debt/roles/scanner/role.md

@@ -18,7 +18,8 @@ Multi-dimension tech debt scanner. Scan codebase across 5 dimensions (code, arch
 | .msg/meta.json | <session>/.msg/meta.json | Yes |
 
 1. Extract session path and scan scope from task description
-2. Read .msg/meta.json for team context
+2. Load debug specs: Run `ccw spec load --category debug` for known issues, workarounds, and root-cause notes
+3. Read .msg/meta.json for team context
 3. Detect project type and framework:
 
 | Signal File | Project Type |

package/.claude/skills/team-testing/roles/executor/role.md

@@ -24,7 +24,8 @@ Execute tests, collect coverage, attempt auto-fix for failures. Acts as the Crit
 | .msg/meta.json | <session>/wisdom/.msg/meta.json | No |
 
 1. Extract session path and test directory from task description
-2. Extract coverage target (default: 80%)
+2. Load test specs: Run `ccw spec load --category test` for test framework conventions and coverage targets
+3. Extract coverage target (default: 80%)
 3. Read .msg/meta.json for framework info (from strategist namespace)
 4. Determine test framework:
 

package/.claude/skills/team-testing/roles/generator/role.md

@@ -22,7 +22,8 @@ Generate test code by layer (L1 unit / L2 integration / L3 E2E). Acts as the Gen
 | .msg/meta.json | <session>/wisdom/.msg/meta.json | No |
 
 1. Extract session path and layer from task description
-2. Read test strategy:
+2. Load test specs: Run `ccw spec load --category test` for test framework conventions and coverage targets
+3. Read test strategy:
 
 ```
 Read("<session>/strategy/test-strategy.md")

package/.claude/skills/team-ultra-analyze/roles/explorer/role.md

@@ -18,7 +18,8 @@ Explore codebase structure through cli-explore-agent, collecting structured cont
 | Task description | From task subject/description | Yes |
 | Session path | Extracted from task description | Yes |
 
-1. Extract session path, topic, perspective, dimensions from task description:
+1. Load debug specs: Run `ccw spec load --category debug` for known issues and root-cause notes
+2. Extract session path, topic, perspective, dimensions from task description:
 
 | Field | Pattern | Default |
 |-------|---------|---------|

package/.claude/skills/team-ux-improve/specs/team-config.json

@@ -27,7 +27,7 @@
       "display_name": "UI Scanner",
       "type": "worker",
       "responsibility_type": "read_only_analysis",
-      "role_spec": "role-specs/scanner.md",
+      "role_spec": "roles/scanner/role.md",
       "task_prefix": "SCAN",
       "inner_loop": false,
       "allowed_tools": ["Read", "Grep", "Glob", "Bash", "mcp__ace-tool__search_context", "mcp__ccw-tools__read_file", "mcp__ccw-tools__team_msg", "TaskList", "TaskGet", "TaskUpdate", "SendMessage"],
@@ -46,7 +46,7 @@
       "display_name": "State Diagnoser",
       "type": "worker",
       "responsibility_type": "orchestration",
-      "role_spec": "role-specs/diagnoser.md",
+      "role_spec": "roles/diagnoser/role.md",
       "task_prefix": "DIAG",
       "inner_loop": false,
       "allowed_tools": ["Read", "Grep", "Bash", "mcp__ace-tool__search_context", "mcp__ccw-tools__read_file", "mcp__ccw-tools__team_msg", "TaskList", "TaskGet", "TaskUpdate", "SendMessage"],
@@ -65,7 +65,7 @@
       "display_name": "UX Designer",
       "type": "worker",
       "responsibility_type": "orchestration",
-      "role_spec": "role-specs/designer.md",
+      "role_spec": "roles/designer/role.md",
       "task_prefix": "DESIGN",
       "inner_loop": false,
       "allowed_tools": ["Read", "Write", "Bash", "mcp__ccw-tools__read_file", "mcp__ccw-tools__write_file", "mcp__ccw-tools__team_msg", "TaskList", "TaskGet", "TaskUpdate", "SendMessage"],
@@ -84,7 +84,7 @@
       "display_name": "Code Implementer",
       "type": "worker",
       "responsibility_type": "code_generation",
-      "role_spec": "role-specs/implementer.md",
+      "role_spec": "roles/implementer/role.md",
       "task_prefix": "IMPL",
       "inner_loop": true,
       "allowed_tools": ["Read", "Write", "Edit", "Bash", "mcp__ccw-tools__read_file", "mcp__ccw-tools__write_file", "mcp__ccw-tools__edit_file", "mcp__ccw-tools__team_msg", "TaskList", "TaskGet", "TaskUpdate", "SendMessage"],
@@ -103,7 +103,7 @@
       "display_name": "Test Engineer",
       "type": "worker",
       "responsibility_type": "validation",
-      "role_spec": "role-specs/tester.md",
+      "role_spec": "roles/tester/role.md",
       "task_prefix": "TEST",
       "inner_loop": false,
       "allowed_tools": ["Read", "Write", "Bash", "mcp__ccw-tools__read_file", "mcp__ccw-tools__write_file", "mcp__ccw-tools__team_msg", "TaskList", "TaskGet", "TaskUpdate", "SendMessage"],
@@ -123,7 +123,7 @@
     {
       "name": "explorer",
       "display_name": "Codebase Explorer",
-      "role_spec": "role-specs/explorer.md",
+      "role_spec": "roles/explorer/role.md",
       "callable_by": "coordinator",
       "purpose": "Explore codebase for UI component patterns, state management conventions, and framework-specific patterns",
       "allowed_tools": ["Read", "Grep", "Glob", "Bash", "mcp__ace-tool__search_context", "mcp__ccw-tools__read_file", "mcp__ccw-tools__team_msg"],

package/.claude/skills/workflow-execute/phases/06-review.md

@@ -93,7 +93,7 @@ rg "password|token|secret|auth" -g "*.{ts,js,py}"
 rg "eval|exec|innerHTML|dangerouslySetInnerHTML" -g "*.{ts,js,tsx}"
 
 # Gemini security analysis
-ccw spec load --category execution
+ccw spec load --category review
 ccw cli -p "
 PURPOSE: Security audit of completed implementation
 TASK: Review code for security vulnerabilities, insecure patterns, auth/authz issues
@@ -105,7 +105,7 @@ RULES: Focus on OWASP Top 10, authentication, authorization, data validation, in
 
 **Architecture Review** (`architecture`):
 ```bash
-ccw spec load --category execution
+ccw spec load --category review
 ccw cli -p "
 PURPOSE: Architecture compliance review
 TASK: Evaluate adherence to architectural patterns, identify technical debt, review design decisions
@@ -117,7 +117,7 @@ RULES: Check for patterns, separation of concerns, modularity, scalability
 
 **Quality Review** (`quality`):
 ```bash
-ccw spec load --category execution
+ccw spec load --category review
 ccw cli -p "
 PURPOSE: Code quality and best practices review
 TASK: Assess code readability, maintainability, adherence to best practices
@@ -139,7 +139,7 @@ for task_file in ${sessionPath}/.task/*.json; do
 done
 
 # Cross-check implementation against requirements
-ccw spec load --category execution
+ccw spec load --category review
 ccw cli -p "
 PURPOSE: Verify all requirements and acceptance criteria are met
 TASK: Cross-check implementation summaries against original requirements

package/.claude/skills/workflow-lite-test-review/SKILL.md

@@ -8,6 +8,8 @@ allowed-tools: Skill, Agent, AskUserQuestion, TodoWrite, Read, Write, Edit, Bash
 
 Test review and fix engine for lite-execute chain or standalone invocation.
 
+**Project Context**: Run `ccw spec load --category test` for test framework conventions, coverage targets, and fixtures.
+
 ---
 
 ## Usage

package/.claude/skills/workflow-plan/phases/05-plan-verify.md

@@ -34,6 +34,10 @@ You **MUST** consider the user input before proceeding (if not empty).
 
 ## Execution
 
+### Step 5.0: Load Validation Context
+
+Run `ccw spec load --category validation` for verification rules and acceptance criteria.
+
 ### Step 5.1: Initialize Analysis Context
 
 ```bash

package/.claude/skills/workflow-tdd-plan/phases/02-context-gathering.md

@@ -222,6 +222,7 @@ Execute complete context-search-agent workflow for TDD implementation planning:
 ### Phase 1: Initialization & Pre-Analysis
 1. **Project State Loading**:
    - Run: \`ccw spec load --category execution\` to load project context, tech stack, and guidelines.
+   - Run: \`ccw spec load --category test\` to load test framework conventions, coverage targets, and fixtures.
    - If files don't exist, proceed with fresh analysis.
 2. **Detection**: Check for existing context-package (early exit if valid)
 3. **Foundation**: Initialize CodexLens, get project structure, load docs

package/.claude/skills/workflow-tdd-plan/phases/05-tdd-task-generation.md

@@ -237,13 +237,14 @@ MCP Capabilities: {exa_code, exa_web, code_index}
 These files provide project-level constraints that apply to ALL tasks:
 
 1. **ccw spec load --category execution** (project specs and tech analysis)
+2. **ccw spec load --category test** (test framework, coverage targets, conventions)
    - Contains: tech_stack, architecture_type, key_components, build_system, test_framework, coding_conventions, naming_rules, forbidden_patterns, quality_gates, custom_constraints
    - Usage: Populate plan.json shared_context, align task tech choices, set correct test commands
    - Apply as HARD CONSTRAINTS on all generated tasks — task implementation steps,
      acceptance criteria, and convergence.verification MUST respect these guidelines
    - If empty/missing: No additional constraints (proceed normally)
 
-Loading order: \`ccw spec load --category execution\` → planning-notes.md → context-package.json
+Loading order: \`ccw spec load --category execution\` → \`ccw spec load --category test\` → planning-notes.md → context-package.json
 
 ## USER CONFIGURATION (from Phase 0)
 Execution Method: ${userConfig.executionMethod}  // agent|hybrid|cli

package/.claude/skills/workflow-test-fix/phases/02-test-context-gather.md

@@ -346,6 +346,7 @@ Execute complete context-search-agent workflow for implementation planning:
 ### Phase 1: Initialization & Pre-Analysis
 1. **Project State Loading**:
    - Run: \`ccw spec load --category execution\` to load project context, tech stack, and guidelines.
+   - Run: \`ccw spec load --category test\` to load test framework conventions, coverage targets, and fixtures.
    - If files don't exist, proceed with fresh analysis.
 2. **Detection**: Check for existing context-package (early exit if valid)
 3. **Foundation**: Initialize CodexLens, get project structure, load docs

package/.claude/skills/workflow-test-fix/phases/05-test-cycle-execute.md

@@ -249,7 +249,8 @@ Task(
     ${selectedStrategy} - ${strategyDescription}
 
     ## PROJECT CONTEXT (MANDATORY)
-    1. Run: \`ccw spec load --category execution\` (tech stack, test framework, build system, constraints)
+    1. Run: \`ccw spec load --category execution\` (tech stack, build system, constraints)
+    2. Run: \`ccw spec load --category test\` (test framework, coverage targets, conventions)
 
     ## MANDATORY FIRST STEPS
     1. Read test results: ${session.test_results_path}