executing-plans

To execute an implementation plan step by step, load the written plan, critically review it for blockers, and process each task sequentially with built-in verifications. This method manages task states and tracks progress continuously to guarantee accurate on-time delivery.

Plan-driven task execution with stop-on-blocker safeguards is a workflow mechanism that halts development when critical issues are detected during plan intake. It ensures readiness by reviewing tasks before execution, preventing errors from cascading through subsequent development steps.

Yes, you can use subagents for task management during plan execution to orchestrate plan-driven work effectively. The workflow integrates required subskills to finalize development tasks, manage task states, and surface measurable results upon completion.

Executing plans with checkpoints supports git-worktree integration to manage task states and isolate development environments. This capability allows stepwise execution and verification of implementation tasks within isolated branches before finalizing the guarded handoff.

The best way to review a written implementation plan for blockers is to load the plan file and perform a critical intake review. This process identifies potential blockers and confirms environmental readiness before initiating stepwise task execution and verifications.

To report completion results after finishing development tasks, finalize the work using required finishing sub-skills and generate a completion report. This approach surfaces measurable results and ensures a guarded handoff after all stepwise verifications succeed.