opsx-apply-change

Implement OpenSpec change tasks with artifact review and progress tracking.

Updated May 25, 2026
One-click install
npx skills add https://github.com/ywh0606/chat-robot --skill opsx-apply-change
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opsx-apply-change
Source: https://github.com/ywh0606/chat-robot/tree/main/.claude/skills/opsx-apply-change
Command: npx skills add https://github.com/ywh0606/chat-robot --skill opsx-apply-change

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers execute OpenSpec change tasks consistently by guiding implementation from change selection through completion tracking.

Core Features & Use Cases

  • Change Workflow Execution: Selects OpenSpec changes, checks status, loads required context files, and follows implementation instructions.
  • Task Progress Management: Tracks pending work, updates completed tasks, and reports implementation status or blockers.
  • Use Case: Use this Skill when a developer needs to implement an OpenSpec change request while maintaining alignment with defined artifacts and task progress.

Quick Start

Ask the skill to implement the specified OpenSpec change and follow the remaining tasks until completion.

Frequently Asked Questions about opsx-apply-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement OpenSpec changes with guided task tracking?

To implement OpenSpec changes, this skill selects the change request, loads required context artifacts, and follows structured implementation instructions while tracking task progress until completion.

What is the best way to manage software engineering workflow automation for specification-driven changes?

Managing specification-driven changes requires coordinating change selection, artifact review, and implementation progress tracking to ensure structured execution and task completion safely.

Do I need the openspec CLI workflow to execute specification-driven change tasks?

Yes, executing specification-driven change tasks requires the openspec CLI workflow, context artifact access, and task state updates to complete the implementation safely.

How does change management workflow handle pending work and implementation blockers?

Change management workflow handles pending work by tracking task progress, updating completed tasks, and reporting implementation status or blockers encountered during the specification-driven execution.

Can I use this approach to maintain alignment with defined artifacts during task implementation?

Yes, you can maintain alignment with defined artifacts by loading required context files during change selection and following the implementation instructions through task completion tracking.

When should I not use structured execution for specification-driven changes?

You should avoid structured execution for specification-driven changes when lacking the openspec CLI workflow, context artifact access, or task state updates required to complete implementation safely.