01-user-story-generation
Installation
SKILL.md
User Story Generation Skill
Use When
- decomposing approved features into INVEST user stories, epics, story points, and initial acceptance criteria; use acceptance-criteria when stories already exist and only test oracles are needed.
- Use this procedure when the required source artefacts are available and
User-story backlog and story mapis the next lifecycle deliverable.
Do Not Use When
- Use
acceptance-criteriawhen that neighbouring route owns the decision or deliverable. - Do not invent missing project evidence, standards clauses, thresholds, or stakeholder decisions.
Required Inputs
| Artefact | Source or provider | Required? | Behaviour when missing |
|---|---|---|---|
| Vision, feature catalogue, personas, glossary, and quality targets | Project _context/ and product owner |
Yes | Stop the affected step, name the missing source, and return only a qualified gap record. |