openspec-apply-change

Automate OpenSpec change application by coordinating selection, status checks, and task execution.

42|Updated Oct 14, 2021
One-click install
npx skills add https://github.com/j5ik2o/oni-comb-rs --skill openspec-apply-change-j5ik2o
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/j5ik2o/oni-comb-rs/tree/main/.cursor/skills/openspec-apply-change
Command: npx skills add https://github.com/j5ik2o/oni-comb-rs --skill openspec-apply-change-j5ik2o

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the end-to-end application of OpenSpec changes by coordinating change selection, status assessment, and task execution to keep projects moving smoothly.

Core Features & Use Cases

  • Orchestrates change selection, status checks, and task implementation across the OpenSpec workflow
  • Reads contextual CLI output, reads context files, updates task status, and provides progress visibility
  • Supports iterative work cycles until all tasks are complete or a blocker is encountered, with guidance for continuation

Quick Start

Initiate an OpenSpec change implementation by providing a change name or letting the system infer it, then follow the guided steps to select, apply, and track task progress.

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 management from start to finish?

Automating OpenSpec change management involves coordinating change selection, status assessment, and task execution. This Skill drives CLI workflows by reading context files, implementing tasks, and updating checkboxes until all changes are complete or blocked.

What is the best way to track incomplete or blocked OpenSpec changes?

Tracking incomplete or blocked OpenSpec changes requires assessing current schema status and progress. This Skill reports on task states, updates task checkboxes iteratively, and provides guidance to continue work when blockages are encountered.

How does CLI workflow automation handle OpenSpec task execution loops?

CLI workflow automation handles OpenSpec task execution by enforcing a continuous loop of reading context files, implementing changes, and updating task status. This cycle repeats until the system reaches full completion or identifies a blocker.

Can I infer an OpenSpec change name automatically without specifying it upfront?

Inferring an OpenSpec change name automatically is supported during implementation. You can provide a specific change name or let the system infer it, followed by guided steps to select, apply, and track task progress.

Do I need context files to apply OpenSpec changes through CLI automation?

Context files are required to apply OpenSpec changes through CLI automation. The Skill reads CLI-provided context files to assess the current schema, report on progress, and execute task implementation within the workflow loop.

Why does my OpenSpec change implementation stop before all tasks are complete?

OpenSpec change implementation stops when a blocker is encountered during task execution. The iterative work cycle halts, reports the blocked status, and provides guidance for continuation so you can resolve the issue.