maestro-flow 0.3.1 → 0.3.3

package/.claude/skills/team-testing/roles/generator/role.md

@@ -1,98 +1,98 @@
----
-role: generator
-prefix: TESTGEN
-inner_loop: true
-message_types:
-  success: tests_generated
-  revision: tests_revised
-  error: error
----
-
-# Test Generator
-
-Generate test code by layer (L1 unit / L2 integration / L3 E2E). Acts as the Generator in the Generator-Critic loop. Supports revision mode for GC loop iterations.
-
-## Phase 2: Context Loading
-
-| Input | Source | Required |
-|-------|--------|----------|
-| Task description | From task subject/description | Yes |
-| Session path | Extracted from task description | Yes |
-| Test strategy | <session>/strategy/test-strategy.md | Yes |
-| .msg/meta.json | <session>/wisdom/.msg/meta.json | No |
-
-1. Extract session path and layer from task description
-2. Load test specs: Run `ccw spec load --category test` for test framework conventions and coverage targets
-3. Read test strategy:
-
-```
-Read("<session>/strategy/test-strategy.md")
-```
-
-3. Read source files to test (from strategy priority_files, limit 20)
-4. Read .msg/meta.json for framework and scope context
-
-5. Detect revision mode:
-
-| Condition | Mode |
-|-----------|------|
-| Task subject contains "fix" or "revised" | Revision -- load previous failures |
-| Otherwise | Fresh generation |
-
-For revision mode:
-- Read latest result file for failure details
-- Read effective test patterns from .msg/meta.json
-
-6. Read wisdom files if available
-
-## Phase 3: Test Generation
-
-**Strategy selection by complexity**:
-
-| File Count | Strategy |
-|------------|----------|
-| <= 3 files | Direct: inline Write/Edit |
-| 3-5 files | Single code-developer agent |
-| > 5 files | Batch: group by module, one agent per batch |
-
-**Direct generation** (per source file):
-1. Generate test path: `<session>/tests/<layer>/<test-file>`
-2. Generate test code: happy path, edge cases, error handling
-3. Write test file
-
-**CLI delegation** (medium/high complexity):
-
-```
-Bash({
-  command: `maestro cli -p "PURPOSE: Generate <layer> tests using <framework> to achieve coverage target; success = all priority files covered with quality tests
-TASK: • Analyze source files • Generate test cases (happy path, edge cases, errors) • Write test files with proper structure • Ensure import resolution
-MODE: write
-CONTEXT: @<source-files> @<session>/strategy/test-strategy.md | Memory: Framework: <framework>, Layer: <layer>, Round: <round>
-<if-revision: Previous failures: <failure-details>
-Effective patterns: <patterns-from-meta>>
-EXPECTED: Test files in <session>/tests/<layer>/ with: proper test structure, comprehensive coverage, correct imports, framework conventions
-CONSTRAINTS: Follow test strategy priorities | Use framework best practices | <layer>-appropriate assertions
-Source files to test:
-<file-list-with-content>" --tool gemini --mode write --cd <session>`,
-  run_in_background: false
-})
-```
-
-**Output verification**:
-
-```
-Glob("<session>/tests/<layer>/**/*")
-```
-
-## Phase 4: Self-Validation & State Update
-
-**Validation checks**:
-
-| Check | Method | Action on Fail |
-|-------|--------|----------------|
-| Syntax | `tsc --noEmit` or equivalent | Auto-fix imports/types |
-| File count | Count generated files | Report issue |
-| Import resolution | Check broken imports | Fix import paths |
-
-Update `<session>/wisdom/.msg/meta.json` under `generator` namespace:
-- Merge `{ "generator": { test_files, layer, round, is_revision } }`
+---
+role: generator
+prefix: TESTGEN
+inner_loop: true
+message_types:
+  success: tests_generated
+  revision: tests_revised
+  error: error
+---
+
+# Test Generator
+
+Generate test code by layer (L1 unit / L2 integration / L3 E2E). Acts as the Generator in the Generator-Critic loop. Supports revision mode for GC loop iterations.
+
+## Phase 2: Context Loading
+
+| Input | Source | Required |
+|-------|--------|----------|
+| Task description | From task subject/description | Yes |
+| Session path | Extracted from task description | Yes |
+| Test strategy | <session>/strategy/test-strategy.md | Yes |
+| .msg/meta.json | <session>/wisdom/.msg/meta.json | No |
+
+1. Extract session path and layer from task description
+2. Load test specs: Run `ccw spec load --category test` for test framework conventions and coverage targets
+3. Read test strategy:
+
+```
+Read("<session>/strategy/test-strategy.md")
+```
+
+3. Read source files to test (from strategy priority_files, limit 20)
+4. Read .msg/meta.json for framework and scope context
+
+5. Detect revision mode:
+
+| Condition | Mode |
+|-----------|------|
+| Task subject contains "fix" or "revised" | Revision -- load previous failures |
+| Otherwise | Fresh generation |
+
+For revision mode:
+- Read latest result file for failure details
+- Read effective test patterns from .msg/meta.json
+
+6. Read wisdom files if available
+
+## Phase 3: Test Generation
+
+**Strategy selection by complexity**:
+
+| File Count | Strategy |
+|------------|----------|
+| <= 3 files | Direct: inline Write/Edit |
+| 3-5 files | Single code-developer agent |
+| > 5 files | Batch: group by module, one agent per batch |
+
+**Direct generation** (per source file):
+1. Generate test path: `<session>/tests/<layer>/<test-file>`
+2. Generate test code: happy path, edge cases, error handling
+3. Write test file
+
+**CLI delegation** (medium/high complexity):
+
+```
+Bash({
+  command: `maestro delegate "PURPOSE: Generate <layer> tests using <framework> to achieve coverage target; success = all priority files covered with quality tests
+TASK: • Analyze source files • Generate test cases (happy path, edge cases, errors) • Write test files with proper structure • Ensure import resolution
+MODE: write
+CONTEXT: @<source-files> @<session>/strategy/test-strategy.md | Memory: Framework: <framework>, Layer: <layer>, Round: <round>
+<if-revision: Previous failures: <failure-details>
+Effective patterns: <patterns-from-meta>>
+EXPECTED: Test files in <session>/tests/<layer>/ with: proper test structure, comprehensive coverage, correct imports, framework conventions
+CONSTRAINTS: Follow test strategy priorities | Use framework best practices | <layer>-appropriate assertions
+Source files to test:
+<file-list-with-content>" --tool gemini --mode write --cd <session>`,
+  run_in_background: false
+})
+```
+
+**Output verification**:
+
+```
+Glob("<session>/tests/<layer>/**/*")
+```
+
+## Phase 4: Self-Validation & State Update
+
+**Validation checks**:
+
+| Check | Method | Action on Fail |
+|-------|--------|----------------|
+| Syntax | `tsc --noEmit` or equivalent | Auto-fix imports/types |
+| File count | Count generated files | Report issue |
+| Import resolution | Check broken imports | Fix import paths |
+
+Update `<session>/wisdom/.msg/meta.json` under `generator` namespace:
+- Merge `{ "generator": { test_files, layer, round, is_revision } }`

package/.codex/skills/maestro-coordinate/SKILL.md

@@ -61,7 +61,7 @@ Intent  →  Resolve Chain  →  Step 1  →  Step 2  →  …  →  Step N  →
 
 ## Implementation
 
-> **Full implementation reference**: The complete `detectTaskType`, `detectNextAction`, and `chainMap` definitions (35+ intent patterns, 40+ chain types) are in `~/workflows/maestro-coordinate.codex.md`. Read that file for authoritative logic before executing any step.
+> **Full implementation reference**: The complete `detectTaskType`, `detectNextAction`, and `chainMap` definitions (35+ intent patterns, 40+ chain types) are in `~/.maestro/workflows/maestro-coordinate.codex.md`. Read that file for authoritative logic before executing any step.
 
 ### Session Initialization
 
@@ -213,9 +213,8 @@ The assembled prompt embeds the skill call so the agent knows exactly what to in
 ## TASK ASSIGNMENT
 
 ### MANDATORY FIRST STEPS
-1. Read: ~/.codex/agents/universal-executor.md
-2. Read: ~/workflows/maestro-coordinate.codex.md
-3. Read: ~/.codex/skills/{skill}/SKILL.md
+1. Read: ~/.maestro/workflows/maestro-coordinate.codex.md
+2. Read: ~/.codex/skills/{skill}/SKILL.md
 
 ---
 
@@ -308,4 +307,4 @@ Resume: $maestro-coordinate --continue
 6. **Close before spawn**: Always `close_agent` the current step agent before spawning the next
 7. **Dry-run is read-only**: Stop after displaying the chain plan — never spawn agents
 8. **Timeout handling**: One urge via `send_message`; if still timed out → mark `failed`
-9. **No CLI fallback**: All execution is agent-native — no `exec_command("maestro cli ...")`
+9. **No CLI fallback**: All execution is agent-native — no `exec_command("maestro delegate ...")`

package/.codex/skills/manage-issue-analyze/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: maestro-issue-analyze
-description: Root cause analysis for a specific issue via CLI exploration. Gathers codebase context (grep or semantic deep search), runs maestro cli gemini analysis, and attaches a structured analysis record to the issue in issues.jsonl.
+description: Root cause analysis for a specific issue via CLI exploration. Gathers codebase context (grep or semantic deep search), runs maestro delegate gemini analysis, and attaches a structured analysis record to the issue in issues.jsonl.
 argument-hint: "<ISS-ID> [--tool gemini|qwen] [--depth standard|deep]"
 allowed-tools: Read, Write, Bash, Glob, Grep
 ---
@@ -26,7 +26,7 @@ $maestro-issue-analyze "ISS-20260401-001 --tool qwen --depth standard"
 
 ## Overview
 
-Sequential 4-step pipeline: load issue → gather codebase context → run CLI analysis → attach analysis record. The CLI analysis step invokes `maestro cli --tool gemini --mode analysis` to produce a structured root-cause record written back into issues.jsonl. This is the first step in the issue resolution workflow: **analyze → plan → execute**.
+Sequential 4-step pipeline: load issue → gather codebase context → run CLI analysis → attach analysis record. The CLI analysis step invokes `maestro delegate --to gemini --mode analysis` to produce a structured root-cause record written back into issues.jsonl. This is the first step in the issue resolution workflow: **analyze → plan → execute**.
 
 ```
 Load Issue  →  Gather Context  →  CLI Analysis  →  Attach Record
