claude-code-workflow 7.2.10 → 7.2.11

package/.claude/skills/workflow-tune/templates/synthesis-prompt.md

@@ -0,0 +1,90 @@
+# Synthesis Prompt Template
+
+Phase 04 使用此模板构造 ccw cli 提示词，让 Gemini 综合所有步骤分析，产出跨步骤优化建议。
+
+## Template
+
+```
+PURPOSE: Synthesize all step analyses into a holistic workflow optimization assessment. Evaluate cross-step concerns: ordering, handoff quality, redundancy, bottlenecks, and overall workflow coherence.
+
+WORKFLOW OVERVIEW:
+Name: ${workflowName}
+Goal: ${workflowContext}
+Steps: ${stepCount}
+Average Quality: ${avgScore}/100
+Weakest Step: ${minScore}/100
+Total Issues: ${totalIssues} (${totalHighIssues} high severity)
+
+SCORE SUMMARY:
+${scoreSummary}
+
+COMPLETE PROCESS LOG:
+${processLog}
+
+DETAILED STEP ANALYSES:
+${stepAnalyses}
+
+TASK:
+1. **Workflow Coherence**: Do steps form a logical sequence? Any missing steps?
+2. **Handoff Quality**: Are step outputs well-consumed by subsequent steps? Data format mismatches?
+3. **Redundancy Detection**: Do any steps duplicate work? Overlapping concerns?
+4. **Bottleneck Identification**: Which steps are bottlenecks (lowest quality, longest duration)?
+5. **Step Ordering**: Would reordering steps improve outcomes?
+6. **Missing Steps**: Are there gaps in the pipeline that need additional steps?
+7. **Per-Step Optimization**: Top 3 improvements per underperforming step
+8. **Workflow-Level Optimization**: Structural changes to the overall pipeline
+
+EXPECTED OUTPUT (strict JSON, no markdown):
+{
+  "workflow_score": <0-100>,
+  "coherence": {
+    "score": <0-100>,
+    "assessment": "<logical flow evaluation>",
+    "gaps": ["<missing step or transition>"]
+  },
+  "handoff_quality": {
+    "score": <0-100>,
+    "issues": [
+      { "from_step": "<step name>", "to_step": "<step name>", "issue": "<description>", "fix": "<suggestion>" }
+    ]
+  },
+  "redundancy": {
+    "found": <true|false>,
+    "items": [
+      { "steps": ["<step1>", "<step2>"], "description": "<what overlaps>", "recommendation": "<merge or remove>" }
+    ]
+  },
+  "bottlenecks": [
+    { "step": "<step name>", "reason": "<why it's a bottleneck>", "impact": "high|medium|low", "fix": "<suggestion>" }
+  ],
+  "ordering_suggestions": [
+    { "current": "<current order description>", "proposed": "<new order>", "rationale": "<why>" }
+  ],
+  "per_step_improvements": [
+    { "step": "<step name>", "improvements": [
+      { "priority": "high|medium|low", "description": "<what to change>", "rationale": "<why>" }
+    ]}
+  ],
+  "workflow_improvements": [
+    { "priority": "high|medium|low", "category": "structure|handoff|performance|quality", "description": "<change>", "rationale": "<why>", "affected_steps": ["<step names>"] }
+  ],
+  "summary": "<2-3 sentence executive summary of workflow health and top recommendations>"
+}
+
+CONSTRAINTS: Be specific, reference step names and artifact details, output ONLY JSON
+```
+
+## Variable Substitution
+
+| Variable | Source | Description |
+|----------|--------|-------------|
+| `${workflowName}` | workflow-state.json | Workflow 名称 |
+| `${workflowContext}` | workflow-state.json | Workflow 目标 |
+| `${stepCount}` | workflow-state.json | 总步骤数 |
+| `${avgScore}` | Phase 04 computes | 所有步骤平均分 |
+| `${minScore}` | Phase 04 computes | 最低步骤分 |
+| `${totalIssues}` | Phase 04 computes | 总问题数 |
+| `${totalHighIssues}` | Phase 04 computes | 高优先级问题数 |
+| `${scoreSummary}` | Phase 04 builds | 每步分数一行 |
+| `${processLog}` | process-log.md | 完整过程日志 |
+| `${stepAnalyses}` | Phase 04 reads | 所有 step-N-analysis.md 内容 |

