/ac:execute

Automated plan execution runs approved development steps to completion across your repository without requiring intermediate approvals. It applies wave-based orchestration, routing tasks to tiered workers and enforcing per-step verification before final code-review gating and commit generation.

Wave-based orchestration executes plan steps in dependency-aware batches, running sequential waves until the plan is complete. Each step is delegated to tier-routed workers—quick, junior, or senior—and must pass a four-layer verification flow before the wave advances.

Run plan execution by issuing the execute command with your plan slug. The executor processes the prepared plan file, running steps in dependency-aware waves, enforcing verification, performing final code review, and generating a commit with optional checkpoints for complex plans.

Chained auto-mode execution is supported for complex plans. It runs steps continuously through wave-based checkpoints, applying tier-routed worker delegation and optional oracle parallelism, pausing only at wave-after checkpoints if the plan complexity requires them.

Plan execution enforces a final gated code review before committing. The gate applies either standard or deep review depending on the plan complexity, ensuring all prior step verifications and wave checkpoints have passed before the final commit and report are generated.

Automated plan execution requires a strictly approved plan file beforehand and cannot handle steps outside the prepared plan structure. It relies on tier-routed worker delegation and four-layer verification to prevent errors, meaning unstructured or loosely defined tasks may fail the verification gates.