openspec-apply-change

Automate OpenSpec change implementation through CLI-driven task workflows.

9|4|Updated Jun 13, 2023
One-click install
npx skills add https://github.com/lbrlabs/pulumi-lbrlabs-eks --skill openspec-apply-change-lbrlabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/lbrlabs/pulumi-lbrlabs-eks/tree/main/.codex/skills/openspec-apply-change
Command: npx skills add https://github.com/lbrlabs/pulumi-lbrlabs-eks --skill openspec-apply-change-lbrlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implement tasks from an OpenSpec change to streamline starting, continuing, or completing work, guiding users through a repeatable, auditable workflow.

Core Features & Use Cases

  • Select the change: identify the target OpenSpec change to apply.
  • Check status: query current progress and artifacts to understand the schema and remaining tasks.
  • Get apply instructions: fetch task lists and context files to drive implementation.
  • Read context files: load relevant specs, proposals, and design artifacts for guided work.
  • Show progress & handle states: display status, handle blocked or all-done scenarios, and prompt for next steps.
  • Implement tasks: perform minimal, focused code changes and update task checkboxes as tasks complete.

Quick Start

Provide the name of the OpenSpec change you want to apply, then follow the prompts to select, inspect, and implement tasks until all 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 OpenSpec change implementation in my development workflow?

Automate OpenSpec change implementation by using an interactive CLI workflow that guides you through selecting the target change, checking status, retrieving instructions, and performing focused code changes. It reads context files, updates task lists, and reports progress until all tasks are complete.

How does OpenSpec change management handle blocked progress or ambiguous inputs?

OpenSpec change management handles blocked progress and ambiguous inputs by querying current progress, displaying status artifacts, and prompting for next steps. It relies on the openspec CLI to read context files and navigate multi-change environments until the block is resolved.

What is the best way to track OpenSpec task completion and update task lists?

Track OpenSpec task completion by applying minimal, focused code changes and updating task checkboxes as tasks finish. The workflow reads relevant specs and design artifacts, then reports the overall progress to ensure all remaining tasks are accurately audited.

Do I need the openspec CLI to apply changes and read context files?

Yes, you need the openspec CLI to apply changes, as the workflow relies on it to fetch task lists, read context files like specs and proposals, and drive the implementation. The CLI orchestrates the status checks and progress updates required for completion.

Can I use OpenSpec to manage multiple changes in a single development environment?

Yes, you can manage multiple changes in a single environment. The workflow identifies the target OpenSpec change to apply, handles ambiguous inputs, and guides you through selecting the specific change before checking status and retrieving apply instructions.