claude-code-workflow 7.2.15 → 7.2.16

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

@@ -0,0 +1,208 @@
+---
+role: analyzer
+prefix: ANALYZE
+inner_loop: false
+message_types:
+  success: rca_ready
+  iteration: need_more_evidence
+  error: error
+---
+
+# Analyzer
+
+Root cause analysis from debug evidence.
+
+## Identity
+- Tag: [analyzer] | Prefix: ANALYZE-*
+- Responsibility: Analyze evidence artifacts, identify root cause, produce RCA report
+
+## Boundaries
+### MUST
+- Load ALL evidence from reproducer before analysis
+- Correlate findings across multiple evidence types
+- Identify specific file:line location when possible
+- Request supplemental evidence if analysis is inconclusive
+- Produce structured RCA report
+### MUST NOT
+- Modify source code or project files
+- Skip loading upstream evidence
+- Guess root cause without evidence support
+- Proceed with low-confidence RCA (request more evidence instead)
+
+## Phase 2: Load Evidence
+
+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)
+   - Read DOM snapshots (structural analysis)
+   - Parse console error messages
+   - Parse network request logs
+   - Read performance trace if available
+5. Load wisdom/ for any prior debug knowledge
+
+## Phase 3: Root Cause Analysis
+
+### Step 3.1: Console Error Analysis
+
+Priority analysis — most bugs have console evidence:
+
+1. Filter console messages by type: error > warn > log
+2. For each error:
+   - Extract error message and stack trace
+   - Identify source file and line number from stack
+   - Classify: TypeError, ReferenceError, SyntaxError, NetworkError, CustomError
+3. Map errors to reproduction steps (correlation by timing)
+
+### Step 3.2: Network Analysis
+
+If network evidence collected:
+
+1. Identify failed requests (4xx, 5xx, timeout, CORS)
+2. For each failed request:
+   - Request URL, method, headers
+   - Response status, body (if captured)
+   - Timing information
+3. Check for:
+   - Missing authentication tokens
+   - Incorrect API endpoints
+   - CORS policy violations
+   - Request/response payload issues
+
+### Step 3.3: DOM Structure Analysis
+
+If snapshots collected:
+
+1. Compare before/after snapshots
+2. Identify:
+   - Missing or extra elements
+   - Incorrect attributes or content
+   - Accessibility tree anomalies
+   - State-dependent rendering issues
+
+### Step 3.4: Performance Analysis
+
+If performance trace collected:
+
+1. Identify long tasks (>50ms)
+2. Check for:
+   - JavaScript execution bottlenecks
+   - Layout thrashing
+   - Excessive re-renders
+   - Memory leaks (growing heap)
+   - Large resource loads
+
+### Step 3.5: Cross-Correlation
+
+Combine findings from all dimensions:
+
+1. Build timeline of events leading to bug
+2. Identify the earliest trigger point
+3. Trace from trigger to visible symptom
+4. Determine if issue is:
+   - Frontend code bug (logic error, missing null check, etc.)
+   - Backend/API issue (wrong data, missing endpoint)
+   - Configuration issue (env vars, build config)
+   - Race condition / timing issue
+
+### Step 3.6: Source Code Mapping
+
+Use codebase search to locate root cause:
+
+```
+mcp__ace-tool__search_context({
+  project_root_path: "<project-root>",
+  query: "<error message or function name from stack trace>"
+})
+```
+
+Read identified source files to confirm root cause location.
+
+### Step 3.7: Confidence Assessment
+
+| Confidence | Criteria | Action |
+|------------|----------|--------|
+| High (>80%) | Stack trace points to specific line + error is clear | Proceed with RCA |
+| Medium (50-80%) | Likely cause identified but needs confirmation | Proceed with caveats |
+| Low (<50%) | Multiple possible causes, insufficient evidence | Request more evidence |
+
+If Low confidence: send `need_more_evidence` message with specific requests.
+
+## Phase 4: RCA Report
+
+Write `<session>/artifacts/ANALYZE-001-rca.md`:
+
+```markdown
+# Root Cause Analysis Report
+
+## Bug Summary
+- **Description**: <bug description>
+- **URL**: <target url>
+- **Reproduction**: <success/partial/failed>
+
+## Root Cause
+- **Category**: <JS Error | Network | Rendering | Performance | State>
+- **Confidence**: <High | Medium | Low>
+- **Source File**: <file path>
+- **Source Line**: <line number>
+- **Root Cause**: <detailed explanation>
+
+## Evidence Chain
+1. <evidence 1 -> finding>
+2. <evidence 2 -> finding>
+3. <correlation -> root cause>
+
+## Fix Recommendation
+- **Approach**: <description of recommended fix>
+- **Files to modify**: <list>
+- **Risk level**: <Low | Medium | High>
+- **Estimated scope**: <lines of code / number of files>
+
+## Additional Observations
+- <any related issues found>
+- <potential regression risks>
+```
+
+Send state_update:
+```json
+{
+  "status": "task_complete",
+  "task_id": "ANALYZE-001",
+  "ref": "<session>/artifacts/ANALYZE-001-rca.md",
+  "key_findings": ["Root cause: <summary>", "Location: <file:line>"],
+  "decisions": ["Recommended fix: <approach>"],
+  "verification": "self-validated"
+}
+```
+
+## Iteration Protocol
+
+When evidence is insufficient (confidence < 50%):
+
+1. Send state_update with `need_more_evidence: true`:
+   ```json
+   {
+     "status": "need_more_evidence",
+     "task_id": "ANALYZE-001",
+     "ref": null,
+     "key_findings": ["Partial analysis: <what we know>"],
+     "decisions": [],
+     "evidence_request": {
+       "dimensions": ["network_detail", "state_inspection"],
+       "specific_actions": ["Capture request body for /api/users", "Evaluate React state after click"]
+     }
+   }
+   ```
+2. Coordinator creates REPRODUCE-002 + ANALYZE-002
+3. ANALYZE-002 loads both original and supplemental evidence
+
+## Error Handling
+
+| Scenario | Resolution |
+|----------|------------|
+| Evidence files missing | Report with available data, note gaps |
+| No clear root cause | Request supplemental evidence via iteration |
+| Multiple possible causes | Rank by likelihood, report top 3 |
+| Source code not found | Report with best available location info |

