openspec-apply-change

Guide OpenSpec change application through status checks and task execution.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/inspedralbes/prj-entrades-bielDom-nguez-2DAW --skill openspec-apply-change-inspedralbes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/inspedralbes/prj-entrades-bielDom-nguez-2DAW/tree/main/prj-entrades-nou/.cursor/skills/openspec-apply-change
Command: npx skills add https://github.com/inspedralbes/prj-entrades-bielDom-nguez-2DAW --skill openspec-apply-change-inspedralbes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a guided, deterministic workflow to apply OpenSpec changes by coordinating status checks, context gathering, and task execution across multiple artifacts.

Core Features & Use Cases

  • Guided change application: reads the current change state, determines required artifacts, and presents next actions.
  • Context-driven execution: fetches relevant context files and updates task progress, with dynamic instructions based on state (blocked, all_done, or in-progress).
  • Guarded workflow: pauses on ambiguity or blockers and suggests artifact updates to keep changes coherent.
  • Fluid integration: supports interleaving with other change-related actions and artifact updates as needed.

Quick Start

Begin applying a change by providing a name, then follow the prompts to implement tasks until all are completed.

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 OpenSpec change application across multiple tasks?

Automate OpenSpec change application by using a guided workflow that coordinates status checks, gathers context files, and sequences task execution end-to-end with dynamic state feedback and guardrails to ensure coherent artifact updates.

How does guided change management handle blocked or in-progress task states?

Guided change management handles blocked or in-progress states by reading current context, pausing on ambiguity, suggesting artifact updates, and providing deterministic next actions until all tasks are completed.

What is the best way to track task progress during code implementation changes?

Track task progress during code implementation by fetching relevant context files, updating task statuses dynamically, and following workflow orchestration that prompts for artifact updates when blockers or completion states are detected.

Can I interleave other change-related actions while applying OpenSpec changes?

Yes, you can interleave other change-related actions and artifact updates fluidly while applying OpenSpec changes, as the workflow supports pausing, continuing, and resuming based on the current state.

Do I need to manually check status before starting or continuing a change application workflow?

No, manual status checks are not needed because the workflow automatically reads the current change state, determines required artifacts, and presents the next actions based on whether you are starting, continuing, or finishing.

Why does workflow orchestration pause during OpenSpec change implementation?

Workflow orchestration pauses during OpenSpec change implementation when it encounters ambiguity or blockers, acting as a guardrail to prompt for necessary artifact updates and keep changes coherent before proceeding.