skills.rest
NexusSema
NexusSemaOFFICIAL
Explore all skills by this author →
GitHub

epics/create

Maps PRD and Architecture functional requirements to epics and stories.

5|3|Updated Mar 4, 2026
Search Tags:#planning#requirements#epics#agile#nfr#story-writing#fr
One-click install
npx skills add https://github.com/NexusSema/omg-marketplace --skill epics-create
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: epics/create
Source: https://github.com/NexusSema/omg-marketplace/tree/main/plugins/sdlc/skills/epics/create
Command: npx skills add https://github.com/NexusSema/omg-marketplace --skill epics-create

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams transform scattered requirements into organized, value-focused epics and actionable stories that align with product strategy and stakeholder goals.

Core Features & Use Cases

  • Design and validate an epic structure that maps FRs/NFRs to user outcomes.
  • Generate a requirements coverage map to ensure every requirement is addressed.
  • Collaborate with stakeholders to approve epic structures before proceeding to story creation.

Quick Start

Provide the project documents (PRD, Architecture, UX) and approve the epics design to begin.

Frequently Asked Questions about epics/create

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

FAQPage Schema
How do I turn PRD and architecture requirements into ready epics and stories?▼

To turn PRD and architecture requirements into epics and stories, provide your project documents for analysis. The system maps functional and non-functional requirements to user outcomes, generating a structured epic and story plan ready for stakeholder approval.

What's the best way to map functional and non-functional requirements to agile epics?▼

Mapping functional and non-functional requirements to agile epics involves generating a coverage map that tracks every requirement to a specific user outcome. This ensures complete FR and NFR coverage while articulating how each epic delivers value.

How do I ensure complete requirements coverage when writing agile epics?▼

Ensure complete requirements coverage during epic creation by generating a dedicated coverage map. This validates that every functional and non-functional requirement from your PRD and architecture documents is explicitly addressed within the epic and story structure.

Can I review and approve epic structures before generating individual user stories?▼

Yes, you can review and approve epic structures before story creation. The process provides a structured plan for epic design that stakeholders validate first, ensuring the mapped requirements align with product strategy before proceeding to story execution.

How do I articulate user value when designing epics from scattered requirements?▼

Articulate user value by mapping each requirement to a specific user outcome during the epic design phase. This transforms scattered specifications into organized, value-focused epics that clearly demonstrate how they deliver value to stakeholders and product strategy.

Related Skills

Explore More Product & Management Skills→
ncptuanncptuan

bmad-check-implementation-readiness

Audit PRD, architecture, UX, and epics for implementation readiness.

Community
Advanced
Yukine5377Yukine5377

bmad-sprint-planning

Convert epic and story details into a structured sprint-status.yaml.

Community
Intermediate
alex-tgkalex-tgk

agile-product-owner

Generate INVEST-compliant user stories with acceptance criteria from epics.

Community
Intermediate
co-cddoco-cddo
4

bmad-create-epics-and-stories

Decompose product requirements into epics and stories with acceptance criteria.

Official
Advanced