What it does

Creates concise user stories with draft acceptance criteria, assumptions, edge cases, and open questions for team review. It helps teams structure requirements without replacing discovery, prioritization, technical design, or validation with users.

How it works

Provide the user segment, research evidence, goal, context, constraints, business rules, and definition of done. Product, design, engineering, and QA should review value, feasibility, ambiguity, edge cases, and testability before adding the stories to a sprint.

Example workflows

• Turn validated discovery findings into backlog candidates.

• Draft acceptance criteria before refinement with engineering and QA.

• Review existing stories for ambiguity, missing cases, and weak outcomes.