skills.rest
HordRicJr
HordRicJrCOMMUNITY
Explore all skills by this author →
GitHub

gds-create-epics-and-stories

Create epics and stories from GDD requirements for game development planning.

6|Updated Aug 29, 2026
Search Tags:#planning#game development#requirements#acceptance criteria#epics#user stories#gdd
One-click install
npx skills add https://github.com/HordRicJr/Akomagni --skill gds-create-epics-and-stories-hordricjr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gds-create-epics-and-stories
Source: https://github.com/HordRicJr/Akomagni/tree/main/bmad-core/.agents/skills/gds-create-epics-and-stories
Command: npx skills add https://github.com/HordRicJr/Akomagni --skill gds-create-epics-and-stories-hordricjr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Game development teams struggle to translate Game Design Document (GDD) requirements, architecture decisions, and UX specifications into actionable, developer-ready work items. This Skill decomposes those planning documents into user-value-focused epics and stories with complete acceptance criteria. ## Core Features & Use Cases - Requirements Extraction: Validates and extracts functional requirements (FRs), non-functional requirements (NFRs), architecture constraints, and UX design requirements from planning documents. - Epic Design: Organizes requirements into standalone, user-value-focused epics with a full FR coverage map, avoiding technical-layer groupings and file-churn anti-patterns. - Story Generation: Produces stories in As a/I want/So that format with Given/When/Then acceptance criteria, sized for a single dev agent and free of forward dependencies. - Use Case: After finishing a GDD and architecture document for a new game, run this workflow to produce a complete epics.md breakdown ready for sprint planning and implementation. ## Quick Start Ask the AI to create epics and stories from your GDD and architecture documents in the planning artifacts folder.

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

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

FAQPage Schema
How do I create epics and stories from a game design document?▼

Provide your GDD, architecture document, and optional UX design spec in the planning artifacts folder, then activate the workflow. It extracts all FRs and NFRs, proposes a user-value-focused epic structure for approval, and generates stories with Given/When/Then acceptance criteria.

What documents are required before creating epics and stories?▼

The workflow requires a GDD containing functional and non-functional requirements, plus an architecture document with technical decisions. A UX design specification is optional but treated as a first-class input when present, with its requirements extracted as separate UX-DRs.

How are stories sized for development agents?▼

Each story must be completable by a single dev agent and can only depend on previously completed stories, never future ones. Database tables and entities are created only when a story needs them, not upfront in bulk.

Can epics be organized by technical layers like database or API?▼

No. The workflow explicitly forbids organizing epics by technical layers such as database setup or API development. Epics must deliver standalone user value, and epics that repeatedly modify the same core files are consolidated into one epic with ordered stories.

What happens if requirements coverage is incomplete?▼

The final validation step checks that every FR maps to at least one story, verifies story dependency ordering, and confirms architecture compliance. The workflow does not complete until all validations pass and the user approves the output.

Related Skills

Explore More Product & Management Skills→
co-cddoco-cddo

System Architect

Design system architectures across monolith, modular monolith, microservices, or serverless patterns with technology selection and NFR mapping.

Official
Basic
bmad-code-orgbmad-code-org
52.5k

bmad-create-story

Generates comprehensive developer story files from epics, architecture, and sprint status artifacts.

Official
Advanced
abhilash-nandkumarabhilash-nandkumar

user-story-fundamentals

Capture user requirements into structured user stories with acceptance criteria.

Community
Intermediate
fusebase-devfusebase-dev
6

requirements-specification

Drafts versioned requirement specifications with acceptance criteria and clarify questions.

Official
Advanced