openspec-apply-change

Implement tasks from an OpenSpec change using CLI-driven context and progress tracking.

Updated Jan 5, 2025
One-click install
npx skills add https://github.com/ValorVie/settingZsh --skill openspec-apply-change-valorvie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/ValorVie/settingZsh/tree/main/.gemini/skills/openspec-apply-change
Command: npx skills add https://github.com/ValorVie/settingZsh --skill openspec-apply-change-valorvie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It removes the guesswork of turning an OpenSpec change proposal into working code by reading the change's tasks, context files, and progress state directly from the openspec CLI and driving implementation task by task. ## Core Features & Use Cases - Change Selection: Infers the target change from conversation context or lists available changes via openspec list --json when ambiguous. - Schema-Aware Context Loading: Reads the context files (proposal, specs, design, tasks) returned by openspec instructions apply so implementation follows the active workflow schema. - Task Loop with Progress Tracking: Implements each pending task, marks checkboxes complete in the tasks file, and reports N/M progress after every step. - Use Case: After drafting a spec-driven change for a new API endpoint, run this Skill to work through all seven tasks, updating code and checking off each task until the change is ready to archive. ## Quick Start Ask the assistant to start implementing the tasks for your current OpenSpec change, optionally naming the change explicitly.

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 tasks from an OpenSpec change?▼

Invoke the apply workflow with a change name or let it be inferred from context. The skill runs openspec status and openspec instructions apply to load context files, then works through each pending task, marking checkboxes complete as it goes.

How does the skill know which change to work on?▼

It uses a provided name first, then infers from conversation context, then auto-selects if only one active change exists. If still ambiguous, it runs openspec list --json and asks you to pick from the available changes.

What happens if an OpenSpec change is blocked or missing artifacts?▼

When the apply instructions return a blocked state due to missing artifacts, the skill shows the message and suggests continuing artifact creation instead of implementing. It never guesses past missing context files.

Does openspec-apply-change require the openspec CLI?▼

Yes, the openspec CLI is a hard requirement. All status checks, apply instructions, and change listings are executed through openspec commands with JSON output, so the CLI must be installed and available in the environment.

What happens when all tasks in a change are complete?▼

The skill reports full progress with a summary of tasks completed in the session and suggests archiving the change. If paused mid-way due to an error or unclear requirement, it explains the issue and waits for guidance.