app-prd skillA
app-prd is agent-read markdown (skill) from richkuo/rk-skills: Use when the user wants an app idea turned into a Product Requirements Document (PRD) committed to a repo — "create a PRD", "/app-prd", "turn this idea into a PRD", or a raw idea dump ending with "save it to this repo". Produces a complete, section-numbered PRD.md landed via worktree + PR, bootstrapping an empty repo if needed. Stage 1 of the new-app-pipeline..
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
# app-prd Turn a raw idea dump into a complete, implementable PRD committed to the target repo. The PRD is the single source of truth every later stage (question refinement, issue filing, workflow execution) builds on — write it so a cold agent could implement from it plus nothing else. ## Input - An idea dump: features, pricing, constraints, platform choices — usually messy prose. Optionally a target repo (defaults to the current checkout). - If no repo exists yet and the user named one, offer `gh repo create <name> --private` before proceeding. ## Steps ### 1. Check repo state `git status`, `git log --oneline -3`, `git remote -v`, `git ls-remote origin`. Three cases: - **Normal repo**: proceed with the standard worktree + PR flow. - **Empty repo with remote** (no commits anywhere): bootstrap first — create `main`, one **empty** initial commit (`git commit --allow-empty -m "Initial commit"` + attribution footer), push. A PR needs a base branch to exist; never put the PRD itself in the bootstrap commit. - **No repo/remote**: confirm repo creation with the user. ### 2. Draft `PRD.md` Structure (adapt section names to the product, keep the skeleton): …
Read the whole file at its exact version.
How to install
mdr add richkuo/rk-skills/app-prd@git:20260901.2e108d4mdr add richkuo/rk-skills/app-prd@sha256:e57c592e1a7770aaPin 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_tgzwf767nwhxd5xg)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260901.2e108d4 latest | 2026-09-01 | 2e108d4 | 6,298 B | A | view · diff |
| git:20260712.e1f6ab3 | 2026-07-12 | e1f6ab3 | 4,838 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 (6298 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
richkuo/rk-skills · 49 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_tgzwf767nwhxd5xg GET https://markdownregistry.com/api/v1/resolve?ref=richkuo/rk-skills/app-prd GET https://markdownregistry.com/api/v1/blob/e57c592e1a7770aa30f046798a898f1dfa6a2a0e7552d9b051e6afd263de5008
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.