maestro-flow 0.5.35 → 0.5.37

package/.claude/skills/team-ultra-analyze/specs/pipelines.md

@@ -1,64 +1,64 @@
-# Pipeline Definitions — Team Ultra Analyze
-
-## Pipeline Modes
-
-### Quick Mode (3 tasks, serial)
-
-```
-EXPLORE-001 -> ANALYZE-001 -> SYNTH-001
-```
-
-| Task | Role | Dependencies |
-|------|------|-------------|
-| EXPLORE-001 | explorer | (none) |
-| ANALYZE-001 | analyst | EXPLORE-001 |
-| SYNTH-001 | synthesizer | ANALYZE-001 |
-
-### Standard Mode (2N+2 tasks, parallel windows)
-
-```
-[EXPLORE-001..N](parallel) -> [ANALYZE-001..N](parallel) -> DISCUSS-001 -> SYNTH-001
-```
-
-| Task | Role | Dependencies |
-|------|------|-------------|
-| EXPLORE-001..N | explorer | (none, parallel) |
-| ANALYZE-001..N | analyst | corresponding EXPLORE-N |
-| DISCUSS-001 | discussant | all ANALYZE tasks |
-| SYNTH-001 | synthesizer | DISCUSS-001 |
-
-### Deep Mode (2N+1 tasks initially, dynamic loop)
-
-Same as Standard but SYNTH-001 is omitted at dispatch. Created dynamically after discussion loop completes.
-
-Dynamic tasks created during discussion loop:
-- `DISCUSS-N` (round N) — created based on user feedback
-- `ANALYZE-fix-N` (direction fix) — created when user requests adjusted focus
-- `SYNTH-001` — created after final discussion round
-
-## Task Metadata Registry
-
-| Task ID | Role | Dependencies | Description |
-|---------|------|-------------|-------------|
-| EXPLORE-1..depth | explorer | (none) | Parallel codebase exploration, one per perspective |
-| ANALYZE-1..depth | analyst | EXPLORE-1..depth (all) | Parallel deep analysis, one per perspective |
-| DISCUSS-001 | discussant | ANALYZE-1..depth (all) | Process analysis results, identify gaps |
-| ANALYZE-fix-N | analyst | DISCUSS-N | Re-analysis for adjusted focus (Deep mode) |
-| DISCUSS-002..N | discussant | ANALYZE-fix-N | Subsequent discussion rounds (Deep mode, max 5) |
-| SYNTH-001 | synthesizer | Last DISCUSS-N | Cross-perspective integration and conclusions |
-
-## Discussion Loop Control
-
-| Mode | Max Rounds | Trigger |
-|------|-----------|---------|
-| quick | 0 | No discussion |
-| standard | 1 | After DISCUSS-001 |
-| deep | 5 | After each DISCUSS-N |
-
-## Checkpoints
-
-| Trigger | Location | Behavior |
-|---------|----------|----------|
-| Discussion round (Deep mode) | After DISCUSS-N completes | Pause, AskUser for direction/continuation |
-| Discussion loop limit | >5 rounds | Force synthesis, offer continuation |
-| Pipeline stall | No ready + no running | Check missing tasks, report to user |
+# Pipeline Definitions — Team Ultra Analyze
+
+## Pipeline Modes
+
+### Quick Mode (3 tasks, serial)
+
+```
+EXPLORE-001 -> ANALYZE-001 -> SYNTH-001
+```
+
+| Task | Role | Dependencies |
+|------|------|-------------|
+| EXPLORE-001 | explorer | (none) |
+| ANALYZE-001 | analyst | EXPLORE-001 |
+| SYNTH-001 | synthesizer | ANALYZE-001 |
+
+### Standard Mode (2N+2 tasks, parallel windows)
+
+```
+[EXPLORE-001..N](parallel) -> [ANALYZE-001..N](parallel) -> DISCUSS-001 -> SYNTH-001
+```
+
+| Task | Role | Dependencies |
+|------|------|-------------|
+| EXPLORE-001..N | explorer | (none, parallel) |
+| ANALYZE-001..N | analyst | corresponding EXPLORE-N |
+| DISCUSS-001 | discussant | all ANALYZE tasks |
+| SYNTH-001 | synthesizer | DISCUSS-001 |
+
+### Deep Mode (2N+1 tasks initially, dynamic loop)
+
+Same as Standard but SYNTH-001 is omitted at dispatch. Created dynamically after discussion loop completes.
+
+Dynamic tasks created during discussion loop:
+- `DISCUSS-N` (round N) — created based on user feedback
+- `ANALYZE-fix-N` (direction fix) — created when user requests adjusted focus
+- `SYNTH-001` — created after final discussion round
+
+## Task Metadata Registry
+
+| Task ID | Role | Dependencies | Description |
+|---------|------|-------------|-------------|
+| EXPLORE-1..depth | explorer | (none) | Parallel codebase exploration, one per perspective |
+| ANALYZE-1..depth | analyst | EXPLORE-1..depth (all) | Parallel deep analysis, one per perspective |
+| DISCUSS-001 | discussant | ANALYZE-1..depth (all) | Process analysis results, identify gaps |
+| ANALYZE-fix-N | analyst | DISCUSS-N | Re-analysis for adjusted focus (Deep mode) |
+| DISCUSS-002..N | discussant | ANALYZE-fix-N | Subsequent discussion rounds (Deep mode, max 5) |
+| SYNTH-001 | synthesizer | Last DISCUSS-N | Cross-perspective integration and conclusions |
+
+## Discussion Loop Control
+
+| Mode | Max Rounds | Trigger |
+|------|-----------|---------|
+| quick | 0 | No discussion |
+| standard | 1 | After DISCUSS-001 |
+| deep | 5 | After each DISCUSS-N |
+
+## Checkpoints
+
+| Trigger | Location | Behavior |
+|---------|----------|----------|
+| Discussion round (Deep mode) | After DISCUSS-N completes | Pause, AskUser for direction/continuation |
+| Discussion loop limit | >5 rounds | Force synthesis, offer continuation |
+| Pipeline stall | No ready + no running | Check missing tasks, report to user |

