openspec-apply-change

To implement OpenSpec changes end-to-end, automate the workflow by selecting a change set, checking its status, reading context files, and updating task progress until completion. The process handles pausing states and interactive prompts for ambiguous changes.

Change management automation handles ambiguous OpenSpec tasks by triggering interactive prompts that provide guidance. For blocked states, it reads context files to determine if work should pause, be archived, or proceed with completion.

Yes, the OpenSpec CLI is required to apply a change set. It drives the automation workflow, reads necessary context files, supports interactive prompts, and manages task status updates for continuous delivery.

The best way to track progress implementing OpenSpec tasks is using the automation workflow to automatically update task status. It checks the current state of each change, processes tasks sequentially, and handles completion or pausing states.

OpenSpec task implementation pauses to handle blocked states or ambiguous changes. The automation workflow detects these conditions, stops execution, and uses interactive prompts to provide guidance before resuming or archiving the change.