openspec-apply-change

Automate applying and tracking OpenSpec changes across tasks.

4.1k|508|Updated Jul 11, 2023
One-click install
npx skills add https://github.com/MetaCubeX/metacubexd --skill openspec-apply-change-metacubex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-apply-change
Source: https://github.com/MetaCubeX/metacubexd/tree/main/.claude/skills/openspec-apply-change
Command: npx skills add https://github.com/MetaCubeX/metacubexd --skill openspec-apply-change-metacubex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the application and tracking of OpenSpec changes across tasks, reducing manual coordination and ensuring consistent progress across a change workflow.

Core Features & Use Cases

  • Guided workflow for selecting and applying an OpenSpec change across multiple tasks.
  • Status-aware progression: checks change status, reads context files, and updates task completion until all tasks are done.
  • Clear guidance for blocked changes and completion, with prompts when requirements are ambiguous or artifacts are missing.

Quick Start

Provide an OpenSpec change name (or allow the system to infer it from context). The skill will announce the selected change and guide you through status checks, context reading, and iterative task implementation until all tasks are completed.

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 across multiple tasks?

Automating OpenSpec change implementation involves selecting a change, checking its status, reading context files, and iteratively implementing tasks until completion. The workflow handles blocked states and prompts for clarification when requirements are ambiguous.

What is a guided workflow for tracking OpenSpec change status?

A guided OpenSpec workflow enforces structured progression by reading CLI output context files, updating task progress, and tracking status changes until all tasks reach completion or encounter blocked states.

How do I handle blocked or ambiguous tasks during OpenSpec change application?

Handling blocked or ambiguous OpenSpec tasks requires the workflow to pause progression, prompt for clarification when requirements are unclear, and provide clear guidance for resolving blocked changes before continuing implementation.

Do I need to manually specify the OpenSpec change name to start the workflow?

You do not need to manually specify the OpenSpec change name, as the system can infer it from context, though providing one directly will announce the selected change and immediately start status checks and context reading.

What's the best way to ensure consistent progress when applying OpenSpec changes?

Ensuring consistent progress when applying OpenSpec changes requires an automated, status-aware workflow that updates task completion sequentially, reducing manual coordination across the entire change implementation process.