executing-plans

To add human verification checkpoints to plan execution, break your project plan into 1-3 task batches. The execution process runs sequentially and pauses at specified checkpoints, requiring human oversight and decision-making before proceeding to the next batch.

Batch processing in task management divides a complex plan into manageable 1-3 task batches. You need this mechanism for project workflows where critical human oversight is required for quality assurance and decision-making before proceeding to subsequent tasks.

Execute a project management plan sequentially by defining tasks in a plan file. The skill processes these tasks in batches, pausing at each specified checkpoint to require human verification, ensuring every step is completed correctly before advancing.

Yes, batch execution is designed specifically for complex project plans requiring quality assurance. It reduces the risk of errors by sequentially executing tasks in small batches and integrating human verification at critical decision points.

The best way to ensure task accuracy during plan execution is using batch processing with human checkpoints. This approach mandates human oversight at critical points, verifying each batch of tasks is correct before moving forward.

You need a markdown plan file, such as 'project-execution-plan.md', to define your tasks. The skill reads this plan and executes the defined tasks sequentially in batches, triggering human verification at the specified checkpoints.