user-stories SKILL.md skillA
user-stories from mattbrailsford/umbraco-devkit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add mattbrailsford/umbraco-devkit/user-stories@git:20261024.874111ePins git:20261024.874111e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- mattbrailsford/umbraco-devkit
- Path
plugins/umbraco-devkit/skills/user-stories/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261024.874111e, committed Oct 24, 2026
- First version recorded
- Oct 14, 2026
- Size
- 7,530 bytes
- Repository stars
- 3
- License
- MIT
Writes, splits and refines user stories with Given/When/Then acceptance criteria in STORIES.md, feeding bdd-specs. Use when turning a feature request or a vague ask into a testable backlog entry.
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
# User stories Turn product intent into stories that flow straight into `bdd-specs` with no manual reshaping. The structure here is a contract, not decoration — get it right and stories become specs become code with nothing lost in translation. **Honest framing:** this is a discipline this plugin introduces, not one already standard across Umbraco projects — don't present it to a team as "the Umbraco way." It's a real, well-understood technique worth adopting on its own merits, and it's what makes `bdd-specs`'s handoff work cleanly. ## Where this writes `STORIES.md` in the feature's plan folder (owned by `feature-plan`, which usually dispatches this skill as its first step). If invoked standalone before `feature-plan` has run, still write to the same file, and note that `feature-plan` still needs to run to turn the stories into an ordered, dependency-aware task list in `PLAN.md`. ## *The pipeline this sits in* ``` feature request ──▶ [user-stories] ──▶ STORIES.md ──▶ [bdd-specs] ──▶ specs ──▶ code ``` Map deliberately: | Story artifact | Becomes in bdd-specs | |---|---| | One story | One Feature (one test class) | …
Read the whole file at its exact version.
How to install
mdr add mattbrailsford/umbraco-devkit/user-stories@sha256:577d080c4891a8a9The line at the top of this page pins the label git:20261024.874111e, 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_hqoacp4nujzefyoa)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Oct 14, 2026 and Oct 24, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261024.874111e latest | 2026-10-24 | 874111e | 7,530 B | A | view · diff |
| git:20261017.8be9de3 | 2026-10-17 | 8be9de3 | 6,291 B | A | view · diff |
| git:20261016.ea2830f | 2026-10-16 | ea2830f | 6,289 B | A | view · diff |
| git:20261016.a78a902 | 2026-10-16 | a78a902 | 5,899 B | A | view · diff |
| git:20261014.eeefa6a | 2026-10-14 | eeefa6a | 6,087 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 (7530 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
mattbrailsford/umbraco-devkit · 3 stars · license MIT · pushed 2026-11-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hqoacp4nujzefyoa GET https://markdownregistry.com/api/v1/resolve?ref=mattbrailsford/umbraco-devkit/user-stories GET https://markdownregistry.com/api/v1/blob/577d080c4891a8a991b81d6b7ad0ce96d2001648dcdd3d49526fd8e9800a3925
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 mattbrailsford/umbraco-devkit
Every file in mattbrailsford/umbraco-devkit