openspec-apply-change

Automates implementation of pending tasks from an AnVIL change via CLI-generated checklists and workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of implementing tasks listed in an OpenSpec change so contributors can make focused, incremental progress without repeatedly parsing CLI output or hunting for context files.

Core Features & Use Cases

  • Change selection: infer or prompt to select the intended change and announce how to override selection.
  • State-aware execution: query openspec status and instructions, interpret schema and contextFiles, and handle states like blocked, all_done, or in-progress.
  • Task-driven implementation loop: read context files, perform minimal scoped changes, update task checklists, present progress, and pause for unclear tasks or blockers.
  • Use Case: a developer asks to continue implementing a partially completed spec-driven change and the Skill iterates through remaining tasks, updating files and reporting progress.

Quick Start

Use the openspec CLI to apply change "my-change" and implement its next pending task while reporting progress.

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 incrementally?

To implement OpenSpec change tasks incrementally, query change status and apply instructions via the openspec CLI. The Skill reads context files, performs minimal scoped changes, and updates task checklists to track progress for spec-driven workflows.

What is spec-driven change management using the openspec CLI?

Spec-driven change management using the openspec CLI involves inspecting change status, retrieving apply instructions in JSON, and updating task checklists. This automates focused, incremental progress without repeatedly parsing CLI output or hunting for context files.

How do I update task checklists when applying an OpenSpec change?

You update task checklists when applying an OpenSpec change by parsing the JSON output from the openspec CLI. The Skill marks items complete in checklist files and presents progress after performing minimal scoped changes for each task.

Can I resume a partially completed spec-driven change with openspec?

Yes, you can resume a partially completed spec-driven change with openspec. The Skill queries the current state, interprets schema and contextFiles, and iterates through remaining pending tasks while reporting progress and updating files.

How does OpenSpec handle blocked or ambiguous task states during implementation?

OpenSpec handles blocked or ambiguous task states by pausing the task-driven implementation loop. The Skill detects these states from the openspec JSON output and prompts the user for clarification or selection before proceeding.

Do I need to manually parse openspec JSON output to implement change artifacts?

No, you do not need to manually parse openspec JSON output to implement change artifacts. The Skill automates parsing the JSON instructions, reading context files, and updating task checklists so contributors can make focused progress.