executing-plans

Batch execution of a development plan processes tasks in predefined groups, defaulting to the first 3 tasks, and pauses for mandatory review checkpoints between each batch. This ensures structured validation at every stage before proceeding.

Managing task execution for a multi-step software feature is best handled by executing tasks in batches and reporting progress for review after each batch. This approach ensures careful validation and potential architectural review before moving to the next step.

Handling blockers or unclear instructions during batch processing requires stopping execution immediately and seeking help. The workflow provides clear guidance on when to halt to prevent deviating from the structured development process.

Yes, you need a separate skill for finalization upon completion of batch execution. The executing-plans skill focuses strictly on implementing the provided plan and reporting for review, leaving final wrap-up to another tool.

The executing-plans skill defaults to executing the first 3 tasks as a batch. You provide the implementation plan, and the system processes these tasks in predefined batches before pausing for review checkpoints.