openspec-apply-change

Coordinate and implement OpenSpec changes through selection, status checks, and task execution.

3|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/g1331/AutoRouter --skill openspec-apply-change-g1331
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/g1331/AutoRouter/tree/main/.claude/skills/openspec-apply-change
Command: npx skills add https://github.com/g1331/AutoRouter --skill openspec-apply-change-g1331

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate and implement OpenSpec changes by guiding users through selecting or inferring a change, verifying its status, retrieving apply instructions, reading necessary context, and iterating task execution until completion or appropriate pause.

Core Features & Use Cases

  • Orchestrates the end-to-end OpenSpec change application, including change selection, status inspection, instruction retrieval, and task implementation.
  • Manages special states such as blocked or all_done with clear guidance and prompts to continue or pause.
  • Works across common OpenSpec schemas, enabling deterministic workflows for development, design, and documentation tasks.

Quick Start

Provide the change name to begin applying the OpenSpec change or ask for clarification if the change is ambiguous.

Frequently Asked Questions about openspec-apply-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I apply OpenSpec changes to my software project?

To apply OpenSpec changes, provide the change name to initiate the workflow. The system verifies status, retrieves apply instructions, reads necessary context, and iterates task execution until completion or pause.

What is OpenSpec change management and when do I need it?

OpenSpec change management is a structured workflow for software development that guides selection, status checks, and task execution. You need it when coordinating design, specs, and implementation tasks across single or concurrent changes.

Can I manage multiple concurrent changes with the OpenSpec CLI?

Yes, you can manage multiple concurrent changes with the OpenSpec CLI. The workflow handles active changes across design, specs, and implementation tasks, providing dynamic guidance for each until tasks are complete or paused.

How do I handle a blocked status when implementing an OpenSpec change?

When an OpenSpec change is blocked, the workflow provides clear guidance and prompts to continue or pause. It manages special states like blocked or all_done with structured instructions to help you resolve the impasse.

Do I need to specify the change name to start the OpenSpec workflow?

You should provide the change name to begin applying the OpenSpec change. If the change is ambiguous or unspecified, the system will ask for clarification to infer the correct change and proceed.

When should I pause or archive an OpenSpec change instead of completing it?

You should pause or archive an OpenSpec change when tasks cannot proceed due to blockers. The workflow enforces structured updates and dynamic guidance, allowing you to pause or archive when completion is not feasible.