skills.rest
product-on-purpose
product-on-purposeOFFICIAL
Explore all skills by this author →
GitHub

deliver-user-stories

Generate user stories and Given/When/Then acceptance criteria from product requirements.

527|69|Updated Jan 9, 2026
Search Tags:#agile#PRD#backlog#INVEST#sprint-planning#user-stories#acceptance-criteria
One-click install
npx skills add https://github.com/product-on-purpose/pm-skills --skill deliver-user-stories
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: deliver-user-stories
Source: https://github.com/product-on-purpose/pm-skills/tree/main/skills/deliver-user-stories
Command: npx skills add https://github.com/product-on-purpose/pm-skills --skill deliver-user-stories

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill generates user stories with clear acceptance criteria from product requirements or feature descriptions. It helps teams break down features into actionable work items and ensures alignment with user value.

Core Features & Use Cases

  • Story generation: Create user stories in the standard "As a [persona], I want [action] so that [benefit]" format with attached acceptance criteria.
  • Context & INVEST: Apply INVEST principles and provide context, dependencies, and notes to support planning.
  • Output template: Use the References template (references/TEMPLATE.md) to structure outputs and ensure consistency across a backlog.

Quick Start

Provide a feature description or PRD to generate a set of user stories with acceptance criteria using the standard template.

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 with acceptance criteria from a PRD?▼

To generate user stories from a PRD, provide your feature description to create standard persona-action-benefit stories with structured Given/When/Then acceptance criteria. This ensures your backlog items are actionable and aligned with user value during sprint planning.

What is the INVEST principle for agile user stories?▼

The INVEST principle for agile user stories ensures each backlog item is Independent, Negotiable, Valuable, Estimable, Small, and Testable. Applying INVEST during story generation helps structure acceptance criteria and confirms the story delivers clear user value.

How do I break down product requirements for backlog refinement?▼

Breaking down product requirements for backlog refinement involves transforming feature descriptions into concrete, testable user stories. This process speeds up backlog creation by outputting structured story headers with defined personas, payoffs, and scope.

Can I use Given/When/Then format for agile acceptance criteria?▼

Yes, you can use Given/When/Then format for agile acceptance criteria to enforce INVEST-aligned testing scenarios. This structured format clarifies preconditions, user actions, and expected outcomes for each generated user story.

What is the best way to structure a user story template for sprint planning?▼

The best way to structure a user story template for sprint planning is using a consistent header that captures the persona, payoff, and scope. Applying a standard template ensures uniformity across your backlog and enforces INVEST-aligned acceptance criteria.

Related Skills

Explore More Product & Management Skills→
mappa-aimappa-ai
1

write-a-prd

Create detailed PRDs from problem descriptions, codebase exploration, and structured interviews.

Official
Advanced
nimeshgurungnimeshgurung

agile-product-owner

Generate INVEST-compliant user stories, acceptance criteria, and sprint plans.

Community
Intermediate
ConnectiveTCSConnectiveTCS

sprint-planner

Plan sprints with story estimation, capacity planning, and goal definition.

Community
Intermediate
wtthorntonwtthornton
4

planner

Creates user stories, epics, and tasks with Fibonacci point estimates.

Community
Advanced