writing-specs SKILL.md skillA
writing-specs from sergeyklay/.agents is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add sergeyklay/.agents/writing-specs@v1.1Pins v1.1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- sergeyklay/.agents
- Path
.agents/skills/writing-specs/SKILL.md- Versions recorded
- 7
- Latest version
- v1.1, committed Sep 20, 2026
- First version recorded
- Jun 25, 2026
- Size
- 17,890 bytes
- Repository stars
- 6
- License
- Apache-2.0
Write technical specifications from feature requests, prompts, or tracker references. Use when asked to specify, architect, design, write a spec, define requirements, create a technical specification, analyze a feature request, or produce a specification document. Also use when given a tracker reference (Jira, GitHub issue, Linear, Asana, etc.) and a specification is the expected output. Do NOT use for code review, implementation, implementation planning, or reviewing existing specs. Produces…
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
# Writing Specifications Transform a feature request into a specification rigorous enough to implement without further clarification. Ambiguity in a spec causes real engineering delay; design errors caught here are orders of magnitude cheaper than design errors caught in code review. The spec binds the implementer's scope and design: it is what stops the coder improvising a second feature or inventing behavior nobody asked for. It does not bind reality. You are an agent writing for other agents, and you can be wrong about the codebase; where the spec and the code disagree, the code is right. Write with that in mind: a spec whose errors are cheap to spot and report beats one whose confident tone makes an implementer follow it off a cliff. The artifact is disposable. It is gitignored, it lives on one machine, and it is discarded days after the work lands. Nobody publishes it, commits it, or reads it later. Do not polish it for an audience, do not write a preamble for a human reviewer, and do not spend words defending a decision to a reader who does not exist. …
Read the whole file at its exact version.
How to install
mdr add sergeyklay/.agents/writing-specs@sha256:82fd9ef11c900432The line at the top of this page pins the label v1.1, 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_7hloth45raeltrkh)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 7 versions of this file, between Jun 25, 2026 and Sep 20, 2026, about one every 14 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.1 latest | 2026-09-20 | 803ca87 | 17,890 B | A | view · diff |
| v1.1 | 2026-09-16 | 08f5454 | 17,890 B | A | view · diff |
| v1.1 | 2026-09-06 | 371110d | 17,848 B | A | view · diff |
| v1.1 | 2026-09-05 | 6d5f818 | 19,726 B | A | view · diff |
| v1.1 | 2026-09-05 | fb3cfb3 | 19,726 B | A | view · diff |
| v1.1 | 2026-09-04 | 208fbfe | 18,334 B | A | view · diff |
| v1.1 | 2026-06-25 | 2bc5e43 | 14,728 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 (17890 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
sergeyklay/.agents · 6 stars · license Apache-2.0 · pushed 2026-10-29 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7hloth45raeltrkh GET https://markdownregistry.com/api/v1/resolve?ref=sergeyklay/.agents/writing-specs GET https://markdownregistry.com/api/v1/blob/82fd9ef11c900432ba59283728f136c589d96879bafe4065f3e4322caf6cc979
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 sergeyklay/.agents
Every file in sergeyklay/.agents