openspec-apply-change

Name: openspec-apply-change
Availability: InStock
Author: Gareth

Automate OpenSpec change application by coordinating status checks and task progression.

1|Updated Apr 4, 2026

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

Ready to run

npx skills add https://github.com/garethbaumgart/mental-metal --skill openspec-apply-change-garethbaumgart

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/garethbaumgart/mental-metal/tree/main/.cursor/skills/openspec-apply-change
Command: npx skills add https://github.com/garethbaumgart/mental-metal --skill openspec-apply-change-garethbaumgart

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implementing OpenSpec changes manually can be error-prone and slow; this skill coordinates applying a change by reading status, selecting tasks, and driving iterative implementation until completion.

Core Features & Use Cases

Workflow coordination: manage change status, schema, and context files across the apply cycle.
Guided execution: step-by-step task progression with real-time progress reporting and guards for blocked states.
Reverse-safe iteration: allows pausing, resuming, and updating artifacts as design issues surface during implementation.

Quick Start

Ask OpenSpec to apply a selected change and proceed through tasks until completion.

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 and task progression?▼

Automating OpenSpec change application involves coordinating status checks and driving iterative task execution until completion. The process reads status, instructions, and context files to guide implementation, handling blocked or completed states automatically.

What is the best way to manage change status and context files in a code-change workflow?▼

Managing change status and context files requires workflow coordination across the apply cycle. Reading status files and schema allows the system to select tasks, apply changes iteratively, and update artifacts as design issues surface during implementation.

Do I need the openspec CLI to start applying changes to my codebase?▼

Yes, the openspec CLI is required to apply changes. It reads the necessary status, instructions, and context files to drive task execution, report real-time progress, and enforce guards for blocked states during the code-change workflow.

Can I pause and resume an iterative code-change workflow if a design issue surfaces?▼

Yes, reverse-safe iteration allows you to pause, resume, and update artifacts when design issues surface during implementation. The workflow coordinates status checks to safely handle blocked states and continue task progression later.

Why does my OpenSpec task workflow get blocked during implementation?▼

Task workflows get blocked when status checks identify incomplete dependencies or design conflicts in the context files. The workflow uses guards to halt execution, requiring you to resolve the blocked state before resuming iterative code-change application.