prd-and-stories skillA
prd-and-stories is agent-read markdown (skill) from nahid-sparktales/agent-dispatcher: Write a scope someone else can build from without asking you what you meant — problem, users, the flow end to end including its unhappy states, acceptance criteria phrased as observable behaviour, and explicit non-goals. Use when turning a settled problem into a brief, spec, PRD, epic or set of stories, or when repairing a ticket that is too vague to estimate or to check. Not for deciding whether the problem is real (product-discovery), not for ranking work (prioritization), and not for choosing.
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 and stories The test of a scope is not that it reads well. It is that two people building from it independently produce the same behaviour, and a third can tell whether they did. ## When this fires A problem is settled and the work needs a written scope before it is designed or built; a ticket is too vague to estimate, to build, or to check. It does not fire while the problem is still in question — go back to `product-discovery` and say why. ## Procedure 1. **Check the problem is actually settled.** One paragraph: who, doing what, blocked how, and what evidence says so — with the grade it came with (observed, reported, assumed). If you are writing that paragraph from imagination, stop and say the scope is resting on an unchecked belief. 2. **State the change in the world.** What will be true after this ships that is not true now, expressed as user behaviour or outcome, not as a shipped artifact. "An agent can see the audit trail while closing a refund", not "we add an audit panel". 3. **Inspect the surface you are scoping.** Read the current screens, routes, data model and …
Read the whole file at its exact version.
How to install
mdr add nahid-sparktales/agent-dispatcher/prd-and-stories@git:20260919.a0d4f55mdr add nahid-sparktales/agent-dispatcher/prd-and-stories@sha256:4c0b6ac4b37df5c5Pin 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_urogufezeox3zixw)
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 (7162 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
nahid-sparktales/agent-dispatcher · 49 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_urogufezeox3zixw GET https://markdownregistry.com/api/v1/resolve?ref=nahid-sparktales/agent-dispatcher/prd-and-stories GET https://markdownregistry.com/api/v1/blob/4c0b6ac4b37df5c5c1eedf4c0121fe391e65ca3a6a999a8a606fcccfbd051036
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.