opsx

Automates the OpenSpec change lifecycle from proposal to archival.

20|3|Updated Feb 2, 2026

Search Tags:#automation #workflow #planning #specification #lifecycle #openspec #change-management

Ready to run

npx skills add https://github.com/re-cinq/wave --skill opsx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: opsx
Source: https://github.com/re-cinq/wave/tree/main/.claude/skills/opsx
Command: npx skills add https://github.com/re-cinq/wave --skill opsx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenSpec workflow management (OpsX) provides a structured lifecycle to coordinate specification-driven development changes from proposal through implementation to archival, reducing bottlenecks and miscommunication.

Core Features & Use Cases

Onboard: Get started with OpenSpec workflow and initialize project scaffolds.
New: Create new OpenSpec change proposals with defined scope.
Fast-Forward: Generate comprehensive planning documentation from proposals.
Apply: Execute implementation tasks and track progress against plans.
Archive: Complete and archive finished changes with a final summary.

Quick Start

Initialize the OpenSpec workflow in your project and start a new change proposal with your initial description.

Frequently Asked Questions about opsx

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

FAQPage Schema

How do I manage the lifecycle of specification-driven changes from proposal to archive?▼

Specification-driven change lifecycle management automates the progression of proposals through planning, implementation, and archival. It standardizes file structures under .openspec and uses configuration templates to coordinate workflow stages, reducing team miscommunication.

What is the best way to create structured change proposals for specification-driven development?▼

Creating structured change proposals for specification-driven development involves defining the scope of changes using standardized configuration templates. The workflow initializes project scaffolds and generates comprehensive planning documentation to guide subsequent implementation tasks.

How does fast-forward planning work for OpenSpec change proposals?▼

Fast-forward planning for OpenSpec change proposals works by taking an initial proposal description and automatically generating comprehensive planning documentation. This structured plan then serves as the baseline to execute implementation tasks and track progress.

Do I need any external dependencies to automate OpenSpec workflows?▼

No external dependencies are required to automate OpenSpec workflows. The lifecycle management operates independently to scaffold the .openspec file structure, apply configuration templates, and manage change progression from onboarding through archival.

Can I track implementation progress against plans in a specification-driven development workflow?▼

Yes, you can track implementation progress against plans in a specification-driven development workflow. The apply phase executes defined implementation tasks from the generated planning documentation and monitors their completion status until ready for archival.

When should I archive finished changes in a specification-driven lifecycle?▼

You should archive finished changes in a specification-driven lifecycle when all implementation tasks are complete. The archival process finalizes the workflow by generating a summary and storing the change records within the standardized .openspec directory structure.