openspec-apply-change

Implement OpenSpec change tasks using the openspec CLI.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec, 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

  • Automated Task Implementation: Executes tasks defined in OpenSpec changes, updating progress and handling different schema types.
  • Contextual Awareness: Infers or prompts for the correct change and reads necessary context files based on the OpenSpec CLI output.
  • Use Case: When a new feature specification is defined in OpenSpec, this Skill can be used to automatically implement the associated development tasks, track progress, and report completion status.

Quick Start

Use the openspec-apply-change skill to implement 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 task implementation for an OpenSpec change?

Automating OpenSpec task implementation involves executing schema-driven workflows that select tasks, check status, and read context files. This Skill systematically processes development tasks defined within an OpenSpec change and updates progress automatically.

What is the best way to track development progress using OpenSpec?

Tracking OpenSpec development progress is handled by automatically executing change tasks and updating their completion status. The Skill reads CLI output to infer the correct change and reports task completion systematically.

Do I need the openspec CLI to run schema-driven development workflows?

Yes, the openspec CLI is required to execute schema-driven development workflows. The Skill depends on the CLI for execution, change management interaction, and retrieving the necessary context files for task implementation.

How does context file reading work when implementing OpenSpec changes?

Context file reading during OpenSpec implementation works by parsing CLI output to infer or prompt for the correct change. The Skill then reads the necessary context files based on schema types to drive iterative task execution.

Can I use this approach to implement features across different schema types?

Yes, you can implement features across different schema types. The Skill handles automated task implementation by executing tasks defined in OpenSpec changes and adapting its workflow based on varying schema-driven requirements.