executing-plans

Execute an implementation plan with automated review checkpoints by loading the written plan, critically reviewing it for gaps, executing tasks sequentially, and enforcing verification gates before transitioning between stages. Progress is reported through gated handoffs.

Gated progress in plan execution workflows is a structured approach where per-task state management enforces verifications before transitioning between stages, ensuring milestones are met and progress is clearly reported before final handoffs.

Track per-task state during implementation plan execution by driving statuses like in_progress and completed through the workflow, enforcing verifications before stage transitions, and reporting completion with gate-based checkpoints.

Yes, you can use git worktrees for isolated plan execution. The workflow integrates with sub-skills like superpowers:using-git-worktrees to ensure isolated workspaces, safe handoffs, and dedicated development branches during task execution.

The best way to coordinate plan loading and critical review is to load the plan, review it critically for gaps or blockers, and begin executing tasks with automated progress tracking and gated handoffs to ensure structured milestone completion.

You should not use gated checkpoints for development branch handoffs when your workflow requires rapid, unstructured prototyping without per-task state management or verification gates, as this approach enforces structured milestone progression and critical review.