executing-plans

Batch execution divides your complete plan into controlled chunks with review checkpoints between each batch. You run the first batch (default: 3 tasks), verify results and status, review outputs, then proceed to the next batch—reducing risk and improving traceability throughout implementation.

Between batches, the Skill pauses for critical review. It reports what was implemented, surfaces verification outputs including linting and type-checking results, and requires you to review before advancing—ensuring issues are caught early rather than compounding across the full plan.

Yes. The Skill generates reports for each batch showing implemented tasks, verification outputs, and status tracking. This traceability lets you audit what changed, see linting and type-check results, and maintain a clear record for review between batches.

Announce you're using the executing-plans skill, load your plan file, and begin the first batch. The Skill runs the default batch size (first 3 tasks), displays verification outputs and status, then waits for your review before proceeding to the next batch.

Use batches for plan-driven projects where staged execution, critical review between phases, and verification steps are essential. Batching reduces risk on large implementations and improves traceability when changes require validation before proceeding further.

The Skill runs linting and type checking before commits, reports results as part of batch verification, and surfaces these outputs for your review. This ensures code quality and catches errors early within each batch before moving to the next stage.