pm-user-story

Convert PRD requirements into user stories with BDD acceptance criteria.

46|8|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/konglong87/superPM --skill pm-user-story
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-user-story
Source: https://github.com/konglong87/superPM/tree/main/skills/02-solution-design/pm-user-story
Command: npx skills add https://github.com/konglong87/superPM --skill pm-user-story

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps product teams transform PRD-level requirements into actionable user stories and BDD-style验收标准, reducing ambiguity before sprint planning and development.

Core Features & Use Cases

  • Requirement-to-Story conversion: Converts a defined scope (Epic/module/function) into user stories with role, goal, value, and structured acceptance criteria.
  • Epic-based workflow with optional parallelism: Identifies Epic boundaries, then generates Story content and acceptance criteria, using subagents for larger story sets.
  • Planning-ready output: Produces a complete user story list document (including Epic overview, Story list, dependency/relationship guidance, and sprint suggestions) suitable for agile execution.

Quick Start

Ask the skill to write user stories by selecting an appropriate story scope for your PRD, then request it to generate the user story list and BDD acceptance criteria.

Frequently Asked Questions about pm-user-story

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

FAQPage Schema
How do I convert PRD requirements into user stories and BDD acceptance criteria?

Epic-based user story generation works by identifying Epic boundaries first, then creating individual stories with roles, goals, and values. For large story sets, it supports parallel Agent generation to produce the content and BDD acceptance criteria efficiently.

Do I need a complete PRD to generate agile user stories?

You need defined PRD inputs to generate agile user stories. The workflow checks for required PRD inputs before scoping the Epic, ensuring the source material has enough detail to produce actionable stories and structured BDD acceptance criteria for sprint planning.

What is the best way to split a large Epic into sprint-ready user stories?

The best way to split a large Epic into sprint-ready user stories is using an Epic-first workflow with interactive scoping. It identifies boundaries, generates and splits stories, and supports parallel Agent generation for large sets to produce a prioritized output list.

What format does the generated user story list document use?

The generated user story list document uses a docs/ template format. It includes an Epic overview, the Story list, dependency and relationship guidance, and sprint suggestions, providing a complete agile execution output with BDD acceptance criteria.

Why use BDD format for agile acceptance criteria in user stories?

BDD format structures agile acceptance criteria to reduce ambiguity before development. It aligns story validation with expected behaviors, ensuring the generated user stories from your PRD are sprint-ready and clearly understood by the agile team.