package/.claude/skills/team-ultra-analyze/specs/team-config.json

@@ -23,7 +23,7 @@
       "message_types_sent": ["exploration_ready", "error"],
       "message_types_received": [],
       "commands": ["explore"],
-      "cli_tools": ["gemini"]    },
+      "cli_tools": ["agy"]    },
     "analyst": {
       "name": "analyst",
       "responsibility": "Read-only analysis (深度分析)",
@@ -32,7 +32,7 @@
       "message_types_sent": ["analysis_ready", "error"],
       "message_types_received": [],
       "commands": ["analyze"],
-      "cli_tools": ["gemini", "codex", "claude"]
+      "cli_tools": ["agy", "codex", "claude"]
     },
     "discussant": {
       "name": "discussant",
@@ -42,8 +42,8 @@
       "message_types_sent": ["discussion_processed", "error"],
       "message_types_received": [],
       "commands": ["deepen"],
-      "cli_tools": ["gemini"],
-      "cli_tools": ["gemini"]    },
+      "cli_tools": ["agy"],
+      "cli_tools": ["agy"]    },
     "synthesizer": {
       "name": "synthesizer",
       "responsibility": "Read-only analysis (综合结论)",
@@ -121,9 +121,9 @@
   },
 
   "analysis_perspectives": {
-    "technical": { "tool": "gemini", "focus": "Implementation, code patterns, technical feasibility" },
+    "technical": { "tool": "agy", "focus": "Implementation, code patterns, technical feasibility" },
     "architectural": { "tool": "claude", "focus": "System design, scalability, component interactions" },
     "business": { "tool": "codex", "focus": "Value, ROI, stakeholder impact, strategy" },
-    "domain_expert": { "tool": "gemini", "focus": "Domain-specific patterns, best practices, standards" }
+    "domain_expert": { "tool": "agy", "focus": "Domain-specific patterns, best practices, standards" }
   }
 }

