executing-plans

To execute a development plan with review checkpoints, this Skill loads written implementation tasks and processes them in predefined batches, automatically pausing between each batch for critical review before proceeding.

Batch processing for iterative development plans is an execution method that breaks complex implementations into manageable task groups, defaulting to three tasks per batch, to facilitate critical review and prevent errors before continuing.

To stop plan execution when encountering blockers, the Skill continuously assesses task viability during batch processing and automatically halts execution, providing clear guidance on when to stop and ask for help if critical gaps are found.

Yes, you can run verifications after each task during plan execution. The Skill ensures specified verifications are executed following every individual task within a batch to maintain correctness before reaching the mandatory review checkpoint.

Batch execution works effectively for complex features requiring distinct coding and testing phases by ensuring each implementation phase is critically reviewed by an architect or human partner before the next phase begins, maintaining quality and alignment.

You should not use automated plan execution with checkpoints when your implementation plan lacks clearly defined discrete tasks, as the batch processing mechanism relies on loading and executing specific task groups sequentially with review pauses.