executing-plans

To execute an implementation plan with review checkpoints, load your plan file into a separate session and critically review it before proceeding through each task. The system creates a TodoWrite list, executes steps exactly as defined, and performs verifications at each gated development phase.

Plan-driven development execution in an isolated workspace runs written implementation tasks in a separate session using git-worktrees. This ensures critical evaluation happens before action, applying gating conditions across development phases while keeping the main branch protected.

Yes, you need a written plan file to start executing development tasks. The execution requires a plan file containing defined steps, verifications, and gating conditions, along with an isolated workspace setup using git-worktrees to separate the work.

You verify tasks when executing a development plan by following the plan steps exactly and performing the verifications defined within the plan file. Each task is tracked with in_progress status, ensuring verifications are met before moving to the next development phase.

After completing all tasks and verifications in an implementation plan, the system triggers sub-skills like finishing-a-development-branch to complete the development process. It then presents options for finalizing the work in your isolated workspace.

Yes, you can use git-worktrees to isolate plan execution from your main branch. The execution requires an isolated workspace, integrating with the using-git-worktrees sub-skill to ensure plan-driven development tasks with gating conditions run separately.