openspec-apply-change

Implement OpenSpec change tasks sequentially and update their status.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the implementation of tasks defined within an OpenSpec change, streamlining the development workflow by executing predefined steps.

Core Features & Use Cases

  • Task Execution: Sequentially implements tasks from a change's tasks.md artifact.
  • Contextual Awareness: Reads necessary context files (e.g., proposal, specs, design) to inform implementation.
  • Progress Tracking: Updates task completion status and reports progress.
  • Use Case: When a new feature is defined in an OpenSpec change, this Skill can be used to start working on the coding tasks outlined in the tasks.md file, ensuring adherence to the defined workflow.

Quick Start

Use the openspec-apply-change skill to start implementing the tasks for the 'add-user-auth' change.

Frequently Asked Questions about openspec-apply-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate task implementation from an OpenSpec change artifact?

You can automate task implementation by applying the openspec-apply-change process, which sequentially executes coding tasks defined in a change's tasks.md file and updates their completion status. It reads context files like proposals and specs to inform the workflow.

What is spec-driven development task execution and how does it track progress?

Spec-driven development task execution processes predefined workflow steps from a tasks.md artifact sequentially. It tracks progress by automatically updating the completion status of each task within the OpenSpec change artifact as coding progresses.

Do I need the OpenSpec CLI to implement change tasks in my project?

Yes, you need the OpenSpec CLI and an active project with an existing tasks artifact. The CLI is required to read the necessary context files, process dynamic instructions, and execute the change management workflow.

How do I start coding tasks for a newly defined feature in OpenSpec?

To start coding tasks for a new feature, invoke the apply change process on your target change. It will read the proposal, specs, and design context files, then sequentially implement the coding steps outlined in the tasks.md artifact.

When should I use automated task implementation for change management?

Use automated task implementation when you have a defined OpenSpec change with a tasks.md file ready for execution. It is designed for spec-driven development workflows that require sequential task execution, contextual awareness, and automated progress tracking.