openspec-apply-change

Apply OpenSpec changes by executing remaining tasks in sequence.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/thistleknot/skills --skill openspec-apply-change-thistleknot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/thistleknot/skills/tree/main/openspec-apply-change
Command: npx skills add https://github.com/thistleknot/skills --skill openspec-apply-change-thistleknot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you implement work defined by an OpenSpec change, turning a change name into a guided, task-by-task implementation workflow with the right context and progress tracking.

Core Features & Use Cases

  • Change selection & disambiguation: Infers a change from conversation context, auto-selects when only one active change exists, or prompts by listing available changes.
  • Status-driven schema handling: Uses openspec status to detect the workflow schema and identify the artifact that contains tasks.
  • Dynamic apply instructions: Calls OpenSpec to retrieve schema-specific contextFiles, task list, and guidance for the current state (including blocked or all-done cases).
  • Task execution loop with guardrails: Reads the required context files first, implements pending tasks with minimal scoped changes, updates task checkboxes, and pauses for unclear tasks or blockers.
  • Progress reporting: Summarizes completed tasks for the current session and overall progress on completion or pause scenarios.

Quick Start

Ask your agent to run openspec-apply-change for the specified OpenSpec change and begin implementing the pending tasks using the provided context files.

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 an OpenSpec change and execute its implementation tasks?

To apply an OpenSpec change, the workflow selects the correct active change, loads schema-specific context files using openspec status, and executes remaining tasks in sequence until completion or a blocked state occurs.

How does schema-driven workflow automation handle paused or partially completed changes?

Schema-driven workflow automation resumes partially completed changes by reading openspec status, retrieving dynamic apply instructions, identifying pending task checkboxes, and continuing the task execution loop from the last completed state.

What is the process for tracking progress during code implementation with OpenSpec?

Progress tracking during code implementation involves updating task completion markers within the context files after each scoped change, then summarizing completed tasks and overall progress when the session pauses or finishes.

Do I need the openspec CLI to manage task automation for code implementation?

Yes, task automation for code implementation requires the openspec CLI to determine the workflow schema, retrieve contextFiles, generate task lists, and provide guidance for blocked or all-done states.

What happens when a task automation workflow encounters unclear tasks or blockers?

When task automation encounters unclear tasks or blockers, the execution loop pauses implementation, leaves the current task checkbox unchecked, and reports the overall progress to await user clarification.

Can I use change management automation if multiple active changes exist simultaneously?

Yes, change management automation handles multiple active changes by disambiguating through conversation context or prompting you to select the correct change from a list of available active workflows.