openspec-apply-change

Implement OpenSpec change tasks by reading CLI instructions and updating artifacts.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/jrmatherly/spacebot --skill openspec-apply-change-jrmatherly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/jrmatherly/spacebot/tree/main/.windsurf/skills/openspec-apply-change
Command: npx skills add https://github.com/jrmatherly/spacebot --skill openspec-apply-change-jrmatherly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many spec-driven development workflows require repeatedly reading CLI-generated instructions, locating context files, and making minimal, targeted code changes while keeping task artifacts in sync; this Skill automates and guides that workflow so implementers can focus on coding rather than orchestration.

Core Features & Use Cases

  • Change selection & validation: Infers or prompts to choose the correct change, lists active changes when ambiguous, and announces the chosen change and how to override it.
  • CLI-driven context retrieval: Calls the openspec CLI to get status and apply instructions, parses JSON output to discover schema, context files, progress, and dynamic instructions.
  • Iterative implementation loop: Reads relevant context files, implements pending tasks with minimal, focused changes, updates task checkboxes, and handles blocked or all_done states with clear guidance.
  • Use Case: A developer continues work on an active OpenSpec change, uses the Skill to fetch current tasks, apply incremental code updates, and mark progress without manually juggling files and JSON outputs.

Quick Start

Use the openspec CLI to fetch apply instructions for the target change and implement the next pending task.

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 spec-driven change tasks using CLI instructions?

To implement spec-driven change tasks, the Skill reads CLI apply instructions, parses JSON status outputs to find pending tasks, and iteratively updates code and task artifacts until all tasks are marked complete.

What is the best way to manage OpenSpec change workflows during development?

Managing OpenSpec change workflows involves invoking the openspec CLI to retrieve context files and dynamic instructions, then applying minimal, targeted code changes while keeping task checkboxes synchronized.

How does the OpenSpec apply process handle ambiguous change selections?

When change selection is ambiguous, the Skill lists active changes and prompts you to choose the correct one, safely handling blocked, all_done, and ambiguous states with clear guidance.

Can I automate task artifact updates while implementing OpenSpec changes?

Yes, task artifact updates are automated by parsing JSON apply outputs, implementing pending tasks with focused changes, and marking task checkboxes complete without manually juggling files.

Do I need the openspec CLI installed to use this spec-driven implementation workflow?

Yes, the openspec CLI is required because the workflow operates by invoking it to fetch status, parse JSON schema outputs, discover context files, and retrieve dynamic apply instructions.

Why is my OpenSpec change implementation blocked during a development session?

Implementation blocks occur when the CLI reports a blocked state; the Skill detects this from JSON status outputs and provides clear guidance on how to resolve the blocked condition before proceeding.