openspec-apply-change

Implements OpenSpec change tasks and updates repository artifacts.

18|3|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/igamenovoer/houmao --skill openspec-apply-change-igamenovoer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/igamenovoer/houmao/tree/main/tests/fixtures/plain-agent-def/skills/openspec-apply-change
Command: npx skills add https://github.com/igamenovoer/houmao --skill openspec-apply-change-igamenovoer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you move from an OpenSpec change (spec/schema + tasks) to concrete code updates without manually figuring out what to implement next or which artifacts to touch.

Core Features & Use Cases

  • Select and validate the target change: Uses an explicit change name or infers it from context, and can list available changes for disambiguation.
  • Read the correct schema and instructions: Pulls workflow schema details and apply-time task lists from the OpenSpec CLI.
  • Implement tasks with progress tracking: Reads the provided context files, works task-by-task, and updates task checkboxes until completion or a blocking pause.
  • Pause safely on uncertainty or blockers: Stops when tasks are unclear, errors occur, or implementation reveals design issues that require artifact updates.

Quick Start

Ask your AI to apply the OpenSpec change by saying: "Apply the OpenSpec change 'my-change' and implement its pending tasks until completion."

Frequently Asked Questions about openspec-apply-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement OpenSpec changes and track task progress automatically?

You can resume partial OpenSpec implementation by running the CLI to load current status and context files, allowing the skill to continue from the last incomplete task and update progress tracking artifacts accordingly.

What happens when an OpenSpec task is blocked or unclear during implementation?

When an OpenSpec task is blocked or unclear, the skill pauses safely to prevent incorrect code updates, stopping execution until design issues are resolved or artifact updates are completed by the user.

Do I need the OpenSpec CLI to apply schema-driven changes to my codebase?

Yes, applying schema-driven changes requires running the OpenSpec CLI because the skill depends on it to retrieve workflow schema details, infer target changes, and read the apply-time task lists needed for implementation.

How does schema-driven change management handle disambiguation between multiple available changes?

Schema-driven change management handles disambiguation by listing available changes from the OpenSpec CLI, allowing you to select an explicit target change name or letting the skill infer the correct one from context.

What is the best way to turn an OpenSpec change into working code without manually tracking artifacts?

The best way to turn an OpenSpec change into working code is using a schema-driven apply process that reads context files, orchestrates task implementation sequentially, and automatically updates repository artifacts and task statuses.