openspec-apply-change

Automates applying OpenSpec workflow changes to the codebase.

Updated Dec 25, 2025
One-click install
npx skills add https://github.com/wtg42/tty-clock-timer --skill openspec-apply-change-wtg42
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/wtg42/tty-clock-timer/tree/main/.opencode/skills/openspec-apply-change
Command: npx skills add https://github.com/wtg42/tty-clock-timer --skill openspec-apply-change-wtg42

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The OpenSpec apply-change skeleton provides a structured way to implement and validate changes across OpenSpec workflows, reducing manual coordination and errors.

Core Features & Use Cases

  • Guided change selection and status checks via the openspec CLI
  • Read context files and track progress for multi-step changes
  • Iterative implementation with built-in safeguards and progress reporting

Quick Start

Provide the change name to begin applying an OpenSpec change and let the system guide the implementation.

Frequently Asked Questions about openspec-apply-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I apply OpenSpec changes to my codebase with CLI automation?

To apply OpenSpec changes, provide the change name to initiate status checks and context reading. The workflow then guides iterative implementation across schemas, tracking progress to drive safe, incremental codebase updates.

What is the best way to track multi-step change implementation progress?

Tracking multi-step changes is handled by reading context files and progress data via the openspec CLI. This monitors task state progression, ensuring structured implementation and reducing manual coordination errors.

How does iterative implementation work with OpenSpec workflows?

Iterative implementation works by reading task state and progress data to apply changes incrementally. Built-in safeguards and status checks validate each step, ensuring safe codebase modifications across various schemas.

Do I need the openspec CLI installed to apply changes to my code?

Yes, the openspec CLI is required to apply changes. It drives guided change selection, executes status checks, and reads the context files necessary for safe, incremental codebase implementation.

Why use OpenSpec for change management instead of manual codebase updates?

Using OpenSpec for change management reduces manual coordination and errors during implementation. It automates status checks and context reading, providing structured validation for incremental updates across complex schemas.

OpenSpec apply-change is not working, what are the limitations?

Limitations include dependency on the openspec CLI and readable context files. Without proper task state and progress data, the system cannot drive incremental changes or validate implementation steps safely.