write-spec SKILL.md skillA

write-spec from dzhng/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add dzhng/skills/write-spec@git:20261110.a7712c1

Pins git:20261110.a7712c1 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
dzhng/skills
Path
skills/plan/write-spec/SKILL.md
Versions recorded
1
Latest version
git:20261110.a7712c1, committed Nov 10, 2026
Size
18,713 bytes
Repository stars
1,507
License
MIT

Break large features into independently verifiable, human-reviewable slices under a feature directory in specs/. Use for risky or multi-step feature work that needs upfront questioning, API seams, browser-playable checkpoints, HTML visualizations, screenshot gates, staged implementation plans, recursive fog-of-war reslicing, or proactive research into reference implementations/best practices before slicing. Pairs with your project's verification harness and screenshot gates…

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

# Write Spec

Turn a large feature into a ladder of small contracts. Each rung should be
understandable to the human, testable by an agent, and useful before the
whole feature is done.

## First Principles

1. **Grill before planning.** Ask one question at a time until you know the
   desired outcome, non-goals, review surface, sacred contracts, missing
   assets, and first useful playable checkpoint. Give your recommended
   answer with each question so the user can accept, reject, or edit it.
   Inspect the repo instead of asking questions the code can answer.
   Close the interview by asking whether the plan must carry backward
   compatibility or data migrations — the default is **neither**: hard
   cutovers, no compat shims, no migration scaffolding, no deploy-order
   dances. Only the user opting in puts them in the plan.

2. **Slice at API seams.** Each slice should behave like a tiny library where
   possible: named module boundary, typed inputs/outputs, deterministic
   fixtures, and tests at the seam. If a slice needs three unrelated systems
   booted before it can be checked, sharpen the seam.

3. **Research the fog.** When the feature depends on an unfamiliar domain,
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_wwb2sl4bhsngaplb/9b03aa3d7c724943dadde164a1dc0f380e44ced244e6562faa98d71ea66628c7.json

Then /plugin install write-spec@markdownregistry-wwb2sl4bhsngaplb in Claude Code. It installs git:20261110.a7712c1, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add dzhng/skills/write-spec@sha256:9b03aa3d7c724943

The line at the top of this page pins the label git:20261110.a7712c1, 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.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_wwb2sl4bhsngaplb.svg)](https://markdownregistry.com/a/art_wwb2sl4bhsngaplb)

2 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in dzhng/skills/write-spec since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of write-spec from somewhere else? Ask it: where did my write-spec come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 1 version of this file, committed on Nov 10, 2026.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20261110.a7712c1 latest2026-11-10 a7712c1 18,713 BA view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (18713 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

GitHub

dzhng/skills · 1,507 stars · license MIT · pushed 2026-11-13 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_wwb2sl4bhsngaplb
GET https://markdownregistry.com/api/v1/resolve?ref=dzhng/skills/write-spec
GET https://markdownregistry.com/api/v1/blob/9b03aa3d7c724943dadde164a1dc0f380e44ced244e6562faa98d71ea66628c7

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 dzhng/skills

audit-agents SKILL.md skill
dzhng/skills · skills/authoring/audit-agents/SKILL.md · Audit or rewrite AGENTS.md so it holds only lasting principles. Run it only when the user asks for it by name; never…
git:20261002.5fa4602 · audit A · 1,507 stars
eval-skills SKILL.md skill
dzhng/skills · skills/authoring/eval-skills/SKILL.md · Eval and improve a skill against golden cases — run the target skill blind in a fresh, context-free subagent on each…
git:20260705.adffd39 · audit A · 1,507 stars
write-skills SKILL.md skill
dzhng/skills · skills/authoring/write-skills/SKILL.md · Create or revise agent skills. Use when adding a new skill file, renaming a skill, simplifying an existing skill…
git:20261004.3e02e02 · audit A · 1,507 stars
cinematic-shot SKILL.md skill
dzhng/skills · skills/graphics/cinematic-shot/SKILL.md · Shoot software UI like a film. A sequence of hero shots, each a steep, oblique, extreme close-up of the interface…
git:20261014.26d0b31 · audit A · 1,507 stars
isometric-motion SKILL.md skill
dzhng/skills · skills/graphics/isometric-motion/SKILL.md · Build animations and interactive elements (explainers, figures, hero visuals, step-through walkthroughs) in the crafted…
git:20261014.22dda8c · audit A · 1,507 stars
launch-video SKILL.md skill
dzhng/skills · skills/graphics/launch-video/SKILL.md · Make a showreel-grade motion-graphics launch video, with music, that introduces a CLI, library, or product from its…
git:20261110.873aba8 · audit A · 1,507 stars
renderer SKILL.md skill
dzhng/skills · skills/graphics/renderer/SKILL.md · Architecture rules for GPU rendering with TypeGPU/WebGPU. Use when adding or changing render passes, shaders, frame…
git:20261028.dc8bdd9 · audit A · 1,507 stars
xiaohei-illustrations SKILL.md skill
dzhng/skills · skills/graphics/xiaohei-illustrations/SKILL.md · Generate Ian-style Xiaohei illustrations for articles, posts, blogs, Notion documents, workflows, methods, processes…
git:20261014.f2fbf92 · audit A · 1,507 stars
claude SKILL.md skill
dzhng/skills · skills/implement/claude/SKILL.md · Use Claude Code as an independent `claude -p` subagent when the user explicitly asks for Claude, wants a second-agent…
git:20261110.a7712c1 · audit A · 1,507 stars
close-spec SKILL.md skill
dzhng/skills · skills/implement/close-spec/SKILL.md · When a spec under specs/<feature>/ is done shipping (a write-spec build, or any planned task that produced a spec)…
git:20261110.a7712c1 · audit A · 1,507 stars
codex SKILL.md skill
dzhng/skills · skills/implement/codex/SKILL.md · Use the local Codex CLI as an independent second agent. Two branches — (1) proactively run `codex review` for a second…
git:20261110.a7712c1 · audit A · 1,507 stars
handoff-spec SKILL.md skill
dzhng/skills · skills/implement/handoff-spec/SKILL.md · Hand a spec that is mid-implementation to another machine or another agent.
git:20261110.a7712c1 · audit A · 1,507 stars

Every file in dzhng/skills

Other files named write-spec

write-spec SKILL.md skill
me2resh/apexyard · .claude/skills/write-spec/SKILL.md · Write a feature spec or PRD from a problem statement or feature idea. Use when creating product requirements documents.
git:20261015.37f5689 · audit A · 551 stars
write-spec SKILL.md skill
accountgo/accountgo · .agents/skills/write-spec/SKILL.md · Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request…
git:20261029.31a77b6 · audit A · 448 stars
write-spec SKILL.md skill
dzhng/duet-agent · .agents/skills/write-spec/SKILL.md · Break large features into independently verifiable, human-reviewable slices under a feature directory in specs/. Use…
git:20261028.649a3d2 · audit A · 53 stars
write-spec SKILL.md skill
eltmon/overdeck · sync-sources/skills/write-spec/SKILL.md · Compatibility redirect: /write-spec has been renamed to /pan-plan
git:20260918.7b95344 · audit A · 36 stars
write-spec SKILL.md skill
hassan-mohiddin/freeflow · .skill-eval/qualification/subjects/neutral/write-spec/SKILL.md · Use when turning settled discovery, explicit requirements, validated design direction, or source evidence into a…
git:20260712.138f16f · audit A · 5 stars
write-spec SKILL.md skill
ninjasln-labs/agent-skills · write-spec/SKILL.md · Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request…
v1.2.0 · audit A · 4 stars

Browse by kind, by grade A, or by owner.