executing-plans

To execute a development plan with verification, review the plan critically, track tasks sequentially, run required checks at each checkpoint, and stop when blocked. This ensures structured execution without skipping validation before completion handoff.

Tracking implementation tasks across separate sessions requires marking progress sequentially and running required checks at each checkpoint. This workflow ensures continuity and validates that each task meets verification standards before moving forward.

Handling blockers during workflow execution requires stopping task progress immediately and escalating the issue. This prevents faulty code from propagating through subsequent tasks and ensures the plan resumes only after the blocker is resolved.

Reviewing an implementation plan critically before development surfaces questions and concerns early. This prevents wasted effort on flawed assumptions and ensures the execution phase proceeds with validated task sequencing and checkpoints.

Completing a development branch after task execution involves validating the final result and transitioning to a branch-completion workflow. This handoff ensures all implementation tasks are fully verified before the code is finalized.