executing-plans

To execute a development plan with verification checkpoints, load the written plan, review it critically, and follow each task sequentially while updating statuses and performing verifications before reporting completion.

The best way to handle blockers during task execution is to stop immediately, request clarification, and avoid guessing. This maintains plan fidelity and ensures accurate implementation until the blocker is resolved.

Yes, you can use git worktrees to isolate your workspace when executing an implementation plan. The execution process integrates worktree management to ensure isolated development before finalizing the development branch.

Yes, plan execution requires a written implementation plan before starting. The execution process loads the existing plan, reviews it critically, splits it into todos, and verifies each task against the plan before completion.

When a plan execution task fails verification, the process stops on the blocker and requests clarification. It avoids guessing to maintain plan fidelity, ensuring the task meets verification standards before proceeding.

To finalize a development branch after completing all plan tasks, the execution process leverages integrated sub-skills for finishing development branches, ensuring all tasks are verified and completed before branch finalization.