prd-builder skillA
prd-builder is agent-read markdown (skill) from vmobifystudio/app-dev-team: Use to construct a complete Product Requirements Document for a mobile app from a vision file. Used primarily by the CPO agent. Triggers on requests to "write the PRD", "spec out the product", or as part of /app-plan..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# PRD builder Build `docs/10-prd.md` and `docs/11-backlog.md` from `docs/00-vision.md` and `docs/01-intake.md`. ## Required sections (in order) 1. **Product summary** — 2-3 sentences. 2. **Personas** — 1-3, each with: name, goal, frustration, context-of-use. 3. **User journeys** — 3-7 prose paragraphs. Each paragraph: entry → steps → exit → success state. 4. **Feature table** — | ID | Name | Description | Priority | Acceptance criteria | |----|------|-------------|----------|---------------------| Use F-001, F-002, ... Priority is P0/P1/P2. 5. **User stories** — for each P0 feature, 1–5 stories: *As a [persona], I want to [action] so that [outcome]* plus Given/When/Then acceptance. 6. **Out of scope** — explicit list. 7. **Open questions** — what needs CEO or user input. ## Backlog format `docs/11-backlog.md` — every backlog item carries both the implementation ticket ID and the PRD feature ID so the chain is traceable end-to-end: ``` # Backlog ## Sprint 1 — MVP foundation - APP-001 [F-001] <feature> — XS/S/M/L/XL - APP-002 [F-002] <feature> — ... ## Sprint 2 — MVP completion - ... ## v1.1+ - ... ``` …
Read the whole file at its exact version.
How to install
mdr add vmobifystudio/app-dev-team/prd-builder@git:20260601.0c38fbamdr add vmobifystudio/app-dev-team/prd-builder@sha256:8173d5fbe75a3525Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_hwwb4yd2drvmfwq5)
1 badge views in 30 days
Versions
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 (1942 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
vmobifystudio/app-dev-team · 4 stars · license MIT · pushed 2026-09-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hwwb4yd2drvmfwq5 GET https://markdownregistry.com/api/v1/resolve?ref=vmobifystudio/app-dev-team/prd-builder GET https://markdownregistry.com/api/v1/blob/8173d5fbe75a3525ec1e7bd00402515f2e0e75470d1528143370c73bd722f24c
Your agent 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.