specify-plan SKILL.md skillA
specify-plan from rsmdt/the-startup is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add rsmdt/the-startup/specify-plan@git:20261026.1fa3434Pins git:20261026.1fa3434 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- rsmdt/the-startup
- Path
plugins/start/skills/specify-plan/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261026.1fa3434, committed Oct 26, 2026
- First version recorded
- Oct 10, 2026
- Size
- 12,288 bytes
- Repository stars
- 577
- License
- MIT
Author the implementation plan — the Plan part of spec.md (target state + phases) plus the implementation TASKS in the spec's tracker that /implement runs. Each phase task holds slice tasks whose bodies are code briefs (features + EARS behavior + quality gates); each slice's holdout acceptance scenarios are separate scenario child tasks. Use after requirements and solution.
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
## Persona Act as an implementation-plan specialist. You translate requirements and solution design into two correlated artifacts: 1. the **Plan part** of `spec.md` — the target state and the phases with the outcome each achieves, plus a pointer to the tracker. It is read for orientation, never parsed for work. 2. the implementation **tasks** in the spec's tracker (`task.js`) — the operational unit `/implement` runs. Everything is a task: one **phase** task per plan phase, under each phase its **slice** tasks (each body is the code brief — features + EARS behavior + quality gates), and under each slice its **scenario** child tasks (the holdout acceptance evidence). A slice describes *what it delivers and how it is proven*, never the steps to build it — `/implement` builds each phase's slices, then evaluates the phase through a barriered code→eval loop, and the loop's code agent owns HOW. The barrier is structural: the code brief lives in the slice task; the scenarios live in separate scenario tasks, so the code agent (reads the slice) and the eval agent (reads the scenarios) never overlap. **Spec Target**: $ARGUMENTS ## Constraints **Always:** …
Read the whole file at its exact version.
How to install
mdr add rsmdt/the-startup/specify-plan@sha256:b7d30693c6ec21a1The line at the top of this page pins the label git:20261026.1fa3434, 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_vgjc6qlma5in6niw)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Oct 10, 2026 and Oct 26, 2026, about one every 4 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261026.1fa3434 latest | 2026-10-26 | 1fa3434 | 12,288 B | A | view · diff |
| git:20261026.2c8aabe | 2026-10-26 | 2c8aabe | 12,090 B | A | view · diff |
| git:20261026.8454ce9 | 2026-10-26 | 8454ce9 | 11,603 B | A | view · diff |
| git:20261026.0dbd6b8 | 2026-10-26 | 0dbd6b8 | 10,461 B | A | view · diff |
| git:20261010.441d9d3 | 2026-10-10 | 441d9d3 | 9,494 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 (12288 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
rsmdt/the-startup · 577 stars · license MIT · pushed 2026-10-26 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_vgjc6qlma5in6niw GET https://markdownregistry.com/api/v1/resolve?ref=rsmdt/the-startup/specify-plan GET https://markdownregistry.com/api/v1/blob/b7d30693c6ec21a1aaec5e3bd8db7834d28eaf79f769ab79075d4ecd452e26bf
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.