Turn a feature request into user stories with criteria

About this exercise

Engineering wants user stories for the first version of the break-reminder feature. You need exactly 3 numbered stories in the form 'As a [role], I want [goal] so that [reason]', each followed by exactly 2 acceptance criteria lines starting with '- Given', plain text. Write them for the specific roles in the request, not a generic 'user', and leave out anything the notes say is not in v1.

Common mistakes when you ask AI for this

• Saying 'write user stories'. The AI writes one story per idea in the notes, often 6 or more, with bold headings. Try: Be exact: "Exactly 3 numbered stories, each followed by 2 lines starting '- Given'. Plain text."
• Generic 'As a user'. Without a nudge, the AI often writes 'As a user', which tells engineering nothing. Try: Add: "Use the real roles: shift worker or shift supervisor."
• No criteria shape. The AI writes vague criteria like 'works well on mobile' or a long checklist. Try: Show it: "Exactly 2 criteria per story, each like '- Given..., when..., then...'"
• Including what was cut. The cut items are still in the notes, and the AI writes stories for everything. Try: Add: "Only the v1 items from the Oct 21 decisions. Skip anything marked not in v1 or undecided."

What a strong prompt includes

• Sets the number of stories
• Shows the criteria shape
• Names the real roles
• Limits to v1
• Asks for plain text

Practice this now ↑

Related exercises

• Announce a new weekend rotation in three clear rules (Productivity AI · Managers and team leads)
• Announce a referral bonus with the steps to claim it (Marketing AI · HR and recruiting)
• Announce a team meeting change people will actually follow (Writing AI · Managers and team leads)
• Answer a 'found an error' question in STAR order (Writing AI · Finance and accounting)
• Answer a wholesale inquiry with clear terms (Writing AI · Small business owners)