package/.codex/skills/team-frontend-debug/roles/coordinator/commands/analyze.md

@@ -0,0 +1,174 @@
+# Analyze Input
+
+Parse user input -> detect mode (feature-test vs bug-report) -> build dependency graph -> assign roles.
+
+**CONSTRAINT**: Text-level analysis only. NO source code reading, NO codebase exploration.
+
+## Step 1: Detect Input Mode
+
+```
+if input contains: 功能, feature, 清单, list, 测试, test, 完成, done, 验收
+  → mode = "test-pipeline"
+elif input contains: bug, 错误, 报错, crash, 问题, 不工作, 白屏, 异常
+  → mode = "debug-pipeline"
+else
+  → request_user_input to clarify
+```
+
+```
+request_user_input({
+  questions: [{
+    question: "请确认调试模式",
+    header: "Mode",
+    multiSelect: false,
+    options: [
+      { label: "功能测试", description: "根据功能清单逐项测试，发现并修复问题" },
+      { label: "Bug修复", description: "针对已知Bug进行复现、分析和修复" }
+    ]
+  }]
+})
+```
+
+---
+
+## Mode A: Feature Test (test-pipeline)
+
+### Parse Feature List
+
+Extract from user input:
+
+| Field | Source | Required |
+|-------|--------|----------|
+| base_url | URL in text or request_user_input | Yes |
+| features | Feature list (bullet points, numbered list, or free text) | Yes |
+| test_depth | User preference or default "standard" | Auto |
+
+Parse features into structured format:
+```json
+[
+  { "id": "F-001", "name": "用户登录", "url": "/login", "description": "..." },
+  { "id": "F-002", "name": "数据列表", "url": "/dashboard", "description": "..." }
+]
+```
+
+If base_url missing:
+```
+request_user_input({
+  questions: [{
+    question: "请提供应用的访问地址",
+    header: "Base URL",
+    multiSelect: false,
+    options: [
+      { label: "localhost:3000", description: "本地开发服务器" },
+      { label: "localhost:5173", description: "Vite默认端口" },
+      { label: "Custom", description: "自定义URL" }
+    ]
+  }]
+})
+```
+
+### Complexity Scoring (Test Mode)
+
+| Factor | Points |
+|--------|--------|
+| Per feature | +1 |
+| Features > 5 | +2 |
+| Features > 10 | +3 |
+| Cross-page workflows | +1 |
+
+Results: 1-3 Low, 4-6 Medium, 7+ High
+
+### Output (Test Mode)
+
+```json
+{
+  "mode": "test-pipeline",
+  "base_url": "<url>",
+  "features": [
+    { "id": "F-001", "name": "<name>", "url": "<path>", "description": "<desc>" }
+  ],
+  "pipeline_type": "test-pipeline",
+  "dependency_graph": {
+    "TEST-001": { "role": "tester", "blockedBy": [], "priority": "P0" },
+    "ANALYZE-001": { "role": "analyzer", "blockedBy": ["TEST-001"], "priority": "P0", "conditional": true },
+    "FIX-001": { "role": "fixer", "blockedBy": ["ANALYZE-001"], "priority": "P0", "conditional": true },
+    "VERIFY-001": { "role": "verifier", "blockedBy": ["FIX-001"], "priority": "P0", "conditional": true }
+  },
+  "roles": [
+    { "name": "tester", "prefix": "TEST", "inner_loop": true },
+    { "name": "analyzer", "prefix": "ANALYZE", "inner_loop": false },
+    { "name": "fixer", "prefix": "FIX", "inner_loop": true },
+    { "name": "verifier", "prefix": "VERIFY", "inner_loop": false }
+  ],
+  "complexity": { "score": 0, "level": "Low|Medium|High" }
+}
+```
+
+---
+
+## Mode B: Bug Report (debug-pipeline)
+
+### Parse Bug Report
+
+Extract from user input:
+
+| Field | Source | Required |
+|-------|--------|----------|
+| bug_description | User text | Yes |
+| target_url | URL in text or request_user_input | Yes |
+| reproduction_steps | Steps in text or request_user_input | Yes |
+| expected_behavior | User description | Recommended |
+| actual_behavior | User description | Recommended |
+| severity | User indication or auto-assess | Auto |
+
+### Debug Dimension Detection
+
+| Keywords | Dimension | Evidence Needed |
+|----------|-----------|-----------------|
+| 渲染, 样式, 显示, 布局, CSS | UI/Rendering | screenshot, snapshot |
+| 请求, API, 接口, 网络, 超时 | Network | network_requests |
+| 错误, 报错, 异常, crash | JavaScript Error | console_messages |
+| 慢, 卡顿, 性能, 加载 | Performance | performance_trace |
+| 状态, 数据, 更新, 不同步 | State Management | console + snapshot |
+| 交互, 点击, 输入, 表单 | User Interaction | click/fill + screenshot |
+
+### Complexity Scoring (Debug Mode)
+
+| Factor | Points |
+|--------|--------|
+| Single dimension (e.g., JS error only) | 1 |
+| Multi-dimension (UI + Network) | +1 per extra |
+| Intermittent / hard to reproduce | +2 |
+| Performance profiling needed | +1 |
+
+Results: 1-2 Low, 3-4 Medium, 5+ High
+
+### Output (Debug Mode)
+
+```json
+{
+  "mode": "debug-pipeline",
+  "bug_description": "<original>",
+  "target_url": "<url>",
+  "reproduction_steps": ["step 1", "step 2"],
+  "dimensions": ["ui_rendering", "javascript_error"],
+  "evidence_plan": {
+    "screenshot": true, "snapshot": true,
+    "console": true, "network": true, "performance": false
+  },
+  "pipeline_type": "debug-pipeline",
+  "dependency_graph": {
+    "REPRODUCE-001": { "role": "reproducer", "blockedBy": [], "priority": "P0" },
+    "ANALYZE-001": { "role": "analyzer", "blockedBy": ["REPRODUCE-001"], "priority": "P0" },
+    "FIX-001": { "role": "fixer", "blockedBy": ["ANALYZE-001"], "priority": "P0" },
+    "VERIFY-001": { "role": "verifier", "blockedBy": ["FIX-001"], "priority": "P0" }
+  },
+  "roles": [
+    { "name": "reproducer", "prefix": "REPRODUCE", "inner_loop": false },
+    { "name": "analyzer", "prefix": "ANALYZE", "inner_loop": false },
+    { "name": "fixer", "prefix": "FIX", "inner_loop": true },
+    { "name": "verifier", "prefix": "VERIFY", "inner_loop": false }
+  ],
+  "complexity": { "score": 0, "level": "Low|Medium|High" }
+}
+```

