openspec-apply-change

To implement spec-driven change tasks, this Skill drives the openspec CLI to fetch apply instructions, read context files, and iteratively apply minimal code updates while tracking task completion. It requires openspec CLI accessible in PATH to obtain JSON context and task lists.

Applying an openspec change involves selecting the active change, running openspec instructions apply --change to fetch context, reading relevant artifacts, and iteratively implementing pending tasks while updating task checkboxes until completion or a blocked state occurs.

Yes, you need the openspec CLI accessible in your PATH to use this workflow. The Skill requires running openspec status --change and openspec instructions apply --change commands to obtain the JSON context and task lists needed for implementation.

During change implementation, the workflow handles blocked or all_done states by pausing for clarifications or design issues, displaying schema and progress, and suggesting next actions such as continuing, updating artifacts, or archiving the change.

Yes, when multiple openspec changes exist, the workflow infers or prompts you to select the active change, or lists available changes when the target is ambiguous, ensuring you implement the correct change tasks.

Automating openspec task implementation applies minimal, focused code updates based on fetched instructions and context files, but it pauses for clarifications or design issues and cannot proceed past blocked states without user intervention or artifact updates.