executing-plans

To execute an implementation plan in controlled batches, apply this skill to a plan file and run tasks sequentially with per-batch verifications and human feedback pauses between batches. This ensures quality and alignment throughout the process.

The best way to run a written plan file sequentially is by using the /execute-plan command, which processes tasks in defined groups and provides progress reporting after each batch completes.

Yes, you can pause plan execution to get human feedback between task batches. The skill runs interim reviews between sequential batches to solicit feedback and adjust before proceeding to the next group of tasks.

After all tasks in a plan file are verified and completed, the skill triggers a final completion protocol that transitions the workflow to finishing-a-development-branch.

You need a written implementation plan stored in a plan file, such as a markdown file like plans/your-plan.md, to run batch execution for your software engineering tasks.