openspec-apply-change

Name: openspec-apply-change
Availability: InStock
Author: Alex

Implement OpenSpec change tasks and synchronize the task list during execution.

Updated Mar 17, 2026

Search Tags:#change management #spec-driven development #openspec #repository coordination #task implementation #cli workflow

Ready to run

npx skills add https://github.com/alexzhang1030/platform-demo --skill openspec-apply-change-alexzhang1030

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/alexzhang1030/platform-demo/tree/main/.agents/skills/openspec-apply-change
Command: npx skills add https://github.com/alexzhang1030/platform-demo --skill openspec-apply-change-alexzhang1030

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of starting and continuing an OpenSpec change by guiding the agent through change selection, status checks, context loading, and task execution.

Core Features & Use Cases

Change selection: Picks a named change, infers one from context, or prompts when multiple changes are available.
Workflow coordination: Reads OpenSpec status and apply instructions so the agent follows the correct schema and context files.
Task completion: Works through pending tasks one by one, updates task checkboxes, and pauses cleanly when blocked or ambiguous.
Use case: Ideal when you need to implement a spec change incrementally while staying aligned with the repository’s OpenSpec artifacts.

Quick Start

Use the openspec-apply-change skill to implement the active OpenSpec change and complete its remaining tasks.

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 OpenSpec changes and keep the task list synchronized?▼

Implement OpenSpec changes by selecting a named change, parsing CLI JSON status output, loading schema-specific context artifacts, and executing pending tasks while updating task checkboxes to keep the repository synchronized. The workflow pauses cleanly when encountering blocked or ambiguous states.

What is spec-driven development workflow coordination for task implementation?▼

Spec-driven development workflow coordination reads OpenSpec status and apply instructions to guide agents through selecting changes, inspecting status, loading context files, and completing remaining tasks incrementally while following repository artifacts and schemas.

How do I handle ambiguous or blocked states during OpenSpec change implementation?▼

Handle ambiguous or blocked states by pausing task execution cleanly and making minimal scoped changes to the repository. The workflow detects these states from CLI JSON output and stops further task implementation until the blockage is resolved.

Can I use OpenSpec CLI workflows for incremental spec change task completion?▼

Yes, OpenSpec CLI workflows support incremental spec change task completion by working through pending tasks one by one, updating task checkboxes, and inferring the active change from context or prompting when multiple changes are available.

Do I need to parse OpenSpec CLI JSON output to load context artifacts for changes?▼

Yes, parsing OpenSpec CLI JSON output is required to load schema-specific context artifacts, inspect change status, and follow apply instructions correctly during task implementation and repository coordination.

What's the best way to manage multiple available OpenSpec changes in a repository?▼

Manage multiple OpenSpec changes by letting the workflow prompt for selection when multiple changes are available, or automatically inferring the correct change from repository context before loading artifacts and executing remaining tasks.