openspec-apply-change

Guide users through applying OpenSpec changes with CLI-driven status checks and task tracking.

273|270|Updated Jun 30, 2025
One-click install
npx skills add https://github.com/LIDR-academy/AI4Devs-LTI-extended --skill openspec-apply-change-lidr-academy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/LIDR-academy/AI4Devs-LTI-extended/tree/main/.cursor/skills/openspec-apply-change
Command: npx skills add https://github.com/LIDR-academy/AI4Devs-LTI-extended --skill openspec-apply-change-lidr-academy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenSpec change workflows can be tedious and error-prone; this Skill guides users through selecting a change, validating its status, fetching actionable instructions, and performing tasks in a controlled, incremental way.

Core Features & Use Cases

  • Guides users to identify and select an OpenSpec change, checks current status, and retrieves apply instructions.
  • Reads relevant context files and displays progress, with dynamic guidance based on the schema and task state.
  • Iterates through pending tasks, applying changes with minimal, scoped edits, and pauses safely on blockers or ambiguities.

Quick Start

Provide the change name to begin applying tasks, or let the system infer it from context and start the guided OpenSpec workflow.

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 execution from the command line?

You can automate OpenSpec change execution by using a guided CLI workflow that validates status, reads context files, and iterates through pending tasks. It applies scoped edits incrementally and pauses safely on blockers.

What is the best way to track task progress during a change management workflow?

Task-tracking updates are driven by reading contextual artifacts and enforcing CLI-driven status checks. The system displays progress dynamically based on the schema and current task state to ensure safe, incremental changes.

How do I handle blockers or ambiguities when applying changes incrementally?

When applying changes incrementally, the guided workflow pauses safely upon encountering blockers or ambiguities. It ensures controlled execution by waiting for resolution before proceeding with further scoped edits.

Do I need to provide a specific change name to start the OpenSpec workflow?

You do not need to provide a specific change name to start the OpenSpec workflow. You can provide the change name explicitly, or let the system infer it from your current context to begin applying tasks.

Can I use this workflow to validate the current status of an OpenSpec change before implementation?

You can use this workflow to validate the current status of an OpenSpec change before implementation. It checks the existing status and retrieves apply instructions to ensure safe, incremental task execution.

Why does my change workflow require reading context files before executing tasks?

Reading context files before executing tasks provides dynamic guidance based on the schema and task state. This ensures that contextual artifacts drive progress and that scoped edits are applied safely during the change workflow.