openspec-apply-change

Apply OpenSpec changes through status checks and per-task execution.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/jason23452/n8n --skill openspec-apply-change-jason23452
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/jason23452/n8n/tree/main/.opencode/skills/openspec-apply-change
Command: npx skills add https://github.com/jason23452/n8n --skill openspec-apply-change-jason23452

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenSpec changes often require coordinated tasks across multiple artifacts and tools. This Skill provides a structured, repeatable workflow to apply, monitor, and evolve an OpenSpec change by guiding the user through change selection, status checks, and per-task implementation.

Core Features & Use Cases

  • Guided change application: orchestrates selecting a change, verifying status, and applying instructions.
  • Progress tracking: summarizes total, completed, and remaining tasks, and handles blocked or all-done states.
  • Context-driven execution: reads context files and updates tasks as work progresses to support iterative development.

Quick Start

Provide the change name to begin applying tasks.

Frequently Asked Questions about openspec-apply-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I apply OpenSpec changes across multiple tasks automatically?

To apply OpenSpec changes automatically, this Skill orchestrates change selection, verifies status via the CLI, and executes per-task instructions iteratively. It coordinates context files and dynamic task progression to guide you end-to-end through implementation.

What is the best way to track progress when applying a change management workflow?

Tracking progress in a change management workflow is handled by summarizing total, completed, and remaining tasks. The Skill reads CLI outputs and context files to provide status updates, automatically handling blocked states and all-done conditions during iteration.

How do I handle ambiguous change names or blocked tasks during development workflow automation?

Handling ambiguous change names and blocked tasks during development workflow automation is built into the guided execution. The Skill detects ambiguous identifiers when selecting changes and pauses or reports blocked states, preventing invalid task progression.

Can I use this to iterate through OpenSpec tasks without manually reading context files?

Yes, you can iterate through OpenSpec tasks without manually reading context files. The Skill performs context-driven execution by automatically retrieving instructions, reading necessary context files, and updating task statuses as work progresses.

Do I need any specific dependencies or components installed to start applying OpenSpec changes?

No specific dependencies or components are required to start applying OpenSpec changes. The Skill operates independently by coordinating OpenSpec CLI outputs and context files to manage the development workflow and task tracking.

Why does my OpenSpec change application stop or report a blocked state?

An OpenSpec change application stops or reports a blocked state when the status checks detect unresolved prerequisites or execution halts. The Skill monitors these conditions during per-task execution to prevent invalid progression.