maestro-flow 0.3.8 → 0.3.9

package/.claude/commands/learn-decompose.md

@@ -145,9 +145,9 @@ Build the decomposition report grouped by dimension:
 6. Display summary with counts and next steps
 
 **Next-step routing:**
-- Follow-along on a specific pattern → `Skill({ skill: "learn-follow", args: "<anchor-file>" })`
-- Get second opinion on findings → `Skill({ skill: "learn-second-opinion", args: "<target>" })`
-- Add all new patterns to specs → `Skill({ skill: "spec-add", args: "pattern ..." })` per pattern
+- Follow-along on a specific pattern → `/learn-follow <anchor-file>`
+- Get second opinion on findings → `/learn-second-opinion <target>`
+- Add all new patterns to specs → `/spec-add pattern ...` per pattern
 </execution>
 
 <error_codes>

package/.claude/commands/learn-follow.md

@@ -134,17 +134,17 @@ Build a structured summary document:
 5. Display summary with key findings and next steps
 
 **Next-step routing:**
-- Deep dive into a discovered pattern → `Skill({ skill: "learn-decompose", args: "<path>" })`
-- Add undocumented pattern to specs → `Skill({ skill: "spec-add", args: "pattern <description>" })`
-- Get second opinion on a finding → `Skill({ skill: "learn-second-opinion", args: "<file>" })`
-- Browse related wiki entries → `Skill({ skill: "wiki-digest", args: "<topic>" })`
+- Deep dive into a discovered pattern → `/learn-decompose <path>`
+- Add undocumented pattern to specs → `/spec-add pattern <description>`
+- Get second opinion on a finding → `/learn-second-opinion <file>`
+- Browse related wiki entries → `/wiki-digest <topic>`
 </execution>
 
 <error_codes>
 | Code | Severity | Condition | Recovery |
 |------|----------|-----------|----------|
 | E001 | error | Target not resolvable (file not found, wiki ID not found, search returned 0) | Check path/ID, or rephrase topic for search |
-| E002 | error | `.workflow/` not initialized | Run `Skill({ skill: "maestro-init" })` first |
+| E002 | error | `.workflow/` not initialized | Run `/maestro-init` first |
 | W001 | warning | Wiki graph unavailable (no .workflow/ wiki entries) — skipping context web | Proceed with code-only context (imports/exports) |
 | W002 | warning | coding-conventions.md not found — skipping convention comparison | Patterns flagged as "unknown convention status" |
 | W003 | warning | Target is very large (>1000 lines) — auto-switching to shallow depth | Use --depth deep to override |

package/.claude/commands/learn-investigate.md

@@ -162,9 +162,9 @@ Write final `report.md`:
 3. Display summary with answer and next steps
 
 **Next-step routing:**
-- Save finding to specs → `Skill({ skill: "spec-add", args: "debug <finding>" })`
-- Follow-along on discovered code → `Skill({ skill: "learn-follow", args: "<path>" })`
-- Decompose patterns found → `Skill({ skill: "learn-decompose", args: "<module>" })`
+- Save finding to specs → `/spec-add debug <finding>`
+- Follow-along on discovered code → `/learn-follow <path>`
+- Decompose patterns found → `/learn-decompose <module>`
 - Create wiki entry for understanding → `maestro wiki create --type note`
 </execution>
 

package/.claude/commands/learn-retro.md

@@ -257,12 +257,12 @@ Write `.workflow/learning/retro-{date}.json` with structured data.
 4. Display summary
 
 **Next-step routing:**
-- Browse insights → `Skill({ skill: "manage-learn", args: "list --tag retro" })`
-- Deep dive on high-churn file → `Skill({ skill: "learn-follow", args: "<path>" })`
-- Fix test gaps → `Skill({ skill: "quality-test-gen", args: "<area>" })`
-- Create issue for questionable decision → `Skill({ skill: "manage-issue", args: "create ..." })`
-- Investigate stale decision → `Skill({ skill: "learn-investigate", args: "<question>" })`
-- Full phase retrospective → `Skill({ skill: "quality-retrospective" })`
+- Browse insights → `/manage-learn list --tag retro`
+- Deep dive on high-churn file → `/learn-follow <path>`
+- Fix test gaps → `/quality-test-gen <area>`
+- Create issue for questionable decision → `/manage-issue create ...`
+- Investigate stale decision → `/learn-investigate <question>`
+- Full phase retrospective → `/quality-retrospective`
 </execution>
 
 <error_codes>

