← ClaudeAtlas

executelisted

Drive a finished plan to ready pull requests with passing CI, merging them only when run with `--merge`, without stopping between issues: take the next unblocked one, hand it to `/work-on`, land it, repeat, across one repo or several. Use it when the plan exists and the next thing is doing it — "we have the plan, go", "build everything in the plan", "ship the whole milestone", "start on the plugin-system work" — and for "pick up where we left off", since a run already in flight resumes from its own recorded state rather than from wherever the working tree happens to sit. An agent that opens a PLAN and starts implementing issue one by hand is the failure this exists to prevent. A `multi-pr` plan is the exception: those run through `/work-on` instead. Do NOT use it to work out a feature that has no plan yet (`/scope`), to write the plan (`/plan`), or to do a single issue (`/work-on`).
tsukumogami/shirabe · ★ 0 · AI & Automation · score 67
Install: claude install-skill tsukumogami/shirabe
!`bash ${CLAUDE_PLUGIN_ROOT}/scripts/skill-preflight.sh execute 2>&1 || true` # Execute `/execute` is the third parent skill in the trio, at the implementation altitude (alongside `/charter` strategic and `/scope` tactical). It owns **plan-level execution**: given a finished PLAN, it drives the plan's issues to ready pull requests (and, with `--merge`, through the merge) and delegates each single issue to `/work-on`'s single-issue engine. `/work-on` itself stays the canonical single-issue executor; `/execute` does not reimplement single-issue mechanics. `/execute` runs a single-pr PLAN end-to-end by lifting `/work-on`'s plan-orchestrator template (now `execute.md`) and pointing each per-issue child at `/work-on`'s `work-on.md` over a cross-skill reference. It runs a coordinated PLAN, whose PR nodes sit in one or more repositories, node by node: the PR node `(repo, pr_group)` is the unit of branching, and the loop runs inside the `execute-coordinated.md` koto envelope, driven by `coordinated-next.sh`. State, cross-branch resume over the durable home PR, and the three exit-path bindings are in the **State**, **Resume**, and **Exit Paths** sections; parent-skill conformance and the six security surfaces are in **Child Inspection** and **Security Considerations**; the autonomy mandate is in **Autonomy**. Backward-compatibility and parity-survival evals live under `skills/execute/evals/`. ## Input Modes From `$ARGUMENTS`: 1. **Path to a PLAN doc** (`docs/plans/PLAN-*.md`, or