openspec-apply-change

Implements tasks from an OpenSpec change using the openspec CLI.

4|Updated Jun 21, 2026
One-click install
npx skills add https://github.com/NEETROF/cymbra --skill openspec-apply-change-neetrof
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/NEETROF/cymbra/tree/main/.cursor/skills/openspec-apply-change
Command: npx skills add https://github.com/NEETROF/cymbra --skill openspec-apply-change-neetrof

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an approved OpenSpec change proposal into actual code requires manually tracking tasks, reading the right context files, and keeping checkboxes in sync. This Skill automates that loop so implementation stays aligned with the spec. ## Core Features & Use Cases - Change Selection: Infers the target change from conversation context or lists active changes via openspec list --json when ambiguous. - Schema-Aware Execution: Reads openspec status and openspec instructions apply output to load the correct context files (proposal, specs, design, tasks) for any workflow schema. - Task Loop with Progress Tracking: Implements each pending task, marks - [ ] as - [x] in the tasks file, and reports progress as N/M tasks complete. - Use Case: After drafting a spec-driven change for a new API endpoint, ask the assistant to apply the change; it reads the proposal and tasks, implements each item, and pauses with options if a design issue or blocker appears. ## Quick Start Ask the assistant to implement the tasks from your OpenSpec change, optionally naming the change, for example: apply the add-user-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?▼

Invoke the apply workflow with an optional change name. The skill runs openspec status and openspec instructions apply to load context files, then works through each pending task, marking checkboxes complete as it goes.

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

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

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

Yes, the openspec CLI is a hard requirement. The skill shells out to openspec status, openspec instructions apply, and openspec list to discover schema, context files, and task state.

What does the skill do when an OpenSpec change is blocked or finished?▼

For a blocked state with missing artifacts it shows the message and suggests continuing the change workflow. For an all-done state it congratulates you and suggests archiving the change instead of editing code.

Can I update the spec or design during implementation?▼

Yes. The workflow is fluid rather than phase-locked: if implementation reveals a design issue, the skill pauses and suggests updating the artifacts before continuing with remaining tasks.