Stats
Actions
Tags
From maestro
Drain the ready queue — implement every issue assigned to me in a ready state, in dependency order, on an integration branch, with each per-issue PR auto-merged into it. The main agent only coordinates; you can participate. Ends when nothing is pending. Use for /maestro:drain (and inside /maestro:auto).
How this skill is triggered — by the user, by Claude, or both
Slash command
/maestro:drainThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are the **coordinator**. You do NOT implement and you NEVER merge the integration PR. You start an integration run, dispatch background workers in dependency order, and report. This is equivalent to looping `/maestro:ship` over the assigned ready queue (the user may also run `/loop /maestro:drain`).
You are the coordinator. You do NOT implement and you NEVER merge the integration PR. You start an integration run, dispatch background workers in dependency order, and report. This is equivalent to looping /maestro:ship over the assigned ready queue (the user may also run /loop /maestro:drain).
cd "$(git rev-parse --show-toplevel)"; source .maestro/config.sh 2>/dev/null || true; S="${MAESTRO_SCRIPTS:-$(pwd)/.maestro/scripts}".INTB=$(bash "$S/integration.sh" start). This opens the integration PR — your single review gate. Tell the user its URL (bash "$S/integration.sh" status).bash "$S/ready-issues.sh" → issues assigned to me, maestro:ready-for-agent or maestro:auto, unblocked (no open blockers; a blocker counts as cleared once it's maestro:waiting-for-human-closure).
b. If it's empty and no workers are still running → the queue is drained. Go to step 4.
c. Otherwise dispatch up to MAESTRO_MAX_PARALLEL workers (default 3) — Agent tool, subagent_type: "issue-implementer", run_in_background: true, one per ready issue, each:
Implement issue #: "". Base branch: <INTB>. Open the per-issue PR against the integration branch. (Fallback to general-purpose following the
implement-issueskill if the agent type isn't loaded yet.) d. End your turn so the user can participate. Each worker, on finishing, merges its per-issue PR into the integration branch and relabels its issuemaestro:waiting-for-human-closure— which unblocks dependents. e. When a worker completes you'll be notified: re-run step (a) and dispatch any newly-unblocked issues (the next dependency layer). As a safety heartbeat you may alsoScheduleWakeupto re-check.
bash "$S/integration.sh" close-integrated closes the maestro:waiting-for-human-closure issues.Never merge the integration PR or the default branch.
npx claudepluginhub neelneelpurk/maestro --plugin maestroGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.