openspec-apply-change

Apply OpenSpec changes by selecting, validating, and executing tasks incrementally.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implementing OpenSpec changes can be error-prone and time-consuming; this skill provides a guided, repeatable workflow to select a change, verify status, read context, and implement tasks with safe, incremental steps.

Core Features & Use Cases

  • Guided change selection and status interpretation based on OpenSpec CLI outputs.
  • Context-aware task execution with progress tracking and dynamic instructions.
  • Safe pausing, issue handling, and minimal, auditable code changes.

Quick Start

Provide the change name or context and begin applying tasks to implement the OpenSpec change.

Frequently Asked Questions about openspec-apply-change

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

FAQPage Schema
How do I implement OpenSpec changes incrementally without losing context?

Implementing OpenSpec changes incrementally requires a guided workflow that reads context files before starting, executes tasks iteratively, and tracks progress by updating task checkboxes to ensure minimal, auditable code modifications.

What is the best way to manage OpenSpec change workflows end-to-end?

Managing OpenSpec change workflows end-to-end involves selecting a specific change, validating its current status via CLI outputs, and executing schema-driven instructions to apply proposals safely with real-time updates.

How does safe halting work when applying code changes to blocked tasks?

Safe halting when applying code changes pauses task execution automatically when blocked by issues, allowing for error handling and safe pausing without breaking the iterative execution flow or losing progress.

Do I need to read context files before starting task automation for change management?

Reading context files before starting task automation is required to enforce guardrails, enabling context-aware task execution that supports dynamic instructions and ensures incremental code changes align with the proposal.

Can I use schema-driven instructions to automate OpenSpec task execution?

Schema-driven instructions automate OpenSpec task execution by providing structured guidance for iterative task completion, interpreting status, and applying minimal code changes while handling completion, pausing, or errors safely.