maestro-flow 0.5.31 → 0.5.33

package/.claude/skills/team-frontend/specs/team-config.json

@@ -0,0 +1,84 @@
+{
+  "team_name": "frontend",
+  "skill_name": "team-frontend",
+  "team_display_name": "Frontend Development",
+  "description": "全栈前端开发团队，内置 ui-ux-pro-max 设计智能。具备需求分析、设计系统生成、前端实现、质量保证的完整能力。",
+  "pipeline_type": "adaptive",
+  "roles": [
+    {
+      "name": "coordinator",
+      "task_prefix": null,
+      "responsibility_type": "Orchestration",
+      "description": "需求澄清、行业识别、流水线编排、进度监控、GC循环控制",
+      "message_types": ["task_unblocked", "sync_checkpoint", "fix_required", "error", "shutdown"]
+    },
+    {
+      "name": "analyst",
+      "task_prefix": "ANALYZE",
+      "responsibility_type": "Read-only analysis",
+      "description": "需求分析、调用 ui-ux-pro-max 获取设计智能、行业推理规则匹配",
+      "message_types": ["analyze_ready", "analyze_progress", "error"]
+    },
+    {
+      "name": "architect",
+      "task_prefix": "ARCH",
+      "responsibility_type": "Code generation",
+      "description": "消费设计智能、定义设计令牌系统、组件架构、技术选型",
+      "message_types": ["arch_ready", "arch_revision", "arch_progress", "error"]
+    },
+    {
+      "name": "developer",
+      "task_prefix": "DEV",
+      "responsibility_type": "Code generation",
+      "description": "消费架构产出、实现前端组件/页面代码",
+      "message_types": ["dev_complete", "dev_progress", "error"]
+    },
+    {
+      "name": "qa",
+      "task_prefix": "QA",
+      "responsibility_type": "Read-only analysis",
+      "description": "5维度代码审查：代码质量、可访问性、设计合规、UX最佳实践、Pre-Delivery验证",
+      "message_types": ["qa_passed", "qa_result", "fix_required", "error"]
+    }
+  ],
+  "pipelines": {
+    "page": {
+      "description": "单页面开发：分析→架构→开发→质检",
+      "task_chain": ["ANALYZE-001", "ARCH-001", "DEV-001", "QA-001"],
+      "collaboration_patterns": ["CP-1", "CP-2"],
+      "complexity": "low"
+    },
+    "feature": {
+      "description": "多组件特性：分析→架构→质检→开发→质检",
+      "task_chain": ["ANALYZE-001", "ARCH-001", "QA-001", "DEV-001", "QA-002"],
+      "collaboration_patterns": ["CP-1", "CP-2", "CP-8"],
+      "complexity": "medium"
+    },
+    "system": {
+      "description": "完整前端系统：分析→架构→[开发令牌 ∥ 架构组件]→质检→开发组件→最终质检",
+      "task_chain": ["ANALYZE-001", "ARCH-001", "QA-001", "ARCH-002||DEV-001", "QA-002", "DEV-002", "QA-003"],
+      "sync_points": ["QA-001", "QA-002"],
+      "collaboration_patterns": ["CP-1", "CP-2", "CP-8", "CP-9"],
+      "complexity": "high"
+    }
+  },
+  "uipro_config": {
+    "search_paths": [
+      "G:/github_lib/ui-ux-pro-max-skill/src/ui-ux-pro-max",
+      "../ui-ux-pro-max-skill/src/ui-ux-pro-max",
+      "./ui-ux-pro-max"
+    ],
+    "fallback": "LLM general design knowledge",
+    "data_domains": ["product", "style", "typography", "color", "landing", "chart", "ux", "web"],
+    "supported_stacks": ["html-tailwind", "react", "nextjs", "vue", "svelte", "shadcn"]
+  },
+  "shared_memory_schema": {
+    "design_intelligence": {},
+    "design_token_registry": {},
+    "component_inventory": [],
+    "style_decisions": [],
+    "qa_history": [],
+    "industry_context": {}
+  },
+  "generated_at": "2026-02-17T00:00:00+08:00"
+}

package/.claude/skills/team-frontend-debug/SKILL.md

