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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
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
---
**Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`). Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.
**Input**: The user's request should include a change name (kebab-case) OR a description of what they want to build.
**Steps**
1. **If no clear 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."
…
The line at the top of this page pins the label v1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_6zeppvh263on7dk7
GET https://markdownregistry.com/api/v1/resolve?ref=jabrena/plinth/openspec-propose
GET https://markdownregistry.com/api/v1/blob/18aebaac7f703478abd58100a3375d0cb21867df62f92d1e497fd73e14ad3d66
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
jabrena/plinth · benchmarks/problem2/scenario3/.agents/skills/openspec-propose/SKILL.md · Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they…
jabrena/plinth · skills/001-commands-inventory/SKILL.md · Use when you need to generate a checklist document with embedded commands inventory, following the embedded template…
jabrena/plinth · skills/002-agents-inventory/SKILL.md · Use when you need to generate a checklist document with embedded agents inventory, following the embedded template…
jabrena/plinth · skills/003-skills-inventory/SKILL.md · Use when you need to generate a checklist document with Java system prompts from skills.xml, following the embedded…
jabrena/plinth · skills/004-commands-installation/SKILL.md · Use when you need to install the embedded project commands into command directories (.github/commands…
jabrena/plinth · skills/005-agents-installation/SKILL.md · Use when you need to install the embedded robot agents into .github/agents, .claude/agents, .cursor/agents, or…
jabrena/plinth · skills/012-agile-epic/SKILL.md · Guides the creation of agile epics with comprehensive definition including business value, success criteria, and…
jabrena/plinth · skills/013-agile-feature/SKILL.md · Guides the creation of detailed agile feature documentation from an existing epic. Use when the user wants to split an…
jabrena/plinth · skills/014-agile-user-story/SKILL.md · Guides the creation of agile user stories. Use when the user wants to create a user story. This should trigger for…
jabrena/plinth · skills/021-problem-framing/SKILL.md · Use when a problem or issue needs explicit framing before deeper analysis begins — establishing the Problem statement…
jabrena/plinth · skills/022-root-cause-analysis/SKILL.md · Use when a framed problem needs root-cause investigation rather than a symptom-level fix, applying Five Whys, Fishbone…
monid-ai/monid · .opencode/skills/openspec-propose/SKILL.md · Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they…
mememeow-studio/mememeow · .agents/skills/openspec-propose/SKILL.md · Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they…
mememeow-studio/mememeow · .opencode/skills/openspec-propose/SKILL.md · Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they…
mememeow-studio/mememeow · .claude/skills/openspec-propose/SKILL.md · Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they…
partcad/partcad · .claude/skills/openspec-propose/SKILL.md · Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they…
partcad/partcad · .cursor/skills/openspec-propose/SKILL.md · Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they…
jabrena/plinth · benchmarks/problem2/scenario3/.agents/skills/openspec-propose/SKILL.md · Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they…
asymmetric-al/core · .agents/skills/openspec-propose/SKILL.md · Propose a new OpenSpec change with all artifacts generated in one step. Use when the user wants to quickly describe…
