openspec-apply-change

Implement OpenSpec change tasks with schema-aware progress tracking.

6|Updated Nov 21, 2025
One-click install
npx skills add https://github.com/remiverdiesen/ark-fork --skill openspec-apply-change-remiverdiesen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/remiverdiesen/ark-fork/tree/main/.claude/skills/openspec-apply-change
Command: npx skills add https://github.com/remiverdiesen/ark-fork --skill openspec-apply-change-remiverdiesen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you implement an OpenSpec change from start to finish without manually reconstructing the workflow, so you can move from planning to code with fewer mistakes and less context switching.

Core Features & Use Cases

  • Change selection: Finds or confirms the correct active change when multiple options exist.
  • Schema-aware execution: Reads OpenSpec status and instructions to follow the right task structure.
  • Context-driven implementation: Loads the exact proposal, specs, design, and task artifacts needed for the current change.
  • Progress tracking and guardrails: Updates task completion status, pauses on ambiguity, and reports blockers clearly.
  • Use case: A developer wants to continue a partially implemented feature request and needs the next tasks, required context, and implementation order handled consistently.

Quick Start

Use the openspec-apply-change skill to continue the current OpenSpec change and complete its remaining tasks.

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 managing task context?

Spec-driven change implementation can be automated by selecting the active change, loading required proposal and design artifacts, and executing workflow steps sequentially using the openspec CLI to track task progress.

What is the best way to resume a partially implemented feature request?

Resuming a partially implemented feature request requires reading the current OpenSpec status, identifying remaining tasks, loading exact context files, and updating task completion accurately as each step finishes.

How does schema-aware execution handle ambiguity in task implementation?

Schema-aware execution detects ambiguity during task implementation, pauses the workflow, and reports blockers clearly rather than proceeding with incomplete context or incorrect task instructions.

Do I need the openspec CLI to track spec-driven workflow progress?

The openspec CLI is required to inspect schema state, gather artifacts, and update task completion accurately during spec-driven implementation sessions.

Can I select a specific active change when multiple options exist?

Active change selection handles multiple options by finding or confirming the correct change based on current schema state before loading its specific proposal, specs, design, and task artifacts.

What context files are loaded during OpenSpec change implementation?

Context-driven implementation loads the exact proposal, specs, design, and task artifacts needed for the current change to ensure accurate task-by-task progress tracking and workflow execution.