package/.claude/commands/learn-second-opinion.md

@@ -136,9 +136,9 @@ Across all perspectives (or from single agent in challenge/consult):
 4. Display summary with verdict and recommendations
 
 **Next-step routing:**
-- Create issue for a finding → `Skill({ skill: "manage-issue", args: "create <description>" })`
-- Decompose patterns found → `Skill({ skill: "learn-decompose", args: "<path>" })`
-- Follow-along on the code → `Skill({ skill: "learn-follow", args: "<path>" })`
+- Create issue for a finding → `/manage-issue create <description>`
+- Decompose patterns found → `/learn-decompose <path>`
+- Follow-along on the code → `/learn-follow <path>`
 </execution>
 
 <error_codes>

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

@@ -1,99 +1,123 @@
----
-name: maestro-analyze
-description: Multi-dimensional analysis with CLI exploration, decision extraction, and intent tracking
-argument-hint: "<phase|topic> [-y] [-c] [-q]"
-allowed-tools:
-  - Read
-  - Write
-  - Edit
-  - Bash
-  - Glob
-  - Grep
-  - Agent
-  - AskUserQuestion
----
-<purpose>
-Perform multi-dimensional analysis of a technical proposal, decision, or architecture choice through iterative CLI-assisted exploration and interactive discussion. Produces a discussion timeline (discussion.md) with evolving understanding, multi-perspective findings, Decision Recording Protocol, Intent Coverage tracking, and a final conclusions package with Go/No-Go recommendation.
-
-Combines structured 6-dimension scoring with iterative deepening and decision extraction. Replaces both analysis and decision-capture workflows — produces analysis.md (scoring) AND context.md (Locked/Free/Deferred decisions for plan).
-
-Use `-q` for quick decision extraction only (skip exploration + scoring).
-</purpose>
-
-<required_reading>
-@~/.maestro/workflows/analyze.md
-</required_reading>
-
-<deferred_reading>
-- [scratch-index.json](~/.maestro/templates/scratch-index.json) — read when operating in scratch mode
-- [index.json](~/.maestro/templates/index.json) — read when operating in phase mode
-</deferred_reading>
-
-<context>
-$ARGUMENTS -- phase number for phase mode, topic text for scratch mode, with optional flags.
-
-**Flags:**
-- `-y` / `--yes`: Auto mode — skip interactive scoping, use recommended defaults, auto-deepen
-- `-c` / `--continue`: Resume from existing session (auto-detect session folder + discussion.md)
-- `-q` / `--quick`: Quick mode — skip exploration + scoring, go straight to decision extraction (context.md only)
-
-**Phase mode** (number): resolves phase directory from state.json + roadmap, updates index.json status to "exploring".
-**Scratch mode** (text): creates `.workflow/scratch/analyze-{slug}-{date}/` with index.json from scratch-index template (type="analyze").
-
-**Output artifacts:**
-| Artifact | Mode | Description |
-|----------|------|-------------|
-| `context.md` | both | Locked/Free/Deferred decisions for downstream plan |
-| `discussion.md` | full | Full discussion timeline with TOC, Current Understanding, rounds, decisions, intent coverage |
-| `analysis.md` | full | Executive summary with 6-dimension scores and risk matrix |
-| `conclusions.json` | full | Final synthesis with recommendations, decision trail, intent coverage |
-| `explorations.json` | full | Codebase exploration findings (single perspective) |
-| `perspectives.json` | full | Multi-perspective findings with synthesis (if multi-perspective) |
-</context>
-
-<execution>
-Follow '~/.maestro/workflows/analyze.md' completely.
-
-**Handoff:** context.md is consumed by maestro-plan (Step 4 loads Locked/Free/Deferred decisions).
-
-**Next-step routing on completion:**
-
-Phase mode:
-- Go recommendation, UI work needed → Skill({ skill: "maestro-ui-design", args: "{phase}" })
-- Go recommendation, ready to plan → Skill({ skill: "maestro-plan", args: "{phase}" })
-- No-Go recommendation → revisit requirements or Skill({ skill: "maestro-brainstorm", args: "{topic}" })
-
-Scratch mode:
-- Ready to plan → Skill({ skill: "maestro-plan", args: "--dir {scratch_dir}" })
-- Need more exploration → Skill({ skill: "maestro-analyze", args: "{topic} -c" })
-</execution>
-
-<error_codes>
-| Code | Severity | Condition | Recovery |
-|------|----------|-----------|----------|
-| E001 | error | Analysis subject required (no arguments provided) | Prompt user for phase number or topic text |
-| E002 | error | Phase directory not found | List available phases, prompt user to select |
-| W001 | warning | CLI exploration failed | Continue with available context, note limitation |
-| W002 | warning | CLI analysis timeout | Retry with shorter prompt, or skip perspective |
-| W003 | warning | Insufficient evidence for scoring dimensions | Note low-confidence dimensions, proceed with available evidence |
-| W004 | warning | Max rounds reached (5) | Force synthesis, offer continuation option |
-</error_codes>
-
-<success_criteria>
-Full mode:
-- [ ] CLI exploration completed with code anchors and call chains
-- [ ] discussion.md created with full timeline, TOC, Current Understanding
-- [ ] analysis.md written with all 6 dimensions scored with evidence
-- [ ] conclusions.json created with recommendations and decision trail
-- [ ] Intent Coverage tracked and verified (no unresolved ❌ items)
-
-Both modes (full + quick):
-- [ ] context.md written with all decisions classified as Locked/Free/Deferred
-- [ ] Gray areas identified through phase-specific analysis
-- [ ] Decision Recording Protocol applied to all decisions
-- [ ] Scope creep redirected to Deferred section
-- [ ] Deferred items auto-created as issues (if any)
-- [ ] project.md Key Decisions updated with Locked decisions (phase mode)
-- [ ] Next step routed (ui-design/plan for Go, brainstorm for No-Go)
-- [ ] index.json timestamps updated
-</success_criteria>
+---
+name: maestro-analyze
+description: Multi-dimensional analysis with CLI exploration, decision extraction, and intent tracking
+argument-hint: "[phase|topic] [-y] [-c] [-q]"
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Glob
+  - Grep
+  - Agent
+  - AskUserQuestion
+---
+<purpose>
+Perform multi-dimensional analysis of a technical proposal, decision, or architecture choice through iterative CLI-assisted exploration and interactive discussion. Produces a discussion timeline (discussion.md) with evolving understanding, multi-perspective findings, Decision Recording Protocol, Intent Coverage tracking, and a final conclusions package with Go/No-Go recommendation.
+
+Combines structured 6-dimension scoring with iterative deepening and decision extraction. Replaces both analysis and decision-capture workflows — produces analysis.md (scoring) AND context.md (Locked/Free/Deferred decisions for plan).
+
+Use `-q` for quick decision extraction only (skip exploration + scoring).
+</purpose>
+
+<required_reading>
+@~/.maestro/workflows/analyze.md
+</required_reading>
+
+<deferred_reading>
+- [state.json](~/.maestro/templates/state.json) — read when registering artifact
+</deferred_reading>
+
+<context>
+$ARGUMENTS -- phase number for milestone-scoped, topic text for adhoc/standalone mode, no args for milestone-wide.
+
+**Flags:**
+- `-y` / `--yes`: Auto mode — skip interactive scoping, use recommended defaults, auto-deepen
+- `-c` / `--continue`: Resume from existing session (auto-detect session folder + discussion.md)
+- `-q` / `--quick`: Quick mode — skip exploration + scoring, go straight to decision extraction (context.md only)
+
+**Scope routing (per architecture):**
+
+| Invocation | Precondition | Scope | Behavior |
+|-----------|-------------|-------|----------|
+| `analyze` (no args) | init + roadmap | milestone | Analyze current milestone's all phases |
+| `analyze 1` | init + roadmap | phase | Analyze phase 1 only |
+| `analyze "topic"` (has milestone) | none | adhoc | Analyze topic, affiliated with current milestone |
+| `analyze "topic"` (no milestone) | none | standalone | Analyze topic, no milestone affiliation |
+
+**Scope detection rule**: Text argument + `state.json.current_milestone` non-null → adhoc. Text argument + no milestone → standalone. No args + no roadmap → error (need topic or roadmap).
+
+**Output directory**: `scratch/analyze-{slug}-{date}/` (relative to `.workflow/`)
+
+**Artifact registration**: On completion, register artifact in `state.json.artifacts[]`:
+```jsonc
+{
+  "id": "ANL-{NNN}",
+  "type": "analyze",
+  "milestone": "{current_milestone or null}",
+  "phase": "{phase_number or null}",
+  "scope": "{milestone|phase|adhoc|standalone}",
+  "path": "scratch/analyze-{slug}-{date}",
+  "status": "completed",
+  "depends_on": null,
+  "harvested": false,
+  "created_at": "...",
+  "completed_at": "..."
+}
+```
+
+**Output artifacts:**
+| Artifact | Mode | Description |
+|----------|------|-------------|
+| `context.md` | both | Locked/Free/Deferred decisions for downstream plan |
+| `discussion.md` | full | Full discussion timeline with TOC, Current Understanding, rounds, decisions, intent coverage |
+| `analysis.md` | full | Executive summary with 6-dimension scores and risk matrix |
+| `conclusions.json` | full | Final synthesis with recommendations, decision trail, intent coverage |
+| `explorations.json` | full | Codebase exploration findings (single perspective) |
+| `perspectives.json` | full | Multi-perspective findings with synthesis (if multi-perspective) |
+</context>
+
+<execution>
+Follow '~/.maestro/workflows/analyze.md' completely.
+
+**Handoff:** context.md is consumed by maestro-plan (loads Locked/Free/Deferred decisions).
+
+**Next-step routing on completion:**
+
+Phase/Milestone scope:
+- Go recommendation, UI work needed → `/maestro-ui-design {phase}`
+- Go recommendation, ready to plan → `/maestro-plan` or `/maestro-plan {phase}`
+- No-Go recommendation → revisit requirements or `/maestro-brainstorm {topic}`
+
+Adhoc/Standalone scope:
+- Ready to plan → `/maestro-plan --dir {scratch_dir}`
+- Need more exploration → `/maestro-analyze {topic} -c`
+</execution>
+
+<error_codes>
+| Code | Severity | Condition | Recovery |
+|------|----------|-----------|----------|
+| E001 | error | No args and no roadmap (cannot determine scope) | Prompt user for topic text or create roadmap first |
+| W001 | warning | CLI exploration failed | Continue with available context, note limitation |
+| W002 | warning | CLI analysis timeout | Retry with shorter prompt, or skip perspective |
+| W003 | warning | Insufficient evidence for scoring dimensions | Note low-confidence dimensions, proceed with available evidence |
+| W004 | warning | Max rounds reached (5) | Force synthesis, offer continuation option |
+</error_codes>
+
+<success_criteria>
+Full mode:
+- [ ] CLI exploration completed with code anchors and call chains
+- [ ] discussion.md created with full timeline, TOC, Current Understanding
+- [ ] analysis.md written with all 6 dimensions scored with evidence
+- [ ] conclusions.json created with recommendations and decision trail
+- [ ] Intent Coverage tracked and verified (no unresolved ❌ items)
+
+Both modes (full + quick):
+- [ ] context.md written with all decisions classified as Locked/Free/Deferred
+- [ ] Gray areas identified through phase-specific analysis
+- [ ] Decision Recording Protocol applied to all decisions
+- [ ] Scope creep redirected to Deferred section
+- [ ] Deferred items auto-created as issues (if any)
+- [ ] Artifact registered in state.json with correct scope/milestone/phase
+- [ ] Next step routed (ui-design/plan for Go, brainstorm for No-Go)
+</success_criteria>

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

