openspec-apply-change

Guides step-by-step execution of OpenSpec changes with progress tracking.

43|1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/liyown/XHSSpec --skill openspec-apply-change-liyown
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/liyown/XHSSpec/tree/main/.claude/skills/openspec-apply-change
Command: npx skills add https://github.com/liyown/XHSSpec --skill openspec-apply-change-liyown

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams apply modifications defined by an OpenSpec change by guiding step-by-step execution and maintaining traceable progress.

Core Features & Use Cases

  • Infer the change name from context when omitted and auto-select when only one active change exists.
  • Check status and fetch apply instructions to understand the workflow schema and required artifacts.
  • Read relevant context files, display current progress, and implement tasks iteratively with guardrails to pause for clarification when needed.
  • Support an agile, fluid workflow that allows updating artifacts or archiving once all tasks complete.

Quick Start

Provide the change name to begin applying 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 apply OpenSpec changes step by step?

OpenSpec changes are applied through guided step-by-step execution that fetches instructions, reads context files, and tracks iterative task implementation until completion.

How does change management work when applying modifications with an automated workflow?

Change management in this workflow infers the change name, checks status to understand the schema, and implements tasks iteratively while maintaining traceable progress throughout the modification process.

Can I apply OpenSpec changes without specifying the change name?

Yes, you can apply OpenSpec changes without specifying the name because the workflow infers the change name from context or auto-selects when only one active change exists.

What happens when task requirements are unclear during change implementation?

When task requirements are unclear during change implementation, guardrails pause execution to handle blocked states and offer options to continue, archive, or update artifacts for clarification.

Do I need any dependencies to use this OpenSpec change automation tool?

No dependencies are required to use this OpenSpec change automation tool, as it operates independently to guide task implementation and manage workflow status without external components.

What is the best way to manage blocked states when implementing OpenSpec tasks?

The best way to manage blocked states is through built-in guardrails that pause execution on unclear requirements, allowing you to clarify context, update artifacts, or archive changes before proceeding.