skills.rest
amplitude
amplitudeOFFICIAL
Explore all skills by this author →
WebsiteGitHub

create-user-stories

Convert PRDs into sprint-sized user stories with acceptance criteria.

142|16|Updated Mar 20, 2026
Search Tags:#handoff#prd#product-management#sprint-planning#user-stories#acceptance-criteria
One-click install
npx skills add https://github.com/amplitude/builder-skills --skill create-user-stories-amplitude
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-user-stories
Source: https://github.com/amplitude/builder-skills/tree/main/product-skills/skills/create-user-stories
Command: npx skills add https://github.com/amplitude/builder-skills --skill create-user-stories-amplitude

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert a PRD or feature description into clear, testable, and sprint-sized user stories so engineering and QA can implement and verify work without ambiguity.

Core Features & Use Cases

  • Structured Story Templates: Outputs a concise Title, an "As a [user]" Story, prioritized Acceptance Criteria, Priority, and Notes for each story.
  • Testable Acceptance Criteria: Emphasizes Given/When/Then style criteria, edge cases, and unhappy paths so QA can validate completion.
  • Sprint Planning & Handoffs: Ideal for product managers preparing engineering handoffs, breaking large specs into sprint-sized pieces, and flagging dependencies or design/API needs.
  • Use Case Example: Take a PRD for a new onboarding flow and produce individual stories for zero state, signup, verification, error handling, and analytics instrumentation.

Quick Start

Provide your PRD or feature description and ask: "Break this into user stories with acceptance criteria and priorities."

Frequently Asked Questions about create-user-stories

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I break a PRD into sprint-ready user stories?▼

To break a PRD into user stories, provide the feature description to generate sprint-sized stories with titles, standardized text, acceptance criteria, priority tags, and dependency notes.

How do I write testable acceptance criteria for engineering handoffs?▼

Generate testable acceptance criteria by structuring them in Given/When/Then formats, emphasizing edge cases and unhappy paths to ensure QA can validate implementation completion without ambiguity.

What is the best way to prepare a product spec for sprint planning?▼

Prepare a product spec for sprint planning by converting the feature description into implementable pieces, flagging items needing design or API changes alongside priority tags and dependencies.

Can I generate user stories for complex onboarding flows from a feature description?▼

Yes, you can input a feature description for an onboarding flow to output individual stories covering zero state, signup, verification, error handling, and analytics instrumentation.

Does generating user stories this way capture API and design dependencies?▼

Yes, generating user stories this way captures dependencies by adding notes that flag specific items requiring design changes or API modifications for engineering and cross-functional teams.

Related Skills

Explore More Product & Management Skills→
me2reshme2resh
489

write-spec

Convert feature ideas into structured PRDs with problem statements and requirements.

Community
Intermediate
alex-tgkalex-tgk

agile-product-owner

Generate INVEST-compliant user stories with acceptance criteria from epics.

Community
Intermediate
tarunccettarunccet
5

test-scenarios

Generate step-by-step test scenarios with objectives and expected outcomes from user stories and acceptance criteria.

Community
Intermediate
simonheimlichersimonheimlicher
1

decomposing-feature-to-stories

Decompose Feature specs into atomic Gherkin Story scenarios with ≤7 stories and BSP ordering.

Community
Basic