Automates the OpenSpec change lifecycle from proposal to archival.
npx skills add https://github.com/re-cinq/wave --skill opsx
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
OpenSpec workflow management (OpsX) provides a structured lifecycle to coordinate specification-driven development changes from proposal through implementation to archival, reducing bottlenecks and miscommunication.
Initialize the OpenSpec workflow in your project and start a new change proposal with your initial description.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
zxyycomAutomate creation of OpenSpec change proposals and required artifacts.
wishx127Implement OpenSpec change tasks using the OpenSpec CLI workflow.
CommunityToolkitAutomates npm release validation, publishing procedures, and post-publish verification for software workflows.
hellyaxsArchive completed OpenSpec changes after validating artifacts and tasks.
