openspec-apply-change

You can implement spec-driven changes by selecting an active OpenSpec change, parsing CLI status and apply instructions, reading context files, and driving a task-by-task implementation loop that keeps changes minimal and updates task checkboxes upon completion.

Applying an OpenSpec change safely involves using CLI commands to list changes, check schema status, and generate apply instructions that drive a task-by-task implementation loop, ensuring every pending task is completed and checkboxes are updated.

Schema status determines where tasks live within workflow artifacts. Checking schema status via CLI allows the implementation process to correctly locate pending spec-driven tasks and generate the appropriate apply instructions for the active change.

When a task is blocked or ambiguous during codebase changes, the implementation loop pauses for guidance. It detects blocked states, errors, or ambiguity, and stops to request user input before continuing the task implementation process.

You do not need to manually update task checkboxes. The CLI-driven implementation loop automatically updates task checkboxes as each spec-driven task completes, and summarizes the final results when the change is fully applied.

You can continue a previously planned OpenSpec change without knowing the exact name. The workflow infers or selects the correct active change by listing available changes and reading the current schema status to identify the right implementation target.