execute

Batch processing for project execution works by loading your plan from docs/plans/ and comparing it against design context in docs/SPEC.md. It splits tasks into logical checkpoints, providing status updates and verification steps while pausing for human feedback between batches.

Batch grouping for project management works by splitting a loaded plan into smaller, verifiable units based on predefined guidelines. This creates logical checkpoints throughout the workflow, requiring human feedback and verification steps between each batch before proceeding to the next set of tasks.

Yes, you need a SPEC.md file to run plan execution because the system reviews your loaded plan against the design context provided in docs/SPEC.md. This comparison surfaces questions or concerns and ensures the batched tasks align with the overall project specifications before proceeding.

When plan execution hits a blocker or missing guidance, the system stops processing immediately. It provides a clear path for next steps, delivers status updates on the current batch, and waits for human feedback to resolve the issue before attempting to resume the workflow.

The best way to coordinate end-to-end plan execution safely is to use batch grouping rules that split work into logical checkpoints. Loading a plan from docs/plans/ and reviewing it against docs/SPEC.md ensures traceability with status updates and verifications while pausing for human feedback.