gds-create-epics-and-stories

Transform GDD requirements into epics, stories, and FR coverage maps.

Updated Nov 6, 2025
One-click install
npx skills add https://github.com/skyoxu/godotgame --skill gds-create-epics-and-stories-skyoxu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-create-epics-and-stories
Source: https://github.com/skyoxu/godotgame/tree/main/.agents/skills/gds-create-epics-and-stories
Command: npx skills add https://github.com/skyoxu/godotgame --skill gds-create-epics-and-stories-skyoxu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translating expansive GDDs and architecture decisions into a clear, executable plan of epics and stories that teams can implement and verify.

Core Features & Use Cases

  • Requirement decomposition: Convert GDD FRs/NFRs and architecture notes into user-focused epics and actionable stories.
  • Validation & mapping: Produce a FR-to-epic coverage map to ensure no requirement is missed.
  • Collaborative workflow: Support workflow steps for activation, design approval, and final validation with user input.
  • Use Case: A product owner asks the skill to break down a new game feature into epics and stories with acceptance criteria ready for sprint planning.

Quick Start

Provide your GDD documents and planning artifacts and ask the skill to generate epics and stories.

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 GDD requirements into agile epics and stories?

To turn GDD requirements into agile epics and stories, you provide your game design document and architecture notes to generate user-focused epics, actionable stories, and acceptance criteria ready for sprint planning.

What is the best way to decompose game architecture requirements into actionable stories?

Decomposing game architecture requirements into actionable stories involves mapping functional requirements to epics and generating structured story templates that preserve validation dependencies for development teams.

Can I generate a coverage map for functional requirements mapped to epics?

Yes, you can generate a FR-to-epic coverage map that validates every functional requirement from your GDD is matched to an epic, ensuring no requirement is missed during decomposition.

How do I write acceptance criteria for game development stories from a GDD?

Writing acceptance criteria for game development stories from a GDD requires translating architecture decisions and non-functional requirements into structured story templates with built-in validation checkpoints.

Does this approach support collaborative workflow steps for design approval and validation?

Yes, the decomposition process supports collaborative workflow steps by requiring user input for activation, design approval, and final validation before producing the approved epics list.

What limitations exist when mapping non-functional requirements to epics?

A key constraint when mapping non-functional requirements to epics is preserving original validation rules and dependencies; any unmapped NFR indicates incomplete coverage in the generated epics list.