gds-create-epics-and-stories

Generates epics and user stories with acceptance criteria from GDD and architecture documents.

Updated May 7, 2026

Search Tags:#planning #game development #requirements #acceptance criteria #epics #user stories #gdd

Ready to run

npx skills add https://github.com/jgabriellima/deep-agent-skill --skill gds-create-epics-and-stories-jgabriellima

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gds-create-epics-and-stories
Source: https://github.com/jgabriellima/deep-agent-skill/tree/main/skills/gds-create-epics-and-stories
Command: npx skills add https://github.com/jgabriellima/deep-agent-skill --skill gds-create-epics-and-stories-jgabriellima

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Game development teams struggle to translate Game Design Documents (GDDs) and architecture decisions into actionable, developer-ready work items. This Skill decomposes GDD requirements into epics and stories with complete acceptance criteria, ensuring no requirement is missed. ## Core Features & Use Cases - Requirements Extraction: Systematically extracts functional requirements (FRs), non-functional requirements (NFRs), architecture constraints, and UX design requirements from planning documents. - User-Value Epic Design: Organizes requirements into standalone epics focused on player value rather than technical layers, with a full FR coverage map. - Story Generation with Acceptance Criteria: Produces stories in Given/When/Then format, sized for a single dev agent, with no forward dependencies. - Use Case: After finishing a GDD and architecture document for a multiplayer game, run this Skill to produce a complete epics.md with stories covering authentication, gameplay, and progression, ready for sprint planning. ## Quick Start Ask the agent to create epics and stories from my GDD and architecture documents.

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, and optional UX design documents, then activate the workflow. It extracts all functional and non-functional requirements, proposes a user-value-focused epic structure for your approval, and generates stories with testable acceptance criteria.

What input documents does this epic creation workflow require?▼

It requires a GDD document and an architecture document, found in the planning artifacts folder as whole files or sharded folders with an index.md. A UX design document is optional but treated as a first-class input when present.

How are acceptance criteria formatted in the generated stories?▼

Each story uses the Given/When/Then format with independently testable criteria, including edge cases and error conditions. Stories follow the As a / I want / So that user story structure and reference the specific FRs they implement.

Can stories depend on future stories within the same epic?▼

No. The workflow enforces a strict dependency rule: each story must be completable using only outputs from previous stories, and each epic must deliver standalone functionality without requiring future epics.

Does the workflow validate that all requirements are covered?▼

Yes. The final validation step checks every FR against the generated stories, verifies architecture compliance such as starter template setup, and confirms epics deliver user value rather than technical milestones.