plan-execlisted

Use whenever the user asks to execute, implement, resume or continue a written plan — a `.context/plans/` document or any plan with checkboxes/phases — however small the phase looks, even a single-file edit: the plan's checkboxes and Execution log are updated by this skill, so do not carry out the phase directly from the plan text. Fires on "implement the plan", "execute plan X", "let's execute the plan", "continue with phase Y", "resume the plan", "run phase 1 of the plan", "run the plan phase by phase". Enforces between-phase discipline: code-review, commit, handoff when context grows. Not for: creating the plan itself (/aidex:plan); one-shot tasks with no phases; bug fixes (/aidex:bugfix); pure refactors with no plan document.
yacb2/aidex · ★ 2 · Code & Development · score 81

Install: claude install-skill yacb2/aidex

# Plan Execution Drive the implementation of a written multi-phase plan with consistent between-phase discipline: review the diff, commit, and hand off the session when context grows. This skill centralizes the workflow so the user does not have to repeat it in every prompt. ## Default autonomy On run start, apply [Mode A autonomy](../conventions/references/autonomy-conventions.md) automatically — do not wait for the user to grant it. Questions live in the initial alignment moment only; after that the run proceeds start-to-finish (deny/pre-authorized/mandated/autonomous — see "Operating mode" below). ## Operating mode **Front-loaded, then autonomous start-to-finish.** Resolve every question at **Orient** (phase 0); after that, run all phases without interrupting. Follow the shared autonomy canon ([autonomy-conventions.md](../conventions/references/autonomy-conventions.md)). The operative rule here: - **Ask everything up front, at Orient.** Surface clarifications and confirm any publication the plan implies (deploy/publish/release) before phase 1. If the plan did not pre-authorize a publish step, surface it at the **end** — not mid-run. - **Evaluate batch-promotion at Orient (mandatory, one line).** Before phase 1, decide whether the plan's `afk-impl` phases should run as a durable `Workflow`, and say so in one line. The full rule is in [`references/01-unattended-batch-execution.md`](references/01-unattended-batch-execution.md) § Promotion at Orient. It is a