openspec-apply-change

Apply OpenSpec changes through status checks and iterative task implementation.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/atman-33/skills --skill openspec-apply-change-atman-33
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/atman-33/skills/tree/main/.github/skills/openspec-apply-change
Command: npx skills add https://github.com/atman-33/skills --skill openspec-apply-change-atman-33

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill orchestrates the end-to-end application of an OpenSpec change by guiding the user through change naming, status checks, context loading, and iterative task implementation, reducing manual coordination and error.

Core Features & Use Cases

  • Guided change application: Select and apply an OpenSpec change, with automatic handling of ambiguity and user prompts when needed.
  • Status-driven workflow: Retrieve current schema, progress, and remaining tasks to inform the next steps.
  • Context-aware execution: Load relevant context files and apply tasks while keeping artifacts coordinated with the OpenSpec change.
  • Progress reporting: Communicate ongoing progress and provide clear instructions for next actions.

Quick Start

Use this skill to apply an OpenSpec change by providing the change name or allowing it to infer from the conversation. The skill will announce the chosen change, fetch status, load context files, and begin implementing remaining tasks until completion or a blocker is encountered.

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 an OpenSpec change across my entire project workflow?

Applying an OpenSpec change end-to-end is automated by selecting the change, checking status, loading context files, and iteratively implementing remaining tasks until completion or a blocker is encountered.

What is the best way to automate OpenSpec task execution and artifact updates?

Automating OpenSpec task execution requires a tool that coordinates artifact updates, retrieves current schema progress, and handles blocked, all_done, and in-progress states during iterative implementation.

Do I need the OpenSpec CLI to automate change management workflows?

Yes, automating OpenSpec change management workflows requires the OpenSpec CLI and access to relevant change artifacts to load context and apply tasks correctly.

How does context-aware execution work when applying OpenSpec changes?

Context-aware execution works by loading relevant context files and applying tasks while keeping artifacts coordinated with the OpenSpec change throughout the implementation process.

What happens if an OpenSpec change encounters a blocker during task implementation?

When a blocker is encountered during OpenSpec task implementation, the automated workflow halts progress reporting and provides clear instructions for the next actions required.

Can I infer an OpenSpec change name from the current conversation context?

Yes, you can infer the OpenSpec change name from the conversation context, allowing the workflow to automatically announce the chosen change, fetch status, and begin implementation.