skills.rest
elsolal
elsolalCOMMUNITY
Explore all skills by this author →
GitHub

pm-stories

Convert PRD and architecture files into Epics and User Stories for GitHub.

1|Updated Jan 20, 2026
Search Tags:#architecture#GitHub#epics#PRD#user stories#issues#INVEST
One-click install
npx skills add https://github.com/elsolal/Skillz-Claude --skill pm-stories
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pm-stories
Source: https://github.com/elsolal/Skillz-Claude/tree/main/.claude/skills/pm-stories
Command: npx skills add https://github.com/elsolal/Skillz-Claude --skill pm-stories

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams transform a PRD and Architecture into clearly defined Epics and User Stories, ready for GitHub publication and aligned with INVEST principles.

Core Features & Use Cases

  • PRD-to-Epics/Stories: generate structured Epics and user stories from product requirements.
  • Architecture alignment: ensure stories reflect architectural decisions and dependencies.
  • Readiness & Publication: perform an Implementation Readiness Check before creating GitHub issues and linking stories to Epics.

Quick Start

Load the PRD and Architecture, then request Epics and Stories for GitHub publication. For example, say "generate stories for Epic 1" or "publish Epics and Stories to GitHub after readiness."

Frequently Asked Questions about pm-stories

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

FAQPage Schema
How do I convert a PRD into GitHub issues and epics?▼

INVEST criteria are enforced during story generation to ensure each user story is Independent, Negotiable, Valuable, Estimable, Small, and Testable. This validation happens before publication to GitHub, preventing poorly defined issues from entering your backlog.

How do I generate user stories from a product requirements document?▼

An Implementation Readiness Check evaluates your generated epics and user stories before they are published to GitHub. This validation step ensures all stories meet quality criteria and are properly linked to their parent epics before issue creation.

Do I need architecture documentation to generate user stories from a PRD?▼

FULL mode generates and publishes all epics and stories to GitHub after passing readiness checks, while LIGHT mode provides a streamlined generation process. Both modes enforce INVEST criteria and link stories to their parent epics during GitHub publication.

What is the best way to structure epics and user stories for GitHub?▼

Yes, generated stories are automatically linked to their parent epics when published to GitHub. The system creates the epic issues first, then publishes the child stories and establishes the linking relationship within GitHub issues.

Related Skills

Explore More Product & Management Skills→
robotics-playgroundrobotics-playground

bmad-create-epics-and-stories

Decompose PRD, Architecture, and UX documents into epics and stories.

Official
Advanced
diegosanchespereira1diegosanchespereira1

bmad-sprint-status

Summarize sprint status and recommend the next BMad workflow action.

Community
Advanced
shysssthanhtrishysssthanhtri

breakdown-plan

Generate GitHub project plans and issue checklists from product artifacts.

Community
Advanced
co-cddoco-cddo
4

bmad-create-epics-and-stories

Decompose product requirements into epics and stories with acceptance criteria.

Official
Advanced