openspec-executing-plans

To execute OpenSpec plans in batched steps, this skill loads the active plan from the openspec/changes directory and processes tasks in controlled iterations. It pauses execution between batches to generate progress reports and prompt for architect review.

Structured batch execution for OpenSpec changes is a controlled iteration process where plan steps are executed in groups. It enforces batch processing limits and requires architect review checkpoints between batches to validate progress before continuing.

Yes, you need an openspec directory to manage plan execution. This skill requires your project to store plans under openspec/changes and reads active changes via the openspec list command to interpret and execute plan steps.

Yes, you can review progress between task batches during plan execution. The skill enforces batch processing with built-in checkpoints, reporting status and prompting for feedback to ensure alignment before continuing to the next batch.

You should not use automated batch execution for OpenSpec when your project lacks plans stored under openspec/changes or does not require structured batch execution with architect review checkpoints for task validation.