What problem does it solve? Writing a full change proposal by hand means creating proposal, spec, design, and task documents separately and keeping them consistent. This Skill automates that by driving the OpenSpec CLI to scaffold a change and generate every required artifact in one guided pass. ## Core Features & Use Cases - One-step change creation: Runs openspec new change and then generates all artifacts the apply phase transitively depends on, including proposal.md, specs, design.md, and tasks.md. - Dependency-aware artifact ordering: Parses openspec status --json to resolve artifact dependency edges and creates artifacts in the correct order, re-reading dependencies from disk for context. - Store and schema awareness: Supports registered OpenSpec stores via --store <id> and respects schema rules such as skip_specs and conditional artifacts like design.md. - Use Case: Describe "add user authentication" and receive a complete add-user-auth change with proposal, capability spec deltas, design notes, and an implementation task list ready for /opsx-apply. ## Quick Start Ask the assistant to propose a new change by describing what you want to build, for example: propose a change to add user authentication to the app.
