openspec-apply-change

OpenSpec change management is automated by selecting a change, reading its status, obtaining apply instructions, and iterating through tasks in order. The workflow pauses automatically whenever blockers appear or clarification is needed.

Tracking progress during OpenSpec changes involves fetching the change status, reading context files, and showing task completion updates iteratively. This status-driven guidance ensures consistent forward movement and clear visibility of remaining work.

Yes, the openspec CLI is required to parse changes and tasks for this workflow. It provides the underlying commands to retrieve status, fetch apply instructions, and read context files needed to drive implementation.

Task-driven implementation handles blockers by pausing the workflow and escalating the issue to the user for clarification. This ensures that tasks are not applied out of order or skipped when dependencies are unresolved.

Yes, you can specify a specific OpenSpec change name to start the implementation process. The workflow then identifies that change, evaluates its current status, and begins applying its tasks sequentially.

To start applying tasks, specify the change name, run openspec status to evaluate current progress, and then run openspec instructions apply to retrieve and execute the next applicable tasks in order.