Vague stories create rework. This lesson turns your Day 1 brief into testable behavior: stories with acceptance criteria an engineer can actually build against.
Story generator
Using this product brief [paste], write user stories in the format: As a [user], I want [action] so that [outcome]. For each story add 3-5 acceptance criteria in Given/When/Then format, plus edge cases for empty states, errors and permissions.
Tip: Ask Claude to play a skeptical engineer and estimate which criteria are ambiguous: it catches the fights before sprint planning does.