openspec-apply-change

Apply OpenSpec changes by selecting, checking, and implementing tasks iteratively.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/cookeyholder/django-devcontainer-template --skill openspec-apply-change-cookeyholder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/cookeyholder/django-devcontainer-template/tree/main/.agent/skills/openspec-apply-change
Command: npx skills add https://github.com/cookeyholder/django-devcontainer-template --skill openspec-apply-change-cookeyholder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, automated approach to applying changes defined in OpenSpec, guiding users through change selection, status verification, context reading, and iterative task implementation until completion.

Core Features & Use Cases

  • Orchestrates end-to-end OpenSpec change application by coordinating change selection, status checks, and task execution.
  • Reads relevant context files (proposal/specs/design/tasks) and updates task artifacts as work progresses.
  • Supports starting a new change, continuing an in-progress change, or resolving blocked changes with guided prompts.

Quick Start

Use this skill to apply an OpenSpec change by selecting a change, reading its instructions, and implementing all tasks to completion.

Frequently Asked Questions about openspec-apply-change

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

FAQPage Schema
How do I apply OpenSpec changes to my software project automatically?

To apply OpenSpec changes, you can use an automated workflow that selects a change, checks its status, reads required context files, and iteratively implements tasks until all are completed. This requires the openspec CLI and access to change data.

What is the process for executing an OpenSpec change end-to-end?

Executing an OpenSpec change end-to-end involves selecting the change, retrieving apply instructions, reading relevant context files like proposal and specs, and iteratively implementing tasks while updating task artifacts until all tasks are completed.

Can I resume an in-progress OpenSpec change if I am interrupted?

Yes, you can resume an in-progress OpenSpec change. The workflow supports starting a new change, continuing a paused change, or resolving blocked changes by checking task progress and guiding you through the remaining implementation steps.

How does change management handle blocked OpenSpec tasks?

Change management for blocked OpenSpec tasks uses guided prompts to help resolve the issue. The workflow checks the current status, reads the required context files, and provides a structured approach to continue or resolve the blocked change.

Do I need the openspec CLI installed to automate task implementation?

Yes, the openspec CLI is required to automate task implementation. You need it installed and available in your environment to select changes, retrieve apply instructions, and update task artifacts as work progresses.

What context files are read when applying an OpenSpec change?

When applying an OpenSpec change, the workflow reads relevant context files including the proposal, specs, design, and tasks. It uses these files to understand the required work and updates the task artifacts as implementation progresses.