openspec-apply-change

Automates OpenSpec change implementation through guided step-by-step task execution.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When an OpenSpec change is ready to be worked on, this Skill helps you systematically implement the required tasks without guessing outputs or schema details, keeping progress and blockers clear.

Core Features & Use Cases

  • Change selection with safe ambiguity handling: Uses the provided change name, or infers from context, and otherwise queries available changes for user selection.
  • Schema-aware guidance: Retrieves workflow schema and the correct product context via CLI status, then reads the exact apply instructions.
  • Task-by-task execution with guardrails: Iterates through tasks, updates checkboxes as completed, and pauses when tasks are unclear, errors occur, or design issues require updating outputs.
  • Progress reporting and integration-friendly flow: Shows current schema, completion counts, remaining overview, and supports interleaving with other “change operations” like continue/archiving.

Quick Start

Ask to apply an OpenSpec change by running the openspec-apply-change skill and (optionally) specifying the change name you want implemented.

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 automatically without guessing schema details?

You can implement OpenSpec changes by using a schema-driven workflow that retrieves apply instructions via CLI status, reads contextFiles from JSON outputs, and guides task-by-task execution with automatic checkbox updates until completion.

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

When OpenSpec task requirements are unclear or impeded, the execution pauses rather than guessing, allowing developers to resolve design issues or errors before resuming the task workflow.

Do I need the openspec-cn CLI to apply change management tasks?

Yes, openspec-cn CLI access is required because the workflow uses list, status, and instructions apply commands to retrieve schema-aware contextFiles and determine the correct execution path for each task.

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

Schema-driven change management handles multiple changes by using the provided name, inferring from context, or querying available changes via CLI to prompt user selection before retrieving apply instructions.

Can I interleave OpenSpec task execution with other change operations like archiving?

Yes, you can interleave OpenSpec task execution with other change operations like continue or archiving, as the workflow supports progress reporting and integration-friendly flow between different change management actions.

What progress reporting is available during OpenSpec change implementation?

Progress reporting during OpenSpec change implementation shows the current schema, completion counts, and remaining task overview, keeping progress and blockers clear throughout the task-by-task execution.