spec-handoff skillA
spec-handoff is agent-read markdown (skill) from clickety-clacks/tightbeam: How a spec moves to implementation and stays authoritative while it is built — readiness, marked holes, content-hash binding, clarifications that amend the canonical file first. Use when handing a spec to builders or answering a build-time question..
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
# Spec handoff ## Before handoff 1. Acceptance is concrete and testable: a coder can check its work against each clause, and a reviewer-spec session can judge each clause satisfied or not from evidence. Each clause has a concrete example (Given/When/Then) attached — the format is what proves the clause is decidable. 2. Open questions are listed explicitly in their own section, not buried in prose, each marked BLOCKING or NON-BLOCKING. A marked hole is one an orchestrator can build around; an unmarked hole it cannot see. A blocking question on a load-bearing concept goes to the user (`tightbeam wake --user <id> --prompt "<the question>"`) and holds back the affected scope; separable scope hands off. 3. Non-goals are named, so implementation cannot drift into them. The eight-section skeleton (spec-homing) is yours to fill; the reviewer-spec session blocks on a load-bearing hole in it, not on its shape. 4. The handoff names the spec by identity, not just topic: the canonical path plus the content the work-item is bound to (`--spec-ref`/`--spec-sha256`, see spec-homing), the in-scope goals, and the work-item id. Bind (or re-bind) the hash AFTER the …
Read the whole file at its exact version.
How to install
mdr add clickety-clacks/tightbeam/spec-handoff@git:20260905.dbe46a8mdr add clickety-clacks/tightbeam/spec-handoff@sha256:a592248c26cef5fePin 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_whm3yigntm7kmbea)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260905.dbe46a8 latest | 2026-09-05 | dbe46a8 | 3,228 B | A | view · diff |
| git:20260903.f172d5d | 2026-09-03 | f172d5d | 3,202 B | A | view · diff |
| git:20260723.7608dd1 | 2026-07-23 | 7608dd1 | 3,069 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 (3228 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_whm3yigntm7kmbea GET https://markdownregistry.com/api/v1/resolve?ref=clickety-clacks/tightbeam/spec-handoff GET https://markdownregistry.com/api/v1/blob/a592248c26cef5fec60aa1a7fc512f1b9706b1632a8d9dab62d9b869d776b8ba
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.