spec-planning 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.
spec-planning from byerlikaya/claude-starter-kit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add byerlikaya/claude-starter-kit/spec-planning@git:20260926.0882e5cPins git:20260926.0882e5c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- byerlikaya/claude-starter-kit
- Path
kit/skills/spec-planning/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260926.0882e5c, committed Sep 26, 2026
- First version recorded
- Sep 24, 2026
- Size
- 5,717 bytes
- Repository stars
- 26
- License
- MIT
Spec-first planning: task breakdown, measurable acceptance criteria, dependency order, risk priority. crew-planner applies it; the plan goes to docs/PLAN.md. Use when the scope is unclear or the work spans more than one change.
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-First Planning <!-- routing-eval reads the next line; why it sits in the body: AGENT_TEMPLATE.md --> Trigger phrases: "plan", "spec", "task breakdown", "acceptance criteria", "roadmap", "how do we split this" Before writing code: what will be done, how it counts as "done", and in what order to proceed become clear. ## Steps 1. **Purpose & scope:** the problem being solved in a single sentence; also write the out-of-scope explicitly (prevent scope creep). 2. **Split into vertical slices:** the smallest end-to-end working pieces (not horizontal layers). Each slice delivers value on its own. 3. **A contract for every task:** input · output · **measurable acceptance criterion** (testable) · estimated risk. 4. **Dependency graph:** which task waits on what; no cycles. **Bring the riskiest/most-unknown to the front** (fail-fast). 5. **Uncertainties:** assumption list + open questions; do not fill ambiguous spots with a guess, ask with explicit options. ## Output (docs/PLAN.md) ``` # <Feature> — Plan ## Acceptance criteria - [ ] AC-1: <measurable outcome> - [ ] AC-2: <measurable outcome> ## Tasks (order) …
Read the whole file at its exact version.
How to install
mdr add byerlikaya/claude-starter-kit/spec-planning@sha256:d3d031a8d932cf52The line at the top of this page pins the label git:20260926.0882e5c, 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_bjt4hvydmaatjwdp)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 24, 2026 and Sep 26, 2026, more than one a day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260926.0882e5c latest | 2026-09-26 | 0882e5c | 5,717 B | A | view · diff |
| git:20260924.a457823 | 2026-09-24 | a457823 | 5,768 B | A | view · diff |
| git:20260924.ccb2bc9 | 2026-09-24 | ccb2bc9 | 6,103 B | A | view · diff |
| git:20260924.bd59e95 | 2026-09-24 | bd59e95 | 6,103 B | A | view · diff |
| git:20260924.ad81b1a | 2026-09-24 | ad81b1a | 6,102 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 (5717 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
byerlikaya/claude-starter-kit · 26 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_bjt4hvydmaatjwdp GET https://markdownregistry.com/api/v1/resolve?ref=byerlikaya/claude-starter-kit/spec-planning GET https://markdownregistry.com/api/v1/blob/d3d031a8d932cf5282455b097ae78f8ce2476a41e43a349753ee6fd526f27994
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 byerlikaya/claude-starter-kit
Every file in byerlikaya/claude-starter-kit