executing-plans

To execute an implementation plan in verified batches, load the plan file, process tasks in groups of three, run required checks, and pause for review feedback before continuing to the next batch.

Review-driven batch execution is a workflow that processes implementation tasks in small isolated groups, runs verification checks, and waits for approval or clarification before proceeding to the next batch.

During plan execution, the workflow pauses automatically when encountering blockers or repeated verification failures, reports the outcomes, and waits for user feedback before attempting to proceed.

Yes, this batch execution workflow integrates with git worktrees to isolate changes, tying into plan-writing and finishing-branch procedures for end-to-end staged delivery.

Yes, you need a written implementation plan file to start, as the workflow performs a critical review of the plan, flags gaps or uncertainties, and seeks clarification before making any changes.

The best way to track progress state during staged plan execution is to process tasks in small batches that mark progress states, run verifications, and report outcomes at review checkpoints before continuing.