create-spec SKILL.md skillA

create-spec from jkaloger/lazyspec is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add jkaloger/lazyspec/create-spec@git:20260309.b2e83d0

Pins git:20260309.b2e83d0 in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: jkaloger/lazyspec
Path: examples/spec/skills/create-spec/SKILL.md
Versions recorded: 1
Latest version: git:20260309.b2e83d0, committed Mar 9, 2026
Size: 9,170 bytes
Repository stars: 10
License: MIT

Use when locking down technical contracts for a vertical slice. Creates Spec documents with data models, API surface, validation rules, error handling, edge cases, and optional acceptance criteria. Specs can be standalone or linked to an RFC. Supports parallel subagent dispatch for RFCs with multiple slices.

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

```
NO IMPLEMENTATION WITHOUT LOCKED CONTRACTS
```

If you can't state the data models, API surface, and error handling, the contracts aren't locked down yet.

> [!IMPORTANT]
> Read `_common.md` in the skills directory for CLI usage, forbidden actions, and subagent tiers.

<HARD-GATE>
Specs can exist standalone or linked to a parent RFC. A parent RFC is NOT required.
After identifying multiple slices, partition upfront and get user approval
before dispatching subagents.
After completion: use the `/create-plan` skill to plan the first implementation.
You already have the Spec context (and RFC context if one exists) from writing
this Spec, so resolve-context is not needed when continuing in the same session.
</HARD-GATE>

<NEVER>
- Do NOT write contract sections without reading the parent RFC first (if one exists).
- Do NOT dispatch subagents without user approval of the partition.
</NEVER>

# Create Spec

## Workflow Position

```d2
lazy -> write-rfc -> create-spec -> resolve-context -> create-plan -> build

create-spec.style.fill: "#4A9EFF"
create-spec.style.font-color: "#FFFFFF"
lazy.style.opacity: 0.4
write-rfc.style.opacity: 0.4
resolve-context.style.opacity: 0.4
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add jkaloger/lazyspec/create-spec@sha256:5e90c35421109689

The line at the top of this page pins the label git:20260309.b2e83d0, 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_xlpbj3hmrtang6rs.svg)](https://markdownregistry.com/a/art_xlpbj3hmrtang6rs)

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

Versions

The registry has recorded 1 version of this file, committed on Mar 9, 2026.

version	committed	commit	size	audit
git:20260309.b2e83d0 latest	2026-03-09	b2e83d0	9,170 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 (9170 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

jkaloger/lazyspec · 10 stars · license MIT · pushed 2026-11-02 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_xlpbj3hmrtang6rs
GET https://markdownregistry.com/api/v1/resolve?ref=jkaloger/lazyspec/create-spec
GET https://markdownregistry.com/api/v1/blob/5e90c354211096897c6b903b924084d5b066c5bb03982a63042b622b06563897

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 jkaloger/lazyspec

AGENTS.md AGENTS.md file

jkaloger/lazyspec · AGENTS.md

git:20260929.ad44f28 · audit A · 10 stars

DESIGN.md DESIGN.md file

jkaloger/lazyspec · DESIGN.md

git:20260701.f139c3a · audit A · 10 stars

create-audit SKILL.md skill

jkaloger/lazyspec · examples/spec/skills/create-audit/SKILL.md · Use when running a criteria-based review (health check, security audit, accessibility review, pen test, bug bash, spec…