openspec-apply-change

Automate OpenSpec change application with task selection and status checks.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/Rushtu99/Codex-ReVamped --skill openspec-apply-change-rushtu99
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/Rushtu99/Codex-ReVamped/tree/main/.agents/skills/openspec-apply-change
Command: npx skills add https://github.com/Rushtu99/Codex-ReVamped --skill openspec-apply-change-rushtu99

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end application of OpenSpec changes by guiding selection, status checks, and task execution within a codebase.

Core Features & Use Cases

  • Guides change selection and provides a deterministic workflow.
  • Reads OpenSpec CLI outputs to determine status, context files, and tasks.
  • Executes tasks iteratively, updating task checkboxes as work progresses and handling blocked or completed states.

Quick Start

Provide a change name to begin applying tasks, or ask the system to infer the change from context and proceed to implement until all tasks are complete.

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 applying OpenSpec changes to my codebase?

You can automate applying OpenSpec changes by using a guided workflow that reads status, context files, and instructions to iteratively execute tasks and update completion markers as work progresses.

What is the process for managing multiple active OpenSpec changes?

When multiple active OpenSpec changes exist, the change management process prompts you to select a specific change, checks its status, and then guides the task execution within the repository.

Do I need the openspec CLI to guide code implementation tasks?

Yes, you need the openspec CLI installed and access to the repository to read status outputs and context files required to drive code implementation and task tracking.

How does change management handle blocked or completed task states?

Change management handles blocked or completed states by reading OpenSpec CLI outputs during task execution and updating task checkboxes accordingly to ensure accurate status tracking.

Can I apply changes if my repository only has a single active OpenSpec change?

Yes, you can apply changes with a single active OpenSpec change; the workflow automatically infers the change from context and proceeds to implement tasks until all are complete.