executing-plans

Batch execution of a plan applies tasks in small structured groups, marking progress and running verifications after each batch. It pauses for human review and integrates feedback before continuing to the next batch.

Critical review of an implementation plan loads the file, highlights questions, and ensures all steps are understood before execution. This prevents unreviewed changes and missed checkpoints during batch processing.

Plan execution works with git worktrees by setting up isolated worktrees, writing development branches, and finalizing work using related finishing development branch workflow skills. This isolates changes during batch processing.

Batch processing software development tasks from a written plan applies a structured execution skill to your plan file. It processes tasks in small batches, marks progress, runs verifications, and reports results after each batch.

A feedback loop is needed when executing development plans to prevent unreviewed changes and missed checkpoints. It pauses for human review after every batch, integrates changes, and continues until the plan is complete.

Batch executing plans without a finishing development branch workflow limits your ability to finalize work cleanly. Proper git integration requires related super-power skills to write development branches and complete the isolated worktree setup.