openspec-propose SKILL.md skillA
openspec-propose from obed0101/notchnull is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add obed0101/notchnull/openspec-propose@v1.0Pins v1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- obed0101/notchnull
- Path
.opencode/skills/openspec-propose/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0, committed Oct 19, 2026
- Size
- 16,689 bytes
- Repository stars
- 3
- License
- GPL-3.0
Propose a new OpenSpec 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. Also use when the user says "openspec propose" or "opsx propose".
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. **Planning boundary**: This workflow creates planning artifacts only. The user request that selected or triggered this workflow authorizes planning only, even if it asks to build or fix something. Do not edit project code. After the planning artifacts are complete, stop. Do not start implementation in the same response, even if the initial request asks for it. Wait for a new user request after the artifacts are presented; then start the apply workflow. I'll create a change with the artifacts your schema defines. With the default spec-driven schema that is: - proposal.md (what & why) - `specs/<capability-path>/spec.md` (what the system must do - a delta, not the main spec) - design.md (how) - tasks.md (implementation steps) `<capability-path>` is the spec directory relative to `specs/` (for example, `user-auth` or `identity/user-auth`). Preserve an existing capability's full path and follow the project's established organization for new capabilities. When the user is ready to implement, they must start the apply workflow explicitly. --- …
Read the whole file at its exact version.
How to install
mdr add obed0101/notchnull/openspec-propose@sha256:1633c31ce0b457f0The 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.
[](https://markdownregistry.com/a/art_t3bhnvd5lgr2w77u)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 19, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (16689 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
obed0101/notchnull · 3 stars · license GPL-3.0 · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_t3bhnvd5lgr2w77u GET https://markdownregistry.com/api/v1/resolve?ref=obed0101/notchnull/openspec-propose GET https://markdownregistry.com/api/v1/blob/1633c31ce0b457f0fec7a6dadcfcd0e59f3c015ef8698fd3a37afc65392703fb
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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from obed0101/notchnull
Every file in obed0101/notchnull