user-story SKILL.md skillA
user-story from deanpeters/product-manager-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add deanpeters/product-manager-skills/user-story@git:20260704.6a4fbf2Pins git:20260704.6a4fbf2 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- deanpeters/product-manager-skills
- Path
skills/user-story/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260704.6a4fbf2, committed Jul 4, 2026
- First version recorded
- Feb 5, 2026
- Size
- 11,457 bytes
- Repository stars
- 7,918
- License
- a license file GitHub does not identify
Create user stories with Mike Cohn format and Gherkin acceptance criteria. Use when turning user needs into development-ready work with clear outcomes and testable conditions.
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
## Purpose Create clear, concise user stories that combine Mike Cohn's user story format with Gherkin-style acceptance criteria. Use this to translate user needs into actionable development work that focuses on outcomes, ensures shared understanding between product and engineering, and provides testable success criteria. This is not a feature spec—it's a conversation starter that captures *who* benefits, *what* they're trying to do, *why* it matters, and *how* you'll know it works. ## Input **Works best with:** The feature or user need the story captures. **Also useful:** The user role, the outcome they want, and edge cases the acceptance criteria must cover. Anything supplied with the invocation itself — text after the skill name, a pasted context dump, or an appended `ARGUMENTS:` line — counts as answers already given. Use it and skip whatever it covers; don't re-ask. **Arriving empty-handed? That works too.** The skill asks who the user is and what they're trying to accomplish before drafting story and Gherkin criteria. **Example invocation:** `Write user stories for password reset via SMS for our banking app — include the lockout edge case.` ## Key Concepts …
Read the whole file at its exact version.
How to install
mdr add deanpeters/product-manager-skills/user-story@sha256:8c2f2a32969bee14The line at the top of this page pins the label git:20260704.6a4fbf2, 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_oolbmiqgigctqpib)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Feb 5, 2026 and Jul 4, 2026, about one every 37 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260704.6a4fbf2 latest | 2026-07-04 | 6a4fbf2 | 11,457 B | A | view · diff |
| git:20260309.0a8f6ac | 2026-03-09 | 0a8f6ac | 10,729 B | A | view · diff |
| git:20260227.26a442b | 2026-02-27 | 26a442b | 10,428 B | A | view · diff |
| git:20260206.7788ebc | 2026-02-06 | 7788ebc | 9,990 B | A | view · diff |
| git:20260205.5d8ce73 | 2026-02-05 | 5d8ce73 | 9,481 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 (11457 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
deanpeters/product-manager-skills · 7,918 stars · license a license file GitHub does not identify · pushed 2026-10-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_oolbmiqgigctqpib GET https://markdownregistry.com/api/v1/resolve?ref=deanpeters/product-manager-skills/user-story GET https://markdownregistry.com/api/v1/blob/8c2f2a32969bee146514d9270dbb88a4368392874c21e5a2523e8168db0bd2df
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.
More from deanpeters/product-manager-skills
Every file in deanpeters/product-manager-skills