openspec-apply-change

Implements tasks from an OpenSpec change using CLI-driven status and instructions.

6|7|Updated Jun 4, 2026
One-click install
npx skills add https://github.com/nodesource/nsolid-plugin --skill openspec-apply-change-nodesource
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/nodesource/nsolid-plugin/tree/main/.opencode/skills/openspec-apply-change
Command: npx skills add https://github.com/nodesource/nsolid-plugin --skill openspec-apply-change-nodesource

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It removes the guesswork of turning an OpenSpec change proposal into working code by reading the change's tasks, context files, and progress state directly from the openspec CLI and guiding implementation task by task. ## Core Features & Use Cases - Change Selection: Infers the target change from conversation context or lists active changes via openspec list --json when ambiguous. - Status-Aware Implementation: Parses openspec status and openspec instructions apply JSON output to determine schema, context files, progress, and blocked or completed states. - Task Loop with Guardrails: Implements each pending task, marks checkboxes complete in the tasks file, and pauses on unclear requirements, design issues, or errors. - Use Case: After drafting an OpenSpec change with proposal, design, and tasks, invoke this skill to work through all 7 tasks sequentially, updating the tasks file as each one completes. ## Quick Start Ask the assistant to implement the tasks from your OpenSpec change, optionally naming the change to apply.

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 a change name or let it infer one from context. It runs openspec status and openspec instructions apply to load context files and tasks, then implements each pending task and marks it complete in the tasks file.

How to continue a partially implemented OpenSpec change?▼

Re-run the apply workflow on the same change. The CLI output reports current progress (N/M tasks complete), so implementation resumes from the first pending task rather than starting over.

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

Yes, the openspec CLI is a stated compatibility requirement. The skill depends on commands like openspec list, openspec status, and openspec instructions apply to discover changes, schemas, and task state.

What happens when an OpenSpec change is blocked or missing artifacts?▼

When the apply instructions return a blocked state due to missing artifacts, the skill shows the message and suggests creating the missing artifacts first instead of attempting implementation.

Can it edit files outside the change's allowed scope?▼

No. It respects the actionContext and allowedEditRoots from the status JSON. In workspace-planning mode with empty edit roots, it treats linked repos as read-only and stops before editing.