openspec-apply-change

Spec-driven development uses specification documents to define requirements before implementation. OpenSpec manages this by tracking change status and task lists, allowing developers to execute required implementation steps methodically while updating progress.

Spec-driven development uses specification documents to define requirements before implementation. OpenSpec manages this by tracking change status and task lists, allowing developers to execute required implementation steps methodically while updating progress.

During change implementation, blocked or ambiguous tasks are handled by pausing execution and reporting the blocker clearly. The skill reads task states and context files to determine whether to proceed, pause, or seek clarification before continuing.

Yes, you can implement multiple OpenSpec changes in one repository. When multiple options exist, the skill handles change selection by picking the correct active change from the context or the active list before loading its specific workflow instructions.

No, you do not need manually written workflow instructions to execute spec-driven development tasks. The skill automatically loads workflow instructions, reads status and context files, and constructs the required implementation steps directly from the OpenSpec change artifacts.