What problem does it solve? Starting a new spec-driven change requires manually scaffolding directories, writing proposal, design, and task documents, and keeping them consistent with project standards. This Skill automates the entire OpenSpec change proposal flow in a single step. ## Core Features & Use Cases - One-Step Change Creation: Runs openspec new change and generates all required artifacts (proposal.md, design.md, tasks.md) in dependency order until the change is apply-ready. - Automated Requirement Enrichment: Spawns an Opus subagent that applies the enrich-us workflow to expand a rough user description into a full functional analysis before writing artifacts. - Optional Jira Integration: Detects KAN-style ticket keys, links them to the change via a .jira file, and transitions the ticket to "En curso" using the Jira REST API or an MCP comment fallback. - Use Case: A developer types /opsx:propose add-supplier-orders and receives a fully scaffolded OpenSpec change with standards-compliant proposal, design, and tasks files, ready for implementation via /opsx:apply. ## Quick Start Ask the assistant to run /opsx:propose followed by a kebab-case change name or a description of what you want to build.