From product
Break a PRD, epic, or feature idea into well-formed user stories — "As a <persona>, I want <goal>, so that <benefit>" — each with clear, testable acceptance criteria (Gherkin given/when/then). Uses real personas when a personas skill is available, sizes stories to be independently shippable, and orders them. Output feeds /scope. Use when the user has a PRD/epic to slice or asks for user stories. Triggers: "user stories", "break into stories", "write stories for this", "slice this epic", "story map".
How this skill is triggered — by the user, by Claude, or both
Slash command
/product:user-storiesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Turn a PRD/epic/feature into a set of user stories that a team could pick up.
Turn a PRD/epic/feature into a set of user stories that a team could pick up. Good stories are INVEST: Independent, Negotiable, Valuable, Estimable, Small, Testable. Each delivers user-visible value and has acceptance criteria you could hand to QA.
PRD.md exists (e.g. in .plan/<feature-slug>/), read it.enernet-personas) if available so stories name
real personas, not "the user" generically.Lay out the user's journey as a backbone (the big steps), then slice stories under each step. This keeps the set coherent and surfaces gaps. Prefer vertical slices (thin end-to-end value) over horizontal layers (all the backend, then all the frontend).
Save to <project>/.plan/<feature-slug>/user-stories.md (or where the user
prefers). For each:
## US-<n>: <short title>
**As a** <persona>
**I want** <goal/capability>
**So that** <benefit/why>
**Priority:** P0 | P1 | P2
**Depends on:** <other story IDs, or —>
### Acceptance Criteria
- [ ] **Given** <context> **when** <action> **then** <expected outcome>
- [ ] …
### Notes
<edge cases, out-of-scope, open questions for grilling later>
Summarize the story set (count, P0s, ordering). Suggest:
"Run /scope to turn these into eng tickets and start the build pipeline."
Provides a checklist for code reviews covering functionality, security, performance, maintainability, tests, and quality. Use for pull requests, audits, team standards, and developer training.
npx claudepluginhub nitintf/ai-skills --plugin product