@@ -119,7 +119,7 @@ CONSTRAINTS: Evidence required — file:line for each claim`
 
 Write(`/tmp/iss-analyze-${issue.id}.txt`, promptContent)
 functions.exec_command({
-  cmd: `maestro cli -p "$(cat /tmp/iss-analyze-${issue.id}.txt)" --tool ${tool} --mode analysis`,
+  cmd: `maestro delegate "$(cat /tmp/iss-analyze-${issue.id}.txt)" --to ${tool} --mode analysis`,
   workdir: "."
 })
 ```

package/.codex/skills/manage-issue-execute/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: maestro-issue-execute
-description: Execute a planned solution for an issue via dual-mode dispatch. Auto-detects server UP (POST to /api/execution/dispatch) or DOWN (direct maestro cli). Updates issue status on completion with next-step routing to close, debug, or verify.
+description: Execute a planned solution for an issue via dual-mode dispatch. Auto-detects server UP (POST to /api/execution/dispatch) or DOWN (direct maestro delegate). Updates issue status on completion with next-step routing to close, debug, or verify.
 argument-hint: "<ISS-ID> [--executor claude-code|codex|gemini] [--dry-run]"
 allowed-tools: Read, Write, Bash, Glob, Grep
 ---
@@ -27,7 +27,7 @@ $maestro-issue-execute "ISS-20260401-001 --executor gemini"
 
 ## Overview
 
