openspec-apply-change

Apply OpenSpec change tasks by parsing CLI JSON and modifying context files.

9|2|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/typemd/typemd --skill openspec-apply-change-typemd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/typemd/typemd/tree/main/.claude/skills/openspec-apply-change
Command: npx skills add https://github.com/typemd/typemd --skill openspec-apply-change-typemd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often struggle to efficiently implement tasks from an OpenSpec change, especially when multiple artifacts and ambiguous states are involved.

Core Features & Use Cases

  • Change selection: Auto-detects or prompts for the target change, handling ambiguous contexts.
  • Status parsing: Interprets OpenSpec CLI JSON to understand schema and task sources.
  • Guided implementation: Reads required context files, shows progress, and iteratively completes tasks with safeguards.
  • Dynamic handling: Pauses for clarification, blockers, or design issues, and suggests next actions.

Quick Start

Ask the skill to apply the change "example-change" and it will walk you through each task until completion.

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 pending change tasks from an OpenSpec change in a CLI environment?

To implement OpenSpec change tasks, you apply the change by selecting the target, parsing CLI JSON output for task status, and iteratively executing required modifications using context files. The process pauses for blockers and suggests next actions.

What is the best way to handle ambiguous OpenSpec changes when automating task implementation?

Handling ambiguous OpenSpec changes involves auto-detecting or prompting for the target change context. The implementation process parses CLI JSON to understand schema sources, then reads required context files to guide task execution.

Do I need the openspec CLI with JSON output support to automate change task execution?

Yes, automating OpenSpec change task execution requires the openspec CLI with JSON output support and the ability to read and modify context files listed by the CLI. This enables status parsing and guided implementation.

How does guided implementation handle design issues during OpenSpec change execution?

Guided implementation dynamically pauses for design issues or blockers during OpenSpec change execution. It reads required context files, shows progress, and suggests next actions to iteratively complete tasks with safeguards.

Why does OpenSpec change implementation pause for clarification during task execution?

OpenSpec change implementation pauses for clarification to handle ambiguous states and ensure accurate task execution. This dynamic handling prevents errors when multiple artifacts or design issues are involved.