write-a-spec SKILL.md skillA
write-a-spec from inkeep/open-knowledge is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add inkeep/open-knowledge/write-a-spec@git:20261014.adeb8b5Pins git:20261014.adeb8b5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- inkeep/open-knowledge
- Path
packages/server/assets/skills/packs/software-lifecycle/write-a-spec/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261014.adeb8b5, committed Oct 14, 2026
- First version recorded
- Aug 4, 2026
- Size
- 19,882 bytes
- Repository stars
- 4,810
- License
- GPL-3.0
Scope a feature end to end and write an implementation spec under specs/ from an accepted proposal — current-system mapping, goals/non-goals, a Decision Log for one-way-door choices, a live Open Questions backlog, and a real migration + test plan. Read when asked to write a spec, scope this feature, turn this proposal into a spec, plan the implementation, or break this into tasks. Do NOT fire on frame a proposal or write the PRD (sibling frame-a-proposal — a PRD frames a change before it is…
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 a spec — scope a feature and commit an implementation spec > This skill is pack guidance. The platform `/open-knowledge` skill (read/write/preview/linking/grounding rules) still governs every markdown operation — this layers spec-writing craft on top. A spec is the contract between "we decided to build this" and "here is how it gets built." It is derived from an ACCEPTED proposal, maps the system that exists TODAY before proposing a change, and records its one-way-door choices in a Decision Log so the reasoning survives the author leaving. A spec that skips the current-system mapping, or resolves its open questions silently, is a liability — it reads authoritative while being unfounded. `specs/` uses a folder-per-spec shape: `specs/NNN-name/` holding `spec.md`, and (when the work is actually going to be built) `plan.md` + `tasks.md`. The pack ships all three templates. `status` on `spec.md` flows `draft → ... → shipped`. ## Autonomy mode | Mode | Behavior | How entered | |---|---|---| …
Read the whole file at its exact version.
How to install
mdr add inkeep/open-knowledge/write-a-spec@sha256:68558c4378442762The line at the top of this page pins the label git:20261014.adeb8b5, 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_mnngczeh7wlaa5aj)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Aug 4, 2026 and Oct 14, 2026, about one every 14 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261014.adeb8b5 latest | 2026-10-14 | adeb8b5 | 19,882 B | A | view · diff |
| git:20260825.3ab979a | 2026-08-25 | 3ab979a | 19,861 B | A | view · diff |
| git:20260824.4c50c94 | 2026-08-24 | 4c50c94 | 19,839 B | A | view · diff |
| git:20260813.12a6ea2 | 2026-08-13 | 12a6ea2 | 19,862 B | A | view · diff |
| git:20260805.f3f8da4 | 2026-08-05 | f3f8da4 | 19,895 B | A | view · diff |
| git:20260804.8471ed3 | 2026-08-04 | 8471ed3 | 19,890 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 (19882 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
inkeep/open-knowledge · 4,810 stars · license GPL-3.0 · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_mnngczeh7wlaa5aj GET https://markdownregistry.com/api/v1/resolve?ref=inkeep/open-knowledge/write-a-spec GET https://markdownregistry.com/api/v1/blob/68558c4378442762bc0b7692553b2595ec5f6139cb258a344130519caedb1b77
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 inkeep/open-knowledge
Every file in inkeep/open-knowledge