openspec-apply-change

Apply and track OpenSpec changes using the OpenSpec CLI.

47|2|Updated Oct 30, 2023
One-click install
npx skills add https://github.com/runtime-env/runtime-env --skill openspec-apply-change-runtime-env
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/runtime-env/runtime-env/tree/main/.gemini/skills/openspec-apply-change
Command: npx skills add https://github.com/runtime-env/runtime-env --skill openspec-apply-change-runtime-env

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of applying and tracking progress for OpenSpec changes, guiding users from initiation to completion while handling ambiguous inputs and context inference.

Core Features & Use Cases

  • Guided change application workflow: infer or select a change, announce the active change, and orchestrate status checks with the OpenSpec CLI.
  • Dynamic progress management: read status, fetch instructions, read context files, and perform tasks iteratively with immediate task completion marks.
  • Flexible collaboration: supports pausing, asking for clarification when requirements are unclear, and updating artifacts as needed.

Quick Start

Start a new OpenSpec change application by invoking the skill with a specific change name or rely on conversation context to infer it.

  • Invoke the skill with a specific OpenSpec change name, e.g., "openspec-apply-change" with --change "<name>".
  • If you omit the name, the skill will try to infer it from context, or list available changes and prompt you to choose.
  • The skill will read current status, apply pending tasks, and update task checkboxes as tasks are completed, until all tasks are done or the change is blocked.

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 tracking progress of OpenSpec changes across development workflows?

To automate OpenSpec change tracking, use a skill that reads status via the OpenSpec CLI, fetches context files, and updates task checkboxes iteratively as tasks are completed.

What is the OpenSpec change application workflow for schema-driven development?

The OpenSpec workflow orchestrates status checks with the CLI, infers or selects a change, reads context files, and provides dynamic instructions based on the current state.

Do I need the OpenSpec CLI to apply and manage schema-driven changes?

Yes, the OpenSpec CLI is required. The skill depends on it to read current status, apply pending tasks, and update task checkboxes dynamically across your development workflow.

Can I pause an OpenSpec change implementation or ask for clarification when requirements are unclear?

Yes, the workflow supports pausing and asking for clarification when requirements are ambiguous, allowing you to update artifacts and resume the change application as needed.

How do I start an OpenSpec change if I don't specify a change name?

If you omit the change name, the skill tries to infer it from conversation context, or lists available changes and prompts you to choose one to begin tracking.

What happens when all tasks in an OpenSpec change are completed or blocked?

The skill stops applying changes once all tasks are done or the change is blocked, ensuring the development workflow pauses appropriately at terminal states.