opsx-verify

Verify OpenSpec changes for completion and readiness before archiving.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users confirm that an OpenSpec change is complete, valid, and ready for archive or implementation by automating verification checks.

Core Features & Use Cases

  • Change Validation: Runs OpenSpec validation commands to detect incomplete or invalid changes.
  • Artifact Status Checks: Reviews change artifacts and task completion status for readiness.
  • Use Case: Use this Skill when reviewing a completed OpenSpec change to ensure all required artifacts and implementation tasks are finished before archiving.

Quick Start

Use the opsx-verify skill to verify whether the OpenSpec change named my-change is complete and ready.

Frequently Asked Questions about opsx-verify

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

FAQPage Schema
How do I verify OpenSpec changes are complete before archiving?

OpenSpec change validation requires running validation commands via the OpenSpec CLI to check artifact status and report task completion. You need the CLI installed to execute these checks and confirm readiness before archiving.

What is OpenSpec change validation in software development?

OpenSpec change validation is the process of automating verification checks to confirm a change is complete, valid, and ready for archive. It involves reviewing change artifacts and tracking task completion status within software development workflows.

When do I need to run artifact status checks for change management?

You need to run artifact status checks when reviewing a completed OpenSpec change to ensure all required artifacts and implementation tasks are finished. This prevents archiving incomplete or invalid changes during change management.

Does OpenSpec verification work without installing any dependencies?

No, OpenSpec verification requires the OpenSpec CLI to validate changes and report artifact and task status. The CLI is a necessary dependency to execute the automated validation checks for change readiness.

What is the best way to track implementation tasks before a release?

The best way to track implementation tasks is by running OpenSpec validation commands to review change artifacts and task completion status. This validates that all required tasks are finished before archiving or implementation.

Why does OpenSpec validation fail before archiving a change?

OpenSpec validation fails when required artifacts are incomplete or implementation tasks are not finished. Running validation checks detects these invalid changes and prevents archiving until all artifact and task status requirements are met.