executing-plans

You can automate stepwise execution of a written plan by loading the plan file and following tasks in order with explicit state transitions. This process runs deterministic task execution with verifications after each step and publishes a final completion report.

Plan-driven development workflow is an approach that turns a written plan into an auditable, step-by-step execution. It requires critical plan review and tracks progress using explicit status updates like in_progress and completed for each task.

To track progress and verify completion, follow plan steps in order and run verifications after each step. This method records explicit status updates for tasks and generates a final completion report to confirm all steps are safely executed.

Executing a plan does not strictly require worktrees, but it coordinates with sub-skills like using-git-worktrees and finishing-a-development-branch. This integration enables safe, end-to-end development workflows with isolated task execution.

Yes, you can review a plan for questions before execution. The workflow requires critically reviewing the loaded plan to identify issues, ensuring deterministic task execution proceeds safely only after the plan is validated.