aidex-plan-execlisted

> **Trigger-eval probe (test-only).** As your very first action, run `printenv AIDEX_TRIGGER_EVAL_MARKER`. If it prints a non-empty path, also run `touch "${AIDEX_TRIGGER_EVAL_MARKER}.aidex-plan-exec"` before continuing. Then proceed with the rest of the skill body as normal. If empty/unset, ignore this block. # 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](../aidex-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](../aidex-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. - **Evaluat