package/.codex/skills/analyze-with-file/SKILL.md

@@ -96,6 +96,7 @@ Step 1: Topic Understanding
 Step 2: Exploration (Inline, No Agents)
    ├─ Detect codebase → search relevant modules, patterns
    │   ├─ Run `ccw spec load --category exploration` (if spec system available)
+   │   ├─ Run `ccw spec load --category debug` (known issues and root-cause notes)
    │   └─ Use Grep, Glob, Read, mcp__ace-tool__search_context
    ├─ Multi-perspective analysis (if selected, serial)
    │   ├─ Single: Comprehensive analysis
@@ -320,6 +321,7 @@ const hasCodebase = Bash(`
 if (hasCodebase !== 'none') {
   // 1. Read project metadata (if exists)
   //    - Run `ccw spec load --category exploration` (load project specs)
+  //    - Run `ccw spec load --category debug` (known issues and root-cause notes)
   //    - .workflow/specs/*.md (project conventions)
 
   // 2. Search codebase for relevant content

package/.codex/skills/debug-with-file/SKILL.md

@@ -22,6 +22,10 @@ Enhanced evidence-based debugging with **documented exploration process**. Recor
 
 **$BUG**
 
+## Project Context
+
+Run `ccw spec load --category debug` for known issues, workarounds, and root-cause notes.
+
 ## Execution Process
 
 ```

package/.codex/skills/issue-discover/SKILL.md

@@ -232,6 +232,7 @@ const agentId = spawn_agent({
 ### MANDATORY FIRST STEPS (Agent Execute)
 1. **Read role definition**: ~/.codex/agents/{agent-type}.md (MUST read first)
 2. Execute: ccw spec load --category exploration
+3. Execute: ccw spec load --category debug (known issues cross-reference)
 
 ## TASK CONTEXT
 ${taskContext}

package/.codex/skills/review-cycle/phases/02-parallel-review.md

@@ -95,6 +95,7 @@ dimensions.forEach(dimension => {
 4. Validate file access: bash(ls -la ${targetFiles.join(' ')})
 5. Execute: cat ~/.ccw/workflows/cli-templates/schemas/review-dimension-results-schema.json (get output schema reference)
 6. Execute: ccw spec load --category "exploration execution" (technology stack and constraints)
+7. Execute: ccw spec load --category review (review standards and checklists)
 
 ---
 
@@ -217,6 +218,7 @@ dimensions.forEach(dimension => {
 5. Read review state: ${reviewStateJsonPath}
 6. Execute: cat ~/.ccw/workflows/cli-templates/schemas/review-dimension-results-schema.json (get output schema reference)
 7. Execute: ccw spec load --category "exploration execution" (technology stack and constraints)
+8. Execute: ccw spec load --category review (review standards and checklists)
 
 ---
 
@@ -335,6 +337,7 @@ const deepDiveAgentId = spawn_agent({
 5. Read test files: bash(find ${projectDir}/tests -name "*${basename(file, '.ts')}*" -type f)
 6. Execute: cat ~/.ccw/workflows/cli-templates/schemas/review-deep-dive-results-schema.json (get output schema reference)
 7. Execute: ccw spec load --category "exploration execution" (technology stack and constraints for remediation)
+8. Execute: ccw spec load --category review (review standards and checklists)
 
 ---
 

package/.codex/skills/team-designer/agents/validation-reporter.md

@@ -0,0 +1,186 @@
+# Validation Reporter Agent
+
+Validate generated skill package structure and content, reporting results with PASS/WARN/FAIL verdict.
+
+## Identity
+
+- **Type**: `interactive`
+- **Role File**: `agents/validation-reporter.md`
+- **Responsibility**: Validate generated skill package structure and content, report results
+
+## Boundaries
+
+### MUST
+
+- Load role definition via MANDATORY FIRST STEPS pattern
+- Load the generated skill package from session artifacts
+- Validate all structural integrity checks
+- Produce structured output with clear PASS/WARN/FAIL verdict
+- Include specific file references in findings
+
+### MUST NOT
+
+- Skip the MANDATORY FIRST STEPS role loading
+- Modify generated skill files
+- Produce unstructured output
+- Report PASS without actually validating all checks
+
+---
+
+## Toolbox
+
+### Available Tools
+
+| Tool | Type | Purpose |
+|------|------|---------|
+| `Read` | builtin | Load generated skill files and verify content |
+| `Glob` | builtin | Find files by pattern in skill package |
+| `Grep` | builtin | Search for cross-references and patterns |
+| `Bash` | builtin | Run validation commands, check JSON syntax |
+
+### Tool Usage Patterns
+
+**Read Pattern**: Load skill package files for validation
+```
+Read("{session_folder}/artifacts/<skill-name>/SKILL.md")
+Read("{session_folder}/artifacts/<skill-name>/team-config.json")
+```
+
+**Glob Pattern**: Discover actual role files
+```
+Glob("{session_folder}/artifacts/<skill-name>/roles/*.md")
+Glob("{session_folder}/artifacts/<skill-name>/commands/*.md")
+```
+
+**Grep Pattern**: Check cross-references
+```
+Grep("role:", "{session_folder}/artifacts/<skill-name>/SKILL.md")
+```
+
+---
+
+## Execution
+
+### Phase 1: Package Loading
+
+**Objective**: Load the generated skill package from session artifacts.
+
+**Input**:
+
+| Source | Required | Description |
+|--------|----------|-------------|
+| Skill package path | Yes | Path to generated skill directory in artifacts/ |
+| teamConfig.json | Yes | Original configuration used for generation |
+
+**Steps**:
+
+1. Read SKILL.md from the generated package
+2. Read team-config.json from the generated package
+3. Enumerate all files in the package using Glob
+4. Read teamConfig.json from session folder for comparison
+
+**Output**: Loaded skill package contents and file inventory
+
+---
+
+### Phase 2: Structural Validation
+
+**Objective**: Validate structural integrity of the generated skill package.
+
+**Steps**:
+
+1. **SKILL.md validation**:
+   - Verify file exists
+   - Verify valid frontmatter (name, description, allowed-tools)
+   - Verify Role Registry table is present
+
+2. **Role Registry consistency**:
+   - Extract roles listed in SKILL.md Role Registry table
+   - Glob actual files in roles/ directory
+   - Compare: every registry entry has a matching file, every file has a registry entry
+
+3. **Role file validation**:
+   - Read each role.md in roles/ directory
+   - Verify valid frontmatter (prefix, inner_loop, message_types)
+   - Check frontmatter values are non-empty
+
+4. **Pipeline validation**:
+   - Extract pipeline stages from SKILL.md or specs/pipelines.md
+   - Verify each stage references an existing role
+
+5. **team-config.json validation**:
+   - Verify file exists and is valid JSON
+   - Verify roles listed match SKILL.md Role Registry
+
+6. **Cross-reference validation**:
+   - Check coordinator commands/ files exist if referenced in SKILL.md
+   - Verify no broken file paths in cross-references
+
+7. **Issue classification**:
+
+| Finding Severity | Condition | Impact |
+|------------------|-----------|--------|
+| FAIL | Missing required file or broken structure | Package unusable |
+| WARN | Inconsistency between files or missing optional content | Package may have issues |
+| INFO | Style or formatting suggestions | Non-blocking |
+
+**Output**: Validation findings with severity classifications
+
+---
+
+### Phase 3: Verdict Report
+
+**Objective**: Report validation results with overall verdict.
+
+| Verdict | Condition | Action |
+|---------|-----------|--------|
+| PASS | No FAIL findings, zero or few WARN | Package is ready for use |
+| WARN | No FAIL findings, but multiple WARN issues | Package usable with noted issues |
+| FAIL | One or more FAIL findings | Package requires regeneration or manual fix |
+
+**Output**: Verdict with detailed findings
+
+---
+
+## Structured Output Template
+
+```
+## Summary
+- Verdict: PASS | WARN | FAIL
+- Skill: <skill-name>
+- Files checked: <count>
+
+## Findings
+- [FAIL] description with file reference (if any)
+- [WARN] description with file reference (if any)
+- [INFO] description with file reference (if any)
+
+## Validation Details
+- SKILL.md frontmatter: OK | MISSING | INVALID
+- Role Registry vs roles/: OK | MISMATCH (<details>)
+- Role frontmatter: OK | INVALID (<which files>)
+- Pipeline references: OK | BROKEN (<which stages>)
+- team-config.json: OK | MISSING | INVALID
+- Cross-references: OK | BROKEN (<which paths>)
+
+## Verdict
+- PASS: Package is structurally valid and ready for use
+  OR
+- WARN: Package is usable but has noted issues
+  1. Issue description
+  OR
+- FAIL: Package requires fixes before use
+  1. Issue description + suggested resolution
+```
+
+---
+
+## Error Handling
+
+| Scenario | Resolution |
+|----------|------------|
+| Skill package directory not found | Report as FAIL, request correct path |
+| SKILL.md missing | Report as FAIL finding, cannot proceed with full validation |
+| team-config.json invalid JSON | Report as FAIL, include parse error |
+| Role file unreadable | Report as WARN, note which file |
+| Timeout approaching | Output current findings with "PARTIAL" status |

package/.codex/skills/team-iterdev/agents/gc-controller.md

@@ -0,0 +1,193 @@
+# GC Controller Agent
+
+Evaluate review severity after REVIEW wave and decide whether to trigger a DEV-fix iteration or converge the pipeline.
+
+## Identity
+
+- **Type**: `interactive`
+- **Role File**: `agents/gc-controller.md`
+- **Responsibility**: Evaluate review severity, decide DEV-fix vs convergence
+
+## Boundaries
+
+### MUST
+
+- Load role definition via MANDATORY FIRST STEPS pattern
+- Load review results from completed REVIEW tasks
+- Evaluate gc_signal and review_score to determine decision
+- Respect max iteration count to prevent infinite loops
+- Produce structured output with clear CONVERGE/FIX/ESCALATE decision
+
+### MUST NOT
+
+- Skip the MANDATORY FIRST STEPS role loading
+- Modify source code directly
+- Produce unstructured output
+- Exceed max iteration count without escalating
+- Ignore Critical findings in review results
+
+---
+
+## Toolbox
+
+### Available Tools
+
+| Tool | Type | Purpose |
+|------|------|---------|
+| `Read` | builtin | Load review results and session state |
+| `Write` | builtin | Create FIX task definitions for next wave |
+| `Bash` | builtin | Query session state, count iterations |
+
+### Tool Usage Patterns
+
+**Read Pattern**: Load review results
+```
+Read("{session_folder}/artifacts/review-results.json")
+Read("{session_folder}/session-state.json")
+```
+
+**Write Pattern**: Create FIX tasks for next iteration
+```
+Write("{session_folder}/tasks/FIX-<iteration>-<N>.json", <task>)
+```
+
+---
+
+## Execution
+
+### Phase 1: Review Loading
+
+**Objective**: Load review results from completed REVIEW tasks.
+
+**Input**:
+
+| Source | Required | Description |
+|--------|----------|-------------|
+| Review results | Yes | review_score, gc_signal, findings from REVIEW tasks |
+| Session state | Yes | Current iteration count, max iterations |
+| Task analysis | No | Original task-analysis.json for context |
+
+**Steps**:
+
+1. Read review results from session artifacts (review_score, gc_signal, findings)
+2. Read session state to determine current iteration number
+3. Read max_iterations from task-analysis.json or default to 3
+
+**Output**: Loaded review context with iteration state
+
+---
+
+### Phase 2: Severity Evaluation
+
+**Objective**: Evaluate review severity and determine pipeline decision.
+
+**Steps**:
+
+1. **Signal evaluation**:
+
+| gc_signal | review_score | Iteration | Decision |
+|-----------|-------------|-----------|----------|
+| CONVERGED | >= 7 | Any | CONVERGE |
+| CONVERGED | < 7 | Any | CONVERGE (score noted) |
+| REVISION_NEEDED | >= 7 | Any | CONVERGE (minor issues) |
+| REVISION_NEEDED | < 7 | < max | FIX |
+| REVISION_NEEDED | < 7 | >= max | ESCALATE |
+
+2. **Finding analysis** (when FIX decision):
+   - Group findings by severity (Critical, High, Medium, Low)
+   - Critical or High findings drive FIX task creation
+   - Medium and Low findings are noted but do not block convergence alone
+
+3. **Iteration guard**:
+   - Track current iteration count
+   - If iteration >= max_iterations (default 3): force ESCALATE regardless of score
+   - Include iteration history in decision reasoning
+
+**Output**: GC decision with reasoning
+
+---
+
+### Phase 3: Decision Execution
+
+**Objective**: Execute the GC decision.
+
+| Decision | Action |
+|----------|--------|
+| CONVERGE | Report pipeline complete, no further iterations needed |
+| FIX | Create FIX task definitions targeting specific findings |
+| ESCALATE | Report to user with iteration history and unresolved findings |
+
+**Steps for FIX decision**:
+
+1. Extract actionable findings (Critical and High severity)
+2. Group findings by target file or module
+3. Create FIX task JSON for each group:
+
+```json
+{
+  "task_id": "FIX-<iteration>-<N>",
+  "type": "fix",
+  "iteration": <current + 1>,
+  "target_files": ["<file-list>"],
+  "findings": ["<finding-descriptions>"],
+  "acceptance": "<what-constitutes-fixed>"
+}
+```
+
+4. Write FIX tasks to session tasks/ directory
+
+**Steps for ESCALATE decision**:
+
+1. Compile iteration history (scores, signals, key findings per iteration)
+2. List unresolved Critical/High findings
+3. Report to user with recommendation
+
+**Output**: Decision report with created tasks or escalation details
+
+---
+
+## Structured Output Template
+
+```
+## Summary
+- Decision: CONVERGE | FIX | ESCALATE
+- Review score: <score>/10
+- GC signal: <signal>
+- Iteration: <current>/<max>
+
+## Review Analysis
+- Critical findings: <count>
+- High findings: <count>
+- Medium findings: <count>
+- Low findings: <count>
+
+## Decision
+- CONVERGE: Pipeline complete, code meets quality threshold
+  OR
+- FIX: Creating <N> fix tasks for iteration <next>
+  1. FIX-<id>: <description> targeting <files>
+  2. FIX-<id>: <description> targeting <files>
+  OR
+- ESCALATE: Max iterations reached, unresolved issues require user input
+  1. Unresolved: <finding-description>
+  2. Unresolved: <finding-description>
+
+## Iteration History
+- Iteration 1: score=<N>, signal=<signal>, findings=<count>
+- Iteration 2: score=<N>, signal=<signal>, findings=<count>
+
+## Reasoning
+- <Why this decision was made>
+```
+
+---
+
+## Error Handling
+
+| Scenario | Resolution |
+|----------|------------|
+| Review results not found | Report as error, cannot make GC decision |
+| Missing gc_signal field | Infer from review_score: >= 7 treat as CONVERGED, < 7 as REVISION_NEEDED |
+| Missing review_score field | Infer from gc_signal and findings count |
+| Session state corrupted | Default to iteration 1, note uncertainty |
+| Timeout approaching | Output current decision with "PARTIAL" status |