executing-plans

To execute a development plan with verification, load the written plan, review it critically, and execute tasks sequentially with explicit verifications and guardrails for blockers after each step.

A structured plan execution workflow enforces task-by-task execution with mandatory review checkpoints, verifying each step before proceeding and handling blockers with guardrails until final development handoff.

Yes, you can use git-worktrees when executing a multi-step development plan; the workflow integrates sub-skills to manage governance, including using-git-worktrees, writing-plans, and finishing-a-development-branch.

The best way to handle blockers during plan execution is to use enforced guardrails that pause the task-by-task workflow, preventing progression until the blocker is resolved and verification passes.

To execute a written plan without losing progress, use a structured workflow that critically reviews the documented plan and processes each task individually with explicit verifications before moving forward.

Yes, you need a documented plan before starting task execution with checkpoints, as the workflow is designed for sessions where a written plan must be critically reviewed and then executed task-by-task.