executing-plans

Batched plan execution groups development tasks into fixed sets, defaulting to three tasks per batch. This workflow enforces review checkpoints and verifications after each batch to prevent chaotic execution and maintain progress visibility.

Load a saved plan file, review it for blockers, execute the first batch of three tasks, perform verifications, and repeat for subsequent batches until complete. Critical review and blocker handling are enforced before starting each batch.

Large plans feel chaotic when tasks are executed without staged reviews or batching. Enforcing batch-based execution with three tasks per batch and performing verifications after each batch solves this by creating clear reporting and checkpointed progress.

The default batch size is three tasks per batch to maintain momentum and visibility. The skill enforces this batch-based execution structure to ensure critical reviews and verifications occur at consistent intervals during development.

After completing the final batch and its verifications, the workflow uses the finishing-a-development-branch flow. This provides a seamless transition to finalize the development branch and conclude the staged review process.

Yes, you need a saved plan file to start. The quick start process requires loading a saved plan file, reviewing it, and then beginning to execute the first batch according to the plan's defined tasks.