openspec-apply-change

Automate applying tasks from an OpenSpec change using the OpenSpec CLI.

Updated Nov 17, 2025
One-click install
npx skills add https://github.com/Valynt/ValueOS --skill openspec-apply-change-valynt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/Valynt/ValueOS/tree/main/.windsurf/skills/openspec-apply-change
Command: npx skills add https://github.com/Valynt/ValueOS --skill openspec-apply-change-valynt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates applying tasks from an OpenSpec change to move a project from planning to implementation.

Core Features & Use Cases

  • Orchestrates the end-to-end OpenSpec change workflow: selecting a change, inspecting status, retrieving apply instructions, and executing tasks until completion.
  • Provides dynamic guidance and guardrails for ambiguous, blocked, or completed changes, including prompts for user input when needed.
  • Tracks progress and surfaces current schema and remaining tasks, enabling auditable change delivery in modern software projects.

Quick Start

Specify the OpenSpec change name to begin applying its tasks.

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 OpenSpec change task execution from planning to implementation?

Automate OpenSpec change task execution by selecting a specific change name, inspecting its status, retrieving apply instructions, and executing tasks until completion. This workflow requires the OpenSpec CLI to read and update task artifacts.

Can I track progress and remaining tasks when applying an OpenSpec change?

Track progress and remaining tasks when applying an OpenSpec change through built-in status inspection. The workflow surfaces the current schema and tracks task artifacts, enabling auditable change delivery across various OpenSpec schemas.

What happens if a task is blocked or ambiguous during OpenSpec change application?

If a task is blocked or ambiguous during OpenSpec change application, the workflow provides dynamic guardrails and prompts for user input. This ensures tasks are not skipped and requires user intervention before proceeding with blocked changes.

Does applying OpenSpec changes require the CLI to read and update task artifacts?

Applying OpenSpec changes requires the OpenSpec CLI to read and update task artifacts. The CLI handles context retrieval and task execution, orchestrating the end-to-end workflow to move a project from planning to implementation.

How do I start applying tasks from a completed or specific OpenSpec change?

Start applying tasks from a specific OpenSpec change by specifying the change name. The workflow handles change selection and provides guardrails if the change is already completed, preventing redundant task execution.