What problem does it solve? Turning a rough feature idea into a structured, implementation-ready change proposal normally requires manually writing proposals, design documents, and task lists. This Skill automates that entire flow through the OpenSpec CLI, producing all required artifacts in one step. ## Core Features & Use Cases - One-step change creation: Runs openspec new change and generates proposal.md, design.md, and tasks.md in dependency order using openspec status and openspec instructions. - Automated requirement enrichment: Spawns a subagent that applies an enrichment workflow to expand the user's raw description into a functional analysis before writing artifacts. - Optional Jira integration: Detects ticket keys like KAN-18, links them to the change, and transitions the ticket to "En curso" via the Atlassian REST API or MCP fallback. - Use Case: A developer says "add supplier order tracking" and receives a scaffolded change directory with a proposal, design, and a tasks.md following the project's mandatory steps (feature branch, tests, curl verification, PR), ready for /opsx:apply. ## Quick Start Ask the assistant to propose a new OpenSpec change for the feature you want to build, for example by describing the feature and letting it derive a kebab-case change name.