skills.rest
serejaris
serejarisCOMMUNITY
Explore all skills by this author →
GitHub

pm-user-stories

Break Epics into INVEST-validated user stories with acceptance criteria and a Story Map.

215|26|Updated Dec 15, 2025
Search Tags:#epic breakdown#acceptance criteria#sprint planning#user stories#prd#invest#story map
One-click install
npx skills add https://github.com/serejaris/personal-corp-skills --skill pm-user-stories
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pm-user-stories
Source: https://github.com/serejaris/personal-corp-skills/tree/main/skills/pm-user-stories
Command: npx skills add https://github.com/serejaris/personal-corp-skills --skill pm-user-stories

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break Epics into INVEST-validated User Stories with acceptance criteria and a Story Map output to enable sprint-ready planning and modular delivery.

Core Features & Use Cases

  • Decompose Epics into discrete User Stories with Given-When-Then acceptance criteria.
  • Validate each Story against INVEST principles (Independent, Negotiable, Valuable, Estimable, Small, Testable).
  • Generate a Story Map and sprint planning guidance for MVP and subsequent sprints.
  • Provide a structured prompt and output layout that can be pasted into Jira, Linear, or GitHub Issues.

Quick Start

Break this Epic into user stories with INVEST validation and a Story Map.

Frequently Asked Questions about pm-user-stories

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

FAQPage Schema
How do I break epics into user stories for sprint planning?▼

To break epics into user stories for sprint planning, decompose them into discrete stories validated against INVEST principles, complete with Given-When-Then acceptance criteria and story point estimates. This yields a structured output ready for your backlog.

What is the INVEST validation method for user stories?▼

The INVEST validation method for user stories ensures each item is Independent, Negotiable, Valuable, Estimable, Small, and Testable. Validating user stories against these criteria guarantees modular delivery and sprint readiness.

Can I generate a story map and acceptance criteria from a PRD?▼

Yes, you can generate a story map and acceptance criteria from a PRD. Inputting your PRD or Epic produces a structured Story Map alongside user stories featuring Given-When-Then acceptance criteria for MVP and subsequent sprints.

Does the generated user story output work with Jira, Linear, or GitHub Issues?▼

Yes, the generated user story output works with Jira, Linear, or GitHub Issues. It provides a structured layout specifically designed to be pasted directly into these platforms for sprint execution.

How do I write Given-When-Then acceptance criteria for an epic breakdown?▼

To write Given-When-Then acceptance criteria during an epic breakdown, decompose the epic into discrete user stories and format each story's conditions as Given [context], When [action], Then [result]. This ensures every story remains testable.

Related Skills

Explore More Product & Management Skills→
ArtemioPadillaArtemioPadilla
3

feature-spec

Generate tiered feature specifications with INVEST-compliant user stories.

Community
Advanced
jtucker9jtucker9

user-story-generator

Generate prioritized user stories with acceptance criteria, story points, and epic groupings.

Community
Intermediate
grandcamelgrandcamel
42

jira-agile-management

Manage Jira Agile workflows for epics, sprints, backlogs, and story points.

Community
Intermediate
AbsolutelySkilledAbsolutelySkilled
207

user-stories

Generate user stories and acceptance criteria using INVEST and Given/When/Then templates.

Official
Advanced