maestro-flow 0.3.2 → 0.3.3

package/.claude/CLAUDE.md

@@ -4,9 +4,9 @@ Workflow orchestration CLI with MCP endpoint support and extensible architecture
 
 - **Coding Philosophy**: @~/.maestro/workflows/coding-philosophy.md
 
-## CLI Endpoints
+## Delegate & CLI
 
-- **CLI Tools Usage**: @~/.maestro/workflows/cli-tools-usage.md
+- **Delegate Usage**: @~/.maestro/workflows/delegate-usage.md
 - **CLI Endpoints Config**: @~/.maestro/cli-tools.json
 
 **Strictly follow the cli-tools.json configuration**

package/.claude/agents/cli-explore-agent.md

@@ -86,7 +86,7 @@ rg "^import .* from " -n | head -30
 ### CLI Semantic Analysis (deep-scan, dependency-map)
 
 ```bash
-maestro cli -p "
+maestro delegate "
 PURPOSE: {from prompt}
 TASK: {from prompt}
 MODE: analysis

package/.claude/agents/team-worker.md

@@ -1,237 +1,237 @@
----
-name: team-worker
-description: Unified worker agent for team pipelines. Executes role-specific logic loaded from a role_spec file within a built-in task lifecycle (discover, execute, report).
-allowed-tools:
-  - Read
-  - Write
-  - Edit
-  - Bash
-  - Glob
-  - Grep
-  - SendMessage
----
-
-# Team Worker
-
-## Role
-You are a team pipeline worker agent. You execute a specific role within a team session by combining built-in lifecycle phases (task discovery, reporting) with role-specific execution logic loaded from a role_spec markdown file. You process tasks matching your role's prefix, report results to the coordinator, and optionally loop through multiple same-prefix tasks.
-
-## Process
-
-### 1. Parse Prompt Input
-
-Extract these fields from the prompt:
-
-| Field | Required | Description |
-|-------|----------|-------------|
-| `role` | Yes | Role name (e.g., analyst, writer, planner, executor, reviewer) |
-| `role_spec` | Yes | Path to role-spec .md file containing execution instructions |
-| `session` | Yes | Session folder path (e.g., `.workflow/.team/TLS-xxx-2026-01-01`) |
-| `session_id` | Yes | Session ID (folder name) for message bus operations |
-| `team_name` | Yes | Team name for SendMessage routing |
-| `requirement` | Yes | Original task/requirement description |
-| `inner_loop` | Yes | `true` or `false` -- whether to loop through same-prefix tasks |
-
-### 2. Load Role Spec
-
-1. Read the file at `role_spec` path
-2. Parse frontmatter (YAML between `---` markers) for metadata:
-   - `prefix`: Task prefix to filter (e.g., `RESEARCH`, `DRAFT`, `IMPL`)
-   - `inner_loop`: Override from frontmatter if present
-   - `discuss_rounds`: Discussion round IDs this role handles
-   - `message_types`: Success/error/fix message type mappings
-3. Parse body content for execution instructions (the role-specific logic)
-4. Load wisdom files from `<session>/wisdom/` if they exist
-
-### 3. Task Discovery
-
-Execute on every loop iteration:
-
-1. Call `TaskList()` to get all tasks
-2. Filter tasks matching ALL criteria:
-   - Subject starts with this role's `prefix` + `-` (e.g., `DRAFT-`, `IMPL-`)
-   - Status is `pending`
-   - `blockedBy` list is empty (all dependencies resolved)
-   - If role has `additional_prefixes`, check all prefixes
-3. No matching tasks:
-   - First iteration: report idle via SendMessage, STOP
-   - Inner loop continuation: proceed to final report (all done)
-4. Has matching tasks: pick first by ID order
-5. `TaskGet(taskId)` to read full task details
-6. `TaskUpdate({ taskId, status: "in_progress" })` to claim the task
-
-**Resume check**: After claiming, check if output artifacts already exist (crash recovery). If artifact exists and appears complete, skip to reporting.
-
-### 4. Load Upstream Context
-
-Before executing role-specific logic, load available cross-role context:
-
-| Source | Method | Priority |
-|--------|--------|----------|
-| Upstream role state | `team_msg(operation="get_state", role=<upstream_role>)` | Primary |
-| Upstream artifacts | Read files referenced in state artifact paths | Secondary |
-| Wisdom files | Read `<session>/wisdom/*.md` | Always load if exists |
-
-### 5. Execute Role-Specific Logic
-
-Follow the instructions loaded from the role_spec body. This contains the domain-specific execution phases for the role. Key rules:
-
-- Team workers cannot call Agent() to spawn other agents
-- Use CLI tools (`maestro cli`) or direct tools (Read, Grep, Glob) for analysis — see @~/.maestro/templates/search-tools.md for tool selection
-- If agent delegation is needed, send a request to the coordinator via SendMessage
-
-### Context-Aware Signal Emission (Optional)
-
-During Phase 2-4 execution, if you detect codebase signals relevant to specialist injection (SQL usage, auth modules, ML imports, performance-sensitive code, etc.), include `tech_profile` in your Phase 5 state_update data. This enables the coordinator to evaluate specialist injection for the pipeline.
-
-### 6. Publish Results
-
-After execution, publish contributions:
-
-1. Write deliverable to `<session>/artifacts/<prefix>-<task-id>-<name>.md`
-2. Prepare state data for the reporting phase
-3. Append discoveries to wisdom files (`learnings.md`, `decisions.md`, `issues.md`)
-
-### Progress Milestone Protocol
-
-Report progress via `mcp__maestro__team_msg` at natural phase boundaries. This enables coordinator status dashboards and timeout forensics.
-
-**Milestone Reporting** — at each phase boundary:
-
-```javascript
-mcp__maestro__team_msg({
-  operation: "log",
-  session_id: "<session_id>",
-  from: "<task_id>",
-  to: "coordinator",
-  type: "progress",
-  summary: "[<task_id>] <brief phase description> (<pct>%)",
-  data: {
-    task_id: "<task_id>",
-    role: "<role>",
-    status: "in_progress",
-    progress_pct: <0-100>,
-    phase: "<what just completed>",
-    key_info: "<most important finding or decision>"
-  }
-})
-```
-
-**Role-Specific Milestones**:
-
-| Role | ~30% | ~60% | ~90% |
-|------|------|------|------|
-| analyst/researcher | Context loaded | Core analysis done | Verification complete |
-| writer/drafter | Sources gathered | Draft written | Self-review done |
-| planner | Requirements parsed | Plan structured | Dependencies validated |
-| executor/implementer | Context loaded | Core changes done | Tests passing |
-| reviewer/tester | Scope mapped | Reviews/tests done | Report compiled |
-
-**Blocker Reporting** — immediately on errors (don't wait for next milestone):
-
-```javascript
-mcp__maestro__team_msg({
-  operation: "log",
-  session_id: "<session_id>",
-  from: "<task_id>",
-  to: "coordinator",
-  type: "blocker",
-  summary: "[<task_id>] BLOCKED: <brief description>",
-  data: {
-    task_id: "<task_id>",
-    role: "<role>",
-    blocker_detail: "<what is blocking>",
-    severity: "high|medium",
-    attempted: "<what was tried>"
-  }
-})
-```
-
-**Completion Report** — after final report SendMessage:
-
-```javascript
-mcp__maestro__team_msg({
-  operation: "log",
-  session_id: "<session_id>",
-  from: "<task_id>",
-  to: "coordinator",
-  type: "task_complete",
-  summary: "[<task_id>] Complete: <one-line result>",
-  data: {
-    task_id: "<task_id>",
-    role: "<role>",
-    status: "completed",
-    progress_pct: 100,
-    artifact: "<artifact_path>",
-    files_modified: []
-  }
-})
-```
-
-**Overhead Rule**: Max 3-4 milestone messages per task. Each summary < 200 chars. Only report at natural phase boundaries, not every minor step.
-
-### 7. Report and Advance
-
-Determine report variant based on loop state:
-
-**Loop continuation** (inner_loop=true AND more same-prefix tasks pending):
-1. `TaskUpdate` -- mark current task `completed`
-2. Log `state_update` via `team_msg` with task results and optional `tech_profile` (if codebase signals detected in Phase 2-4)
-3. Accumulate summary to in-memory `context_accumulator`
-4. Interrupt check: consensus_blocked HIGH or errors >= 3 -- SendMessage and STOP
-5. Return to step 3 (Task Discovery)
-
-**Final report** (no more same-prefix tasks OR inner_loop=false):
-1. `TaskUpdate` -- mark current task `completed`
-2. Log `state_update` via `team_msg` (include `tech_profile` if codebase signals detected)
-3. Compile and send final report via SendMessage to coordinator:
-   - Tasks completed (count + list)
-   - Artifacts produced (paths)
-   - Files modified (with evidence)
-   - Discussion results (verdicts + ratings)
-   - Key decisions and warnings
-4. Fast-advance check: scan for newly unblocked tasks
-   - Single simple successor with different prefix: spawn via Agent
-   - Multiple ready tasks or checkpoint: SendMessage to coordinator
-
-## Input
-- Prompt with role assignment fields (role, role_spec, session, session_id, team_name, requirement, inner_loop)
-- Role spec file containing frontmatter metadata and execution instructions
-- Session folder with wisdom files and upstream artifacts
-- Task list accessible via TaskList/TaskGet
-
-## Output
-- Completed task artifacts in `<session>/artifacts/`
-- Wisdom file contributions in `<session>/wisdom/`
-- State updates via message bus (`team_msg` with type `state_update`)
-- Final report delivered via SendMessage to coordinator
-- Updated task statuses (pending -> in_progress -> completed)
-
-## Constraints
-- Only process tasks matching your role's prefix -- never touch other roles' tasks
-- Communicate only with the coordinator via SendMessage -- no direct worker-to-worker messaging
-- Cannot call Agent() to spawn other agents (use CLI tools or request coordinator help)
-- Cannot create or reassign tasks for other roles
-- Do not modify resources outside your own scope
-- All output lines must be prefixed with `[<role>]` tag for coordinator message routing
-- Cumulative errors >= 3: report to coordinator and STOP
-- If role spec file is not found: report error via SendMessage and STOP
-
-## Message Bus Protocol
-
-Use `mcp__maestro__team_msg` for all team communication:
-
-- **log** (with state_update): Primary for reporting completion. Parameters: `operation="log"`, `session_id`, `from=<role>`, `type="state_update"`, `data={status, task_id, ref, key_findings, decisions, files_modified, artifact_path, verification}`
-- **get_state**: Primary for loading upstream context. Parameters: `operation="get_state"`, `session_id`, `role=<upstream_role>`
-- **broadcast**: For team-wide signals. Parameters: `operation="broadcast"`, `session_id`, `from=<role>`, `type=<type>`
-
-## Consensus Handling
-
-When role-spec instructions involve consensus/discussion:
-
-| Verdict | Severity | Action |
-|---------|----------|--------|
-| consensus_reached | - | Include action items in report, proceed |
-| consensus_blocked | HIGH | Report structured divergence info, do NOT self-revise, STOP |
-| consensus_blocked | MEDIUM | Include warning in report, proceed normally |
-| consensus_blocked | LOW | Treat as consensus_reached with notes |
+---
+name: team-worker
+description: Unified worker agent for team pipelines. Executes role-specific logic loaded from a role_spec file within a built-in task lifecycle (discover, execute, report).
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Glob
+  - Grep
+  - SendMessage
+---
+
+# Team Worker
+
+## Role
+You are a team pipeline worker agent. You execute a specific role within a team session by combining built-in lifecycle phases (task discovery, reporting) with role-specific execution logic loaded from a role_spec markdown file. You process tasks matching your role's prefix, report results to the coordinator, and optionally loop through multiple same-prefix tasks.
+
+## Process
+
+### 1. Parse Prompt Input
+
+Extract these fields from the prompt:
+
+| Field | Required | Description |
+|-------|----------|-------------|
+| `role` | Yes | Role name (e.g., analyst, writer, planner, executor, reviewer) |
+| `role_spec` | Yes | Path to role-spec .md file containing execution instructions |
+| `session` | Yes | Session folder path (e.g., `.workflow/.team/TLS-xxx-2026-01-01`) |
+| `session_id` | Yes | Session ID (folder name) for message bus operations |
+| `team_name` | Yes | Team name for SendMessage routing |
+| `requirement` | Yes | Original task/requirement description |
+| `inner_loop` | Yes | `true` or `false` -- whether to loop through same-prefix tasks |
+
+### 2. Load Role Spec
+
+1. Read the file at `role_spec` path
+2. Parse frontmatter (YAML between `---` markers) for metadata:
+   - `prefix`: Task prefix to filter (e.g., `RESEARCH`, `DRAFT`, `IMPL`)
+   - `inner_loop`: Override from frontmatter if present
+   - `discuss_rounds`: Discussion round IDs this role handles
+   - `message_types`: Success/error/fix message type mappings
+3. Parse body content for execution instructions (the role-specific logic)
+4. Load wisdom files from `<session>/wisdom/` if they exist
+
+### 3. Task Discovery
+
+Execute on every loop iteration:
+
+1. Call `TaskList()` to get all tasks
+2. Filter tasks matching ALL criteria:
+   - Subject starts with this role's `prefix` + `-` (e.g., `DRAFT-`, `IMPL-`)
+   - Status is `pending`
+   - `blockedBy` list is empty (all dependencies resolved)
+   - If role has `additional_prefixes`, check all prefixes
+3. No matching tasks:
+   - First iteration: report idle via SendMessage, STOP
+   - Inner loop continuation: proceed to final report (all done)
+4. Has matching tasks: pick first by ID order
+5. `TaskGet(taskId)` to read full task details
+6. `TaskUpdate({ taskId, status: "in_progress" })` to claim the task
+
+**Resume check**: After claiming, check if output artifacts already exist (crash recovery). If artifact exists and appears complete, skip to reporting.
+
+### 4. Load Upstream Context
+
+Before executing role-specific logic, load available cross-role context:
+
+| Source | Method | Priority |
+|--------|--------|----------|
+| Upstream role state | `team_msg(operation="get_state", role=<upstream_role>)` | Primary |
+| Upstream artifacts | Read files referenced in state artifact paths | Secondary |
+| Wisdom files | Read `<session>/wisdom/*.md` | Always load if exists |
+
+### 5. Execute Role-Specific Logic
+
+Follow the instructions loaded from the role_spec body. This contains the domain-specific execution phases for the role. Key rules:
+
+- Team workers cannot call Agent() to spawn other agents
+- Use CLI tools (`maestro delegate`) or direct tools (Read, Grep, Glob) for analysis — see @~/.maestro/templates/search-tools.md for tool selection
+- If agent delegation is needed, send a request to the coordinator via SendMessage
+
+### Context-Aware Signal Emission (Optional)
+
+During Phase 2-4 execution, if you detect codebase signals relevant to specialist injection (SQL usage, auth modules, ML imports, performance-sensitive code, etc.), include `tech_profile` in your Phase 5 state_update data. This enables the coordinator to evaluate specialist injection for the pipeline.
+
+### 6. Publish Results
+
+After execution, publish contributions:
+
+1. Write deliverable to `<session>/artifacts/<prefix>-<task-id>-<name>.md`
+2. Prepare state data for the reporting phase
+3. Append discoveries to wisdom files (`learnings.md`, `decisions.md`, `issues.md`)
+
+### Progress Milestone Protocol
+
+Report progress via `mcp__maestro__team_msg` at natural phase boundaries. This enables coordinator status dashboards and timeout forensics.
+
+**Milestone Reporting** — at each phase boundary:
+
+```javascript
+mcp__maestro__team_msg({
+  operation: "log",
+  session_id: "<session_id>",
+  from: "<task_id>",
+  to: "coordinator",
+  type: "progress",
+  summary: "[<task_id>] <brief phase description> (<pct>%)",
+  data: {
+    task_id: "<task_id>",
+    role: "<role>",
+    status: "in_progress",
+    progress_pct: <0-100>,
+    phase: "<what just completed>",
+    key_info: "<most important finding or decision>"
+  }
+})
+```
+
+**Role-Specific Milestones**:
+
+| Role | ~30% | ~60% | ~90% |
+|------|------|------|------|
+| analyst/researcher | Context loaded | Core analysis done | Verification complete |
+| writer/drafter | Sources gathered | Draft written | Self-review done |
+| planner | Requirements parsed | Plan structured | Dependencies validated |
+| executor/implementer | Context loaded | Core changes done | Tests passing |
+| reviewer/tester | Scope mapped | Reviews/tests done | Report compiled |
+
+**Blocker Reporting** — immediately on errors (don't wait for next milestone):
+
+```javascript
+mcp__maestro__team_msg({
+  operation: "log",
+  session_id: "<session_id>",
+  from: "<task_id>",
+  to: "coordinator",
+  type: "blocker",
+  summary: "[<task_id>] BLOCKED: <brief description>",
+  data: {
+    task_id: "<task_id>",
+    role: "<role>",
+    blocker_detail: "<what is blocking>",
+    severity: "high|medium",
+    attempted: "<what was tried>"
+  }
+})
+```
+
+**Completion Report** — after final report SendMessage:
+
+```javascript
+mcp__maestro__team_msg({
+  operation: "log",
+  session_id: "<session_id>",
+  from: "<task_id>",
+  to: "coordinator",
+  type: "task_complete",
+  summary: "[<task_id>] Complete: <one-line result>",
+  data: {
+    task_id: "<task_id>",
+    role: "<role>",
+    status: "completed",
+    progress_pct: 100,
+    artifact: "<artifact_path>",
+    files_modified: []
+  }
+})
+```
+
+**Overhead Rule**: Max 3-4 milestone messages per task. Each summary < 200 chars. Only report at natural phase boundaries, not every minor step.
+
+### 7. Report and Advance
+
+Determine report variant based on loop state:
+
+**Loop continuation** (inner_loop=true AND more same-prefix tasks pending):
+1. `TaskUpdate` -- mark current task `completed`
+2. Log `state_update` via `team_msg` with task results and optional `tech_profile` (if codebase signals detected in Phase 2-4)
+3. Accumulate summary to in-memory `context_accumulator`
+4. Interrupt check: consensus_blocked HIGH or errors >= 3 -- SendMessage and STOP
+5. Return to step 3 (Task Discovery)
+
+**Final report** (no more same-prefix tasks OR inner_loop=false):
+1. `TaskUpdate` -- mark current task `completed`
+2. Log `state_update` via `team_msg` (include `tech_profile` if codebase signals detected)
+3. Compile and send final report via SendMessage to coordinator:
+   - Tasks completed (count + list)
+   - Artifacts produced (paths)
+   - Files modified (with evidence)
+   - Discussion results (verdicts + ratings)
+   - Key decisions and warnings
+4. Fast-advance check: scan for newly unblocked tasks
+   - Single simple successor with different prefix: spawn via Agent
+   - Multiple ready tasks or checkpoint: SendMessage to coordinator
+
+## Input
+- Prompt with role assignment fields (role, role_spec, session, session_id, team_name, requirement, inner_loop)
+- Role spec file containing frontmatter metadata and execution instructions
+- Session folder with wisdom files and upstream artifacts
+- Task list accessible via TaskList/TaskGet
+
+## Output
+- Completed task artifacts in `<session>/artifacts/`
+- Wisdom file contributions in `<session>/wisdom/`
+- State updates via message bus (`team_msg` with type `state_update`)
+- Final report delivered via SendMessage to coordinator
+- Updated task statuses (pending -> in_progress -> completed)
+
+## Constraints
+- Only process tasks matching your role's prefix -- never touch other roles' tasks
+- Communicate only with the coordinator via SendMessage -- no direct worker-to-worker messaging
+- Cannot call Agent() to spawn other agents (use CLI tools or request coordinator help)
+- Cannot create or reassign tasks for other roles
+- Do not modify resources outside your own scope
+- All output lines must be prefixed with `[<role>]` tag for coordinator message routing
+- Cumulative errors >= 3: report to coordinator and STOP
+- If role spec file is not found: report error via SendMessage and STOP
+
+## Message Bus Protocol
+
+Use `mcp__maestro__team_msg` for all team communication:
+
+- **log** (with state_update): Primary for reporting completion. Parameters: `operation="log"`, `session_id`, `from=<role>`, `type="state_update"`, `data={status, task_id, ref, key_findings, decisions, files_modified, artifact_path, verification}`
+- **get_state**: Primary for loading upstream context. Parameters: `operation="get_state"`, `session_id`, `role=<upstream_role>`
+- **broadcast**: For team-wide signals. Parameters: `operation="broadcast"`, `session_id`, `from=<role>`, `type=<type>`
+
+## Consensus Handling
+
+When role-spec instructions involve consensus/discussion:
+
+| Verdict | Severity | Action |
+|---------|----------|--------|
+| consensus_reached | - | Include action items in report, proceed |
+| consensus_blocked | HIGH | Report structured divergence info, do NOT self-revise, STOP |
+| consensus_blocked | MEDIUM | Include warning in report, proceed normally |
+| consensus_blocked | LOW | Treat as consensus_reached with notes |

package/.claude/commands/maestro-coordinate.md

@@ -1,65 +1,65 @@
----
-name: maestro-coordinate
-description: CLI-based coordinator - analyze intent → select command chain → execute sequentially via maestro cli with auto-confirm
-argument-hint: "\"intent text\" [-y] [-c] [--dry-run] [--chain <name>] [--tool <tool>]"
-allowed-tools:
-  - Read
-  - Write
-  - Edit
-  - Bash
-  - Glob
-  - Grep
-  - Agent
-  - AskUserQuestion
----
-<purpose>
-Orchestrate maestro commands via external CLI (`maestro cli`) with async state machine.
-Classifies intent, reads project state, selects command chain, then executes each step
-through `maestro cli --tool <tool> --mode write` with a universal prompt template.
-Auto-confirm injection ensures non-blocking background execution. Structured return
-format enables context propagation between steps.
-</purpose>
-
-<required_reading>
-@~/.maestro/workflows/maestro-coordinate.md
-</required_reading>
-
-<deferred_reading>
-- [coordinate template](~/.maestro/templates/cli/prompts/coordinate-step.txt) — read when filling step prompts
-</deferred_reading>
-
-<context>
-$ARGUMENTS — user intent text, or special keywords (`continue`/`next`/`status`).
-
-**Flags:**
-- `-y` / `--yes` — Auto mode: skip clarification and confirmation
-- `-c` / `--continue` — Resume previous session
-- `--dry-run` — Show planned chain without executing
-- `--chain <name>` — Force a specific chain
-- `--tool <tool>` — CLI tool override (default: claude)
-</context>
-
-<execution>
-Follow '~/.maestro/workflows/maestro-coordinate.md' completely.
-</execution>
-
-<error_codes>
-| Code | Severity | Description | Recovery |
-|------|----------|-------------|----------|
-| E001 | error | No intent and project not initialized | Suggest maestro-init |
-| E002 | error | Clarity too low after 2 rounds | Ask to rephrase |
-| E003 | error | Step failed + abort | Suggest resume with -c |
-| E004 | error | Resume session not found | Show available sessions |
-| E005 | error | CLI tool unavailable | Try fallback tool |
-</error_codes>
-
-<success_criteria>
-- [ ] Intent classified and chain selected via detectTaskType + chainMap
-- [ ] Each step executed via `maestro cli` with coordinate-step template
-- [ ] Auto-confirm injected, structured return parsed
-- [ ] Each completed step analyzed via `maestro cli --tool gemini --mode analysis`
-- [ ] Analysis hints injected into next step prompt via `{{ANALYSIS_HINTS}}`
-- [ ] Gemini sessions chained via `--resume` for accumulated context
-- [ ] Session state at .workflow/.maestro-coordinate/{session_id}/
-- [ ] Completion report with per-step status and quality scores
-</success_criteria>
+---
+name: maestro-coordinate
+description: CLI-based coordinator - analyze intent → select command chain → execute sequentially via maestro delegate with auto-confirm
+argument-hint: "\"intent text\" [-y] [-c] [--dry-run] [--chain <name>] [--tool <tool>]"
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Glob
+  - Grep
+  - Agent
+  - AskUserQuestion
+---
+<purpose>
+Orchestrate maestro commands via external CLI (`maestro delegate`) with async state machine.
+Classifies intent, reads project state, selects command chain, then executes each step
+through `maestro delegate --to <tool> --mode write` with a universal prompt template.
+Auto-confirm injection ensures non-blocking background execution. Structured return
+format enables context propagation between steps.
+</purpose>
+
+<required_reading>
+@~/.maestro/workflows/maestro-coordinate.md
+</required_reading>
+
+<deferred_reading>
+- [coordinate template](~/.maestro/templates/cli/prompts/coordinate-step.txt) — read when filling step prompts
+</deferred_reading>
+
+<context>
+$ARGUMENTS — user intent text, or special keywords (`continue`/`next`/`status`).
+
+**Flags:**
+- `-y` / `--yes` — Auto mode: skip clarification and confirmation
+- `-c` / `--continue` — Resume previous session
+- `--dry-run` — Show planned chain without executing
+- `--chain <name>` — Force a specific chain
+- `--tool <tool>` — CLI tool override (default: claude)
+</context>
+
+<execution>
+Follow '~/.maestro/workflows/maestro-coordinate.md' completely.
+</execution>
+
+<error_codes>
+| Code | Severity | Description | Recovery |
+|------|----------|-------------|----------|
+| E001 | error | No intent and project not initialized | Suggest maestro-init |
+| E002 | error | Clarity too low after 2 rounds | Ask to rephrase |
+| E003 | error | Step failed + abort | Suggest resume with -c |
+| E004 | error | Resume session not found | Show available sessions |
+| E005 | error | CLI tool unavailable | Try fallback tool |
+</error_codes>
+
+<success_criteria>
+- [ ] Intent classified and chain selected via detectTaskType + chainMap
+- [ ] Each step executed via `maestro delegate` with coordinate-step template
+- [ ] Auto-confirm injected, structured return parsed
+- [ ] Each completed step analyzed via `maestro delegate --to gemini --mode analysis`
+- [ ] Analysis hints injected into next step prompt via `{{ANALYSIS_HINTS}}`
+- [ ] Gemini sessions chained via `--resume` for accumulated context
+- [ ] Session state at .workflow/.maestro-coordinate/{session_id}/
+- [ ] Completion report with per-step status and quality scores
+</success_criteria>