What problem does it solve? Writing a full change proposal with design documents, specifications, and implementation tasks is slow and inconsistent. This Skill turns a short description of what you want to build into a complete, structured OpenSpec change in one step. ## Core Features & Use Cases - One-Step Change Creation: Runs the openspec CLI to scaffold a change directory and generate all required artifacts (proposal.md, design.md, tasks.md) in dependency order. - Schema-Driven Artifacts: Reads per-artifact instructions, templates, and rules from the openspec CLI so every output file follows the project's specification schema. - Interactive Clarification: Asks open-ended questions when the request is unclear and derives kebab-case change names automatically. - Use Case: Describe "add user authentication" and receive a ready-to-implement change at openspec/changes/add-user-auth/ with proposal, design, and tasks files, then run /opsx:apply to start implementation. ## Quick Start Ask the assistant to propose a new change by describing what you want to build, for example: propose a change to add OAuth login to the app.
