skills.rest
richardnguyen0715
richardnguyen0715COMMUNITY
Explore all skills by this author →
GitHub

deliver-user-stories

Generates user stories with acceptance criteria from product requirements and feature descriptions.

Updated May 19, 2026
Search Tags:#requirements#acceptance criteria#agile#sprint planning#user stories#backlog#prd
One-click install
npx skills add https://github.com/richardnguyen0715/agent-sharing --skill deliver-user-stories-richardnguyen0715
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deliver-user-stories
Source: https://github.com/richardnguyen0715/agent-sharing/tree/main/.github/skills/deliver-user-stories
Command: npx skills add https://github.com/richardnguyen0715/agent-sharing --skill deliver-user-stories-richardnguyen0715

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning an approved PRD or feature description into actionable engineering work is slow and inconsistent. This Skill converts requirements into well-formed user stories with testable acceptance criteria, so teams can plan sprints and write tickets without ambiguity. ## Core Features & Use Cases - Structured Story Generation: Produces stories in the "As a [persona], I want [action] so that [benefit]" format tied to specific personas. - Acceptance Criteria: Writes Given/When/Then criteria that define done for every story. - INVEST Validation: Checks each story against Independent, Negotiable, Valuable, Estimable, Small, and Testable criteria. - Use Case: After PRD approval, feed the feature description in and receive a sprint-ready backlog of stories with acceptance criteria, dependencies, and design notes. ## Quick Start Break down the attached PRD into user stories with acceptance criteria for sprint planning.

Frequently Asked Questions about deliver-user-stories

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

FAQPage Schema
How do I write user stories from a PRD?▼

Review the PRD for goals, target users, and scope, then decompose the feature into distinct user goals per persona. Write each story as "As a [persona], I want [action] so that [benefit]" and add Given/When/Then acceptance criteria.

What is the correct format for user story acceptance criteria?▼

Acceptance criteria use the Given/When/Then format: Given a context, When an action occurs, Then an expected outcome results. Each criterion must be testable so anyone can verify pass or fail.

What are INVEST criteria for user stories?▼

INVEST stands for Independent, Negotiable, Valuable, Estimable, Small, and Testable. Stories meeting these criteria can be built in any order, sized for a single sprint, and verified objectively.

When should I create user stories in the product workflow?▼

Create user stories after PRD approval when breaking features down for implementation, during sprint planning, or when writing engineering tickets. Stories should trace back to documented requirements.

Why do user stories fail sprint planning?▼

Stories fail when they are too large for one sprint, lack testable acceptance criteria, contain implementation details, or miss the benefit clause explaining user value. Validate against INVEST before finalizing.

Related Skills

Explore More Product & Management Skills→
JohnnnmaiJohnnnmai
1

prd-development

Guide users through a structured workflow to create a Product Requirements Document.

Community
Advanced
openshift-hyperfleetopenshift-hyperfleet
5

JIRA Story Point Estimator

Estimate Jira ticket story points from ticket details and historical velocity.

Official
Advanced
yuyuxinliyuyuxinli
1

lean-ux-canvas

Guide teams through the eight Lean UX Canvas v2 boxes to define hypotheses and experiments.

Official
Intermediate
Choi-KeithChoi-Keith

job-stories

Creates JTBD job stories with acceptance criteria using the When-I want-so I can format.

Community
Basic