openspec-apply-change

Implement pending tasks from an OpenSpec change using CLI status and instructions.

5|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/Catsofsuffering/CCGS --skill openspec-apply-change-catsofsuffering
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/Catsofsuffering/CCGS/tree/main/.agents/skills/openspec-apply-change
Command: npx skills add https://github.com/Catsofsuffering/CCGS --skill openspec-apply-change-catsofsuffering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides implementers through applying and completing tasks produced by an OpenSpec change, removing uncertainty about which files to read, which tasks remain, and how to mark progress.

Core Features & Use Cases

  • Change Selection & Discovery: Infer a change from conversation context, auto-select when only one active change exists, or prompt the user to choose from openspec list output when ambiguous.
  • Status & Instruction Parsing: Run openspec status and openspec instructions apply to determine schema, context files, task progress, and dynamic apply instructions.
  • Context-aware Implementation Loop: Read context files, show current progress, implement pending tasks iteratively, update task checkboxes, and pause when tasks are unclear or blockers arise.
  • Guardrails & Outputs: Handles blocked and all_done states, suggests next steps (e.g., continue, update artifacts, archive), and provides structured session summaries of completed and remaining tasks.

Quick Start

Use the skill to implement the OpenSpec change named "my-change" and follow prompts to work through each pending task.

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 during a development workflow?

To implement OpenSpec change tasks, select a change, run openspec status and openspec instructions apply to parse context files, and execute pending tasks iteratively while updating task checkboxes.

What is the best way to track spec-driven implementation progress using the openspec CLI?

Tracking spec-driven implementation progress involves running openspec status to output JSON schemas and task progress, reading context files, and checking off completed tasks as you implement them.

How does the OpenSpec apply workflow handle ambiguity or blockers during task implementation?

The OpenSpec apply workflow pauses implementation when it encounters ambiguity, blockers, or design issues, suggesting next steps like continuing, updating artifacts, or archiving the change.

Do I need the openspec CLI to apply spec-driven changes to my project?

Yes, you need the openspec CLI installed to apply spec-driven changes, as the workflow requires it to provide JSON status outputs and dynamic apply instructions for reading context files.

Can I automatically select an OpenSpec change if only one active change exists?

Yes, the workflow can auto-select an OpenSpec change when only one active change exists, or prompt you to choose from openspec list output when the target change is ambiguous.

What happens when all OpenSpec implementation tasks are completed?

When all OpenSpec implementation tasks are completed, the workflow enters an all_done state, providing a structured session summary and suggesting downstream steps like updating artifacts or archiving.