openspec-apply-change

Implement OpenSpec change tasks and update task statuses.

1|1|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/kevintsengtw/dotnet-testing-agent-orchestration --skill openspec-apply-change-kevintsengtw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/kevintsengtw/dotnet-testing-agent-orchestration/tree/main/.github/skills/openspec-apply-change
Command: npx skills add https://github.com/kevintsengtw/dotnet-testing-agent-orchestration --skill openspec-apply-change-kevintsengtw

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the implementation of tasks defined within an OpenSpec change, ensuring that development work aligns with specified requirements and progresses efficiently.

Core Features & Use Cases

  • Task Implementation: Executes defined tasks from an OpenSpec change, updating progress and handling various states.
  • Contextual Awareness: Infers or prompts for the correct change if not explicitly provided, and reads necessary context files.
  • Use Case: When a new feature is defined in OpenSpec, use this Skill to automatically start implementing the associated tasks, updating the codebase and tracking progress against the specification.

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 change tasks to update code and artifacts. This workflow reads necessary context files and updates task statuses automatically, ensuring development aligns with specified requirements.

What is spec-driven development and how does it manage change tasks?

Spec-driven development manages change tasks by defining feature requirements before implementation. It reads context files to apply changes to the codebase and tracks progress against the specification, ensuring development aligns efficiently.

Do I need the openspec CLI to apply changes to my codebase?

Yes, applying changes to your codebase requires the openspec CLI for change management and instruction retrieval. This dependency ensures the implementation process correctly reads context files and updates task statuses.

How do I execute tasks from a specific OpenSpec change like 'feature-x'?

To execute tasks from a specific OpenSpec change, you apply the change named 'feature-x'. The process infers or prompts for the correct change if not explicitly provided, then reads context files to implement the associated tasks.

Can I update task statuses automatically when implementing OpenSpec changes?

Yes, you can update task statuses automatically when implementing OpenSpec changes. The process executes defined tasks, updates progress, and handles various states while applying changes to code and artifacts.

What happens if I don't specify the change name when applying an OpenSpec task?

If you do not specify the change name when applying an OpenSpec task, the process infers or prompts for the correct change. This contextual awareness ensures the right context files are read before implementing the associated tasks.