deliver-user-stories SKILL.md skillA
deliver-user-stories from product-on-purpose/pm-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add product-on-purpose/pm-skills/deliver-user-stories@v2.1.0Pins v2.1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- product-on-purpose/pm-skills
- Path
skills/deliver-user-stories/SKILL.md- Versions recorded
- 5
- Latest version
- v2.1.0, committed Jun 10, 2026
- First version recorded
- Mar 25, 2026
- Size
- 4,205 bytes
- Repository stars
- 790
- License
- Apache-2.0
Generates user stories in the standard persona, action, benefit story format from product requirements or feature descriptions. Use when breaking a feature into stories for sprint planning, writing tickets, or communicating scope to engineering. For testable Given/When/Then acceptance criteria on a story, use deliver-acceptance-criteria; for boundary and failure scenarios, use deliver-edge-cases.
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
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 --> # User Stories User stories are concise descriptions of functionality from the user's perspective. They capture who needs something, what they need, and why - without prescribing how to build it. Good user stories enable teams to break large features into estimable, deliverable increments while maintaining focus on user value. ## When to Use - After PRD approval, when breaking down features for implementation - During sprint planning to create actionable work items - When writing tickets for engineering teams - When communicating requirements to stakeholders in accessible terms - When prioritizing a backlog based on user value ## When NOT to Use - You need deeper, QA-ready Given/When/Then coverage for a single story or slice -> use `deliver-acceptance-criteria` - You need the feature-wide catalog of boundary conditions and failure scenarios -> use `deliver-edge-cases` - The feature itself is not yet specified -> use `deliver-prd` first; stories should trace back to documented requirements …
Read the whole file at its exact version.
How to install
mdr add product-on-purpose/pm-skills/deliver-user-stories@sha256:d737dbb3c646b9f5The line at the top of this page pins the label v2.1.0, 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_m6zey5yyqeacrore)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Mar 25, 2026 and Jun 10, 2026, about one every 19 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v2.1.0 latest | 2026-06-10 | bf23914 | 4,205 B | A | view · diff |
| v2.0.1 | 2026-06-10 | b8ccff6 | 3,410 B | A | view · diff |
| v2.0.0 | 2026-05-20 | be1352b | 3,231 B | A | view · diff |
| v2.0.0 | 2026-04-23 | 8ab0f81 | 3,225 B | A | view · diff |
| v2.0.0 | 2026-03-25 | 0ab0a60 | 3,233 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 (4205 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
product-on-purpose/pm-skills · 790 stars · license Apache-2.0 · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_m6zey5yyqeacrore GET https://markdownregistry.com/api/v1/resolve?ref=product-on-purpose/pm-skills/deliver-user-stories GET https://markdownregistry.com/api/v1/blob/d737dbb3c646b9f527a56ee8ad0ea919cf1958e4090bdb40f2f418352982030c
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.