maestro
FreeIntent-to-chain planner over the canonical Session/Run lifecycle
The English summary is being prepared. Showing the original description.
Unified team skill for issue resolution. Uses team-worker agent architecture with role directories for domain logic. Coordinator orchestrates pipeline, workers are team-worker agents. Triggers on "team issue".
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
<required_reading> @~/.maestro/workflows/run-mode-lite.md </required_reading>
Orchestrate issue resolution pipeline: explore context -> plan solution -> review (optional) -> marshal queue -> implement. Supports Quick, Full, and Batch pipelines with review-fix cycle.
Skill(skill="team-issue", args="<issue-ids> [--mode=<mode>]")
|
SKILL.md (this file) = Router
|
+--------------+--------------+
| |
no --role flag --role <name>
| |
Coordinator Worker
roles/coordinator/role.md roles/<name>/role.md
|
+-- clarify -> dispatch -> spawn workers -> STOP
|
+-------+-------+-------+-------+
v v v v v
[explor] [plann] [review] [integ] [imple]
| Role | Path | Prefix | Inner Loop |
|---|---|---|---|
| coordinator | roles/coordinator/role.md | — | — |
| explorer | roles/explorer/role.md | EXPLORE-* | false |
| planner | roles/planner/role.md | SOLVE-* | false |
| reviewer | roles/reviewer/role.md | AUDIT-* | false |
| integrator | roles/integrator/role.md | MARSHAL-* | false |
| implementer | roles/implementer/role.md | BUILD-* | false |
.workflow/codebase/ARCHITECTURE.md exists, read for module boundariesmaestro load --type spec --category coding — load coding constraints as shared contextmaestro load --type spec --category debug — load debug constraints as shared contextmaestro search "issue resolution fix" --json — top 5 entries as prior contextParse $ARGUMENTS:
--role <name> → Read roles/<name>/role.md, execute Phase 2-4--role → @roles/coordinator/role.md, execute entry routerTISL{run_dir}/work/team/issuemaestro delegate --mode analysis (read-only), maestro delegate --mode write (modifications)mcp__maestro__team_msg(session_id=<run-id>, ...)Coordinator spawns workers using this template:
Agent({
subagent_type: "team-worker",
description: "Spawn <role> worker",
team_name: "issue",
name: "<role>",
run_in_background: true,
prompt: `## Role Assignment
role: <role>
role_spec: <skill_root>/roles/<role>/role.md
session: {run_dir}/work/team
session_id: <run-id>
team_name: issue
requirement: <task-description>
inner_loop: false
## Progress Milestones
session_id: <run-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).`
})
Parallel spawn (Batch mode, N explorer or M implementer instances):
Agent({
subagent_type: "team-worker",
name: "<role>-<N>",
team_name: "issue",
run_in_background: true,
prompt: `## Role Assignment
role: <role>
role_spec: <skill_root>/roles/<role>/role.md
session: {run_dir}/work/team
session_id: <run-id>
team_name: issue
requirement: <task-description>
agent_name: <role>-<N>
inner_loop: false
## Progress Milestones
session_id: <run-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, owner=<role>-<N>) -> role Phase 2-4 -> built-in Phase 5 (report).`
})
| Command | Action |
|---|---|
check / status | View execution status graph, no advancement |
resume / continue | Check worker states, advance next step |
{run_dir}/work/team/
├── team-session.json # Session metadata + pipeline + fix_cycles
├── task-analysis.json # Coordinator analyze output
├── .msg/
│ ├── messages.jsonl # Message bus log
│ └── meta.json # Session state + cross-role state
├── wisdom/ # Cross-task knowledge
│ ├── learnings.md
│ ├── decisions.md
│ ├── conventions.md
│ └── issues.md
├── explorations/ # Explorer output
│ └── context-<issueId>.json
├── {run_dir}/outputs/solutions/ # Planner output
│ └── solution-<issueId>.json
├── {run_dir}/outputs/audits/ # Reviewer output
│ └── audit-report.json
├── {run_dir}/outputs/queue/ # Integrator output
└── {run_dir}/outputs/builds/ # Implementer output
| Scenario | Resolution |
|---|---|
| Unknown command | Error with available command list |
| Role not found | Error with role registry |
| CLI tool fails | Worker fallback to direct implementation |
| Fast-advance conflict | Coordinator reconciles on next callback |
| Completion action fails | Default to Keep Active |
| Review rejection exceeds 2 rounds | Force convergence to integrator |
| No issues found for given IDs | Coordinator reports error to user |
| Deferred BUILD count unknown | Defer to MARSHAL callback |
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Intent-to-chain planner over the canonical Session/Run lifecycle
The English summary is being prepared. Showing the original description.
Quick execution for small tasks — minimal run lifecycle (start + done) with evidence recording. Full LLM capability, scoped to mechanically clear tasks.
The English summary is being prepared. Showing the original description.
Create or sync session worktree for parallel dev
The English summary is being prepared. Showing the original description.
Manage editing boundary restrictions
The English summary is being prepared. Showing the original description.
Maestro Flow 命令帮助系统。搜索命令、浏览技能、工作流推荐、新手引导。Triggers on "maestro-help", "帮助", "命令", "怎么用", "skill", "workflow", "maestro 怎么用".
The English summary is being prepared. Showing the original description.
Use when designing, reviewing, refining, fixing, or codifying frontend UI with Maestro's self-contained Impeccable core
The English summary is being prepared. Showing the original description.