openspec-apply-change

Implement OpenSpec change tasks using the OpenSpec CLI workflow.

Updated Jul 6, 2025
One-click install
npx skills add https://github.com/wishx127/mirror-server --skill openspec-apply-change-wishx127
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/wishx127/mirror-server/tree/main/.codebuddy/skills/openspec-apply-change
Command: npx skills add https://github.com/wishx127/mirror-server --skill openspec-apply-change-wishx127

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you move from an OpenSpec change request to concrete implementation without manually hunting for the right tasks, files, or workflow steps.

Core Features & Use Cases

  • Change Selection: Picks the right OpenSpec change from context or available options when the request is ambiguous.
  • Status-Driven Workflow: Checks schema status, loads the required context files, and follows the correct apply instructions.
  • Task Implementation: Works through pending tasks one by one, updates progress, and pauses when it encounters blockers or unclear requirements.
  • Use Case: A developer can ask to continue an in-progress OpenSpec change and get the remaining tasks implemented in order with clear progress updates.

Quick Start

Ask me to apply an OpenSpec change by name or from context, and I will inspect its status, read the required files, and implement the pending 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 implement OpenSpec change tasks without manually finding the right files?

OpenSpec change implementation automates file discovery by using the OpenSpec CLI to inspect change status, load required context files, and process pending tasks sequentially. You initiate the workflow by name or context, and the system tracks progress by updating task checkboxes as work completes.

What is a spec-driven workflow for change management?

A spec-driven workflow uses defined OpenSpec changes to guide code implementation. It checks schema status, loads context files, and follows apply instructions to implement tasks one by one, ensuring development aligns with the specified requirements and tracks progress automatically.

Do I need the OpenSpec CLI to automate task implementation?

Yes, the OpenSpec CLI is required to automate task implementation. The CLI inspects change status, loads context files, tracks task progress, and updates task checkboxes as work completes within the spec-driven workflow.

Can I continue partial work on an in-progress OpenSpec change?

Yes, you can continue partial work on an in-progress OpenSpec change. The workflow detects the current status, loads the required context, and resumes implementation by processing remaining pending tasks in order with clear progress updates.

What happens when task implementation encounters blockers or unclear requirements?

When task implementation encounters blockers or unclear requirements, the workflow pauses execution. This prevents incorrect implementation and allows you to resolve the ambiguity before continuing with the remaining OpenSpec change tasks.