openspec-apply-change

Implement OpenSpec change tasks using schema definitions and context files.

1|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/CloudDevCrusader/riddle-rush-mono-repo --skill openspec-apply-change-clouddevcrusader
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/CloudDevCrusader/riddle-rush-mono-repo/tree/main/.claude/skills/openspec-apply-change
Command: npx skills add https://github.com/CloudDevCrusader/riddle-rush-mono-repo --skill openspec-apply-change-clouddevcrusader

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec-cli, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the implementation of tasks defined within an OpenSpec change, streamlining the development workflow and ensuring tasks are completed systematically.

Core Features & Use Cases

  • Task Implementation: Executes defined tasks from an OpenSpec change, updating progress and handling different states.
  • Contextual Awareness: Infers or prompts for the correct change if not explicitly provided, and reads necessary context files.
  • Use Case: A developer receives a new feature specification via OpenSpec. They can use this Skill to automatically start implementing the tasks outlined in the specification, ensuring adherence to the defined workflow and progress tracking.

Quick Start

Use the openspec-apply-change skill to start implementing the tasks for the change named 'feature-x'.

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 implementing tasks from an OpenSpec change?

This Skill automates OpenSpec change implementation by executing defined tasks based on schema definitions and context files. It systematically applies changes, updates task progression, and provides status updates throughout the development workflow lifecycle.

What is the best way to track task progression and identify blockers during a change implementation?

Tracking task progression and identifying blockers during change implementation is handled automatically by reading context files and schema definitions. The system continuously monitors task states, providing status updates and highlighting blockers as they arise.

Do I need the openspec CLI to apply changes to my development workflow?

Yes, the openspec CLI is required for execution and status checks when applying changes to your development workflow. The Skill relies on this command-line interface to automate task implementation and update progress.

Can I start implementing tasks if the change name is not explicitly provided?

Yes, you can start implementing tasks without an explicit change name. The Skill infers or prompts for the correct OpenSpec change by reading necessary context files, ensuring the implementation process begins smoothly.

What are the limitations of automating task implementation with schema definitions?

A limitation of automating task implementation with schema definitions is that it depends entirely on the openspec CLI environment and accurate context files. If schemas are incomplete or the CLI is absent, task progression and blocker identification will fail.