Home / inkeep / open-knowledge-skills · GitHub

write-a-spec SKILL.md skillA

This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.

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

Install it, pinned

mdr add inkeep/open-knowledge-skills/write-a-spec@git:20261014.2bb8524

Pins git:20261014.2bb8524 in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: inkeep/open-knowledge-skills
Path: skills/starter-packs/software-lifecycle/write-a-spec/SKILL.md
Versions recorded: 6
Latest version: git:20261014.2bb8524, committed Oct 14, 2026
First version recorded: Aug 4, 2026
Size: 19,882 bytes
Repository stars: 17
License: MIT

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

The exact contents, by fingerprint

mdr add inkeep/open-knowledge-skills/write-a-spec@sha256:68558c4378442762

The line at the top of this page pins the label git:20261014.2bb8524, 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](https://markdownregistry.com/badge/art_3esqautbglry6j52.svg)](https://markdownregistry.com/a/art_3esqautbglry6j52)

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.2bb8524 latest	2026-10-14	2bb8524	19,882 B	A	view · diff
git:20260825.dda5ab1	2026-08-25	dda5ab1	19,861 B	A	view · diff
git:20260824.159d280	2026-08-24	159d280	19,839 B	A	view · diff
git:20260813.be5d62e	2026-08-13	be5d62e	19,862 B	A	view · diff
git:20260805.99a8b17	2026-08-05	99a8b17	19,895 B	A	view · diff
git:20260804.8a506ba	2026-08-04	8a506ba	19,890 B	A	view

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 (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

GitHub

inkeep/open-knowledge-skills · 17 stars · license MIT · pushed 2026-10-27 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_3esqautbglry6j52
GET https://markdownregistry.com/api/v1/resolve?ref=inkeep/open-knowledge-skills/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-skills

open-knowledge-discovery SKILL.md skill

inkeep/open-knowledge-skills · skills/core/open-knowledge-discovery/SKILL.md · Read when the user asks what OpenKnowledge is, wants to install it on a repository, wants to open or preview a single…