executing-plans

Executing a project plan with checkpoints involves loading a written plan file, conducting critical review, tracking per-task state like in_progress and completed, and handling blockers before final verification.

Structured plan execution is a disciplined workflow that coordinates end-to-end task completion by enforcing critical plan review, deterministic step execution, and strict verification checkpoints throughout the process.

Handling blockers during task execution requires a workflow that identifies concerns during initial plan review, actively tracks per-task state, and pauses execution to resolve blockers before proceeding to subsequent steps.

Structured plan execution supports optional subskill handoffs, allowing subagents to manage downstream tasks like finishing a development branch after the core plan execution and verification workflows are completed.

A written plan file is required before starting task execution because the workflow begins by loading the plan, conducting a critical review, and identifying concerns before deterministically executing any tasks.

The best way to verify task completion in a multi-step workflow is applying strict verification steps after each task reaches a completed state, ensuring all plan requirements are satisfied before reporting final completion.