openspec-apply-change

Automate end-to-end task execution from an OpenSpec change.

1|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/ssd-mkdocs-platform/teams-board --skill openspec-apply-change-ssd-mkdocs-platform
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/ssd-mkdocs-platform/teams-board/tree/main/.claude/skills/openspec-apply-change
Command: npx skills add https://github.com/ssd-mkdocs-platform/teams-board --skill openspec-apply-change-ssd-mkdocs-platform

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end execution of tasks from an OpenSpec change by guiding users through selection, status checks, context reading, and task implementation in a schema-driven workflow.

Core Features & Use Cases

  • Select and apply changes from OpenSpec by name or context, with status-aware guidance.
  • Read contextual artifacts and progress, handling blocked or completed states, and provide dynamic instructions.
  • Implement tasks iteratively, updating task completion status and continuing until all tasks are done or blocked.

Quick Start

Provide a change name to start applying changes and let the system guide you through status checks and task implementation.

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 task execution for an OpenSpec change from start to finish?

OpenSpec change execution automates end-to-end task implementation by guiding you through change selection, status checks, context reading, and iterative task updates until all tasks are done or blocked.

What is schema-driven workflow orchestration for change management?

Schema-driven workflow orchestration applies state-machine logic to manage change execution, dynamically providing instructions based on the current state, handling blocked conditions, and tracking progress across different schemas.

How do I handle blocked or completed states when applying changes from OpenSpec?

Applying changes from OpenSpec handles blocked and completed states by reading contextual artifacts, evaluating current progress, and providing status-aware guidance to navigate or resolve execution halts.

Can I use CLI-driven orchestration to track task automation progress incrementally?

CLI-driven orchestration supports incremental task updates by inspecting status, reading context, and updating task completion states iteratively without losing track of the overall change execution progress.

Do I need a specific change name to start task-driven OpenSpec change execution?

Task-driven OpenSpec change execution requires a change name or context to initiate, using that input to select the appropriate change and begin guiding you through the schema-driven workflow.

When should I not use automated state-machine task automation for change management?

Automated state-machine task automation is not suitable when changes lack defined schemas or when tasks require manual, non-iterative interventions that cannot be processed through incremental status updates and context reading.