openspec-apply-change

Implement pending OpenSpec change tasks by parsing CLI status and updating checklists.

Updated Apr 11, 2025
One-click install
npx skills add https://github.com/pabloimrik17/monolab --skill openspec-apply-change-pabloimrik17
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/pabloimrik17/monolab/tree/main/.junie/skills/openspec-apply-change
Command: npx skills add https://github.com/pabloimrik17/monolab --skill openspec-apply-change-pabloimrik17

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implementing and tracking work items defined by an OpenSpec change can be tedious, error-prone, and disconnected from the authoritative CLI-driven workflow; this Skill provides a guided, repeatable process to select a change, read authoritative context, and implement tasks until completion or blockage.

Core Features & Use Cases

  • Change selection and discovery: Infer a change from context, auto-select a single active change, or prompt the user with openspec list when ambiguous.
  • Context-aware implementation: Query openspec status and apply instructions, read provided context files, show progress, and implement tasks in a focused loop while updating task checklists.
  • Robust state handling: Detect blocked, all_done, or in-progress states and either pause with clear issues or congratulate and suggest archival; suitable for starting, continuing, or resuming implementation sessions.

Quick Start

Apply the 'feature-x' change and implement its pending tasks by following the openspec CLI instructions and updating task checkboxes as you complete them.

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 pending tasks from an OpenSpec change using the openspec CLI?

To implement OpenSpec change tasks, this Skill parses openspec status and apply instructions JSON, reads referenced context files, and updates task checklists until work is completed or blocked.

What is the best way to track spec-driven change implementations in a developer workflow?

Spec-driven change implementation is tracked by driving the openspec CLI outputs, showing progress, and updating task checkboxes in a focused loop to ensure reliable completion of developer workflow items.

How do I handle blocked or ambiguous states when applying an OpenSpec change?

When applying an OpenSpec change, blocked, ambiguous, or all_done states are detected automatically, pausing implementation with clear issues or suggesting archival upon completion.

How to auto-select a single active OpenSpec change when multiple changes exist?

If a single active OpenSpec change exists, it is auto-selected; if ambiguous, the user is prompted with openspec list output to manually select the correct change for implementation.

Can I resume an in-progress OpenSpec implementation session without losing task context?

Yes, in-progress OpenSpec implementation sessions can be resumed by querying openspec status, reading provided context files, and continuing the task implementation loop from the last saved state.

Do I need to manually parse openspec apply instructions JSON to implement change tasks?

No, apply instructions JSON is parsed automatically by the Skill to drive the implementation workflow, read context files, and update task checklists without manual JSON parsing.