openspec-apply-change

Automate OpenSpec change application with CLI-driven task progression and artifact updates.

Updated Jun 4, 2025

Search Tags:#workflow #implementation #cli #openspec #change-management #task-automation

Ready to run

npx skills add https://github.com/alexei-lexx/budget --skill openspec-apply-change-alexei-lexx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/alexei-lexx/budget/tree/main/.gemini/skills/openspec-apply-change
Command: npx skills add https://github.com/alexei-lexx/budget --skill openspec-apply-change-alexei-lexx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenSpec change implementation is often fragmented across proposals, specs, designs, and tasks. This Skill provides a structured, repeatable workflow to apply, track, and complete changes, reducing drift and manual overhead.

Core Features & Use Cases

Guided change selection, status checks, and context loading via the OpenSpec CLI.
Context-aware task progression with automatic updates to tasks and artifacts.
End-to-end workflow from proposal to implementation with guardrails for blocked or completed changes.

Quick Start

Provide a change name to start implementing, or let me infer the active change and I will drive the apply-change workflow to implement 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 automate OpenSpec change implementation from proposal to completion?▼

OpenSpec change implementation is automated by guiding change selection, loading schema-aware context, executing tasks, and incrementally updating artifacts to ensure end-to-end completion. This structured workflow reduces manual overhead and drift across proposals, specs, and designs.

How does task progression work when applying OpenSpec changes via CLI?▼

Task progression applies OpenSpec changes by performing status checks, loading schema-aware context, and automatically updating tasks and artifacts. It safely drives incremental execution while enforcing guardrails for blocked or completed changes.

What is the best way to track OpenSpec specs and design tasks without manual overhead?▼

Tracking OpenSpec specs and design tasks without manual overhead requires a structured workflow that performs status checks and automatic context-aware progress reporting. This ensures incremental task updates while maintaining alignment across proposals and implementations.

Do I need the OpenSpec CLI to manage change workflows for my software team?▼

Yes, you need the OpenSpec CLI to manage change workflows, as the automation relies on it to guide change selection, load schema-aware context, and execute tasks. The CLI enables progressive completion and safe artifact updates for software teams.

What happens if an OpenSpec change is blocked or already completed during task automation?▼

When an OpenSpec change is blocked or already completed, the task automation enforces guardrails to halt progression. It performs status checks to detect these states, preventing unsafe incremental updates to tasks and artifacts.

Can I infer the active OpenSpec change automatically instead of providing a name?▼

Yes, you can infer the active OpenSpec change automatically. The workflow can infer the active change and drive the apply-change process to implement tasks without requiring you to explicitly provide a change name.