1---2name: openspec-propose3description: Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.4license: MIT5compatibility: Requires openspec CLI.6metadata:7 author: openspec8 version: "1.0"9 generatedBy: "1.4.1"10---1112Propose a new change - create the change and generate all artifacts in one step.1314I'll create a change with artifacts:15- proposal.md (what & why)16- design.md (how)17- tasks.md (implementation steps)1819When ready to implement, run /opsx:apply2021---2223**Input**: The user's request should include a change name (kebab-case) OR a description of what they want to build.2425**Steps**26271. **If no clear input provided, ask what they want to build**2829 Use the **AskUserQuestion tool** (open-ended, no preset options) to ask:30 > "What change do you want to work on? Describe what you want to build or fix."3132 From their description, derive a kebab-case name (e.g., "add user authentication" → `add-user-auth`).3334 **IMPORTANT**: Do NOT proceed without understanding what the user wants to build.35362. **Create the change directory**37 ```bash38 openspec new change "<name>"39 ```40 This creates a scaffolded change in the planning home resolved by the CLI with `.openspec.yaml`.41423. **Get the artifact build order**43 ```bash44 openspec status --change "<name>" --json45 ```46 Parse the JSON to get:47 - `applyRequires`: array of artifact IDs needed before implementation (e.g., `["tasks"]`)48 - `artifacts`: list of all artifacts with their status and dependencies49 - `planningHome`, `changeRoot`, `artifactPaths`, and `actionContext`: path and scope context. Use these instead of assuming repo-local paths.50514. **Create artifacts in sequence until apply-ready**5253 Use the **TodoWrite tool** to track progress through the artifacts.5455 Loop through artifacts in dependency order (artifacts with no pending dependencies first):5657 a. **For each artifact that is `ready` (dependencies satisfied)**:58 - Get instructions:59 ```bash60 openspec instructions <artifact-id> --change "<name>" --json61 ```62 - The instructions JSON includes:63 - `context`: Project background (constraints for you - do NOT include in output)64 - `rules`: Artifact-specific rules (constraints for you - do NOT include in output)65 - `template`: The structure to use for your output file66 - `instruction`: Schema-specific guidance for this artifact type67 - `resolvedOutputPath`: Resolved path or pattern to write the artifact68 - `dependencies`: Completed artifacts to read for context69 - Read any completed dependency files for context70 - Create the artifact file using `template` as the structure and write it to `resolvedOutputPath`71 - Apply `context` and `rules` as constraints - but do NOT copy them into the file72 - Show brief progress: "Created <artifact-id>"7374 b. **Continue until all `applyRequires` artifacts are complete**75 - After creating each artifact, re-run `openspec status --change "<name>" --json`76 - Check if every artifact ID in `applyRequires` has `status: "done"` in the artifacts array77 - Stop when all `applyRequires` artifacts are done7879 c. **If an artifact requires user input** (unclear context):80 - Use **AskUserQuestion tool** to clarify81 - Then continue with creation82835. **Show final status**84 ```bash85 openspec status --change "<name>"86 ```8788**Output**8990After completing all artifacts, summarize:91- Change name and location92- List of artifacts created with brief descriptions93- What's ready: "All artifacts created! Ready for implementation."94- Prompt: "Run `/opsx:apply` or ask me to implement to start working on the tasks."9596**Artifact Creation Guidelines**9798- Follow the `instruction` field from `openspec instructions` for each artifact type99- The schema defines what each artifact should contain - follow it100- Read dependency artifacts for context before creating new ones101- Use `template` as the structure for your output file - fill in its sections102- **IMPORTANT**: `context` and `rules` are constraints for YOU, not content for the file103 - Do NOT copy `<context>`, `<rules>`, `<project_context>` blocks into the artifact104 - These guide what you write, but should never appear in the output105106**Guardrails**107- Create ALL artifacts needed for implementation (as defined by schema's `apply.requires`)108- Always read dependency artifacts before creating a new one109- If context is critically unclear, ask the user - but prefer making reasonable decisions to keep momentum110- If a change with that name already exists, ask if user wants to continue it or create a new one111- Verify each artifact file exists after writing before proceeding to next