executing-plans

Batch-oriented plan execution loads a written implementation plan, validates it, creates a task-tracking record for all tasks, and processes them in batches with explicit review checkpoints between batches to prevent drift.

Yes, parallel-task support executes tasks marked as parallel in the plan and aggregates results before proceeding to the next batch or review checkpoint.

Task-tracking integration creates records for all tasks in a plan, enforcing deterministic steps, per-plan verifications, and structured handoffs to human partners to ensure safe progress and accountability.

The skill enforces clear stop conditions and escalation pathways to handle blockers, requiring task-tracking integration to ensure safe progress and structured handoffs when issues arise.

You need a written implementation plan with tasks defined, optionally marked for parallel execution, and task-tracking integration to create records and begin execution with the default first batch.

Plan validation is enforced by loading the plan, checking deterministic steps, verifying per-plan conditions, and creating a task-tracking record for all tasks before beginning batch execution.