@@ -0,0 +1,198 @@
+---
+name: team-frontend-debug
+description: Frontend debugging team using Chrome DevTools MCP. Dual-mode — feature-list testing or bug-report debugging. Triggers on "team-frontend-debug", "frontend debug".
+allowed-tools: TeamCreate(*), TeamDelete(*), SendMessage(*), TaskCreate(*), TaskUpdate(*), TaskList(*), TaskGet(*), Agent(*), AskUserQuestion(*), Read(*), Write(*), Edit(*), Bash(*), Glob(*), Grep(*), mcp__maestro__team_msg(*), mcp__chrome-devtools__*(*)
+---
+
+# Frontend Debug Team
+
+Dual-mode frontend debugging: feature-list testing or bug-report debugging, powered by Chrome DevTools MCP.
+
+## Architecture
+
+```
+Skill(skill="team-frontend-debug", args="feature list or bug description")
+                    |
+         SKILL.md (this file) = Router
+                    |
+     +--------------+--------------+
+     |                             |
+  no --role flag              --role <name>
+     |                             |
+  Coordinator                  Worker
+  roles/coordinator/role.md    roles/<name>/role.md
+     |
+     +-- analyze input → select pipeline → dispatch → spawn → STOP
+                                    |
+         ┌──────────────────────────┼──────────────────────┐
+         v                         v                       v
+    [test-pipeline]          [debug-pipeline]          [shared]
+     tester(DevTools)        reproducer(DevTools)      analyzer
+                                                       fixer
+                                                       verifier
+```
+
+## Pipeline Modes
+
+| Input | Pipeline | Flow |
+|-------|----------|------|
+| Feature list / 功能清单 | `test-pipeline` | TEST → ANALYZE → FIX → VERIFY |
+| Bug report / 错误描述 | `debug-pipeline` | REPRODUCE → ANALYZE → FIX → VERIFY |
+
+## Role Registry
+
+| Role | Path | Prefix | Inner Loop |
+|------|------|--------|------------|
+| coordinator | [roles/coordinator/role.md](roles/coordinator/role.md) | — | — |
+| tester | [roles/tester/role.md](roles/tester/role.md) | TEST-* | true |
+| reproducer | [roles/reproducer/role.md](roles/reproducer/role.md) | REPRODUCE-* | false |
+| analyzer | [roles/analyzer/role.md](roles/analyzer/role.md) | ANALYZE-* | false |
+| fixer | [roles/fixer/role.md](roles/fixer/role.md) | FIX-* | true |
+| verifier | [roles/verifier/role.md](roles/verifier/role.md) | VERIFY-* | false |
+
+
+## Pre-load (coordinator, before dispatch)
+
+1. **Codebase docs**: If `.workflow/codebase/ARCHITECTURE.md` exists, read for module boundaries
+2. **Specs (debug)**: `maestro spec load --category debug` — load debug constraints as shared context
+3. **Specs (ui)**: `maestro spec load --category ui` — load ui constraints as shared context
+4. **Wiki knowledge**: `maestro search "frontend debug devtools" --json` — top 5 entries as prior context
+5. All optional — proceed without if unavailable
+## Role Router
+
+Parse `$ARGUMENTS`:
+- Has `--role <name>` → Read `roles/<name>/role.md`, execute Phase 2-4
+- No `--role` → `@roles/coordinator/role.md`, execute entry router
+
+## Shared Constants
+
+- **Session prefix**: `TFD`
+- **Session path**: `.workflow/.team/TFD-<slug>-<date>/`
+- **CLI tools**: `maestro delegate --mode analysis` (read-only), `maestro delegate --mode write` (modifications)
+- **Message bus**: `mcp__maestro__team_msg(session_id=<session-id>, ...)`
+
+## Workspace Resolution
+
+Coordinator MUST resolve paths at Phase 2 before TeamCreate:
+
+1. Run `Bash({ command: "pwd" })` → capture `project_root` (absolute path)
+2. `skill_root = <project_root>/.claude/skills/team-frontend-debug`
+3. Store in `team-session.json`:
+   ```json
+   { "project_root": "/abs/path/to/project", "skill_root": "/abs/path/to/skill" }
+   ```
+4. All worker `role_spec` values MUST use `<skill_root>/roles/<role>/role.md` (absolute)
+
+This ensures workers spawned with `run_in_background: true` always receive an absolute, resolvable path regardless of their working directory.
+
+## Chrome DevTools MCP Tools
+
+All browser inspection operations use Chrome DevTools MCP. Reproducer and Verifier are primary consumers.
+
+| Tool | Purpose |
+|------|---------|
+| `mcp__chrome-devtools__navigate_page` | Navigate to target URL |
+| `mcp__chrome-devtools__take_screenshot` | Capture visual state |
+| `mcp__chrome-devtools__take_snapshot` | Capture DOM/a11y tree |
+| `mcp__chrome-devtools__list_console_messages` | Read console logs |
+| `mcp__chrome-devtools__get_console_message` | Get specific console message |
+| `mcp__chrome-devtools__list_network_requests` | Monitor network activity |
+| `mcp__chrome-devtools__get_network_request` | Inspect request/response detail |
+| `mcp__chrome-devtools__performance_start_trace` | Start performance recording |
+| `mcp__chrome-devtools__performance_stop_trace` | Stop and analyze trace |
+| `mcp__chrome-devtools__click` | Simulate user click |
+| `mcp__chrome-devtools__fill` | Fill form inputs |
+| `mcp__chrome-devtools__hover` | Hover over elements |
+| `mcp__chrome-devtools__evaluate_script` | Execute JavaScript in page |
+| `mcp__chrome-devtools__wait_for` | Wait for element/text |
+| `mcp__chrome-devtools__list_pages` | List open browser tabs |
+| `mcp__chrome-devtools__select_page` | Switch active tab |
+
+## Worker Spawn Template
+
+Coordinator spawns workers using this template:
+
+```
+Agent({
+  subagent_type: "team-worker",
+  description: "Spawn <role> worker",
+  team_name: <team-name>,
+  name: "<role>",
+  run_in_background: true,
+  prompt: `## Role Assignment
+role: <role>
+role_spec: <skill_root>/roles/<role>/role.md
+session: <session-folder>
+session_id: <session-id>
+team_name: <team-name>
+requirement: <task-description>
+inner_loop: <true|false>
+
+## Progress Milestones
+session_id: <session-id>
+Report progress via team_msg at natural phase boundaries (context loaded -> core work done -> verification).
+Report blockers immediately via team_msg type="blocker".
+Report completion via team_msg type="task_complete" after final SendMessage.
+
+Read role_spec file (@<skill_root>/roles/<role>/role.md) to load Phase 2-4 domain instructions.
+Execute built-in Phase 1 (task discovery) -> role Phase 2-4 -> built-in Phase 5 (report).`
+})
+```
+
+## User Commands
+
+| Command | Action |
+|---------|--------|
+| `check` / `status` | View execution status graph |
+| `resume` / `continue` | Advance to next step |
+| `revise <TASK-ID> [feedback]` | Revise specific task |
+| `feedback <text>` | Inject feedback for revision |
+| `retry <TASK-ID>` | Re-run a failed task |
+
+## Completion Action
+
+When pipeline completes, coordinator presents:
+
+```
+AskUserQuestion({
+  questions: [{
+    question: "Pipeline complete. What would you like to do?",
+    header: "Completion",
+    multiSelect: false,
+    options: [
+      { label: "Archive & Clean (Recommended)", description: "Archive session, clean up team" },
+      { label: "Keep Active", description: "Keep session for follow-up debugging" },
+      { label: "Export Results", description: "Export debug report and patches" }
+    ]
+  }]
+})
+```
+
+## Specs Reference
+
+- [specs/pipelines.md](specs/pipelines.md) — Pipeline definitions and task registry
+- [specs/debug-tools.md](specs/debug-tools.md) — Chrome DevTools MCP usage patterns and evidence collection
+
+## Session Directory
+
+```
+.workflow/.team/TFD-<slug>-<date>/
+├── team-session.json           # Session state + role registry
+├── evidence/                   # Screenshots, snapshots, network logs
+├── artifacts/                  # Test reports, RCA reports, patches, verification reports
+├── wisdom/                     # Cross-task debug knowledge
+└── .msg/                       # Team message bus
+```
+
+## Error Handling
+
+| Scenario | Resolution |
+|----------|------------|
+| All features pass test | Report success, pipeline completes without ANALYZE/FIX/VERIFY |
+| Bug not reproducible | Reproducer reports failure, coordinator asks user for more details |
+| Browser not available | Report error, suggest manual reproduction steps |
+| Analysis inconclusive | Analyzer requests more evidence via iteration loop |
+| Fix introduces regression | Verifier reports fail, coordinator dispatches re-fix |
+| No issues found in test | Skip downstream tasks, report all-pass |
+| Unknown command | Error with available command list |
+| Role not found | Error with role registry |

package/.claude/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:
+
+```
+({
+  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/.claude/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
+  → AskUserQuestion to clarify
+```
+
+```
+AskUserQuestion({
+  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 AskUserQuestion | 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:
+```
+AskUserQuestion({
+  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 AskUserQuestion | Yes |
+| reproduction_steps | Steps in text or AskUserQuestion | 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" }
+}
+```