openspec-apply-change

Name: openspec-apply-change
Availability: InStock
Author: Artagon

Implement OpenSpec change tasks by fetching instructions and reading context files.

Updated Nov 12, 2025

Search Tags:#developer workflow #implementation #task automation #progress tracking #schema-driven #openspec #workspace updates

Ready to run

npx skills add https://github.com/artagon/artagon-vscode-profiles --skill openspec-apply-change-artagon

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/artagon/artagon-vscode-profiles/tree/main/agents/skills/openspec-apply-change
Command: npx skills add https://github.com/artagon/artagon-vscode-profiles --skill openspec-apply-change-artagon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you turn an OpenSpec change plan into actual code and task progress, without losing track of required context files and completion state.

Core Features & Use Cases

Select and validate the right change: infers or prompts for the target change, then announces exactly which change is being applied.
Drive implementation from OpenSpec instructions: fetches apply instructions, reads the required context files, and follows schema-aware task locations.
Execute tasks safely and incrementally: processes pending tasks in a loop, marks checkboxes as complete, and pauses on ambiguity, blockers, or errors.

Quick Start

Tell your AI to run openspec-apply-change for the specific change you want implemented, or omit the name to let it infer from the conversation.

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 tasks from an OpenSpec change plan incrementally?▼

Implementing OpenSpec tasks requires fetching apply instructions via the CLI, reading required context files, and processing pending tasks in a loop while marking checkboxes complete and pausing on ambiguity or errors.

How does schema-driven task automation handle blocked or partially complete workspace updates?▼

Schema-driven task automation parses JSON output from the CLI to identify task states across schemas, iterating through pending, blocked, or complete tasks while updating progress checkboxes and pausing safely on unresolved blockers.

What's the best way to track progress when applying spec-driven changes to a developer workflow?▼

Tracking spec-driven changes involves running OpenSpec CLI status commands, parsing JSON for schema and context files, and updating task checkboxes incrementally as each implementation step completes.

Do I need the openspec CLI to automate task implementation and progress tracking?▼

Yes, the openspec CLI is required to run status checks and fetch apply instructions, parse JSON outputs for schema details, and read context files needed to guide implementation and update task states.

Can I use this approach to apply changes when some tasks are already complete or blocked?▼

Yes, the implementation loop processes tasks across different states including partial, blocked, and fully complete, iterating through pending items while skipping completed ones and pausing on blocked tasks.

What happens when task automation encounters ambiguity or errors during implementation?▼

Task automation pauses execution immediately upon encountering ambiguity, blockers, or errors, preventing incorrect workspace updates and requiring manual resolution before resuming the implementation loop.