irwebtools user-story
When to use
Use when the task matches: user-story, user stories, as a user.
Purpose
Break product intent into stories Development and AI can implement.
Inputs
- Feature brief
- Users in scope
- Business rules
Process
- Write stories as role + need + outcome.
- Keep one primary outcome per story.
- Mark priority and dependencies between stories.
- Exclude technical tasks disguised as stories.
Outputs
- User stories
- Story priority notes
- Out-of-scope story list
Verification
- Confirm each output exists and is reviewable.
- Keep Product validation and engineering verification distinct.
- Do not claim completion without evidence.
Restrictions
- Do not encode architecture choices inside stories.
- Do not invent personas without Product agreement.
- Do not skip acceptance-criteria linkage.