openspec-apply-change

Orchestrate OpenSpec change application with status checks and task execution.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates the end-to-end application of an OpenSpec change by coordinating status checks, context retrieval, and task execution across artifacts.

Core Features & Use Cases

  • Change discovery and selection: automatically identify the active OpenSpec changes or prompt for a specific name.
  • Status & context orchestration: fetch status, understand the schema, and load relevant context files (proposal/specs/design).
  • Task execution loop: read task lists, apply changes to codebase, and mark tasks as completed.
  • Progress visibility & guidance: report progress, handle blocked states, and suggest next steps or archiving when done.
  • Use cases include starting a new change, continuing a partially completed change, and iterating on remaining tasks with dynamic instructions.

Quick Start

Provide the change name to begin applying tasks, or ask me to infer it from the conversation.

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 management from start to finish?

Automating OpenSpec change management involves orchestrating status checks, context loading, and task execution across artifacts. You select a change, load its proposal and specs, apply tasks to the codebase, and update progress until completion.

How do I resume a partially completed OpenSpec change?

To resume a partially completed OpenSpec change, you continue the application process by selecting the active change, evaluating its current progress status, and iterating through the remaining tasks listed in the context files.

What context files are loaded when applying an OpenSpec change?

Applying an OpenSpec change loads proposal, spec, and design context files. These files provide the necessary schema and instructions to read task lists, implement codebase changes, and accurately mark tasks as completed.

Can I execute OpenSpec tasks without manually checking the change status first?

Executing OpenSpec tasks requires an automated status check first. The process enforces structured steps for status inspection and context retrieval before applying any changes to ensure task implementation aligns with the current progress.

What happens when an OpenSpec change application is blocked?

When an OpenSpec change application is blocked, the orchestration process reports the progress visibility, handles the blocked state, and suggests next steps or archiving guidance to help you resolve the issue and move forward.

Does this OpenSpec workflow automation support iterating on remaining tasks?

Yes, this OpenSpec workflow automation supports iterating on remaining tasks. It provides dynamic instructions to read the task list, apply changes to artifacts, and update progress until all change tasks are fully completed.