claude-code-workflow 7.2.10 → 7.2.12

package/.claude/skills/workflow-lite-plan/SKILL.md

@@ -40,7 +40,7 @@ Produces exploration results, a structured plan (plan.json), independent task fi
 
 **Output Directory**: `.workflow/.lite-plan/{task-slug}-{YYYY-MM-DD}/`
 
-**Agent Usage**: Low → Direct Claude planning (no agent) | Medium/High → `cli-lite-planning-agent`
+**Agent Usage**: All complexities → `cli-lite-planning-agent`
 
 **Schema Reference**: `~/.ccw/workflows/cli-templates/schemas/plan-overview-base-schema.json`
 
@@ -51,7 +51,7 @@ Produces exploration results, a structured plan (plan.json), independent task fi
 | LP-0 | Initialize workflowPreferences | autoYes, forceExplore |
 | LP-1 | Complexity assessment → parallel cli-explore-agents (1-4) | exploration-*.json + manifest |
 | LP-2 | Aggregate + dedup clarification_needs → multi-round AskUserQuestion | clarificationContext (in-memory) |
-| LP-3 | Low: Direct Claude planning / Medium+High: cli-lite-planning-agent | plan.json + .task/TASK-*.json |
+| LP-3 | cli-lite-planning-agent | plan.json + .task/TASK-*.json |
 | LP-4 | Display plan → AskUserQuestion (Confirm + Execution + Review) | userSelection |
 | LP-5 | Build executionContext → Skill("lite-execute") | handoff (Mode 1) |
 