package/.claude/skills/team-ux-improve/SKILL.md

@@ -1,151 +1,151 @@
----
-name: team-ux-improve
-description: Unified team skill for UX improvement. Systematically discovers and fixes UI/UX interaction issues including unresponsive buttons, missing feedback, and state refresh problems. Uses team-worker agent architecture with roles/ for domain logic. Coordinator orchestrates pipeline, workers are team-worker agents. Triggers on "team ux improve".
-allowed-tools: Agent, AskUserQuestion, Read, Write, Edit, Bash, Glob, Grep, TaskList, TaskGet, TaskUpdate, TaskCreate, TeamCreate, TeamDelete, SendMessage, mcp__maestro__read_file, mcp__maestro__write_file, mcp__maestro__edit_file, mcp__maestro__team_msg
----
-
-# Team UX Improve
-
-Systematic UX improvement pipeline: scan -> diagnose -> design -> implement -> test. Built on **team-worker agent architecture** — all worker roles share a single agent definition with role-specific Phase 2-4 loaded from `roles/<role>/role.md`.
-
-## Architecture
-
-```
-Skill(skill="team-ux-improve", args="<project-path> [--framework react|vue]")
-                    |
-         SKILL.md (this file) = Router
-                    |
-     +--------------+--------------+
-     |                             |
-  no --role flag              --role <name>
-     |                             |
-  Coordinator                  Worker
-  roles/coordinator/role.md    roles/<name>/role.md
-     |
-     +-- analyze → dispatch → spawn workers → STOP
-                                    |
-                    +-------+-------+-------+-------+
-                    v       v       v       v       v
-           [team-worker agents, each loads roles/<role>/role.md]
-          scanner  diagnoser  designer  implementer  tester
-```
-
-## Role Registry
-
-| Role | Path | Prefix | Inner Loop |
-|------|------|--------|------------|
-| coordinator | [roles/coordinator/role.md](roles/coordinator/role.md) | — | — |
-| scanner | [roles/scanner/role.md](roles/scanner/role.md) | SCAN-* | false |
-| diagnoser | [roles/diagnoser/role.md](roles/diagnoser/role.md) | DIAG-* | false |
-| designer | [roles/designer/role.md](roles/designer/role.md) | DESIGN-* | false |
-| implementer | [roles/implementer/role.md](roles/implementer/role.md) | IMPL-* | true |
-| tester | [roles/tester/role.md](roles/tester/role.md) | TEST-* | false |
-
-## Utility Member Registry
-
-**Coordinator-only**: Utility members can only be spawned by Coordinator. Workers CANNOT call Agent() to spawn utility members.
-
-| Utility Member | Path | Callable By | Purpose |
-|----------------|------|-------------|---------|
-| explorer | [roles/explorer/role.md](roles/explorer/role.md) | Coordinator only | Explore codebase for UI component patterns and framework-specific patterns |
-
-
-## Pre-load (coordinator, before dispatch)
-
-1. **Codebase docs**: If `.workflow/codebase/ARCHITECTURE.md` exists, read for module boundaries
-2. **Specs (ui)**: `maestro spec load --category ui` — load ui constraints as shared context
-3. **Wiki knowledge**: `maestro search "UX improvement interaction" --json` — top 5 entries as prior context
-4. 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**: `ux-improve`
-- **Session path**: `.workflow/.team/ux-improve-<timestamp>/`
-- **CLI tools**: `maestro delegate --mode analysis` (read-only), `maestro delegate --mode write` (modifications)
-- **Message bus**: `mcp__maestro__team_msg(session_id=<session-id>, ...)`
-- **Max test iterations**: 5
-
-## Worker Spawn Template
-
-Coordinator spawns workers using this template:
-
-```
-Agent({
-  subagent_type: "team-worker",
-  description: "Spawn <role> worker for <task-id>",
-  team_name: "ux-improve",
-  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: ux-improve
-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 |
-
-## Specs Reference
-
-- [specs/pipelines.md](specs/pipelines.md) — Pipeline definitions and task registry
-- [specs/design-standards.md](specs/design-standards.md) — Impeccable visual design standards
-- [specs/anti-patterns.md](specs/anti-patterns.md) — AI slop detection catalog (20 items)
-- [specs/heuristics.md](specs/heuristics.md) — Nielsen's 10 usability heuristics evaluation framework
-
-## Session Directory
-
-```
-.workflow/.team/ux-improve-<timestamp>/
-├── .msg/
-│   ├── messages.jsonl      # Team message bus
-│   └── meta.json           # Pipeline config + role state snapshot
-├── artifacts/              # Role deliverables
-│   ├── scan-report.md      # Scanner output
-│   ├── diagnosis.md        # Diagnoser output
-│   ├── design-guide.md     # Designer output
-│   ├── fixes/              # Implementer output
-│   └── test-report.md      # Tester output
-├── explorations/           # Explorer cache
-│   └── cache-index.json
-└── wisdom/                 # Session knowledge base
-    ├── contributions/      # Worker contributions (write-only for workers)
-    ├── principles/
-    ├── patterns/
-    └── anti-patterns/
-```
-
-## Error Handling
-
-| Scenario | Resolution |
-|----------|------------|
-| Unknown command | Error with available command list |
-| Role not found | Error with role registry |
-| Project path invalid | Re-prompt user for valid path |
-| Framework detection fails | AskUserQuestion for framework selection |
-| Session corruption | Attempt recovery, fallback to manual |
-| Fast-advance conflict | Coordinator reconciles on next callback |
-| No UI issues found | Complete with empty fix list, generate clean bill report |
-| Test iterations exceeded | Accept current state, continue to completion |
+---
+name: team-ux-improve
+description: Unified team skill for UX improvement. Systematically discovers and fixes UI/UX interaction issues including unresponsive buttons, missing feedback, and state refresh problems. Uses team-worker agent architecture with roles/ for domain logic. Coordinator orchestrates pipeline, workers are team-worker agents. Triggers on "team ux improve".
+allowed-tools: Agent, AskUserQuestion, Read, Write, Edit, Bash, Glob, Grep, TaskList, TaskGet, TaskUpdate, TaskCreate, TeamCreate, TeamDelete, SendMessage, mcp__maestro__read_file, mcp__maestro__write_file, mcp__maestro__edit_file, mcp__maestro__team_msg
+---
+
+# Team UX Improve
+
+Systematic UX improvement pipeline: scan -> diagnose -> design -> implement -> test. Built on **team-worker agent architecture** — all worker roles share a single agent definition with role-specific Phase 2-4 loaded from `roles/<role>/role.md`.
+
+## Architecture
+
+```
+Skill(skill="team-ux-improve", args="<project-path> [--framework react|vue]")
+                    |
+         SKILL.md (this file) = Router
+                    |
+     +--------------+--------------+
+     |                             |
+  no --role flag              --role <name>
+     |                             |
+  Coordinator                  Worker
+  roles/coordinator/role.md    roles/<name>/role.md
+     |
+     +-- analyze → dispatch → spawn workers → STOP
+                                    |
+                    +-------+-------+-------+-------+
+                    v       v       v       v       v
+           [team-worker agents, each loads roles/<role>/role.md]
+          scanner  diagnoser  designer  implementer  tester
+```
+
+## Role Registry
+
+| Role | Path | Prefix | Inner Loop |
+|------|------|--------|------------|
+| coordinator | [roles/coordinator/role.md](roles/coordinator/role.md) | — | — |
+| scanner | [roles/scanner/role.md](roles/scanner/role.md) | SCAN-* | false |
+| diagnoser | [roles/diagnoser/role.md](roles/diagnoser/role.md) | DIAG-* | false |
+| designer | [roles/designer/role.md](roles/designer/role.md) | DESIGN-* | false |
+| implementer | [roles/implementer/role.md](roles/implementer/role.md) | IMPL-* | true |
+| tester | [roles/tester/role.md](roles/tester/role.md) | TEST-* | false |
+
+## Utility Member Registry
+
+**Coordinator-only**: Utility members can only be spawned by Coordinator. Workers CANNOT call Agent() to spawn utility members.
+
+| Utility Member | Path | Callable By | Purpose |
+|----------------|------|-------------|---------|
+| explorer | [roles/explorer/role.md](roles/explorer/role.md) | Coordinator only | Explore codebase for UI component patterns and framework-specific patterns |
+
+
+## Pre-load (coordinator, before dispatch)
+
+1. **Codebase docs**: If `.workflow/codebase/ARCHITECTURE.md` exists, read for module boundaries
+2. **Specs (ui)**: `maestro load --type spec --category ui` — load ui constraints as shared context
+3. **Wiki knowledge**: `maestro search "UX improvement interaction" --json` — top 5 entries as prior context
+4. 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**: `ux-improve`
+- **Session path**: `.workflow/.team/ux-improve-<timestamp>/`
+- **CLI tools**: `maestro delegate --mode analysis` (read-only), `maestro delegate --mode write` (modifications)
+- **Message bus**: `mcp__maestro__team_msg(session_id=<session-id>, ...)`
+- **Max test iterations**: 5
+
+## Worker Spawn Template
+
+Coordinator spawns workers using this template:
+
+```
+Agent({
+  subagent_type: "team-worker",
+  description: "Spawn <role> worker for <task-id>",
+  team_name: "ux-improve",
+  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: ux-improve
+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 |
+
+## Specs Reference
+
+- [specs/pipelines.md](specs/pipelines.md) — Pipeline definitions and task registry
+- [specs/design-standards.md](specs/design-standards.md) — Impeccable visual design standards
+- [specs/anti-patterns.md](specs/anti-patterns.md) — AI slop detection catalog (20 items)
+- [specs/heuristics.md](specs/heuristics.md) — Nielsen's 10 usability heuristics evaluation framework
+
+## Session Directory
+
+```
+.workflow/.team/ux-improve-<timestamp>/
+├── .msg/
+│   ├── messages.jsonl      # Team message bus
+│   └── meta.json           # Pipeline config + role state snapshot
+├── artifacts/              # Role deliverables
+│   ├── scan-report.md      # Scanner output
+│   ├── diagnosis.md        # Diagnoser output
+│   ├── design-guide.md     # Designer output
+│   ├── fixes/              # Implementer output
+│   └── test-report.md      # Tester output
+├── explorations/           # Explorer cache
+│   └── cache-index.json
+└── wisdom/                 # Session knowledge base
+    ├── contributions/      # Worker contributions (write-only for workers)
+    ├── principles/
+    ├── patterns/
+    └── anti-patterns/
+```
+
+## Error Handling
+
+| Scenario | Resolution |
+|----------|------------|
+| Unknown command | Error with available command list |
+| Role not found | Error with role registry |
+| Project path invalid | Re-prompt user for valid path |
+| Framework detection fails | AskUserQuestion for framework selection |
+| Session corruption | Attempt recovery, fallback to manual |
+| Fast-advance conflict | Coordinator reconciles on next callback |
+| No UI issues found | Complete with empty fix list, generate clean bill report |
+| Test iterations exceeded | Accept current state, continue to completion |

package/.claude/skills/team-ux-improve/roles/coordinator/commands/analyze.md

@@ -1,62 +1,62 @@
-# Analyze Task
-
-Parse user task -> detect UX improvement scope -> assess complexity -> determine pipeline configuration.
-
-**CONSTRAINT**: Text-level analysis only. NO source code reading, NO codebase exploration.
-
-## Signal Detection
-
-| Keywords | Signal | Pipeline Hint |
-|----------|--------|---------------|
-| button, click, tap, unresponsive | interaction-issues | standard |
-| loading, spinner, feedback, progress | feedback-missing | standard |
-| state, refresh, update, stale | state-issues | standard |
-| form, input, validation, error | input-issues | standard |
-| accessibility, a11y, keyboard, screen reader | accessibility | standard |
-| performance, slow, lag, freeze | performance | standard |
-| all, full, complete, comprehensive | full-scope | standard |
-
-## Framework Detection
-
-| Keywords | Framework |
-|----------|-----------|
-| react, jsx, tsx, useState, useEffect | React |
-| vue, .vue, ref(), reactive(), v-model | Vue |
-| angular, ng-, @Component | Angular |
-| Default | auto-detect |
-
-## Complexity Scoring
-
-| Factor | Points |
-|--------|--------|
-| Single component scope | +1 |
-| Multiple components | +2 |
-| Full project scope | +3 |
-| Accessibility required | +1 |
-| Performance issues | +1 |
-| Complex state management | +1 |
-
-Results: 1-2 Low (targeted fix), 3-4 Medium (standard pipeline), 5+ High (full pipeline)
-
-## Scope Determination
-
-| Signal | Pipeline Mode |
-|--------|---------------|
-| Specific component or file mentioned | targeted |
-| Multiple issues or general project | standard |
-| "Full audit" or "complete scan" | standard |
-| Unclear | ask user |
-
-## Output
-
-Write scope context to coordinator memory:
-```json
-{
-  "pipeline_mode": "standard",
-  "project_path": "<detected-or-provided-path>",
-  "framework": "<react|vue|angular|auto>",
-  "scope": "<detected-scope>",
-  "issue_signals": ["interaction", "feedback", "state"],
-  "complexity": { "score": 0, "level": "Low|Medium|High" }
-}
-```
+# Analyze Task
+
+Parse user task -> detect UX improvement scope -> assess complexity -> determine pipeline configuration.
+
+**CONSTRAINT**: Text-level analysis only. NO source code reading, NO codebase exploration.
+
+## Signal Detection
+
+| Keywords | Signal | Pipeline Hint |
+|----------|--------|---------------|
+| button, click, tap, unresponsive | interaction-issues | standard |
+| loading, spinner, feedback, progress | feedback-missing | standard |
+| state, refresh, update, stale | state-issues | standard |
+| form, input, validation, error | input-issues | standard |
+| accessibility, a11y, keyboard, screen reader | accessibility | standard |
+| performance, slow, lag, freeze | performance | standard |
+| all, full, complete, comprehensive | full-scope | standard |
+
+## Framework Detection
+
+| Keywords | Framework |
+|----------|-----------|
+| react, jsx, tsx, useState, useEffect | React |
+| vue, .vue, ref(), reactive(), v-model | Vue |
+| angular, ng-, @Component | Angular |
+| Default | auto-detect |
+
+## Complexity Scoring
+
+| Factor | Points |
+|--------|--------|
+| Single component scope | +1 |
+| Multiple components | +2 |
+| Full project scope | +3 |
+| Accessibility required | +1 |
+| Performance issues | +1 |
+| Complex state management | +1 |
+
+Results: 1-2 Low (targeted fix), 3-4 Medium (standard pipeline), 5+ High (full pipeline)
+
+## Scope Determination
+
+| Signal | Pipeline Mode |
+|--------|---------------|
+| Specific component or file mentioned | targeted |
+| Multiple issues or general project | standard |
+| "Full audit" or "complete scan" | standard |
+| Unclear | ask user |
+
+## Output
+
+Write scope context to coordinator memory:
+```json
+{
+  "pipeline_mode": "standard",
+  "project_path": "<detected-or-provided-path>",
+  "framework": "<react|vue|angular|auto>",
+  "scope": "<detected-scope>",
+  "issue_signals": ["interaction", "feedback", "state"],
+  "complexity": { "score": 0, "level": "Low|Medium|High" }
+}
+```