openspec-apply-change

OpenSpec task implementation is automated by selecting the target change, loading schema-specific context artifacts via CLI output, and looping through pending tasks while marking completion. It pauses automatically on blocked or ambiguous states.

Progress tracking works by retrieving dynamic apply instructions through JSON, parsing contextFiles from CLI output, and reporting task completion as the workflow iterates through the change task list.

When workflow implementation encounters missing artifacts or ambiguous tasks, it pauses with a clear reason, requests clarification for unclear instructions, and stops on errors instead of guessing the next action.

You can interleave other actions while implementing an OpenSpec change because the workflow supports fluid operation before completion. It can also suggest artifact updates when implementation reveals issues.

You do not need to specify the change name to start task implementation. The workflow can infer or select the correct active OpenSpec change if the name is omitted from the initial command.

Your OpenSpec change task loop stops when it detects blocked states like missing artifacts, encounters unclear tasks requiring clarification, or hits error states, pausing with a clear reason instead of proceeding incorrectly.