tiny-spec-scope SKILL.md skillA
tiny-spec-scope from grayma77er/tiny-spec is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add grayma77er/tiny-spec/tiny-spec-scope@git:20261008.b72cfb4Pins git:20261008.b72cfb4 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- grayma77er/tiny-spec
- Path
tiny-spec-scope/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261008.b72cfb4, committed Oct 8, 2026
- First version recorded
- Sep 4, 2026
- Size
- 13,314 bytes
- Repository stars
- 3
- License
- MIT
The greenfield on-ramp — turn a rough idea, or an existing PRD, into BREAKDOWN.md at the project root - a flat list of well-defined Features, each with draft acceptance criteria, a slug, and an optional needs: naming the features it must follow, plus a shared Decisions block. The one skill that works from a blank page. Does not scaffold .spec/ or touch the constitution — tiny-spec-create reads BREAKDOWN.md in seeded mode and does that. For an existing codebase use tiny-spec-adopt…
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
# tiny-spec-scope The **greenfield front door**. Takes what you have — a one-line idea, loose notes, a PRD someone else wrote, wireframes — and turns it into the set of **features** to spec, *before* any one of them is picked up. It is the moment **before** `tiny-spec-create`: that skill takes **one feature → one spec**; this one decides what the features *are*. You create the work items in your tracker from the result, then run the normal flow per feature. **A feature is the unit of work.** One feature = one spec = one branch = one plan→build loop. There is no Story level beneath it — a feature is written well-defined enough to build directly, and its acceptance criteria are what the spec's requirements come from. **Starting from an existing codebase instead?** Use `tiny-spec-adopt` — it derives the constitution from the code that's already there. The two are the suite's two front doors, and you generally want exactly one of them. The exception is a **PRD for new work on an existing codebase**: the PRD still needs carving into features, so run this too (`tiny-spec-run` does both on its own: adopt for the constitution, scope for the features). …
Read the whole file at its exact version.
How to install
mdr add grayma77er/tiny-spec/tiny-spec-scope@sha256:a687224b587b07caThe line at the top of this page pins the label git:20261008.b72cfb4, 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_slh5qrqou4pygxmb)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Sep 4, 2026 and Oct 8, 2026, about one every 11 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261008.b72cfb4 latest | 2026-10-08 | b72cfb4 | 13,314 B | A | view · diff |
| git:20261002.f20c947 | 2026-10-02 | f20c947 | 12,581 B | A | view · diff |
| git:20260930.39dc17d | 2026-09-30 | 39dc17d | 12,551 B | A | view · diff |
| git:20260904.bbac9b4 | 2026-09-04 | bbac9b4 | 11,085 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 (13314 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
grayma77er/tiny-spec · 3 stars · license MIT · pushed 2026-10-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_slh5qrqou4pygxmb GET https://markdownregistry.com/api/v1/resolve?ref=grayma77er/tiny-spec/tiny-spec-scope GET https://markdownregistry.com/api/v1/blob/a687224b587b07cab1b623f87f05863dc5ad9b36d2b946e1326cc72f7e4b0fe5
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.