openspec-apply-change

Implement pending OpenSpec change tasks using CLI instructions and context files.

54|3|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/mrclrchtr/SuPi --skill openspec-apply-change-mrclrchtr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/mrclrchtr/SuPi/tree/main/.claude/skills/openspec-apply-change
Command: npx skills add https://github.com/mrclrchtr/SuPi --skill openspec-apply-change-mrclrchtr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implements pending tasks for an OpenSpec change by using CLI-provided instructions and project context, removing the manual steps of locating, understanding, and marking off implementation tasks so development progresses reliably.

Core Features & Use Cases

  • Change selection and validation: Infers or prompts to select the correct change and announces how to override the choice.
  • State-aware implementation: Queries openspec status and apply instructions to determine schema, context files, progress, and dynamic guidance before making changes.
  • Context-driven edits and task tracking: Reads contextFiles, makes focused code changes per task, and updates task checkboxes while pausing for clarification, blockers, or design issues.
  • Use Case: A developer or coding agent picks up a spec-driven change, iterates through remaining tasks across proposal, design, and tasks files, implements code, and marks tasks complete without losing traceability.

Quick Start

Start implementing the next pending tasks for a specified OpenSpec change by invoking the skill, confirming or selecting the target change when prompted, and following prompts to review context and apply each task.

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 spec-driven changes without manually tracking task progress?

Spec-driven changes can be implemented automatically by querying CLI-provided instructions to read context files, make focused code edits, and update task checkboxes end-to-end without manual tracking.

What is the best way to execute pending tasks from an OpenSpec change proposal?

Executing OpenSpec change tasks requires querying the openspec CLI for status and instructions in JSON, implementing code changes based on context files, and marking task checkboxes complete as you progress.

Do I need the openspec CLI to automate spec-driven implementation tasks?

Yes, the openspec CLI is required to provide status, schema, context files, and dynamic apply instructions in JSON before making code changes for a spec-driven implementation.

How does state-aware implementation handle blocked states or ambiguous task selection?

State-aware implementation handles blocked states and ambiguous task selection by pausing to present interactive prompts, allowing users to select target changes, provide clarifications, or resolve design issues.

Can I override the inferred change selection when applying code changes?

Yes, when a change is inferred during implementation, the system announces how to override the choice, allowing you to manually select the correct target change before applying tasks.

What happens when a design issue or blocker occurs during spec-driven code changes?

When a design issue or blocker occurs during spec-driven code changes, the implementation pauses to request user clarification, preventing unreliable progress until the design issue is resolved.