openspec-apply-change

Implement planned software changes from OpenSpec task artifacts.

4|9|Updated Jun 16, 2026
One-click install
npx skills add https://github.com/DataDave-Dev/weftmap --skill openspec-apply-change-datadave-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/DataDave-Dev/weftmap/tree/main/.codex/skills/openspec-apply-change
Command: npx skills add https://github.com/DataDave-Dev/weftmap --skill openspec-apply-change-datadave-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns an OpenSpec change plan into completed implementation work by organizing task selection, context review, code changes, progress tracking, and blocker handling.

Core Features & Use Cases

  • Change Selection: Identify a named change, infer the intended change from context, or help resolve ambiguity among active changes.
  • Structured Implementation: Inspect the workflow schema, read all required context artifacts, implement pending tasks incrementally, and update task status as work progresses.
  • Guardrails and Progress Reporting: Pause when requirements are unclear or blocked, keep implementation scoped, and report completion status throughout the workflow.
  • Use Case: Apply an OpenSpec feature change by reviewing its proposal, design, specifications, and tasks, then implementing each task while keeping the change checklist synchronized.

Quick Start

Use the OpenSpec apply change skill to implement the pending tasks for the specified change and report progress until completion or a blocker is encountered.

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 software changes from an OpenSpec task plan?

To implement software changes from an OpenSpec task plan, use this Skill to inspect the workflow schema, read context artifacts, and update task status incrementally as code changes are completed.

What is the best way to track progress when applying OpenSpec code changes?

To track progress when applying OpenSpec code changes, the Skill coordinates guarded task completion and synchronizes the change checklist as each pending task is implemented.

How does OpenSpec handle blocked tasks during change implementation?

OpenSpec handles blocked tasks during change implementation by pausing the workflow and reporting the blocker when requirements are unclear or progress cannot continue.

Do I need the OpenSpec CLI to apply planned feature changes?

Yes, you need the OpenSpec CLI to apply planned feature changes, as it is required to inspect change status, retrieve workflow instructions, and read context artifacts.

Can I use OpenSpec to continue partially completed software development changes?

Yes, you can use OpenSpec to continue partially completed software development changes by identifying the active change, resolving ambiguity, and implementing remaining pending tasks.

Why does my OpenSpec change implementation pause before completion?

Your OpenSpec change implementation pauses before completion to maintain guardrails, keeping the work scoped and pausing when requirements are unclear or a blocker is encountered.