@@ -85,7 +85,7 @@ bash(`mkdir -p ${sessionFolder} && test -d ${sessionFolder} && echo "SUCCESS: ${
 TodoWrite({ todos: [
   { content: `LP-Phase 1: Exploration [${complexity}] ${selectedAngles.length} angles`, status: "in_progress", activeForm: `Exploring: ${selectedAngles.join(', ')}` },
   { content: "LP-Phase 2: Clarification", status: "pending" },
-  { content: `LP-Phase 3: Planning [${planningStrategy}]`, status: "pending" },
+  { content: "LP-Phase 3: Planning [cli-lite-planning-agent]", status: "pending" },
   { content: "LP-Phase 4: Confirmation", status: "pending" },
   { content: "LP-Phase 5: Execution", status: "pending" }
 ]})
@@ -154,12 +154,7 @@ function selectAngles(taskDescription, count) {
 
 const selectedAngles = selectAngles(task_description, complexity === 'High' ? 4 : (complexity === 'Medium' ? 3 : 1))
 
-// Direct Claude planning ONLY for: Low + no prior analysis + single angle
-const planningStrategy = (
-  complexity === 'Low' && !hasPriorAnalysis && selectedAngles.length <= 1
-) ? 'Direct Claude Planning' : 'cli-lite-planning-agent'
-
-console.log(`Exploration Plan: ${complexity} | ${selectedAngles.join(', ')} | ${planningStrategy}`)
+console.log(`Exploration Plan: ${complexity} | ${selectedAngles.join(', ')} | cli-lite-planning-agent`)
 ```
 
 **Launch Parallel Explorations**:
@@ -328,56 +323,7 @@ taskFiles.forEach(taskPath => {
 })
 ```
 
-**Low Complexity** — Direct planning by Claude:
-```javascript
-const schema = Bash(`cat ~/.ccw/workflows/cli-templates/schemas/plan-overview-base-schema.json`)
-
-const manifest = file_exists(`${sessionFolder}/explorations-manifest.json`)
-  ? JSON.parse(Read(`${sessionFolder}/explorations-manifest.json`))
-  : { explorations: [] }
-manifest.explorations.forEach(exp => {
-  console.log(`\n### Exploration: ${exp.angle}\n${Read(exp.path)}`)
-})
-
-// When handoffSpec exists, use it as primary planning input
-// implementation_scope[].acceptance_criteria -> convergence.criteria
-// implementation_scope[].target_files -> files[]
-// implementation_scope[].objective -> task title/description
-if (handoffSpec) {
-  console.log(`\n### Handoff Spec from ${handoffSpec.source}`)
-  console.log(`Scope items: ${handoffSpec.implementation_scope.length}`)
-  handoffSpec.implementation_scope.forEach((item, i) => {
-    console.log(`  ${i+1}. ${item.objective} [${item.priority}] — Done when: ${item.acceptance_criteria.join('; ')}`)
-  })
-}
-
-// Generate tasks — MUST incorporate exploration insights OR handoff spec
-// When handoffSpec: map implementation_scope[] → tasks[] (1:1 or group by context)
-// Field names: convergence.criteria (not acceptance), files[].change (not modification_points), test (not verification)
-const tasks = [
-  {
-    id: "TASK-001", title: "...", description: "...", depends_on: [],
-    convergence: { criteria: ["..."] },  // From handoffSpec: item.acceptance_criteria
-    files: [{ path: "...", change: "..." }],  // From handoffSpec: item.target_files + item.change_summary
-    implementation: ["..."], test: "..."
-  }
-]
-
-const taskDir = `${sessionFolder}/.task`
-Bash(`mkdir -p "${taskDir}"`)
-tasks.forEach(task => Write(`${taskDir}/${task.id}.json`, JSON.stringify(task, null, 2)))
-
-const plan = {
-  summary: "...", approach: "...",
-  task_ids: tasks.map(t => t.id), task_count: tasks.length,
-  complexity: "Low", estimated_time: "...", recommended_execution: "Agent",
-  _metadata: { timestamp: getUtc8ISOString(), source: "direct-planning", planning_mode: "direct", plan_type: "feature" }
-}
-Write(`${sessionFolder}/plan.json`, JSON.stringify(plan, null, 2))
-// MUST continue to LP-Phase 4 — DO NOT execute code here
-```
-
-**Medium/High Complexity** — Invoke cli-lite-planning-agent:
+**Invoke cli-lite-planning-agent**:
 
 ```javascript
 Task(
@@ -492,8 +438,8 @@ ${tasks.map((t, i) => `${i+1}. ${t.title} (${t.scope || t.files?.[0]?.path || ''
 let userSelection
 
 if (workflowPreferences.autoYes) {
-  console.log(`[Auto] Allow & Execute | Auto | Skip`)
-  userSelection = { confirmation: "Allow", execution_method: "Auto", code_review_tool: "Skip" }
+  console.log(`[Auto] Allow & Execute | Auto | Skip + Skip`)
+  userSelection = { confirmation: "Allow", execution_method: "Auto", code_review_tool: "Skip", convergence_review_tool: "Skip" }
 } else {
   // "Other" in Execution allows specifying CLI tools from ~/.claude/cli-tools.json
   userSelection = AskUserQuestion({
@@ -519,14 +465,25 @@ if (workflowPreferences.autoYes) {
         ]
       },
       {
-        question: "Code review after execution?",
-        header: "Review",
+        question: "Code review after execution? (runs in lite-execute)",
+        header: "Code Review",
         multiSelect: false,
         options: [
-          { label: "Gemini Review", description: "Gemini CLI review" },
-          { label: "Codex Review", description: "Git-aware review (prompt OR --uncommitted)" },
+          { label: "Gemini Review", description: "Gemini CLI: git diff quality review" },
+          { label: "Codex Review", description: "Codex CLI: git-aware code review (--mode review)" },
           { label: "Agent Review", description: "@code-reviewer agent" },
-          { label: "Skip", description: "No review" }
+          { label: "Skip", description: "No code review" }
+        ]
+      },
+      {
+        question: "Convergence review in test-review phase?",
+        header: "Convergence Review",
+        multiSelect: false,
+        options: [
+          { label: "Agent", description: "Agent: verify convergence criteria against implementation" },
+          { label: "Gemini", description: "Gemini CLI: convergence verification" },
+          { label: "Codex", description: "Codex CLI: convergence verification" },
+          { label: "Skip", description: "Skip convergence review, run tests only" }
         ]
       }
     ]
@@ -534,7 +491,7 @@ if (workflowPreferences.autoYes) {
 }
 ```
 
-// TodoWrite: Phase 4 → completed `[${userSelection.execution_method} + ${userSelection.code_review_tool}]`, Phase 5 → in_progress
+// TodoWrite: Phase 4 → completed `[${userSelection.execution_method} | CR:${userSelection.code_review_tool} | CVR:${userSelection.convergence_review_tool}]`, Phase 5 → in_progress
 
 ## 10. LP-Phase 5: Handoff to Execution
 
@@ -561,6 +518,7 @@ executionContext = {
   clarificationContext: clarificationContext || null,
   executionMethod: userSelection.execution_method,
   codeReviewTool: userSelection.code_review_tool,
+  convergenceReviewTool: userSelection.convergence_review_tool,
   originalUserInput: task_description,
   executorAssignments: executorAssignments,  // { taskId: { executor, reason } } — overrides executionMethod
   session: {
@@ -588,7 +546,7 @@ TodoWrite({ todos: [
   { content: "LP-Phase 1: Exploration", status: "completed" },
   { content: "LP-Phase 2: Clarification", status: "completed" },
   { content: "LP-Phase 3: Planning", status: "completed" },
-  { content: `LP-Phase 4: Confirmed [${userSelection.execution_method}]`, status: "completed" },
+  { content: `LP-Phase 4: Confirmed [${userSelection.execution_method} | CR:${userSelection.code_review_tool} | CVR:${userSelection.convergence_review_tool}]`, status: "completed" },
   { content: `LP-Phase 5: Handoff → lite-execute`, status: "completed" },
   { content: `LE-Phase 1: Task Loading [${taskCount} tasks]`, status: "in_progress", activeForm: "Loading tasks" }
 ]})
@@ -605,6 +563,7 @@ Skill("lite-execute")
 ├── explorations-manifest.json        # Exploration index
 ├── planning-context.md               # Evidence paths + understanding
 ├── plan.json                         # Plan overview (task_ids[])
+├── code-review.md                    # Generated by lite-execute Step 4
 ├── test-checklist.json               # Generated by lite-test-review
 ├── test-review.md                    # Generated by lite-test-review
 └── .task/
@@ -618,9 +577,12 @@ Skill("lite-execute")
 ```
 lite-plan (LP-Phase 1-5)
   └─ Skill("lite-execute")     ← executionContext (global)
-       ├─ Step 1-4: Execute + Review
+       ├─ Step 1-3: Task Execution
+       ├─ Step 4: Code Review (quality/correctness/security)
        └─ Step 5: Skill("lite-test-review")  ← testReviewContext (global)
-            ├─ TR-Phase 1-4: Test + Fix
+            ├─ TR-Phase 1: Detect test framework
+            ├─ TR-Phase 2: Convergence verification (plan criteria)
+            ├─ TR-Phase 3-4: Run tests + Auto-fix
             └─ TR-Phase 5: Report + Sync specs
 ```
 
@@ -629,7 +591,7 @@ lite-plan (LP-Phase 1-5)
 | Error | Resolution |
 |-------|------------|
 | Exploration agent failure | Skip exploration, continue with task description only |
-| Planning agent failure | Fallback to direct planning by Claude |
+| Planning agent failure | Retry with reduced complexity or suggest breaking task |
 | Clarification timeout | Use exploration findings as-is |
 | Confirmation timeout | Save context, display resume instructions |
 | Modify loop > 3 times | Suggest breaking task or using /workflow-plan |
@@ -649,7 +611,7 @@ Auto mode authorizes the complete plan-and-execute workflow with a single confir
 - [ ] Parallel exploration agents launched with run_in_background=false
 - [ ] Explorations manifest built from auto-discovered files
 - [ ] Clarification needs aggregated, deduped, and presented in batches of 4
-- [ ] Plan generated via direct Claude (Low) or cli-lite-planning-agent (Medium/High)
+- [ ] Plan generated via cli-lite-planning-agent
 - [ ] Plan output as two-layer: plan.json (task_ids[]) + .task/TASK-*.json
 - [ ] User confirmation collected (or auto-approved in auto mode)
 - [ ] executionContext fully built with all artifacts and session references

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
@@ -29,31 +31,31 @@ Test review and fix engine for lite-execute chain or standalone invocation.
 
 **Input Source**: `testReviewContext` global variable set by lite-execute Step 4
 
-**Behavior**: Skip session discovery, inherit reviewTool from execution chain, proceed directly to TR-Phase 1.
+**Behavior**: Skip session discovery, inherit convergenceReviewTool from execution chain, proceed directly to TR-Phase 1.
 
-> **Note**: lite-execute Step 4 is the chain gate. Mode 1 invocation means execution is complete — proceed with test review.
+> **Note**: lite-execute Step 5 is the chain gate. Mode 1 invocation means execution + code review are complete — proceed with convergence verification + tests.
 
 ### Mode 2: Standalone
 
 **Trigger**: User calls with session path or `--last`
 
-**Behavior**: Discover session → load plan + tasks → `reviewTool = 'agent'` → proceed to TR-Phase 1.
+**Behavior**: Discover session → load plan + tasks → `convergenceReviewTool = 'agent'` → proceed to TR-Phase 1.
 
 ```javascript
-let sessionPath, plan, taskFiles, reviewTool
+let sessionPath, plan, taskFiles, convergenceReviewTool
 
 if (testReviewContext) {
   // Mode 1: from lite-execute chain
   sessionPath = testReviewContext.session.folder
   plan = testReviewContext.planObject
   taskFiles = testReviewContext.taskFiles.map(tf => JSON.parse(Read(tf.path)))
-  reviewTool = testReviewContext.reviewTool || 'agent'
+  convergenceReviewTool = testReviewContext.convergenceReviewTool || 'agent'
 } else {
   // Mode 2: standalone — find last session or use provided path
   sessionPath = resolveSessionPath($ARGUMENTS)  // Glob('.workflow/.lite-plan/*/plan.json'), take last
   plan = JSON.parse(Read(`${sessionPath}/plan.json`))
   taskFiles = plan.task_ids.map(id => JSON.parse(Read(`${sessionPath}/.task/${id}.json`)))
-  reviewTool = 'agent'
+  convergenceReviewTool = 'agent'
 }
 
 const skipFix = $ARGUMENTS?.includes('--skip-fix') || false
@@ -64,7 +66,7 @@ const skipFix = $ARGUMENTS?.includes('--skip-fix') || false
 | Phase | Core Action | Output |
 |-------|-------------|--------|
 | TR-Phase 1 | Detect test framework + gather changes | testConfig, changedFiles |
-| TR-Phase 2 | Review implementation against convergence criteria | reviewResults[] |
+| TR-Phase 2 | Convergence verification against plan criteria | reviewResults[] |
 | TR-Phase 3 | Run tests + generate checklist | test-checklist.json |
 | TR-Phase 4 | Auto-fix failures (iterative, max 3 rounds) | Fixed code + updated checklist |
 | TR-Phase 5 | Output report + chain to session:sync | test-review.md |
@@ -91,32 +93,45 @@ Output: `testConfig = { command, framework, type }` + `changedFiles[]`
 
 // TodoWrite: Phase 1 → completed, Phase 2 → in_progress
 
-## TR-Phase 2: Review Implementation Against Plan
+## TR-Phase 2: Convergence Verification
 
-**Skip if**: `reviewTool === 'skip'`  — set all tasks to PASS, proceed to Phase 3.
+**Skip if**: `convergenceReviewTool === 'skip'`  — set all tasks to PASS, proceed to Phase 3.
 
-For each task, verify convergence criteria and identify test gaps.
+Verify each task's convergence criteria are met in the implementation and identify test gaps.
 
-**Agent Review** (reviewTool === 'agent', default):
+**Agent Convergence Review** (convergenceReviewTool === 'agent', default):
 
 For each task in taskFiles:
-1. Extract `convergence.criteria[]` and `test` requirements
-2. Find changed files matching `task.files[].path` against `changedFiles`
-3. Read matched files, evaluate each criterion against implementation
-4. Check test coverage: if `task.test.unit` exists but no test files in changedFiles → mark as test gap
-5. Same for `task.test.integration`
-6. Build `reviewResult = { taskId, title, criteria_met[], criteria_unmet[], test_gaps[], files_reviewed[] }`
+1. Extract `convergence.criteria[]` from the task
+2. Match `task.files[].path` against `changedFiles` to find actually-changed files
+3. Read each matched file, verify each convergence criterion with file:line evidence
+4. Check test coverage gaps:
+   - If `task.test.unit` defined but no matching test files in changedFiles → mark as test gap
+   - If `task.test.integration` defined but no integration test in changedFiles → mark as test gap
+5. Build `reviewResult = { taskId, title, criteria_met[], criteria_unmet[], test_gaps[], files_reviewed[] }`
+
+**Verdict logic**:
+- PASS = all `convergence.criteria` met + no test gaps
+- PARTIAL = some criteria met OR has test gaps
+- FAIL = no criteria met
 
-**CLI Review** (reviewTool === 'gemini' or 'codex'):
+**CLI Convergence Review** (convergenceReviewTool === 'gemini' or 'codex'):
 
 ```javascript
-const reviewId = `${sessionId}-tr-review`
-Bash(`ccw cli -p "PURPOSE: Post-execution test review — verify convergence criteria met and identify test gaps
-TASK: • Read plan.json and .task/*.json convergence criteria • For each criterion, check implementation in changed files • Identify missing unit/integration tests • List unmet criteria with file:line evidence
+const reviewId = `${sessionId}-convergence`
+const taskCriteria = taskFiles.map(t => `${t.id}: [${(t.convergence?.criteria || []).join(' | ')}]`).join('\n')
+Bash(`ccw cli -p "PURPOSE: Convergence verification — check each task's completion criteria against actual implementation
+TASK: • For each task below, verify every convergence criterion is satisfied in the changed files • Mark each criterion as MET (with file:line evidence) or UNMET (with what's missing) • Identify test coverage gaps (planned tests not found in changes)
+
+TASK CRITERIA:
+${taskCriteria}
+
+CHANGED FILES: ${changedFiles.join(', ')}
+
 MODE: analysis
-CONTEXT: @${sessionPath}/plan.json @${sessionPath}/.task/*.json @**/* | Memory: lite-execute completed, reviewing convergence
-EXPECTED: Per-task verdict table (PASS/PARTIAL/FAIL) + unmet criteria list + test gap list
-CONSTRAINTS: Read-only | Focus on convergence verification" --tool ${reviewTool} --mode analysis --id ${reviewId}`, { run_in_background: true })
+CONTEXT: @${sessionPath}/plan.json @${sessionPath}/.task/*.json @**/* | Memory: lite-execute completed
+EXPECTED: Per-task verdict (PASS/PARTIAL/FAIL) with per-criterion evidence + test gap list
+CONSTRAINTS: Read-only | Focus strictly on convergence criteria verification, NOT code quality (code review already done in lite-execute)" --tool ${convergenceReviewTool} --mode analysis --id ${reviewId}`, { run_in_background: true })
 // STOP - wait for hook callback, then parse CLI output into reviewResults format
 ```
 
@@ -205,13 +220,13 @@ Skill({ skill: "workflow:session:sync", args: `-y "Test review: ${testChecklist.
 
 ## Data Structures
 
-### testReviewContext (Input - Mode 1, set by lite-execute)
+### testReviewContext (Input - Mode 1, set by lite-execute Step 5)
 
 ```javascript
 {
   planObject: { /* same as executionContext.planObject */ },
   taskFiles: [{ id: string, path: string }],
-  reviewTool: "skip" | "agent" | "gemini" | "codex",
+  convergenceReviewTool: "skip" | "agent" | "gemini" | "codex",
   executionResults: [...],
   originalUserInput: string,
   session: {

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}

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 |