executing-plans

To execute an implementation plan in batches, you load your plan file, run the first batch of tasks, and present results for human review before proceeding to the next batch. This structured workflow ensures visibility and governance between each batch of development work.

A plan-driven workflow is a structured execution process that runs implementation tasks in defined batches with mandatory human review checkpoints between them. It requires loading a written plan, executing tasks, verifying outcomes, and pausing for feedback before continuing.

You can structure QA reviews between development batches by using a batch-based execution workflow that pauses after each batch. The process generates concise progress reports after tasks complete, presenting outcomes to stakeholders for feedback before continuing.

Yes, you can finalize a development branch after batch execution by integrating with the finishing-a-development-branch sub-skill. This integration allows you to complete the plan-driven workflow and finalize work directly in your development branch.

The best way to track progress when executing multi-step plans is through batch-based execution with clear in-progress and completed statuses. This approach generates concise progress reports after each batch, ensuring QA and stakeholders have full visibility.