openspec-apply-change

Implement OpenSpec change tasks sequentially and track progress.

1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/dungsnowaxe/prometheus-red-team-bot --skill openspec-apply-change-dungsnowaxe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/dungsnowaxe/prometheus-red-team-bot/tree/main/.windsurf/skills/openspec-apply-change
Command: npx skills add https://github.com/dungsnowaxe/prometheus-red-team-bot --skill openspec-apply-change-dungsnowaxe

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec-cli, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the implementation of tasks defined within an OpenSpec change, streamlining the development and modification process.

Core Features & Use Cases

  • Task Implementation: Executes defined tasks from an OpenSpec change, updating progress and marking tasks as complete.
  • Contextual Awareness: Infers or prompts for the correct change name based on conversation context or available changes.
  • Progress Tracking: Reports current progress, remaining tasks, and handles different states like 'blocked' or 'all_done'.
  • Use Case: When a new feature specification is created in OpenSpec, this Skill can be used to systematically implement all the associated development tasks, ensuring adherence to the spec.

Quick Start

Use the openspec-apply-change skill to implement the tasks for the change named 'feature-x'.

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 for an OpenSpec change?

Automating OpenSpec task implementation involves executing defined development tasks sequentially, updating artifacts, and tracking progress automatically. This Skill handles various schema types and reports remaining tasks or blocked states during the workflow.

Do I need the openspec CLI to implement OpenSpec change tasks?

Yes, the openspec CLI is required for execution and status retrieval. It provides the necessary infrastructure to retrieve change specifications, track task progress, and update completion states within the development workflow.

What is the best way to track progress when implementing OpenSpec specifications?

Tracking progress for OpenSpec specifications is handled automatically by reporting current progress, remaining tasks, and handling different states like 'blocked' or 'all_done'. This ensures systematic adherence to the defined feature specification.

How does contextual awareness work when applying an OpenSpec change?

Contextual awareness for OpenSpec changes works by inferring or prompting for the correct change name based on conversation context or available changes. This streamlines the implementation process without requiring manual specification lookups.

Can I implement OpenSpec development tasks sequentially based on the workflow?

Yes, OpenSpec development tasks can be implemented sequentially or as defined by the OpenSpec workflow. The automation ensures tasks are completed in the correct order, updating artifacts and marking tasks as complete throughout the process.