executing-plans

Automate plan execution by loading a written plan, executing tasks in batches, and enforcing critical review checkpoints between each batch. Per-task verification and progress reporting ensure structured governance before advancing to the next set of development steps.

Batch processing for complex project plans is managed by loading the written plan, executing a batch of tasks, verifying each task, and reporting progress. Critical review checkpoints between batches govern the progression of development work based on feedback.

Git-worktrees provide isolated workspaces for batch task execution by allowing planned development steps to run independently without affecting the main branch. This isolation ensures verifications and review checkpoints occur safely before finalizing any development branch.

Yes, this workflow is applicable when a written plan already exists. You provide the plan to activate the execution workflow, which then handles loading, critical review, batch execution, verification, and progression based on feedback until completion.

Finalizing a development branch after batch plan execution involves integrating with related skills designed for finishing development work. Once all planned batches are executed, verified, and pass critical review checkpoints, the workflow progresses to finalizing the branch.

Batch-driven execution with per-task verification prevents unchecked errors by inserting critical review checkpoints between batches. This approach ensures structured governance, allowing you to assess progress, validate feedback, and verify tasks before continuing with further plan execution.