gds-create-epics-and-stories

Break down Game Design Document requirements into user-centric epics and stories.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and templates (resource) and steps (resource) components.

What problem does it solve?

This Skill streamlines the creation of game epics and stories from Game Design Documentation (GDD), enabling game developers to generate high-quality, well-organized planning artifacts efficiently.

Core Features & Use Cases

  • GDD to Epics and Stories: Transform game requirements into user-value-focused epics and detailed stories.
  • Automated Planning: Automated document generation based on step-by-step guidelines and templates.
  • Use Case: Ideal for developers who need to break down GDD into actionable development tasks.

Quick Start

Use the 'gds-create-epics-and-stories' skill to generate epic and story plans for your next game project based on the GDD file you provide.

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 break down a Game Design Document into epics and stories?

To break down a Game Design Document (GDD) into epics and stories, you can use predefined workflows that parse structured requirements and automatically generate user-centric planning artifacts step by step.

What is the best way to automate game development planning from a GDD?

The best way to automate game development planning from a GDD is using step-based document generation workflows that transform game requirements directly into actionable epics and detailed stories.

Can I generate user-centric game stories directly from my design documentation?

Yes, you can generate user-centric game stories directly from design documentation by applying predefined templates that extract game requirements and structure them into detailed development tasks.

Does automated epic creation work without a structured Game Design Document?

Automated epic creation requires a structured Game Design Document because the parsing workflows depend on extracting specific game requirements to generate well-organized planning artifacts.

When do I need to use templates for generating game epics?

You need to use templates for generating game epics when you want to ensure your planning artifacts remain user-value-focused and consistently structured across the entire game development workflow.