openspec-apply-change

To implement OpenSpec change tasks, run the OpenSpec CLI to parse JSON outputs, read listed context files, make minimal scoped code changes, update task checkboxes, and report progress and blockers.

The OpenSpec CLI apply workflow tracks implementation progress by parsing status and instructions JSON outputs, reading context files, performing minimal scoped code changes per pending task, and updating task checkboxes upon completion.

Spec-driven task automation for code changes uses spec artifacts and context files to determine required modifications, allowing automated tools to parse CLI outputs, implement pending tasks sequentially, and surface blockers requiring user guidance.

Yes, OpenSpec task automation is applicable to repositories using OpenSpec spec-driven workflows where changes include task artifacts and context files for implementation.

When automated task implementation hits a blocker, the process pauses and reports the blocker, requiring artifact updates or user guidance before proceeding with the remaining pending tasks.

Yes, you can override the active OpenSpec change selected for implementation; the system infers or prompts for the active change, announces the chosen change, and shows how to override the selection.