openspec-apply-change

Apply and track OpenSpec changes with status updates and task progress.

Updated Feb 4, 2026

Search Tags:#automation #workflow #cli #openspec #task-tracking #change-management

Ready to run

npx skills add https://github.com/SQDR2/PortableConversationScriptAssistant --skill openspec-apply-change-sqdr2

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/SQDR2/PortableConversationScriptAssistant/tree/main/.github/skills/openspec-apply-change
Command: npx skills add https://github.com/SQDR2/PortableConversationScriptAssistant --skill openspec-apply-change-sqdr2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates applying and coordinating OpenSpec changes, enabling teams to start, continue, or complete implementation work within a structured change workflow.

Core Features & Use Cases

Select and apply an OpenSpec change, with guided prompts and status updates
Inspect current schema and task progress to understand the workflow
Read and apply dynamic instructions based on CLI output, updating tasks in place
Handle common states such as blocked or all_done to guide next steps
Integrate into a developer workflow for iterative change implementation across specs, tests, and docs (where applicable)

Quick Start

Provide an OpenSpec change name or let the tool infer one, then follow the prompts to apply and implement tasks until all tasks are completed.

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 implementations across different schemas?▼

You can automate OpenSpec change implementations by selecting a change, reading context, and applying tasks across different schemas. The tool guides you with prompts and updates task progress in place as work proceeds.

What is the best way to track OpenSpec task progress during a workflow?▼

Tracking OpenSpec task progress is handled by inspecting the current schema and updating task status in place. The workflow reads CLI output to apply dynamic instructions and reflects ongoing implementation state.

How do I handle ambiguous changes or blocked states in OpenSpec workflows?▼

Handling ambiguous changes in OpenSpec workflows involves built-in guardrails that prompt for clarification before proceeding. The tool recognizes common states like blocked and guides you on the appropriate next steps.

Can I integrate OpenSpec change management into an iterative developer workflow?▼

Integrating OpenSpec change management into a developer workflow supports iterative implementation across specs, tests, and docs. You provide a change name or let the tool infer one, then follow prompts to complete tasks.

Do I need a specific CLI environment to apply OpenSpec changes?▼

Applying OpenSpec changes relies on reading and applying dynamic instructions based on CLI output. You provide a change name and the tool uses command-line interactions to check status and update tasks.

Why does my OpenSpec change workflow prompt for clarification during implementation?▼

Your OpenSpec change workflow prompts for clarification because it enforces guardrails to handle ambiguous changes safely. This mechanism ensures structured task tracking and prevents incorrect implementations from proceeding.