source-command-opsx-proposelisted

# source-command-opsx-propose Use this skill when the user asks to run the migrated source command `opsx-propose`. ## Command Template Propose a new change - create the change and generate all artifacts in one step. I'll create a change with artifacts: - proposal.md (what & why) - design.md (how) - tasks.md (implementation steps) When ready to implement, run /opsx:apply --- **Input**: The argument after `/opsx:propose` is the change name (kebab-case), OR a description of what the user wants to build. **Steps** 1. **If no input provided, ask what they want to build** Use the **AskUserQuestion tool** (open-ended, no preset options) to ask: > "What change do you want to work on? Describe what you want to build or fix." From their description, derive a kebab-case name (e.g., "add user authentication" → `add-user-auth`). **IMPORTANT**: Do NOT proceed without understanding what the user wants to build. 2. **Create the change directory** ```bash openspec new change "<name>" ``` This creates a scaffolded change at `openspec/changes/<name>/` with `.openspec.yaml`. 3. **Get the artifact build order** ```bash openspec status --change "<name>" --json ``` Parse the JSON to get: - `applyRequires`: array of artifact IDs needed before implementation (e.g., `["tasks"]`) - `artifacts`: list of all artifacts with their status and dependencies 4. **Create artifacts in sequence until apply-ready** Use the **TodoWrite tool** to tra