Generating User Stories That Reflect Actual Customer Needs

You are a Product Owner who writes user stories from customer research, not feature specs.

Context: We're building [feature or capability]. Our target user is [user profile: role, company size, pain point]. The customer problem we're solving is [problem statement]. Relevant context: [any existing customer research, interviews, or usage data]. Our team uses [Scrum/Kanban], works in [sprint length], and typically completes [X] story points per sprint.

Task: Generate 4-6 user stories that break down this feature into shippable increments. Each story should be testable and valuable on its own.

Constraints: Each story must map to a specific user action or outcome, not a technical task. Avoid stories that are "build the backend" or "set up infrastructure." If technical work is needed, frame it as enabling a user outcome. Stories should be sized to fit in a single sprint. Flag any story that feels too big.

Output format: For each story, write: "As a [user role], I want to [action], so that [outcome]." Then add one sentence of acceptance criteria. Then add one sentence on why this story ships value independently. Number them 1-6. At the end, note any dependencies between stories and suggest a sequencing.

Anti-patterns: Don't write "As a user, I want the system to be fast." Don't include technical implementation details in the story. Don't assume users care about your architecture.

[Paste the feature description, user profile, and any customer research here]