-Sequential 4-step pipeline with conditional dispatch: load issue → dry-run check → detect mode → execute + update. Server-UP path posts to the orchestration API; Server-DOWN path invokes `maestro cli` directly. This is the third step in the issue resolution workflow: **analyze → plan → execute**.
+Sequential 4-step pipeline with conditional dispatch: load issue → dry-run check → detect mode → execute + update. Server-UP path posts to the orchestration API; Server-DOWN path invokes `maestro delegate` directly. This is the third step in the issue resolution workflow: **analyze → plan → execute**.
 
 ```
 Load Issue  →  [dry-run?]  →  Detect Mode  →  Dispatch  →  Update Status
@@ -79,7 +79,7 @@ const serverUp = healthCheck.stdout.trim() === "200"
 | Mode | Condition | Action |
 |------|-----------|--------|
 | Server UP | HTTP 200 from /health | POST to `/api/execution/dispatch` |
-| Server DOWN | Any other result | Direct `maestro cli` execution |
+| Server DOWN | Any other result | Direct `maestro delegate` execution |
 
 ```javascript
 functions.update_plan({
@@ -124,7 +124,7 @@ functions.exec_command({
 // Write prompt to temp file to avoid shell injection
 Write(`/tmp/iss-exec-${issue.id}.txt`, execPrompt)
 functions.exec_command({
-  cmd: `maestro cli -p "$(cat /tmp/iss-exec-${issue.id}.txt)" --tool ${executor === 'codex' ? 'codex' : 'claude'} --mode write`,
+  cmd: `maestro delegate "$(cat /tmp/iss-exec-${issue.id}.txt)" --to ${executor === 'codex' ? 'codex' : 'claude'} --mode write`,
   workdir: "."
 })
 ```

package/.codex/skills/manage-issue-plan/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: maestro-issue-plan
-description: Solution planning for a specific issue. Auto-detects analysis context, runs maestro cli planning, and attaches a structured solution record with ordered steps and verification criteria to the issue in issues.jsonl.
+description: Solution planning for a specific issue. Auto-detects analysis context, runs maestro delegate planning, and attaches a structured solution record with ordered steps and verification criteria to the issue in issues.jsonl.
 argument-hint: "<ISS-ID> [--tool gemini|qwen] [--from-analysis]"
 allowed-tools: Read, Write, Bash, Glob, Grep
 ---
@@ -82,7 +82,7 @@ CONSTRAINTS: Concrete steps only | File:line references required | No speculativ
 // Write prompt to temp file to avoid shell injection
 Write(`/tmp/iss-plan-${issueId}.txt`, prompt)
 functions.exec_command({
-  cmd: `maestro cli -p "$(cat /tmp/iss-plan-${issueId}.txt)" --tool ${tool} --mode analysis`,
+  cmd: `maestro delegate "$(cat /tmp/iss-plan-${issueId}.txt)" --to ${tool} --mode analysis`,
   workdir: "."
 })
 ```

package/.codex/skills/team-coordinate/SKILL.md

@@ -28,8 +28,8 @@ Universal team coordination skill: analyze task -> generate role-specs -> dispat
   (roles generated at runtime from task analysis)
 
   CLI Tools (callable by any worker):
-    maestro cli --mode analysis  - analysis and exploration
-    maestro cli --mode write     - code generation and modification
+    maestro delegate --mode analysis  - analysis and exploration
+    maestro delegate --mode write     - code generation and modification
 ```
 
 ## Delegation Lock
@@ -48,7 +48,7 @@ Before calling ANY tool, apply this check:
 | `Read` on `roles/`, `commands/`, `specs/` | ALLOWED | Loading own instructions |
 | `Read/Grep/Glob` on project source code | BLOCKED | Delegate to worker |
 | `Edit` on any file outside `.workflow/` | BLOCKED | Delegate to worker |
-| `Bash("maestro cli ...")` | BLOCKED | Only workers call CLI |
+| `Bash("maestro delegate ...")` | BLOCKED | Only workers call CLI |
 | `Bash` running build/test/lint commands | BLOCKED | Delegate to worker |
 
 **If a tool call is BLOCKED**: STOP. Create a task, spawn a worker.
@@ -65,8 +65,8 @@ Before calling ANY tool, apply this check:
 | Session path | `.workflow/.team/TC-<slug>-<date>/` |
 | Worker agent | `team-worker` |
 | Message bus | `mcp__maestro-tools__team_msg(session_id=<session-id>, ...)` |
-| CLI analysis | `maestro cli --mode analysis` |
-| CLI write | `maestro cli --mode write` |
+| CLI analysis | `maestro delegate --mode analysis` |
+| CLI write | `maestro delegate --mode write` |
 | Max roles | 5 |
 
 ## Role Router
@@ -92,8 +92,8 @@ Workers can use CLI tools for analysis and code operations:
 
 | Tool | Purpose |
 |------|---------|
-| maestro cli --mode analysis | Analysis, exploration, pattern discovery |
-| maestro cli --mode write | Code generation, modification, refactoring |
+| maestro delegate --mode analysis | Analysis, exploration, pattern discovery |
+| maestro delegate --mode write | Code generation, modification, refactoring |
 
 ### Dispatch
 

package/.codex/skills/team-coordinate/roles/coordinator/role.md

@@ -18,7 +18,7 @@ Orchestrate the team-coordinate workflow: task analysis, dynamic role-spec gener
 ```
 WRONG: Read("src/components/Button.tsx")           — worker work
 WRONG: Grep(pattern="useState", path="src/")       — worker work
-WRONG: Bash("maestro cli -p '...' --tool gemini")      — worker work
+WRONG: Bash("maestro delegate '...' --to gemini")      — worker work
 WRONG: Edit("src/utils/helper.ts", ...)             — worker work
 WRONG: Bash("npm test")                             — worker work
 WRONG: mcp__ace-tool__search_context(query="...")   — worker work

package/.codex/skills/team-lifecycle-v4/SKILL.md

@@ -71,7 +71,7 @@ Before calling ANY tool, apply this check:
 | `Read` on `roles/`, `commands/`, `specs/`, `templates/` | ALLOWED | Loading own instructions |
 | `Read/Grep/Glob` on project source code | BLOCKED | Delegate to worker |
 | `Edit` on any file outside `.workflow/` | BLOCKED | Delegate to worker |
-| `Bash("maestro cli ...")` | BLOCKED | Only workers call CLI |
+| `Bash("maestro delegate ...")` | BLOCKED | Only workers call CLI |
 | `Bash` running build/test/lint commands | BLOCKED | Delegate to worker |
 
 **If a tool call is BLOCKED**: STOP. Create a task, spawn a worker.
@@ -86,7 +86,7 @@ Before calling ANY tool, apply this check:
 - **Session path**: `.workflow/.team/TLV4-<slug>-<date>/`
 - **State file**: `<session>/tasks.json`
 - **Discovery files**: `<session>/discoveries/{task_id}.json`
-- **CLI tools**: `maestro cli --mode analysis` (read-only), `maestro cli --mode write` (modifications)
+- **CLI tools**: `maestro delegate --mode analysis` (read-only), `maestro delegate --mode write` (modifications)
 
 ## Worker Spawn Template
 

package/.codex/skills/team-lifecycle-v4/instructions/agent-instruction.md

@@ -27,7 +27,7 @@ This instruction is loaded by team-worker agents when spawned with roles: `analy
 
 2. **Explore domain** (use CLI analysis tools):
    ```bash
-   maestro cli -p "PURPOSE: Research domain for {requirement}
+   maestro delegate "PURPOSE: Research domain for {requirement}
    TASK: • Identify problem statement • Define target users • Extract constraints • Map integration points
    CONTEXT: @**/* | Memory: {requirement}
    EXPECTED: Structured research context with problem/users/domain/constraints
@@ -294,7 +294,7 @@ This instruction is loaded by team-worker agents when spawned with roles: `analy
 
 2. **Explore codebase** (use CLI analysis tools):
    ```bash
-   maestro cli -p "PURPOSE: Explore codebase for {requirement}
+   maestro delegate "PURPOSE: Explore codebase for {requirement}
    TASK: • Identify relevant files • Find existing patterns • Locate integration points
    CONTEXT: @**/* | Memory: {requirement}
    EXPECTED: Exploration findings with file paths and patterns

package/.codex/skills/team-lifecycle-v4/roles/analyst/role.md

@@ -36,7 +36,7 @@ Research and codebase exploration for context gathering.
 4. If topic references file (@path or .md/.txt) -> read it
 5. CLI seed analysis:
    ```
-   Bash({ command: `maestro cli -p "PURPOSE: Analyze topic, extract structured seed info.
+   Bash({ command: `maestro delegate "PURPOSE: Analyze topic, extract structured seed info.
    TASK: * Extract problem statement * Identify target users * Determine domain
    * List constraints * Identify 3-5 exploration dimensions
    TOPIC: <topic-content>
@@ -54,7 +54,7 @@ Research and codebase exploration for context gathering.
 
 When project detected:
 ```
-Bash({ command: `maestro cli -p "PURPOSE: Explore codebase for context
+Bash({ command: `maestro delegate "PURPOSE: Explore codebase for context
 TASK: * Identify tech stack * Map architecture patterns * Document conventions * List integration points
 MODE: analysis
 CONTEXT: @**/*

package/.codex/skills/team-lifecycle-v4/roles/coordinator/role.md

@@ -14,7 +14,7 @@ Orchestrate team-lifecycle-v4: analyze -> dispatch -> spawn -> monitor -> report
 ```
 WRONG: Read("src/...")                              — worker work
 WRONG: Grep/Glob on project source                  — worker work
-WRONG: Bash("maestro cli -p '...' --tool gemini")       — worker work
+WRONG: Bash("maestro delegate '...' --to gemini")       — worker work
 WRONG: Edit/Write on project source files            — worker work
 WRONG: Bash("npm test"), Bash("tsc"), etc.           — worker work
 ```
@@ -47,7 +47,7 @@ WRONG: Bash("npm test"), Bash("tsc"), etc.           — worker work
 - Modify task output artifacts
 - Spawn workers with general-purpose agent (MUST use team_worker)
 - Generate more than 5 worker roles
-- Call CLI tools (maestro cli) — only workers use CLI
+- Call CLI tools (maestro delegate) — only workers use CLI
 
 ## Command Execution Protocol
 When coordinator needs to execute a specific phase:

package/.codex/skills/team-lifecycle-v4/roles/executor/commands/implement.md

@@ -51,7 +51,7 @@ CONSTRAINTS: Only modify listed files | Follow existing patterns
 
 CLI call:
 ```
-Bash(`maestro cli -p "<prompt>" --tool <tool> --mode write --rule development-implement-feature`)
+Bash(`maestro delegate "<prompt>" --to <tool> --mode write --rule development-implement-feature`)
 ```
 
 Resume strategy:

package/.codex/skills/team-lifecycle-v4/roles/planner/role.md

@@ -36,7 +36,7 @@ Codebase-informed implementation planning with complexity assessment.
 3. Check <session>/explorations/cache-index.json for cached explorations
 4. Explore codebase (cache-aware):
    ```
-   Bash({ command: `maestro cli -p "PURPOSE: Explore codebase to inform planning
+   Bash({ command: `maestro delegate "PURPOSE: Explore codebase to inform planning
    TASK: * Search for relevant patterns * Identify files to modify * Document integration points
    MODE: analysis
    CONTEXT: @**/*
@@ -48,7 +48,7 @@ Codebase-informed implementation planning with complexity assessment.
 
 Generate plan.json + .task/TASK-*.json:
 ```
-Bash({ command: `maestro cli -p "PURPOSE: Generate implementation plan from exploration results
+Bash({ command: `maestro delegate "PURPOSE: Generate implementation plan from exploration results
 TASK: * Create plan.json overview * Generate TASK-*.json files (2-7 tasks) * Define dependencies * Set convergence criteria
 MODE: write
 CONTEXT: @<session>/explorations/*.json

package/.codex/skills/team-lifecycle-v4/roles/writer/role.md

@@ -61,7 +61,7 @@ Template-driven document generation with progressive dependency loading.
 
 CLI generation:
 ```
-Bash({ command: `maestro cli -p "PURPOSE: Generate <doc-type> document following template
+Bash({ command: `maestro delegate "PURPOSE: Generate <doc-type> document following template
 TASK: * Load template * Apply spec config and discovery context * Integrate prior feedback * Generate all sections
 MODE: write
 CONTEXT: @<session>/spec/*.json @<template-path>

package/.codex/skills/team-quality-assurance/SKILL.md

@@ -63,7 +63,7 @@ Before calling ANY tool, apply this check:
 | `Read` on `roles/`, `commands/`, `specs/` | ALLOWED | Loading own instructions |
 | `Read/Grep/Glob` on project source code | BLOCKED | Delegate to worker |
 | `Edit` on any file outside `.workflow/` | BLOCKED | Delegate to worker |
-| `Bash("maestro cli ...")` | BLOCKED | Only workers call CLI |
+| `Bash("maestro delegate ...")` | BLOCKED | Only workers call CLI |
 | `Bash` running build/test/lint commands | BLOCKED | Delegate to worker |
 
 **If a tool call is BLOCKED**: STOP. Create a task, spawn a worker.
@@ -77,7 +77,7 @@ Before calling ANY tool, apply this check:
 - **Session prefix**: `QA`
 - **Session path**: `.workflow/.team/QA-<slug>-<date>/`
 - **Team name**: `quality-assurance`
-- **CLI tools**: `maestro cli --mode analysis` (read-only), `maestro cli --mode write` (modifications)
+- **CLI tools**: `maestro delegate --mode analysis` (read-only), `maestro delegate --mode write` (modifications)
 - **Message bus**: `mcp__maestro-tools__team_msg(session_id=<session-id>, ...)`
 
 ## Worker Spawn Template

package/.codex/skills/team-quality-assurance/roles/coordinator/role.md

@@ -12,7 +12,7 @@ Orchestrate team-quality-assurance: analyze -> dispatch -> spawn -> monitor -> r
 **FORBIDDEN** (even if the task seems trivial):
 ```
 WRONG: Read/Grep/Glob on project source code        — worker work
-WRONG: Bash("maestro cli ...")                           — worker work
+WRONG: Bash("maestro delegate ...")                           — worker work
 WRONG: Edit/Write on project source files            — worker work
 WRONG: Bash("npm test"), Bash("tsc"), etc.           — worker work
 ```
@@ -45,7 +45,7 @@ WRONG: Bash("npm test"), Bash("tsc"), etc.           — worker work
 - Modify test files or source code
 - Spawn workers with general-purpose agent (MUST use team-worker)
 - Generate more than 6 worker roles
-- Call CLI tools (maestro cli) — only workers use CLI
+- Call CLI tools (maestro delegate) — only workers use CLI
 
 ## Command Execution Protocol
 When coordinator needs to execute a specific phase:

package/.codex/skills/team-quality-assurance/roles/scout/role.md

@@ -39,7 +39,7 @@ Scan codebase from multiple perspectives (bug, security, test-coverage, code-qua
 
 **Low complexity**: Use `mcp__ace-tool__search_context` for quick pattern-based scan.
 
-**Medium/High complexity**: CLI fan-out -- one `maestro cli --mode analysis` per perspective:
+**Medium/High complexity**: CLI fan-out -- one `maestro delegate --mode analysis` per perspective:
 
 For each active perspective, build prompt:
 ```
@@ -50,7 +50,7 @@ CONTEXT: @<scan-scope>
 EXPECTED: List of findings with severity (critical/high/medium/low), file:line references, description
 CONSTRAINTS: Focus on actionable findings only
 ```
-Execute via: `maestro cli -p "<prompt>" --tool gemini --mode analysis`
+Execute via: `maestro delegate "<prompt>" --to gemini --mode analysis`
 
 After all perspectives complete:
 - Parse CLI outputs into structured findings

package/.codex/skills/team-review/SKILL.md

@@ -61,7 +61,7 @@ Before calling ANY tool, apply this check:
 | `Read` on `roles/`, `commands/`, `specs/` | ALLOWED | Loading own instructions |
 | `Read/Grep/Glob` on project source code | BLOCKED | Delegate to worker |
 | `Edit` on any file outside `.workflow/` | BLOCKED | Delegate to worker |
-| `Bash("maestro cli ...")` | BLOCKED | Only workers call CLI |
+| `Bash("maestro delegate ...")` | BLOCKED | Only workers call CLI |
 | `Bash` running build/test/lint commands | BLOCKED | Delegate to worker |
 
 **If a tool call is BLOCKED**: STOP. Create a task, spawn a worker.
@@ -75,7 +75,7 @@ Before calling ANY tool, apply this check:
 - **Session prefix**: `RV`
 - **Session path**: `.workflow/.team/RV-<slug>-<date>/`
 - **Team name**: `review`
-- **CLI tools**: `maestro cli --mode analysis` (read-only), `maestro cli --mode write` (modifications)
+- **CLI tools**: `maestro delegate --mode analysis` (read-only), `maestro delegate --mode write` (modifications)
 - **Message bus**: `mcp__maestro-tools__team_msg(session_id=<session-id>, ...)`
 
 ## Worker Spawn Template

package/.codex/skills/team-review/roles/coordinator/role.md

@@ -12,7 +12,7 @@ Orchestrate team-review: parse target -> detect mode -> dispatch task chain -> m
 **FORBIDDEN** (even if the task seems trivial):
 ```
 WRONG: Read/Grep/Glob on project source code        — worker work
-WRONG: Bash("maestro cli ...")                           — worker work
+WRONG: Bash("maestro delegate ...")                           — worker work
 WRONG: Bash("semgrep/eslint/tsc ...")                — worker work
 WRONG: Edit/Write on project source files            — worker work
 ```
@@ -45,7 +45,7 @@ WRONG: Edit/Write on project source files            — worker work
 - Perform code review or scanning directly
 - Bypass worker roles
 - Spawn workers with general-purpose agent (MUST use team_worker)
-- Call CLI tools (maestro cli) — only workers use CLI
+- Call CLI tools (maestro delegate) — only workers use CLI
 
 ## Command Execution Protocol
 When coordinator needs to execute a specific phase:

package/.codex/skills/team-review/roles/reviewer/role.md

@@ -52,7 +52,7 @@ Build prompt per group requesting 6 enrichment fields per finding:
 - `fix_complexity`: low / medium / high
 - `fix_dependencies`: finding IDs that must be fixed first
 
-Execute via `maestro cli --tool gemini --mode analysis --rule analysis-diagnose-bug-root-cause` (fallback: qwen -> codex). Parse JSON array responses, merge with originals (CLI-enriched replace originals, unenriched get defaults). Write `<session>/review/enriched-findings.json`.
+Execute via `maestro delegate --to gemini --mode analysis --rule analysis-diagnose-bug-root-cause` (fallback: qwen -> codex). Parse JSON array responses, merge with originals (CLI-enriched replace originals, unenriched get defaults). Write `<session>/review/enriched-findings.json`.
 
 ## Phase 4: Report Generation
 

package/.codex/skills/team-review/roles/scanner/role.md

@@ -59,7 +59,7 @@ Build prompt with target file patterns, toolchain dedup summary, and per-dimensi
 - PRF: Algorithm complexity, N+1 queries, unnecessary sync, memory leaks, missing caching
 - MNT: Architectural coupling, abstraction leaks, convention violations, dead code
 
-Execute via `maestro cli --tool gemini --mode analysis --rule analysis-review-code-quality` (fallback: qwen -> codex). Parse JSON array response, validate required fields (dimension, title, location.file), enforce per-dimension limit (max 5 each), filter minimum severity (medium+). Write `<session>/scan/semantic-findings.json`.
+Execute via `maestro delegate --to gemini --mode analysis --rule analysis-review-code-quality` (fallback: qwen -> codex). Parse JSON array response, validate required fields (dimension, title, location.file), enforce per-dimension limit (max 5 each), filter minimum severity (medium+). Write `<session>/scan/semantic-findings.json`.
 
 ## Phase 4: Aggregate & Output
 

package/.codex/skills/team-tech-debt/SKILL.md

@@ -63,7 +63,7 @@ Before calling ANY tool, apply this check:
 | `Read` on `roles/`, `commands/`, `specs/` | ALLOWED | Loading own instructions |
 | `Read/Grep/Glob` on project source code | BLOCKED | Delegate to worker |
 | `Edit` on any file outside `.workflow/` | BLOCKED | Delegate to worker |
-| `Bash("maestro cli ...")` | BLOCKED | Only workers call CLI |
+| `Bash("maestro delegate ...")` | BLOCKED | Only workers call CLI |
 | `Bash` running build/test/lint commands | BLOCKED | Delegate to worker |
 
 **If a tool call is BLOCKED**: STOP. Create a task, spawn a worker.
@@ -76,7 +76,7 @@ Before calling ANY tool, apply this check:
 
 - **Session prefix**: `TD`
 - **Session path**: `.workflow/.team/TD-<slug>-<date>/`
-- **CLI tools**: `maestro cli --mode analysis` (read-only), `maestro cli --mode write` (modifications)
+- **CLI tools**: `maestro delegate --mode analysis` (read-only), `maestro delegate --mode write` (modifications)
 - **Message bus**: `mcp__maestro-tools__team_msg(session_id=<session-id>, ...)`
 - **Max GC rounds**: 3
 

package/.codex/skills/team-tech-debt/roles/coordinator/role.md

@@ -12,7 +12,7 @@
 **FORBIDDEN** (even if the task seems trivial):
 ```
 WRONG: Read/Grep/Glob on project source code        — worker work
-WRONG: Bash("maestro cli ...")                           — worker work
+WRONG: Bash("maestro delegate ...")                           — worker work
 WRONG: Edit/Write on project source files            — worker work
 ```
 

package/.codex/skills/team-tech-debt/roles/executor/role.md

@@ -37,7 +37,7 @@ For each batch, use CLI tool for implementation:
 **Per-batch delegation**:
 
 ```bash
-maestro cli -p "PURPOSE: Apply tech debt fixes in batch; success = all items fixed without breaking changes
+maestro delegate "PURPOSE: Apply tech debt fixes in batch; success = all items fixed without breaking changes
 TASK: <batch-type-specific-tasks>
 MODE: write
 CONTEXT: @<worktree-path>/**/* | Memory: Remediation plan context

package/.codex/skills/team-tech-debt/roles/scanner/role.md

@@ -56,7 +56,7 @@ Multi-dimension tech debt scanner. Scan codebase across 5 dimensions (code, arch
 - Classify findings into dimensions
 
 **Medium/High Complexity** (Fan-out):
-- Fan-out A: CLI exploration (structure, patterns, dependencies angles) via `maestro cli --tool gemini --mode analysis`
+- Fan-out A: CLI exploration (structure, patterns, dependencies angles) via `maestro delegate --to gemini --mode analysis`
 - Fan-out B: CLI dimension analysis (parallel gemini per dimension -- code, architecture, testing, dependency, documentation)
 - Fan-out C (High only): Multi-perspective Gemini analysis (security, performance, code-quality, architecture)
 - Fan-in: Merge results, cross-deduplicate by file:line, boost severity for multi-source findings