executing-plans

To execute a development plan in batches, you load the written plan and process tasks in staged groups with explicit in_progress and completed statuses. Review checkpoints are inserted between batches to validate outcomes before continuing to the next group.

The load-review-execute-report cycle is a task management workflow where you load a plan, execute tasks in batches, review verifications at checkpoints, and report results. It ensures quality control and reduces drift before proceeding to the next development phase.

Yes, plan execution includes explicit stop conditions when blockers arise during batch processing. If critical verifications fail at review checkpoints, the workflow halts to prevent further drift and allows for course adjustment before resuming.

You track task status updates by applying explicit in_progress and completed states to each task during batch execution. The workflow manages these iterative state transitions across batches to maintain visibility throughout the development workflow.

The best way to prevent plan drift during project execution is using staged batches with critical reviews and verifications between each group. This controlled execution approach validates outcomes at checkpoints and adjusts course as needed before continuing.

Yes, you need to provide a written implementation plan file before starting batch execution. The workflow requires a loaded plan to group tasks into staged batches and apply review checkpoints effectively throughout the execution cycle.