drafting-requirements skillA
drafting-requirements is agent-read markdown (skill) from clickety-clacks/tightbeam: The craft of a single requirement — verifiability, atomicity, active voice, banned vague words, examples as acceptance, and two-way traceability. Use while drafting or tightening the requirements in a spec..
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 before it reaches your agent: the main file against the SHA-256 recorded here, the others against the git hashes of its source commit. The deterministic audit below grades the latest version, and the same checks always give the same file the same grade.
What the file says
# Drafting requirements The kernel's filter decides whether a line is a requirement at all: can it be checked pass/fail? This skill is how you make each surviving line unambiguous, atomic, and traceable. These requirements live inside the spec's canonical skeleton — the eight sections spec-homing names (Goal, Non-Goals, Terms, Assumptions, Invariants, Architecture, Acceptance, Open Questions). That set is canonical, not a starting point: every spec carries all eight. This skill sharpens the individual lines that fill it. ## Kill the vague words Keep a banned list open while you draft; each word marks a decision you have not made: - **and/or** — forces the reader to choose the interpretation. State exactly which case(s) apply. - **etc. / and so on / including but not limited to** — you stopped enumerating before the thinking was done. Finish the list. - **fast, robust, user-friendly, seamless, intuitive, efficient, flexible** — subjective, no test. Replace with a measured, checkable criterion. - **minimize / maximize / optimize / better / faster / improved** — a comparative with no baseline. Better than what, toward which measurable target? …
Read the whole file at its exact version.
How to install
mdr add clickety-clacks/tightbeam/drafting-requirements@git:20260723.7608dd1mdr add clickety-clacks/tightbeam/drafting-requirements@sha256:e173a2594a032c0fPin to a label to follow the author's releases, or to a sha256 for exact bytes. Either way the resolved hash is written to mdr.lock, and mdr install fetches those bytes again and checks them, so it installs them exactly or fails.
[](https://markdownregistry.com/a/art_36tzyxh2ka3kk7tw)
1 badge views in 30 days
Versions
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 (3466 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
clickety-clacks/tightbeam · 14 stars · license none · pushed 2026-09-27 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_36tzyxh2ka3kk7tw GET https://markdownregistry.com/api/v1/resolve?ref=clickety-clacks/tightbeam/drafting-requirements GET https://markdownregistry.com/api/v1/blob/e173a2594a032c0f9824d5a2eabe726c2dd9f7acc06386e2822ef394dc871d8b
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.