openspec-status

Generates a read-only status snapshot of an OpenSpec change with slices, reports, and next-command recommendations.

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/pavelvdo/universal-xml-exchange2 --skill openspec-status-pavelvdo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-status
Source: https://github.com/pavelvdo/universal-xml-exchange2/tree/main/.cursor/skills/openspec-status
Command: npx skills add https://github.com/pavelvdo/universal-xml-exchange2 --skill openspec-status-pavelvdo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When working with OpenSpec changes in a 1C development workflow, it is hard to quickly tell where a change stands: which slices are accepted, which are awaiting acceptance, what reports exist, and which command to run next. This Skill assembles a compact read-only snapshot from the change artifacts without running heavy verification. ## Core Features & Use Cases - Status Snapshot: Reads openspec/changes/<name>/ artifacts (proposal, tasks, debug, reports) and renders a structured summary following the T-STATUS output template. - Slice & Gate Tracking: Parses slice-mode tasks.md, acceptance checkboxes, and Slice Gate Decisions from debug.md, highlighting awaiting-acceptance items that need user action. - Next Command Recommendation: Suggests the appropriate follow-up command (/opsx:apply, /opsx:verify, /opsx:archive, /opsx:new) based on the current change state. - Use Case: After returning to a change mid-work, run /opsx:status my-change to instantly see that slice S2 is awaiting acceptance and that /opsx:apply is the recommended next step. ## Quick Start Ask the assistant to show the status of an OpenSpec change by name, optionally with the --short or --reports flag for a condensed view.

Frequently Asked Questions about openspec-status

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

FAQPage Schema
How do I check the status of an OpenSpec change?▼

Run /opsx:status with the change name to get a snapshot of schema, slice progress, gate decisions, and recent reports. Use the --short flag for a one-line summary or --reports for only the reports table.

How do I know which opsx command to run next on a change?▼

The status output includes a recommendation section. If a slice is awaiting acceptance it suggests /opsx:apply; if all slices are accepted it suggests /opsx:archive; missing verification reports point to /opsx:verify.

Does openspec-status modify change artifacts or run subagents?▼

No. It is strictly read-only: it only reads artifacts under openspec/changes/<name>/ and never edits files, runs subagents, or reads .bsl source files.

What happens if the change name does not exist?▼

The skill reports that the change was not found among active changes and points you to archived changes via openspec list --archived, then stops without further output.

What are the limitations of the status snapshot compared to verify?▼

The snapshot only reflects artifact state such as checkboxes, gate decisions, and report files. It does not validate code correctness or run any verification logic, so use /opsx:verify for substantive checks.