openspec-apply-change

Coordinate and implement tasks from an OpenSpec change.

2|2|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/raiden076/Prism --skill openspec-apply-change-raiden076
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/raiden076/Prism/tree/main/.qwen/skills/openspec-apply-change
Command: npx skills add https://github.com/raiden076/Prism --skill openspec-apply-change-raiden076

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill coordinates and executes tasks from an OpenSpec change, enabling teams to start implementing, continue, or work through tasks in a structured, repeatable way.

Core Features & Use Cases

  • OpenSpec change orchestration: guides users through selecting a change, checking status, retrieving apply instructions, reading context files, and updating task progress.
  • State-aware execution: handles blocked, all_done, and in-progress states with clear prompts and next-step guidance.
  • Iterative task implementation: loops through pending tasks, applies changes with minimal scope, and updates task checkboxes as tasks are completed.

Quick Start

Provide a change name or let the tool infer it to begin applying tasks and observe live progress updates.

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

OpenSpec change orchestration automates task selection, status checks, instruction retrieval, context reading, and progress reporting. It loops through pending tasks iteratively, applying minimal scoped code changes and updating task checkboxes upon completion.

What is state-aware execution in change-based development workflows?

State-aware execution handles blocked, all_done, and in-progress states during OpenSpec change implementation. It provides clear prompts and next-step guidance, ensuring structured, repeatable progression through tasks while managing blockers and ambiguity.

How do I implement OpenSpec changes task by task with minimal scope?

Implementing OpenSpec changes task by task involves looping through pending tasks, applying minimal scoped code changes, and updating task checkboxes. The process retrieves apply instructions and reads context files to perform guarded interactions and structured execution.

Can I continue an in-progress OpenSpec change from where I left off?

Yes, you can continue an in-progress OpenSpec change. The workflow determines the active change, queries its status, and resumes task implementation from pending items, updating progress reports and task checkboxes as each scoped code change completes.

How does OpenSpec change management handle blockers and ambiguity?

OpenSpec change management handles blockers and ambiguity through guarded interactions during task implementation. It detects blocked states, prompts users with clear next-step guidance, and ensures minimal code changes remain scoped to the active change context.

Do I need to provide a change name to start applying OpenSpec tasks?

No, you do not need to provide a change name to start applying OpenSpec tasks. You can provide a change name explicitly or let the tool infer the active change to begin retrieving apply instructions and executing tasks with live progress updates.