openspec-apply-change

Implement tasks from an OpenSpec change using the openspec CLI.

5|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/8007342/tillandsias --skill openspec-apply-change-8007342
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/8007342/tillandsias/tree/main/.opencode/skills/openspec-apply-change
Command: npx skills add https://github.com/8007342/tillandsias --skill openspec-apply-change-8007342

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an OpenSpec change proposal into working code requires tracking task progress, reading the right context artifacts, and updating task checklists consistently, which is error-prone when done manually. ## Core Features & Use Cases - Change Selection: Resolves the target change from user input, conversation context, or by listing active changes when ambiguous. - Status-Driven Implementation: Reads schema, progress, and apply instructions from the openspec CLI, then works through pending tasks one by one. - Guardrailed Execution: Pauses on unclear tasks, design issues, or scope creep instead of silently narrowing specified behavior. - Use Case: After drafting a spec-driven change with proposal, design, and tasks artifacts, run this skill to implement each task, mark checkboxes complete, and finish with an archive-ready change. ## Quick Start Ask the assistant to implement the tasks for your OpenSpec change, for example by saying "apply the add-auth change".

Frequently Asked Questions about openspec-apply-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement tasks from an OpenSpec change?▼

Run the apply workflow with a change name, such as /opsx-apply add-auth. The skill checks status via openspec status --json, fetches apply instructions, reads the context files, then implements each pending task and marks its checkbox complete.

What happens if I don't specify a change name?▼

The skill infers the change from conversation context or auto-selects when only one active change exists. If ambiguous, it runs openspec list --json and asks you to pick from the available changes.

Does openspec-apply-change require the openspec CLI?▼

Yes, the openspec CLI is a hard requirement. All status checks, instructions, and change listing operations run through openspec commands, and the skill restricts itself to Bash(openspec:*) tool calls.

What does the skill do when a change is blocked?▼

When status returns state blocked due to missing artifacts, it shows the message and suggests creating the missing artifact, either via /opsx-continue or by running openspec instructions for the next artifact id.

How do I work with a registered OpenSpec store?▼

Run openspec store list --json to discover store ids, then pass --store <id> on commands that read or write specs and changes. The flag stays sticky for the rest of the workflow.

When does the skill pause instead of completing a task?▼

It pauses when a task is unclear, implementation reveals a design issue, work exceeds what the spec describes, or an error occurs. It never silently narrows or defers specified behavior and only marks tasks complete when fully implemented.