package/.codex/skills/team-frontend-debug/roles/coordinator/commands/dispatch.md

@@ -0,0 +1,198 @@
+# Dispatch Debug Tasks
+
+Create task chains from dependency graph with proper blockedBy relationships.
+
+## Workflow
+
+1. Read task-analysis.json -> extract pipeline_type and dependency_graph
+2. Read specs/pipelines.md -> get task registry for selected pipeline
+3. Topological sort tasks (respect blockedBy)
+4. Validate all owners exist in role registry (SKILL.md)
+5. For each task (in order):
+   - Build JSON entry with structured description (see template below)
+   - Set blockedBy and owner fields in the entry
+6. Write all entries to `<session>/tasks.json`
+7. Update team-session.json with pipeline.tasks_total
+8. Validate chain (no orphans, no cycles, all refs valid)
+
+## Task Description Template
+
+Each task is a JSON entry in the tasks array:
+
+```json
+{
+  "id": "<TASK-ID>",
+  "subject": "<TASK-ID>",
+  "description": "PURPOSE: <goal> | Success: <criteria>\nTASK:\n  - <step 1>\n  - <step 2>\nCONTEXT:\n  - Session: <session-folder>\n  - Base URL / Bug URL: <url>\n  - Upstream artifacts: <list>\nEXPECTED: <artifact path> + <quality criteria>\nCONSTRAINTS: <scope limits>\n---\nInnerLoop: <true|false>\nRoleSpec: ~  or <project>/.codex/skills/team-frontend-debug/roles/<role>/role.md",
+  "status": "pending",
+  "owner": "<role>",
+  "blockedBy": ["<dependency-list>"]
+}
+```
+
+---
+
+## Test Pipeline Tasks (mode: test-pipeline)
+
+### TEST-001: Feature Testing
+
+```json
+{
+  "id": "TEST-001",
+  "subject": "TEST-001",
+  "description": "PURPOSE: Test all features from feature list and discover issues | Success: All features tested with pass/fail results\nTASK:\n  - Parse feature list from task description\n  - For each feature: navigate to URL, explore page, generate test scenarios\n  - Execute test scenarios using Chrome DevTools MCP (click, fill, hover, etc.)\n  - Capture evidence: screenshots, console logs, network requests\n  - Classify results: pass / fail / warning\n  - Compile test report with discovered issues\nCONTEXT:\n  - Session: <session-folder>\n  - Base URL: <base-url>\n  - Features: <feature-list-from-task-analysis>\nEXPECTED: <session>/artifacts/TEST-001-report.md + <session>/artifacts/TEST-001-issues.json\nCONSTRAINTS: Use Chrome DevTools MCP only | Do not modify any code | Test all listed features\n---\nInnerLoop: true\nRoleSpec: ~  or <project>/.codex/skills/team-frontend-debug/roles/tester/role.md",
+  "status": "pending",
+  "owner": "tester",
+  "blockedBy": []
+}
+```
+
+### ANALYZE-001 (Test Mode): Analyze Discovered Issues
+
+```json
+{
+  "id": "ANALYZE-001",
+  "subject": "ANALYZE-001",
+  "description": "PURPOSE: Analyze issues discovered by tester to identify root causes | Success: RCA for each discovered issue\nTASK:\n  - Load test report and issues list from TEST-001\n  - For each high/medium severity issue: analyze evidence, identify root cause\n  - Correlate console errors, network failures, DOM anomalies to source code\n  - Produce consolidated RCA report covering all issues\nCONTEXT:\n  - Session: <session-folder>\n  - Upstream: <session>/artifacts/TEST-001-issues.json\n  - Test evidence: <session>/evidence/\nEXPECTED: <session>/artifacts/ANALYZE-001-rca.md with root causes for all issues\nCONSTRAINTS: Read-only analysis | Skip low-severity warnings unless user requests\n---\nInnerLoop: false\nRoleSpec: ~  or <project>/.codex/skills/team-frontend-debug/roles/analyzer/role.md",
+  "status": "pending",
+  "owner": "analyzer",
+  "blockedBy": ["TEST-001"]
+}
+```
+
+**Conditional**: If TEST-001 reports zero issues -> skip ANALYZE-001, FIX-001, VERIFY-001. Pipeline completes.
+
+### FIX-001 (Test Mode): Fix All Issues
+
+```json
+{
+  "id": "FIX-001",
+  "subject": "FIX-001",
+  "description": "PURPOSE: Fix all identified issues from RCA | Success: All high/medium issues resolved\nTASK:\n  - Load consolidated RCA report from ANALYZE-001\n  - For each root cause: locate code, implement fix\n  - Run syntax/type check after all modifications\n  - Document all changes\nCONTEXT:\n  - Session: <session-folder>\n  - Upstream: <session>/artifacts/ANALYZE-001-rca.md\nEXPECTED: Modified source files + <session>/artifacts/FIX-001-changes.md\nCONSTRAINTS: Minimal changes per issue | Follow existing code style\n---\nInnerLoop: true\nRoleSpec: ~  or <project>/.codex/skills/team-frontend-debug/roles/fixer/role.md",
+  "status": "pending",
+  "owner": "fixer",
+  "blockedBy": ["ANALYZE-001"]
+}
+```
+
+### VERIFY-001 (Test Mode): Re-Test After Fix
+
+```json
+{
+  "id": "VERIFY-001",
+  "subject": "VERIFY-001",
+  "description": "PURPOSE: Re-run failed test scenarios to verify fixes | Success: Previously failed scenarios now pass\nTASK:\n  - Load original test report (failed scenarios only)\n  - Re-execute failed scenarios using Chrome DevTools MCP\n  - Capture evidence and compare with original\n  - Report pass/fail per scenario\nCONTEXT:\n  - Session: <session-folder>\n  - Original test report: <session>/artifacts/TEST-001-report.md\n  - Fix changes: <session>/artifacts/FIX-001-changes.md\n  - Failed features: <from TEST-001-issues.json>\nEXPECTED: <session>/artifacts/VERIFY-001-report.md with pass/fail per previously-failed scenario\nCONSTRAINTS: Only re-test failed scenarios | Use Chrome DevTools MCP only\n---\nInnerLoop: false\nRoleSpec: ~  or <project>/.codex/skills/team-frontend-debug/roles/verifier/role.md",
+  "status": "pending",
+  "owner": "verifier",
+  "blockedBy": ["FIX-001"]
+}
+```
+
+---
+
+## Debug Pipeline Tasks (mode: debug-pipeline)
+
+### REPRODUCE-001: Evidence Collection
+
+```json
+{
+  "id": "REPRODUCE-001",
+  "subject": "REPRODUCE-001",
+  "description": "PURPOSE: Reproduce reported bug and collect debug evidence | Success: Bug reproduced with evidence artifacts\nTASK:\n  - Navigate to target URL\n  - Execute reproduction steps using Chrome DevTools MCP\n  - Capture evidence: screenshots, DOM snapshots, console logs, network requests\n  - If performance dimension: run performance trace\n  - Package all evidence into session evidence/ directory\nCONTEXT:\n  - Session: <session-folder>\n  - Bug URL: <target-url>\n  - Steps: <reproduction-steps>\n  - Evidence plan: <from task-analysis.json>\nEXPECTED: <session>/evidence/ directory with all captures + reproduction report\nCONSTRAINTS: Use Chrome DevTools MCP only | Do not modify any code\n---\nInnerLoop: false\nRoleSpec: ~  or <project>/.codex/skills/team-frontend-debug/roles/reproducer/role.md",
+  "status": "pending",
+  "owner": "reproducer",
+  "blockedBy": []
+}
+```
+
+### ANALYZE-001 (Debug Mode): Root Cause Analysis
+
+```json
+{
+  "id": "ANALYZE-001",
+  "subject": "ANALYZE-001",
+  "description": "PURPOSE: Analyze evidence to identify root cause | Success: RCA report with specific file:line location\nTASK:\n  - Load evidence from REPRODUCE-001\n  - Analyze console errors and stack traces\n  - Analyze failed/abnormal network requests\n  - Compare DOM snapshot against expected structure\n  - Correlate findings to source code location\nCONTEXT:\n  - Session: <session-folder>\n  - Upstream: <session>/evidence/\n  - Bug description: <bug-description>\nEXPECTED: <session>/artifacts/ANALYZE-001-rca.md with root cause, file:line, fix recommendation\nCONSTRAINTS: Read-only analysis | Request more evidence if inconclusive\n---\nInnerLoop: false\nRoleSpec: ~  or <project>/.codex/skills/team-frontend-debug/roles/analyzer/role.md",
+  "status": "pending",
+  "owner": "analyzer",
+  "blockedBy": ["REPRODUCE-001"]
+}
+```
+
+### FIX-001 (Debug Mode): Code Fix
+
+```json
+{
+  "id": "FIX-001",
+  "subject": "FIX-001",
+  "description": "PURPOSE: Fix the identified bug | Success: Code changes that resolve the root cause\nTASK:\n  - Load RCA report from ANALYZE-001\n  - Locate the problematic code\n  - Implement fix following existing code patterns\n  - Run syntax/type check on modified files\nCONTEXT:\n  - Session: <session-folder>\n  - Upstream: <session>/artifacts/ANALYZE-001-rca.md\nEXPECTED: Modified source files + <session>/artifacts/FIX-001-changes.md\nCONSTRAINTS: Minimal changes | Follow existing code style | No breaking changes\n---\nInnerLoop: true\nRoleSpec: ~  or <project>/.codex/skills/team-frontend-debug/roles/fixer/role.md",
+  "status": "pending",
+  "owner": "fixer",
+  "blockedBy": ["ANALYZE-001"]
+}
+```
+
+### VERIFY-001 (Debug Mode): Fix Verification
+
+```json
+{
+  "id": "VERIFY-001",
+  "subject": "VERIFY-001",
+  "description": "PURPOSE: Verify bug is fixed | Success: Original bug no longer reproduces\nTASK:\n  - Navigate to same URL as REPRODUCE-001\n  - Execute same reproduction steps\n  - Capture evidence and compare with original\n  - Confirm bug is resolved and no regressions\nCONTEXT:\n  - Session: <session-folder>\n  - Original evidence: <session>/evidence/\n  - Fix changes: <session>/artifacts/FIX-001-changes.md\nEXPECTED: <session>/artifacts/VERIFY-001-report.md with pass/fail verdict\nCONSTRAINTS: Use Chrome DevTools MCP only | Same steps as reproduction\n---\nInnerLoop: false\nRoleSpec: ~  or <project>/.codex/skills/team-frontend-debug/roles/verifier/role.md",
+  "status": "pending",
+  "owner": "verifier",
+  "blockedBy": ["FIX-001"]
+}
+```
+
+---
+
+## Dynamic Iteration Tasks
+
+### REPRODUCE-002 (Debug Mode): Supplemental Evidence
+
+Created when Analyzer requests more evidence -- add new entry to `<session>/tasks.json`:
+```json
+{
+  "id": "REPRODUCE-002",
+  "subject": "REPRODUCE-002",
+  "description": "PURPOSE: Collect additional evidence per Analyzer request | Success: Targeted evidence collected\nTASK: <specific evidence requests from Analyzer>\nCONTEXT: Session + Analyzer request\n---\nInnerLoop: false\nRoleSpec: ~  or <project>/.codex/skills/team-frontend-debug/roles/reproducer/role.md",
+  "status": "pending",
+  "owner": "reproducer",
+  "blockedBy": []
+}
+```
+
+### FIX-002 (Either Mode): Re-Fix After Failed Verification
+
+Created when Verifier reports fail -- add new entry to `<session>/tasks.json`:
+```json
+{
+  "id": "FIX-002",
+  "subject": "FIX-002",
+  "description": "PURPOSE: Re-fix based on verification failure feedback | Success: Issue resolved\nTASK: Review VERIFY-001 failure details, apply corrective fix\nCONTEXT: Session + VERIFY-001-report.md\n---\nInnerLoop: true\nRoleSpec: ~  or <project>/.codex/skills/team-frontend-debug/roles/fixer/role.md",
+  "status": "pending",
+  "owner": "fixer",
+  "blockedBy": ["VERIFY-001"]
+}
+```
+
+## Conditional Skip Rules
+
+| Condition | Action |
+|-----------|--------|
+| test-pipeline + TEST-001 finds 0 issues | Skip ANALYZE/FIX/VERIFY -> pipeline complete |
+| test-pipeline + TEST-001 finds only warnings | request_user_input: fix warnings or complete |
+| debug-pipeline + REPRODUCE-001 cannot reproduce | request_user_input: retry with more info or abort |
+
+## InnerLoop Flag Rules
+
+- true: tester (iterates over features), fixer (may need multiple fix passes)
+- false: reproducer, analyzer, verifier (single-pass tasks)
+
+## Dependency Validation
+
+- No orphan tasks (all tasks have valid owner)
+- No circular dependencies
+- All blockedBy references exist
+- Session reference in every task description
+- RoleSpec reference in every task description