spec-homing skillA
spec-homing is agent-read markdown (skill) from clickety-clacks/tightbeam: How a spec's identity binds to the work it drives. Use when writing a new spec, looking for an existing spec, or referencing spec conventions..
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 homing ## Binding a spec to its work A path alone names a location, not a version. When a spec drives a work-item, bind its actual path by content: `tightbeam work-item-create --title "<feature>" --spec-ref <name> --spec-sha256 <hex>` records the exact spec the work serves, so a coder or reviewer-spec session reads the version you handed off and not a later edit. Re-bind on a material amendment (`work-item-update --spec-ref … --spec-sha256 …`) so the thread always names current truth — a stale pin indicts the spec, not the builder. Shipped Kung Fu does not prescribe where a spec lives. By default, write it in the responsible agent's workdir. An organization may establish its own shared workspace, repository, or other location convention. The recorded spec reference and hash—not a universal folder—identify the ruling. A spec must not exist only as prose in a work-item note. ## Finding a spec First follow the work item's spec reference when one exists. Otherwise, search the responsible workdir and any organization-defined spec location for the feature's terms. A spec that covers the topic is extended or superseded, not duplicated. Organizations …
Read the whole file at its exact version.
How to install
mdr add clickety-clacks/tightbeam/spec-homing@git:20260905.dbe46a8mdr add clickety-clacks/tightbeam/spec-homing@sha256:5669c076798fea24Pin 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_jm7m32u4qbshhliv)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260905.dbe46a8 latest | 2026-09-05 | dbe46a8 | 2,548 B | A | view · diff |
| git:20260903.f172d5d | 2026-09-03 | f172d5d | 2,522 B | A | view · diff |
| git:20260817.a18d8b3 | 2026-08-17 | a18d8b3 | 2,383 B | A | view · diff |
| git:20260723.7608dd1 | 2026-07-23 | 7608dd1 | 2,667 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 (2548 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_jm7m32u4qbshhliv GET https://markdownregistry.com/api/v1/resolve?ref=clickety-clacks/tightbeam/spec-homing GET https://markdownregistry.com/api/v1/blob/5669c076798fea24efeaeecadc2d2f4f8a3d342673ca6020b086716f93578b3e
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.