openspec-apply-change

Implement OpenSpec change tasks by parsing CLI outputs and updating code.

Updated Feb 25, 2026
One-click install
npx skills add https://github.com/futuretea/x-project --skill openspec-apply-change-futuretea
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/futuretea/x-project/tree/main/.claude/skills/openspec-apply-change
Command: npx skills add https://github.com/futuretea/x-project --skill openspec-apply-change-futuretea

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of turning OpenSpec change artifacts into concrete code and documentation updates so implementers don't have to manually track status, locate context files, or manage task checklists across a repository.

Core Features & Use Cases

  • Change selection & discovery: Infer or prompt for the active OpenSpec change and announce the selection and override options.
  • CLI-driven context parsing: Run openspec status and instructions apply, parse JSON outputs, and read the context files the CLI identifies.
  • Task-driven implementation loop: Present progress, implement pending tasks one at a time with minimal scoped changes, update checklist items, and handle blocked or ambiguous tasks by pausing and asking for guidance.
  • Use Case: Start or continue implementing a spec-driven change where tasks, proposals, and design docs must be read and code/tests updated until all tasks are complete or a blocker is encountered.

Quick Start

Ask the assistant to apply the OpenSpec change named my-change and implement pending tasks until completion or until you instruct it to pause for clarification.

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 change tasks automatically from CLI status outputs?

To implement OpenSpec change tasks, this Skill parses CLI status outputs and context files to apply required code updates. It reads the JSON outputs from OpenSpec commands, identifies pending tasks, and makes minimal scoped code changes while updating task checklists.

What is spec-driven implementation workflow for applying changes to a repository?

Spec-driven implementation workflow turns change artifacts into concrete code updates by parsing proposals, design docs, and task checklists. This Skill automates tracking status, locating context files, and managing checklists across the repository until all tasks complete or hit a blocker.

Do I need the openspec CLI installed to apply change tasks to my repository?

Yes, you need openspec CLI access to run status and instructions apply commands. The Skill requires CLI outputs to identify context files and parse dynamic apply instructions for starting, continuing, or resuming implementation of change tasks.

Can I resume implementing an OpenSpec change if I encounter a blocker midway?

Yes, the Skill handles resuming implementation by parsing current task checklist state from CLI outputs. It pauses on ambiguous or blocked tasks to ask for guidance, then continues implementing pending tasks one at a time with minimal changes once unblocked.

How do I update task checklists when implementing spec-driven code changes?

The Skill updates task checklists automatically after implementing each pending task. It tracks progress by parsing CLI status JSON, completes checklist items as code changes are made, and pauses to request guidance when encountering ambiguous requirements.

What happens when an OpenSpec change task has ambiguous implementation instructions?

When implementation instructions are ambiguous, the Skill pauses and asks for guidance rather than guessing. It identifies blockers from context files and CLI outputs, then requests clarification before continuing with minimal scoped code changes.