spec-to-tickets SKILL.md skillA
spec-to-tickets from aethrox/doctrine is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add aethrox/doctrine/spec-to-tickets@git:20260809.2a45dbbPins git:20260809.2a45dbb in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- aethrox/doctrine
- Path
skills/spec-to-tickets/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260809.2a45dbb, committed Aug 9, 2026
- First version recorded
- Aug 9, 2026
- Size
- 5,468 bytes
- Repository stars
- 19
- License
- MIT
Turns an already-discussed plan into a written spec and a set of tracer-bullet tickets, synthesizing rather than re-interviewing, slicing work end-to-end rather than by layer, and gating entry/exit with a written Definition of Ready and Definition of Done rather than by feel. Use when the user asks to turn a conversation or plan into a spec, break work into tickets, or size and sequence a set of tasks before implementation starts.
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
# Spec to Tickets A spec synthesizes what's already been decided; it does not re-interview the user from scratch. And a ticket is not "ready to start" or "done" by feel; both are gated by a written, agreed checklist, so two people (or two sessions) apply the same bar instead of a different one each time. ## Phase 1: Synthesize the spec Pull together what the conversation, plan, or existing notes have already established (problem statement, scope, explicit non-goals, and any real constraints (technical, timeline, dependency)) into one written document. This is a **synthesis** step, not a fresh discovery interview: if a genuine open question surfaces that nothing already discussed has answered, ask it once, narrowly, rather than re-covering ground already settled. Write the spec and its tickets without em dashes, using a comma, colon, period, or a reworded sentence instead. A spec worth ticketing states: - **The problem**, in one or two sentences: what's wrong or missing, for whom. - **Scope**, concretely enough that a reader can tell what's in and what's out. …
Read the whole file at its exact version.
How to install
mdr add aethrox/doctrine/spec-to-tickets@sha256:011bfee13f9c4d6aThe line at the top of this page pins the label git:20260809.2a45dbb, 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_4kyzd7me5x66ibxx)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, all committed on Aug 9, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260809.2a45dbb latest | 2026-08-09 | 2a45dbb | 5,468 B | A | view · diff |
| git:20260809.5c2aad2 | 2026-08-09 | 5c2aad2 | 5,356 B | A | view · diff |
| git:20260809.21f29b0 | 2026-08-09 | 21f29b0 | 5,425 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 (5468 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
aethrox/doctrine · 19 stars · license MIT · pushed 2026-09-11 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_4kyzd7me5x66ibxx GET https://markdownregistry.com/api/v1/resolve?ref=aethrox/doctrine/spec-to-tickets GET https://markdownregistry.com/api/v1/blob/011bfee13f9c4d6abc6265b397cbdc16cb12086fea40f95bd462db044e547944
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.