TechnicalCollectible prompt

User stories with acceptance criteria and edge cases

Turn a feature into user stories with testable acceptance criteria that you or an AI can build from.

ClaudeChatGPTGemini

Curated by Nvoka

Nvoka wordmark logo
Nvoka wordmark logoTechnical

User stories with acceptance criteria and edge cases

Act as a senior product owner. Write user stories for {{page_or_feature}} in {{app_idea}}. The roles are {{user_roles}}. For each story: - As a role, I want an action, so that a benefit, in plain words - Acceptance criteria as Given, When, Then scenarios covering the happy path, empty states, errors, permissions and phones - Edge cases, such as double clicks, slow connections, expired sessions, very long text and time zones - Priority: must, should or could - Size: small, medium or large, with a note if it should be split Rules: - Each story is small enough to build and test in a day or two - Every criterion is testable; no vague words like fast or easy unless you put a number on them - Include what each role must not be able to do, not just what they can do Return the stories in the order they should be built, followed by open questions and the assumptions you made. Ask me up to three questions first if the roles or scope are unclear.
Technicalnvoka.com/library/nvoka-user-stories-with-acceptance-criteriaScan to open
Technical

User stories with acceptance criteria and edge cases

Turn a feature into user stories with testable acceptance criteria that you or an AI can build from.

Nvoka logo

Curated by Nvoka

ClaudeChatGPTGemini
Add to my library

Make it yours

Fill in the blanks and change any word. Only your copy changes, never the card.

Fill in the blanks

0 of 3 filled

Your prompt

Act as a senior product owner. Write user stories for {{page_or_feature}} in {{app_idea}}. The roles are {{user_roles}}. For each story: - As a role, I want an action, so that a benefit, in plain words - Acceptance criteria as Given, When, Then scenarios covering the happy path, empty states, errors, permissions and phones - Edge cases, such as double clicks, slow connections, expired sessions, very long text and time zones - Priority: must, should or could - Size: small, medium or large, with a note if it should be split Rules: - Each story is small enough to build and test in a day or two - Every criterion is testable; no vague words like fast or easy unless you put a number on them - Include what each role must not be able to do, not just what they can do Return the stories in the order they should be built, followed by open questions and the assumptions you made. Ask me up to three questions first if the roles or scope are unclear.
See all