openspec-apply-change

Implements pending OpenSpec change tasks using CLI-provided context files and instructions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns OpenSpec change definitions into concrete, incremental code work so you can implement features without losing track of required tasks, context, or progress.

Core Features & Use Cases

  • Selects the right change automatically or by prompt: Infers from conversation context or prompts you to choose when multiple active changes exist.
  • Reads the correct schema and artifacts: Uses openspec status and openspec instructions apply to determine workflow schema and the concrete context files to load.
  • Executes tasks one-by-one with guardrails: Implements each pending task, pauses on ambiguity or blockers, and marks task checkboxes complete as it goes.

Quick Start

Ask the AI to apply the current OpenSpec change and implement all pending tasks until the change is complete or blocked.

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 changes incrementally without losing track of pending tasks?

Applying OpenSpec changes incrementally requires reading schema status and fetching apply instructions to loop through pending tasks. The workflow executes tasks one-by-one with guardrails, pausing on ambiguity or blockers, and updating task completion state while reporting progress.

What is the best way to automate task orchestration for code changes defined in a schema-driven workflow?

Task orchestration for schema-driven code changes uses CLI commands to determine workflow schema and load concrete context files. It automatically selects the right change from context or prompts you when multiple active changes exist, ensuring minimal scoped modifications.

How do I apply code changes when an implementation task is partially complete or blocked?

Applying code changes to partially complete or blocked tasks requires a workflow that pauses for user prompting when needed. It reads the correct schema, executes pending tasks sequentially, and marks task checkboxes complete as it progresses through the implementation.

Does OpenSpec apply instructions support selecting changes automatically when multiple are active?

OpenSpec apply instructions support automatic change selection by inferring from conversation context. When multiple active changes exist, the system prompts you to choose the correct change before reading the workflow schema and fetching context files.

Can I use OpenSpec status commands to track progress for incremental code implementations?

OpenSpec status commands enable progress tracking for incremental code implementations by determining the workflow schema. The system reads status to identify pending tasks, fetches apply instructions, and updates task completion state while reporting implementation progress.

Why does my agent automation workflow pause during OpenSpec task implementation?

Agent automation workflows pause during OpenSpec task implementation when encountering ambiguity or blockers in pending tasks. The system needs user prompting to resolve these issues before continuing the incremental workflow and marking task checkboxes complete.