From vamfi-software-consultancy
This skill should be used when the user asks to "shape stories", "create a backlog", "break this epic into stories", "write user stories with acceptance criteria", "define the product backlog", "estimate stories", or needs to convert a PRD or delivery plan into an executable sprint backlog.
How this skill is triggered — by the user, by Claude, or both
Slash command
/vamfi-software-consultancy:backlog-and-story-shapingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Convert PRD requirements and delivery plan phases into well-shaped, independently deployable user stories with acceptance criteria and estimates. Apply the Definition of Ready so stories enter the sprint ready to execute.
Convert PRD requirements and delivery plan phases into well-shaped, independently deployable user stories with acceptance criteria and estimates. Apply the Definition of Ready so stories enter the sprint ready to execute.
Well-shaped stories are the unit of delivery. A poorly shaped story is the root cause of missed sprint goals, rework, and scope creep. This skill produces stories that are ready to implement without further clarification.
Organise stories into epics aligned to delivery phases and user outcomes:
# Epic [N]: [Epic Title]
Objective: [The business or user outcome this epic achieves]
Phase: [Which delivery phase this epic belongs to]
Priority: Must Have / Should Have / Could Have
## Stories
- [STORY-N]: [Title]
- [STORY-N+1]: [Title]
For each story:
# STORY-[N]: [Short, descriptive title]
**Epic**: [Parent epic]
**Priority**: Must Have / Should Have / Could Have
**Estimate**: XS (< 0.5d) | S (0.5-1d) | M (1-2d) | L (2-3d) | XL (> 3d)
## User Story
As a [persona], I want [capability] so that [outcome].
## Acceptance Criteria
- [ ] Given [context], when [action], then [result]
- [ ] Given [invalid context], when [action], then [error handling]
- [ ] Given [edge case], when [action], then [expected behaviour]
## Technical Notes
[Key implementation hints — which components, APIs, or data this story touches]
## Dependencies
[Stories or external items that must complete before this story can start]
## Definition of Ready Checklist
- [ ] User story is clear and understood by the team
- [ ] Acceptance criteria are testable and agreed
- [ ] Dependencies are identified and resolved or scheduled
- [ ] Estimate is agreed
- [ ] Technical approach is understood (no unknowns requiring a spike)
Use reference stories to calibrate estimates:
Order the backlog by:
For the first sprint, produce a sprint plan:
| Story | Estimate | Assignee (role) | Acceptance Test |
|---|---|---|---|
| STORY-1 | S | Backend Engineer | API returns 200 with correct schema |
| STORY-2 | M | Full-stack | Form submits and data persists |
Stories are Done when:
references/story-splitting-patterns.md — How to split large stories safelyassets/backlog-template.md — Blank backlog template with epic and story structurenpx claudepluginhub vamfi/vamfi-plugins --plugin vamfi-software-consultancyGenerates prioritized user stories with Given/When/Then acceptance criteria, story point estimates, and MoSCoW prioritization for sprint planning.
Use this skill when the user asks to "write user stories", "decompose this into user stories", "break this into stories", "write acceptance criteria for this feature", "turn this PRD into stories", "create a story map", "help me write stories for sprint planning", or has a feature or PRD and wants to decompose it into shippable units for engineering. Do NOT use this skill to write a full PRD — use prd-authoring for that.
Decomposes epics into INVEST-validated user stories with Given-When-Then acceptance criteria, Fibonacci/T-shirt estimates (default Sprint-level), and a Story Map for sprint planning.