to-spec SKILL.md skillA
This file is byte-identical to the first copy the registry indexed, one of 9 indexed copies. Same content hash, so the same checks give both the same grade.
to-spec from fabiandistler/agents is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add fabiandistler/agents/to-spec@git:20260930.0a9e31dPins git:20260930.0a9e31d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- fabiandistler/agents
- Path
.claude/skills/to-spec/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260930.0a9e31d, committed Sep 30, 2026
- Size
- 3,043 bytes
- Repository stars
- 2
- License
- none declared
Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.
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
This skill takes the current conversation context and codebase understanding and produces a spec. Do NOT interview the user; just synthesize what you already know. The issue tracker and triage label vocabulary should have been provided to you. If not, tell the user to run `/setup-matt-pocock-skills`. ## Process 1. Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the spec, and respect any ADRs in the area you're touching. 2. Sketch out the seams at which you're going to test the feature. Existing seams should be preferred to new ones. Use the highest seam possible. If new seams are needed, propose them at the highest point you can. The fewer seams across the codebase, the better - the ideal number is one. Check with the user that these seams match their expectations. 3. Write the spec using the template below, then publish it to the project issue tracker. Apply the `ready-for-agent` triage label - no need for additional triage. <spec-template> ## Problem Statement The problem that the user is facing, from the user's perspective. ## Solution …
Read the whole file at its exact version.
How to install
mdr add fabiandistler/agents/to-spec@sha256:43ad9cf318e5e7d3The line at the top of this page pins the label git:20260930.0a9e31d, 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_da7denejlriulhdl)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 30, 2026.
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 (3043 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
fabiandistler/agents · 2 stars · license none declared · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_da7denejlriulhdl GET https://markdownregistry.com/api/v1/resolve?ref=fabiandistler/agents/to-spec GET https://markdownregistry.com/api/v1/blob/43ad9cf318e5e7d3d1fa360253a37021796dc87a0c2e595ad262661a10f85088
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.
More from fabiandistler/agents
Every file in fabiandistler/agents