openspec-apply-change

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

Automate OpenSpec change application with task selection and status checks.

Updated Mar 4, 2026

Search Tags:#automation #context-awareness #openspec #development-workflow #progress-tracking #change-management

Ready to run

npx skills add https://github.com/kunish/muon --skill openspec-apply-change-kunish

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implement tasks from OpenSpec changes in a structured, automated fashion, reducing manual overhead and ensuring consistent application of changes across artifacts.

Core Features & Use Cases

Change-aware orchestration: selects the target change, checks status, and guides implementation.
Context-driven execution: reads relevant artifacts (proposal, specs, design, tasks) to drive tasks with minimal ambiguity.
Progress tracking & state handling: handles blocked, in-progress, and all-done states with clear guidance and safe fallbacks.

Quick Start

Provide the change name to begin applying the OpenSpec change and follow the on-screen prompts to complete 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 automate OpenSpec change implementation end-to-end?▼

Automating OpenSpec changes involves orchestrating task selection, status checks, and implementation steps across multiple schemas. It reads relevant artifacts like proposals, specs, and tasks to drive context-aware execution with minimal ambiguity and safe fallbacks.

What is context-aware execution for development workflow changes?▼

Context-aware execution reads relevant artifacts like proposals, specs, design, and tasks to drive implementation with minimal ambiguity. It ensures changes are scoped minimally and applied consistently across varying artifact contexts during the development workflow.

How do I apply OpenSpec changes when tasks are blocked or in-progress?▼

Applying OpenSpec changes handles blocked, in-progress, and completed states by providing clear guidance and safe fallbacks. It tracks progress dynamically and offers state-specific instructions to prevent errors when encountering blockers during implementation.

Can I use automated change management across multiple artifact schemas?▼

Automated change management supports varying artifact contexts and applies across multiple change schemas. It orchestrates implementation steps regardless of schema differences, ensuring consistent application while maintaining progress tracking and context-awareness.

What's the best way to track progress when implementing spec changes?▼

The best way to track progress is through dynamic guidance based on current state, with built-in safeguards for ambiguity or blockers. Progress tracking handles all states from in-progress to all-done, ensuring structured and consistent application of spec changes.

Do I need to manually resolve ambiguity when applying OpenSpec changes?▼

You do not need to manually resolve ambiguity because the process includes built-in safeguards for ambiguity or blockers. It reads relevant artifacts to drive tasks with minimal ambiguity and provides safe fallbacks when blocked states are encountered.