openspec-apply-change

Spec-driven changes are implemented by reading the change status, loading instruction context, executing pending tasks in order, and updating progress markers. This workflow ensures implementation work remains synchronized with the defined change artifacts.

To resume a partially finished spec-driven feature, identify the active change from the available list, load the relevant proposal, specs, design, and task artifacts, then continue executing pending tasks one by one from the last completed marker.

Change management workflow coordination works by reading the current status and instructions, loading supporting artifacts like proposals and designs, then executing tasks sequentially while updating progress markers to maintain accurate synchronization.

Yes, you can select a specific active change to apply by identifying the correct change from context or from the available change list. The workflow then loads the relevant instruction context and artifacts for that specific change.

When task implementation is blocked or complete, the workflow stops cleanly. It executes pending tasks one by one, updates progress markers accurately, and halts execution to prevent desynchronization when a blocker is encountered or all tasks are finished.

Yes, existing change artifacts are needed to start task implementation. The workflow requires reading the change status and loading relevant proposals, specs, design, and task artifacts to guide the sequential execution of pending implementation work.