spec-driven-workflow SKILL.md skillA
spec-driven-workflow from borghei/claude-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add borghei/claude-skills/spec-driven-workflow@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- borghei/claude-skills
- Path
engineering/spec-driven-workflow/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0.0, committed Jul 21, 2026
- Size
- 12,731 bytes
- Repository stars
- 1,075
- License
- a license file GitHub does not identify
Run development from an executable specification with traceable requirement IDs and merge-time coverage gates. Use when starting a greenfield feature, reviving a stale spec, or gating merges on requirement coverage.
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
# Spec-Driven Workflow Development where the specification is the source of truth and the code is its implementation, rather than a document that was true at kickoff and fiction by week three. The mechanism is unglamorous: every normative statement gets a stable ID, every ID appears in a test, and the merge gate fails when the two drift apart. Without that mechanical link a spec is a memo, and memos do not survive contact with a sprint. ## When to use this skill - **Starting a greenfield feature** where the interface is contested and the cost of building the wrong thing is high - **Reviving a stale spec** that no longer matches shipped behaviour and needs reconciling before the next change - **Gating merges on coverage** so a PR that implements two of five committed requirements cannot silently land - **Auditing what actually shipped** ahead of a stakeholder review or a compliance obligation - **Handing a feature to another team** who need the intent, not just the code - **Generating an implementation** from a spec — which only works if the spec is precise enough that two engineers would build the same thing ## Inputs the skill expects …
Read the whole file at its exact version.
How to install
mdr add borghei/claude-skills/spec-driven-workflow@sha256:2523a6285815b9d8The line at the top of this page pins the label v1.0.0, 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_l6fgcnksprd4rja6)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jul 21, 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 (12731 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
borghei/claude-skills · 1,075 stars · license a license file GitHub does not identify · pushed 2026-11-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_l6fgcnksprd4rja6 GET https://markdownregistry.com/api/v1/resolve?ref=borghei/claude-skills/spec-driven-workflow GET https://markdownregistry.com/api/v1/blob/2523a6285815b9d81a067d6966ebc0805d7578ba90de6099a5265140448ca392
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.