specify-requirements SKILL.md skillA
specify-requirements 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-requirements@git:20261026.e975c51Pins git:20261026.e975c51 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-requirements/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261026.e975c51, committed Oct 26, 2026
- First version recorded
- Sep 30, 2026
- Size
- 6,122 bytes
- Repository stars
- 577
- License
- MIT
Create and validate product requirements documents (PRD). Use when writing requirements, defining user stories, specifying acceptance criteria, analyzing user needs, or working on the Requirements part of a spec.md in .start/specs/.
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 a product requirements specialist that creates and validates PRDs focusing on WHAT needs to be built and WHY it matters.
**Spec Target**: $ARGUMENTS
## Interface
PRDSection {
name: string
status: Complete | NeedsInput | InProgress
topic?: string // what needs clarification, if NeedsInput
}
State {
specId = ""
sections: PRDSection[]
clarificationMarkers: number
}
## Constraints
**Always:**
- Write the `## Requirements` part of `spec.md` and keep its section structure exactly as the spec template defines it.
- Draft every section, validate, then close the part with one approval gate — not one review per section.
- Obtain user disposition (confirm / correct / discard) on research findings before folding them into the PRD — an unconfirmed finding is a hypothesis, not a requirement. Ask each observable finding (a product rule users could tell apart in the UI or the interface the brief or contract defines) as its own question, batched up to four per call; list the rest for confirmation with the approval. Error precedence, unknown or null fields, and Origin, Host, or CSRF checks are never observable: take the recommended default.
…Read the whole file at its exact version.
How to install
mdr add rsmdt/the-startup/specify-requirements@sha256:e58eaf6b654b56e7The line at the top of this page pins the label git:20261026.e975c51, 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_brfwzsju2m23owra)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 30, 2026 and Oct 26, 2026, about one every 7 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261026.e975c51 latest | 2026-10-26 | e975c51 | 6,122 B | A | view · diff |
| git:20261026.8454ce9 | 2026-10-26 | 8454ce9 | 6,191 B | A | view · diff |
| git:20261026.0dbd6b8 | 2026-10-26 | 0dbd6b8 | 5,560 B | A | view · diff |
| git:20261010.441d9d3 | 2026-10-10 | 441d9d3 | 5,285 B | A | view · diff |
| git:20260930.f89b416 | 2026-09-30 | f89b416 | 5,379 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 (6122 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_brfwzsju2m23owra GET https://markdownregistry.com/api/v1/resolve?ref=rsmdt/the-startup/specify-requirements GET https://markdownregistry.com/api/v1/blob/e58eaf6b654b56e7577bc30c9fd460805852984d686a7ff9644df9e1958a573c
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.