executing-plans

To execute a development plan with review checkpoints, load the written plan in a separate session, critically evaluate it, and track each task with explicit verifications before advancing. This structured approach ensures reliable completion through task execution tracking and blocker escalation.

The best way to manage blockers during plan execution is to halt the workflow immediately upon detection and request clarifications before continuing. This governance approach prevents compounding errors and ensures each task meets verification standards before advancing to the next step.

Subskill orchestration in a development workflow leverages related skills to ensure safe, auditable task execution. By integrating subskills, the system maintains strict plan loading, tracks progress, and applies verifications to guarantee reliable completion across end-to-end development processes.

Yes, you can use this approach for end-to-end development workflows requiring strict governance. It applies discipline by loading the plan, reviewing it critically, executing tasks sequentially, and finalizing with verifications to ensure every step is tracked and auditable.

Your implementation plan execution halts because the workflow requires explicit verifications and blocker detection before advancing. If a task fails review or a blocker is identified, the system stops to request clarifications, ensuring strict governance and reliable completion.

Yes, you need a written implementation plan to use this execution workflow. The process requires strict plan loading to critically evaluate the tasks, execute them exactly as written, and report progress with verification results throughout the development workflow.