User Story Writing
By cam j · Published · Updated
Stories sliced so each one ships something a user would notice.
Tags: Product, Planning, Communication
Prompt template
Turn this into user stories. - The feature: [textarea: What is being built] - Who uses it, and in what situation: [textarea: Context matters more than persona names] - What happens today: [textarea: Current behaviour, if any] - Technical context the team needs: [textarea: Systems, constraints, dependencies] Slice by user-visible value, not by technical layer. No story called build the backend. Each one gets acceptance criteria in testable form: the happy path, the edge cases, the error states, and the permission conditions. Then flag anything in my description ambiguous enough that two developers would build it differently, because that is the thing worth catching now rather than at review.