Gemini Business intermediate

User Story Writer with Acceptance Criteria

Added Apr 1, 2026

You are a product manager who writes exceptionally clear user stories. Write a complete set of user stories for [FEATURE_NAME] in a [PRODUCT_TYPE]. The feature should enable users to [FEATURE_DESCRIPTION]. For each user story, provide: the story in standard format ('As a [persona], I want [action], so that [benefit]'), acceptance criteria using Given/When/Then (Gherkin) format with at least 3 scenarios per story including happy path and edge cases, story points estimate (using Fibonacci: 1, 2, 3, 5, 8, 13), dependencies on other stories or systems, and technical notes for the engineering team. Organize stories into an epic with a clear implementation order. Include one spike story for any area requiring technical investigation before development begins.

Try in Gemini

About This Prompt

User stories bridge the gap between business requirements and engineering implementation, but poorly written stories are the leading cause of sprint scope creep and rework. This prompt generates stories with the specificity that engineers need: Gherkin acceptance criteria that can be directly translated into test cases, story point estimates for sprint planning, dependency mapping for sequencing, and technical notes that flag implementation considerations. The spike story ensures technical unknowns are investigated before committing to delivery estimates. Essential for product managers, scrum masters, and engineering leads during backlog grooming.

Variables to Customize


[FEATURE_NAME]

Name of the feature

Example: Team Workspace Sharing


[PRODUCT_TYPE]

Type of product

Example: project management SaaS application


[FEATURE_DESCRIPTION]

What users should be able to do

Example: share workspaces with team members, assign roles with different permission levels, and transfer workspace ownership

Tips for Best Results

Review acceptance criteria with QA before sprint planning for testability
Keep individual stories small enough to complete in one sprint
Add non-functional requirements (performance, security) as separate stories

Example Output

## Epic: Team Workspace Sharing
**Epic Description:** Enable collaborative workspace management with role-based access control
**Total Estimated Points:** 34

### Story 1: Invite Team Members to Workspace
**As a** workspace owner, **I want to** invite team members by email address, **so that** they can access and contribute to shared projects.

**Story Points:** 5 | **Priority:** P1 | **Dependencies:** None

**Acceptance Criteria:**
```gherkin
Scenario: Successfully invite a new member
  Given I am the owner of workspace 'Marketing Q3'
  When I enter the email '[email protected]' and select the 'Editor' role
  And I click 'Send Invitation'
  Then an invitation email is sent to '[email protected]'
  And the invitation appears in the Pending Invitations list
  And the invitation expires after 7 days

Scenario: Invite an existing platform user
  Given the email '[email protected]' belongs to a registered user
  When I invite them to my workspace
  Then they receive an in-app notification in addition to email
```

user-stories agile product-management scrum acceptance-criteria