openspec-apply-change

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

Apply OpenSpec changes by sequencing status checks and iterative task execution.

Updated Apr 26, 2026

Search Tags:#automation #workflow #cli #openspec #task-management #change-management

Ready to run

npx skills add https://github.com/rangechow/LotGameClient --skill openspec-apply-change-rangechow

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/rangechow/LotGameClient/tree/main/.claude/skills/openspec-apply-change
Command: npx skills add https://github.com/rangechow/LotGameClient --skill openspec-apply-change-rangechow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates and automates the application of OpenSpec changes, guiding users through change selection, status checks, and incremental task implementation to reduce manual effort and errors.

Core Features & Use Cases

Structured change workflow: select a change, check status, fetch apply instructions, and progress through tasks.
Context-aware execution: reads context files and adapts steps based on the current artifact schema.
Progress visibility and guardrails: reports progress, handles blocked states, and suggests remedies when needed.

Quick Start

Provide the change name to begin implementing, or let the system infer it from context.

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 and track their progress?▼

OpenSpec change management automates sequencing status checks, fetching instructions, and executing tasks iteratively. It handles blocked, in-progress, and completed states across artifacts to ensure safe, documented, and scoped code updates.

How does OpenSpec handle blocked or in-progress change states?▼

OpenSpec change workflows handle blocked, in-progress, and completed states by sequencing status checks and iterative task execution. Progress visibility features report status and suggest remedies when blocked states are encountered.

What is the best way to automate task management for OpenSpec changes?▼

Automating OpenSpec change workflows involves sequencing status checks, instructions, and iterative task execution via CLI. This approach minimizes manual effort, ensures scoped code updates, and provides progress tracking across multiple artifacts.

Do I need to manually provide context files when applying an OpenSpec change?▼

No, the system reads context files automatically and adapts steps based on the current artifact schema. This context-aware execution ensures safe, documented changes with minimal, scoped code updates during the OpenSpec workflow.

Can I let the system infer the change name during an OpenSpec workflow?▼

Yes, you can let the system infer the change name from context to begin implementing tasks immediately. Alternatively, you can provide the change name explicitly to start the structured change workflow and status checks.

Why does my OpenSpec change workflow keep getting blocked?▼

OpenSpec change workflows get blocked when status checks fail or dependencies are unmet across artifacts. The system identifies these blocked states, reports progress visibility, and suggests remedies to safely resume task execution.