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
---
**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."
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"]`)
…
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_ngotid5jxzyf5est
GET https://markdownregistry.com/api/v1/resolve?ref=tekkiiiii/the-agency/openspec-propose
GET https://markdownregistry.com/api/v1/blob/88ad070e30256107d8989c2bf4b0ff9e4ee1c8976dd32829675c88f00618dad6
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.
tekkiiiii/the-agency · agents-archive/dept-sunset-2026-10-08/skills/dept-resume/SKILL.md · Read dept-state.md and spawn a Dept Head with a lean briefing. Department-operations parallel of /pd-resume.
tekkiiiii/the-agency · agents-archive/dept-sunset-2026-10-08/skills/dept-save-state/SKILL.md · Write dept-state.md and member-roster.md at end of department session. Department-operations parallel of /save-state.
tekkiiiii/the-agency · agents-archive/dept-sunset-2026-10-08/skills/dept-status/SKILL.md · Read-only department status digest. No spawns. Shows active coords, pipelines, open issues, and incoming tasks.
tekkiiiii/the-agency · agents-archive/dept-sunset-2026-10-08/skills/room-manager-digest/SKILL.md · Use on /room-manager-digest, a 12h cron, or when a dept head wants a fresh report. Reads each dept room's rolling.md…
tekkiiiii/the-agency · agents-archive/dept-sunset-2026-10-08/skills/room-manager/SKILL.md · Use on /room-manager, every 10 minutes as a background loop, or when new room activity is suspected (handoff file…
tekkiiiii/the-agency · agents-archive/rev001-curator-2026-10-12/skills/obsidian-vault/SKILL.md · Use to forward decisions, project learnings, skill creations and generated assets to the Obsidian vault, and to read it…
tekkiiiii/the-agency · scripts/tests/fixtures/jev/router-skills/content-polish/SKILL.md · Polish drafted content to publish-ready in one pass; English and Vietnamese.
tekkiiiii/the-agency · scripts/tests/fixtures/jev/router-skills/frontend/SKILL.md · Use when building frontend UIs: "build a landing page", "make a dashboard", "write a React component". Not for…
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/problem1/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 · 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…