@@ -30,8 +30,8 @@ $ARGUMENTS -- topic text for auto mode, or role name for single role mode.
 
 **Auto mode**: topic text (e.g., "Build real-time collaboration platform") triggers full pipeline.
 **Single role mode**: valid role name (e.g., "system-architect") runs one role analysis.
-**Phase mode** (number): resolves phase directory, creates .brainstorming/ inside it.
-**Scratch mode** (text): creates `.workflow/scratch/brainstorm-{slug}-{date}/`.
+**All output** goes to `.workflow/scratch/brainstorm-{slug}-{date}/`.
+**Artifact registration**: On completion, registers artifact (type=brainstorm) in state.json.
 
 **Valid roles**: data-architect, product-manager, product-owner, scrum-master, subject-matter-expert, system-architect, test-strategist, ui-designer, ux-expert
 

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

@@ -1,97 +1,137 @@
----
-name: maestro-execute
-description: Execute phase plan with wave-based parallel execution and atomic commits
-argument-hint: "<phase> [--auto-commit] [--method agent|cli|auto] [--executor <tool>] [--dir <path>]"
-allowed-tools:
-  - Read
-  - Write
-  - Edit
-  - Bash
-  - Glob
-  - Grep
-  - Agent
-  - AskUserQuestion
----
-<purpose>
-Execute all tasks in a phase plan using wave-based parallel execution with dependency-aware ordering. Invoked after Skill({ skill: "maestro-plan" }) produces a confirmed plan.json. Produces task summaries, updated task statuses, commits, and execution progress in index.json.
-</purpose>
-
-<required_reading>
-@~/.maestro/workflows/execute.md
-</required_reading>
-
-<deferred_reading>
-- [task.json](~/.maestro/templates/task.json) — read when reading task definitions
-- [index.json](~/.maestro/templates/index.json) — read when updating phase index
-</deferred_reading>
-
-<context>
-Phase: $ARGUMENTS (required -- phase number or slug)
-
-**Flags:**
-- `--auto-commit` -- Automatically commit after each task completion
-- `--method agent|cli|auto` -- Override execution method (default: from config.json or index.json)
-- `--executor <tool>` -- Default CLI tool: gemini|codex|qwen|opencode|claude (used when method is cli or auto)
-- `--dir <path>` -- Use arbitrary directory instead of phase resolution (scratch mode, skip roadmap validation)
-
-Context files resolved from `.workflow/phases/{NN}-{slug}/` (or `--dir` path):
-- index.json (phase metadata + plan.waves + execution progress)
-- plan.json (plan overview)
-- .task/TASK-{NNN}.json (individual task definitions, lazy-loaded per wave)
-
-**executionContext handoff:** If received from Skill({ skill: "maestro-plan" }) confirmation, skip disk reload and use in-memory plan + explorations + clarifications.
-</context>
-
-<execution>
-### Pre-flight: team conflict check
-
-Before any task execution, run:
-```
-Bash("maestro team preflight --phase <phase-number>")
-```
-If exit code is 1, the command prints warnings about teammates active on the same phase. Present the warnings to the user and ask whether to proceed. If the user confirms or says "force", continue. If they decline, abort with a clear message.
-
-If exit code is 0, or `maestro team preflight` is unavailable (e.g., team mode not enabled), continue normally.
-
-Follow '~/.maestro/workflows/execute.md' completely.
-
-**Report format on completion:**
-
-```
-=== EXECUTION COMPLETE ===
-Phase:     {phase_name}
-Completed: {completed_count}/{total_count} tasks
-Failed:    {failed_count} tasks
-Waves:     {waves_executed}/{total_waves}
-
-Summaries: {phase_dir}/.summaries/
-Tasks:     {phase_dir}/.task/
-
-Next steps:
-  Skill({ skill: "maestro-verify", args: "{phase}" })  -- Verify execution results
-  Skill({ skill: "manage-status" })          -- View project dashboard
-```
-
-If this was a gap-fix execution (plan originated from `--gaps`), emphasize re-verification:
-  "Gap-fix execution complete. Run Skill({ skill: "maestro-verify", args: "{phase}" }) to confirm gaps are resolved."
-
-If failed tasks exist, suggest Skill({ skill: "quality-debug" }) for investigation.
-</execution>
-
-<error_codes>
-| Code | Severity | Condition | Recovery |
-|------|----------|-----------|----------|
-| E001 | error | Phase argument required | Check arguments format, re-run with correct input |
-| E002 | error | Phase directory not found | Check arguments format, re-run with correct input |
-| E003 | error | plan.json not found in phase directory | Verify plan.json exists, run maestro-plan first |
-| E004 | error | No pending tasks, all tasks already completed | Check task statuses, reset if needed |
-| W001 | warning | Executor completed with partial failures | Check task dependencies, retry failed wave |
-</error_codes>
-
-<success_criteria>
-- [ ] All pending tasks executed (completed or explicitly failed)
-- [ ] `.summaries/TASK-{NNN}-summary.md` written for each completed task
-- [ ] `.task/TASK-{NNN}.json` statuses updated
-- [ ] index.json execution progress updated
-- [ ] state.json project progress updated
-</success_criteria>
+---
+name: maestro-execute
+description: Execute plan with wave-based parallel execution and atomic commits
+argument-hint: "[phase] [--auto-commit] [--method agent|cli|auto] [--executor <tool>] [--dir <path>]"
+allowed-tools:
+  - Read
+  - Write
+  - Edit
+  - Bash
+  - Glob
+  - Grep
+  - Agent
+  - AskUserQuestion
+---
+<purpose>
+Execute all tasks in a plan using wave-based parallel execution with dependency-aware ordering. Each plan is executed independently (plans串行, plan内wave并行). Task summaries are written to the plan's scratch directory under `.summaries/`. Registers EXC artifact in state.json.
+
+Invoked after /maestro-plan produces a confirmed plan. When called without args on a milestone, finds all pending plans and executes them sequentially.
+</purpose>
+
+<required_reading>
+@~/.maestro/workflows/execute.md
+</required_reading>
+
+<deferred_reading>
+- [task.json](~/.maestro/templates/task.json) — read when reading task definitions
+- [state.json](~/.maestro/templates/state.json) — read when registering artifact
+</deferred_reading>
+
+<context>
+$ARGUMENTS — phase number, or no args for milestone-wide execution, with optional flags.
+
+**Flags:**
+- `--auto-commit` -- Automatically commit after each task completion
+- `--method agent|cli|auto` -- Override execution method (default: from config.json)
+- `--executor <tool>` -- Default CLI tool: gemini|codex|qwen|opencode|claude
+- `--dir <path>` -- Execute specific plan directory (e.g., `scratch/plan-auth-2026-04-20`)
+
+**Scope routing:**
+
+| Invocation | Behavior |
+|-----------|----------|
+| `execute` (no args) | Find all pending plans for current milestone, execute sequentially |
+| `execute 1` | Find pending plans for phase 1, execute sequentially |
+| `execute --dir scratch/plan-xxx` | Execute the specific plan |
+
+**Resolution logic (no-args / phase):**
+```
+1. Read state.json.artifacts
+2. Filter: milestone=target, type=plan, status=completed, AND no corresponding EXC artifact
+3. If phase specified: further filter by phase=target
+4. Sort by phase dependency order (roadmap phase order), adhoc last
+5. Execute each plan sequentially
+```
+
+**Output**: Task summaries written to plan's scratch dir:
+```
+scratch/plan-{slug}-{date}/
+├── plan.json
+├── .task/
+│   ├── TASK-001.json    # status updated to completed|blocked
+│   └── TASK-002.json
+└── .summaries/          ← execute writes here
+    ├── TASK-001-summary.md
+    └── TASK-002-summary.md
+```
+
+**Incremental learning extraction**: After each plan completes, extract strategy adjustments / patterns / pitfalls from `.summaries/` and append to `specs/learnings.md`. Mark artifact `harvested: true`.
+
+**Artifact registration**: For each plan executed, register in `state.json.artifacts[]`:
+```jsonc
+{
+  "id": "EXC-{NNN}",
+  "type": "execute",
+  "milestone": "{current_milestone or null}",
+  "phase": "{phase or null}",
+  "scope": "{inherited from plan}",
+  "path": "{same as plan path}",
+  "status": "completed",
+  "depends_on": "PLN-{NNN}",
+  "harvested": false,
+  "created_at": "...",
+  "completed_at": "..."
+}
+```
+</context>
+
+<execution>
+### Pre-flight: team conflict check
+
+Before any task execution, run:
+```
+Bash("maestro collab preflight --phase <phase-number>")
+```
+If exit code is 1, present warnings and ask whether to proceed.
+
+Follow '~/.maestro/workflows/execute.md' completely.
+
+**Report format on completion:**
+
+```
+=== EXECUTION COMPLETE ===
+Plans executed: {plans_count}
+Completed: {completed_count}/{total_count} tasks
+Failed:    {failed_count} tasks
+
+Summaries: {plan_dir}/.summaries/
+Tasks:     {plan_dir}/.task/
+
+Next steps:
+  /maestro-verify              -- Verify execution results
+  /maestro-verify --dir {dir}  -- Verify specific plan
+  /manage-status               -- View project dashboard
+```
+
+If failed tasks exist, suggest /quality-debug for investigation.
+</execution>
+
+<error_codes>
+| Code | Severity | Condition | Recovery |
+|------|----------|-----------|----------|
+| E001 | error | No pending plans found | Verify plans exist, run maestro-plan first |
+| E002 | error | Plan directory not found | Check --dir path |
+| E003 | error | plan.json not found in directory | Verify plan.json exists, run maestro-plan first |
+| E004 | error | No pending tasks, all tasks already completed | Check task statuses, reset if needed |
+| W001 | warning | Executor completed with partial failures | Check task dependencies, retry failed wave |
+</error_codes>
+
+<success_criteria>
+- [ ] All pending plans identified and executed sequentially
+- [ ] Within each plan: waves executed in parallel, waves串行
+- [ ] `.summaries/TASK-{NNN}-summary.md` written for each completed task
+- [ ] `.task/TASK-{NNN}.json` statuses updated (completed|blocked)
+- [ ] EXC artifact registered in state.json for each plan executed
+- [ ] Incremental learnings extracted to specs/learnings.md
+- [ ] state.json updated with execution progress
+</success_criteria>