openspec-apply-change

Run the apply workflow with a change name, or let it be inferred from context. The skill runs openspec status and openspec instructions apply to load context files and the task list, then implements each pending task and marks it complete in the tasks file.

An OpenSpec change is a unit of planned work containing artifacts like a proposal, specs, design, and a tasks checklist. The apply workflow reads those artifacts as context and works through the tasks until the change is fully implemented.

Yes. If the work lives in a registered store, the skill runs openspec store list --json to discover store ids and passes --store <id> on commands that read or write specs and changes. Without a store, commands act on the nearest local openspec root.

When the status returns a blocked state, the skill shows the message and suggests creating the missing artifact, either via the continue command or by running openspec instructions for the next artifact. It does not bypass the blocked state.

Pause when a task is ambiguous, when implementation reveals a design issue, or when the work requires scope beyond what the spec describes. The skill surfaces the added scope and asks rather than silently narrowing or deferring specified behavior.