skills.rest
DavidsonGomes
DavidsonGomesCOMMUNITY
Explore all skills by this author →
GitHub

evo-create-epics-and-stories

Structure product requirements into epics and user stories with acceptance criteria.

Updated Apr 6, 2026
Search Tags:#planning#requirements#epics#agile#synthesis#project-management#user-stories
One-click install
npx skills add https://github.com/DavidsonGomes/claude_cowork_workspace --skill evo-create-epics-and-stories
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: evo-create-epics-and-stories
Source: https://github.com/DavidsonGomes/claude_cowork_workspace/tree/main/.claude/skills/evo-create-epics-and-stories
Command: npx skills add https://github.com/DavidsonGomes/claude_cowork_workspace --skill evo-create-epics-and-stories

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform scattered product requirements into structured epics and user stories, reducing planning time and alignment errors.

Core Features & Use Cases

  • Automates the extraction and grouping of requirements into hierarchies of epics and associated stories with clear acceptance criteria.
  • Supports multiple scenarios, including feature upgrades, new capabilities, and maintenance work, with consistent governance.
  • Use Case: A product team provides a list of user needs; the skill outputs a prioritized backlog of epics and stories ready for grooming sessions.

Quick Start

Break the provided requirements into epics and user stories.

Frequently Asked Questions about evo-create-epics-and-stories

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

FAQPage Schema
How do I turn product requirements into epics and user stories?▼

To turn product requirements into epics and user stories, provide a list of user needs to be grouped into hierarchies of associated stories with clear acceptance criteria and estimates.

What is the best way to structure user stories with acceptance criteria for agile planning?▼

Structuring user stories with acceptance criteria requires decomposing gathered user needs across features and milestones, generating a prioritized backlog ready for agile grooming sessions.

Can I use this skill to break down feature upgrades and maintenance work into a backlog?▼

Yes, you can break down feature upgrades, new capabilities, and maintenance work into a backlog, applying consistent governance to synthesize requirements across multiple project scenarios.

How does automating epic and story synthesis reduce project planning time?▼

Automating epic and story synthesis reduces project planning time by transforming scattered product requirements into structured hierarchies, minimizing alignment errors during product planning sessions.

Does this approach generate estimates for the user stories it creates?▼

Yes, this approach generates estimates for the user stories it creates, outputting a fully prioritized backlog of epics and stories complete with acceptance criteria based on your requirements.

Related Skills

Explore More Product & Management Skills→
alexsandrocruzalexsandrocruz

requirements-engineering

Convert stakeholder needs into structured, testable specifications with templates.

Community
Basic
adolfoaranaes12adolfoaranaes12
2

breakdown-epic

Break down epics into user stories with acceptance criteria and sprint groupings.

Community
Advanced
imonmiimonmi

bmad-sprint-planning

Convert epics and stories into a sprint-status.yaml file.

Community
Intermediate
tikazyqtikazyq
5

user-story-format

Validate User Stories against the As-I-Want-So structure and quality criteria.

Community
Intermediate