executing-plans

To execute a written plan with review checkpoints, load the document, critically review it for concerns, and implement tasks in sequential batches with explicit verification steps and human validation between each batch.

The best way to prevent project drift is batch execution with reviewer checkpoints, stopping on blockers to ask for human guidance, and utilizing progress reporting and feedback loops between batches to ensure disciplined task completion.

Yes, you need a clear plan input before starting batch execution. The skill loads the written plan, critically reviews it, and proceeds with implementation only when concerns are addressed to ensure structured progression.

Progress reporting works by documenting completed work and verifications between batches to enable timely feedback. This structured reporting guides progress and highlights decision points before moving to the next batch.

When a blocker is encountered during task implementation, the system stops on the blocker and asks for human guidance to avoid guessing. This escalation prevents miscommunication and ensures disciplined task completion.

Yes, you can use this batch processing approach for general project management tasks. It is designed for project and development work where a plan exists and must be implemented in sequential batches with formal reporting.