spec-authoring skillA
spec-authoring is agent-read markdown (skill) from muvon/octomind-tap: How to write a behavioral spec an autonomous agent can implement with zero unstated assumptions: EARS requirement patterns, the requirements/constraints/verification triple, wording discipline, the clarification protocol for interactive and autonomous runs, and the thin-spec file split. Activate when writing, revising, or reviewing a feature spec or acceptance criteria..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
## Overview A spec is the contract between intent and code. An autonomous implementer follows it exactly — including its gaps: underspecified intent does not get corrected, it gets implemented. The spec's job is to make every requirement checkable, every boundary explicit, and every unresolved question visible rather than guessed. Write a spec when the work is not describable in one sentence. Skip it when it is. ## Mental model Three ingredients, three jobs. All three are required; none substitutes for another. | Ingredient | Answers | Lives in | |---|---|---| | Requirements | What must be true when done | EARS statements, one per test | | Constraints | What the implementer may not do | Guardrails: forbidden moves, protected surfaces, budgets | | Verification | How done is proven | The exact command that must exit 0 | Requirements without constraints let the implementer widen scope. Constraints without requirements produce a cautious no-op. Either without a verification command is unfalsifiable prose. Two properties govern everything else. …
Read the whole file at its exact version.
How to install
mdr add muvon/octomind-tap/spec-authoring@git:20260918.44e86b9mdr add muvon/octomind-tap/spec-authoring@sha256:317db2f561bde56ePin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_ioyw262ausb6abz6)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260918.44e86b9 latest | 2026-09-18 | 44e86b9 | 10,329 B | A | view · diff |
| git:20260918.581103e | 2026-09-18 | 581103e | 13,456 B | A | view · diff |
| git:20260918.07f4be1 | 2026-09-18 | 07f4be1 | 13,205 B | A | view |
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 (10329 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
muvon/octomind-tap · 4 stars · license Apache-2.0 · pushed 2026-09-19 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_ioyw262ausb6abz6 GET https://markdownregistry.com/api/v1/resolve?ref=muvon/octomind-tap/spec-authoring GET https://markdownregistry.com/api/v1/blob/317db2f561bde56e5d97d8aad8d11d2474fce490e898ce852f38f21e126da9ec
Your agent 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.
More from muvon/octomind-tap
Every file in muvon/octomind-tap