executing-plans

To execute a development plan with review checkpoints, load your written implementation plan and the skill will process it in batched steps, pausing after each batch to report progress and await your feedback before proceeding.

Batched execution for code implementation is a workflow mechanism that breaks down a development plan into manageable task batches, defaulting to the first three, ensuring structured development through mandatory verification and feedback loops.

You add feedback loops to your development workflow by using a batch execution process that pauses after completing a set of tasks, presenting the results for critical review before allowing the next batch to proceed.

Yes, task management execution runs specified verifications automatically after completing each individual task within a batch to ensure correctness before reaching the mandatory review checkpoint.

To start structured development with batched execution, you need a detailed written implementation plan file, such as 'implementation_plan.md', containing the specific task steps and verifications for the skill to reference.

You should not use batched plan execution for simple, single-step tasks that do not require a detailed technical plan or when your development workflow does not need mandatory review checkpoints and feedback loops between batches.