What problem does it solve? Starting a new change in an OpenSpec workflow requires manually creating the change scaffold and writing proposal, design, and task documents one by one, which slows down the planning phase of feature development. ## Core Features & Use Cases - One-Step Change Proposal: Creates a new OpenSpec change and generates proposal.md, design.md, and tasks.md artifacts in a single /opsx:propose invocation. - Codebase-Aware Planning: Uses CodeGraph exploration to ground the proposal in the existing codebase before generating artifacts. - Guided Artifact Generation: Follows the OpenSpec build order and per-artifact instructions so each document conforms to the expected structure. - Use Case: A developer wants to add a new authentication feature. They run /opsx:propose add-oauth-login, and the skill explores the codebase, creates the change, and produces the proposal, design, and task breakdown ready for review. ## Quick Start Ask the assistant to propose a new OpenSpec change by describing what you want to build, for example: propose a change to add OAuth login support.