executing-plans

To execute an implementation plan with review checkpoints, load a written plan file and process tasks in coordinated batches, pausing for mandatory human review and approval between each batch.

Yes, dependency management identifies runnable tasks and prompts you to choose between parallel or sequential execution, ensuring task dependencies are intelligently resolved during plan execution.

Yes, a written implementation plan file is required before starting batch execution, serving as the input to manage task dependencies and coordinate human review checkpoints.

Managing scope creep during code implementation is best handled by breaking the plan into manageable batches with checkpoint reviews, ensuring human oversight and alignment before proceeding.

Batch execution integrates with verification and hygienic review sub-skills by pausing between task batches, triggering these sub-skills during the mandatory human review checkpoints before proceeding to the next batch.

Batch execution for development workflow is not suitable when a plan lacks defined task dependencies or when continuous automated deployment is required without mandatory human review checkpoints between task batches.