openspec-apply-change

Apply and track OpenSpec changes through CLI-driven task workflows.

Updated Apr 6, 2026

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

Ready to run

npx skills add https://github.com/ybenitezf/pi-github --skill openspec-apply-change-ybenitezf

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/ybenitezf/pi-github/tree/main/.opencode/skills/openspec-apply-change
Command: npx skills add https://github.com/ybenitezf/pi-github --skill openspec-apply-change-ybenitezf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams automate the implementation and progression of OpenSpec changes by guiding the user through inference, status checks, and task execution, while keeping changes organized and auditable.

Core Features & Use Cases

Guided change selection: detect and select the target OpenSpec change to apply, with options to infer or specify a name.
Status-driven workflow: read current change state, determine schema, and present next actionable steps.
Task implementation loop: iteratively apply tasks, mark progress, handle blockers, and provide real-time feedback.
Artifact-aware updates: read and use relevant context files to drive implementation decisions and artifacts.

Quick Start

Provide the change name to apply, or ask to infer it from context, and start applying tasks step by step.

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 end-to-end?▼

Automate OpenSpec changes by using a status-driven workflow that detects the target change, reads context files, iteratively applies tasks, and updates task statuses through state transitions like blocked and all_done.

How do I manage blocked tasks in an OpenSpec change workflow?▼

Manage blocked OpenSpec tasks by reading the current change state, determining the schema, handling blockers iteratively, and updating task statuses to reflect state transitions while prompting the user when context is ambiguous.

Can I infer the target OpenSpec change name from context automatically?▼

Yes, you can infer the target OpenSpec change name automatically from context, or specify it manually, to begin guiding the implementation and progression of changes step by step.

What is the best way to track task status when implementing OpenSpec changes?▼

Track OpenSpec task status through a task implementation loop that reads current state, applies tasks iteratively, marks progress, handles blockers, and ensures state transitions like all_done are updated.

Do I need the OpenSpec CLI to apply and track changes?▼

Yes, applying and tracking OpenSpec changes requires interaction with the OpenSpec CLI to read context files, determine schema, update task statuses, and handle state transitions end-to-end.

Why does my OpenSpec change workflow prompt me for context during task execution?▼

OpenSpec change workflows prompt for context when information is unclear or ambiguous, ensuring artifact-aware updates and correct implementation decisions before proceeding with task state transitions.