gds-create-epics-and-stories

Transform GDD requirements into structured epics and stories with acceptance criteria.

Updated Dec 23, 2025
One-click install
npx skills add https://github.com/joekhosbayar/go-mighty --skill gds-create-epics-and-stories-joekhosbayar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-create-epics-and-stories
Source: https://github.com/joekhosbayar/go-mighty/tree/main/.gemini/skills/gds-create-epics-and-stories
Command: npx skills add https://github.com/joekhosbayar/go-mighty --skill gds-create-epics-and-stories-joekhosbayar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams convert GDD requirements into a clear, executable plan by generating epics and stories with aligned acceptance criteria, FR/NFR mappings, and an approval-ready structure.

Core Features & Use Cases

  • Transforms GDD requirements into an organized epic and story hierarchy aligned with user value.
  • Generates a complete FR/NFR mapping, epic list, and detailed stories with acceptance criteria per epic.
  • Supports collaborative approval workflows with templates and step-by-step execution guidance.

Quick Start

Provide the GDD input and let the workflow generate the full epics-and-stories document using the approved templates.

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 turn game design documents into agile epics and stories?

To turn game design documents (GDDs) into agile epics and stories, provide the GDD input to generate a structured hierarchy with aligned acceptance criteria, functional requirement mappings, and an approval-ready format.

What is the best way to map functional and non-functional requirements to user stories?

Mapping functional and non-functional requirements to user stories involves extracting GDD constraints and organizing them into an epic list, then generating detailed stories with aligned acceptance criteria per epic.

Can I use this for cross-functional product design initiatives outside of game development?

Yes, you can use this for cross-functional product design initiatives. It transforms broad requirements into structured epics and stories suitable for any agile planning scenario requiring clear traceability.

How do I set up a collaborative approval workflow for generated agile stories?

Setting up a collaborative approval workflow for agile stories uses provided templates and step-by-step execution guidance to review the generated FR/NFR mappings and acceptance criteria before finalizing documentation.

Do I need to manually format the epic and story hierarchy outputs?

No, you do not need to manually format the epic and story hierarchy. Providing the GDD input automatically generates the complete epics-and-stories document using approved documentation templates.