gds-create-epics-and-stories

Consolidate GDD, architecture, and UX inputs into structured epics and stories.

1|Updated Aug 3, 2025

Search Tags:#planning #requirements #epics #agile #stories #product-management #gdd

Ready to run

npx skills add https://github.com/MazenMrad/Obsidio --skill gds-create-epics-and-stories

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams transform scattered GDD, architecture notes, and UX considerations into a coherent set of epics and stories ready for planning and development.

Core Features & Use Cases

Epics driven by user value, each standalone and capable of enabling future epics
Requirements mapping and FR coverage to ensure every FR is traced to an epic
Collaborative review and explicit approval workflow to finalize epics before creating stories
Template-driven documentation that enforces structure and consistency across epics and stories
Integration of UX requirements (UX-DRs) into epics where applicable for comprehensive planning

Quick Start

Provide the GDD and architecture notes, and I will generate an approved epics-and-stories blueprint.

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 requirements into actionable epics and stories?▼

To turn game design requirements into actionable epics, consolidate your GDD, architecture notes, and UX inputs. This process maps functional requirements to standalone epics and details story-level acceptance criteria for development planning.

What is the best way to map functional requirements to epics in agile game development?▼

The best way to map functional requirements to epics is using a structured template that ensures FR coverage and traceability. Each epic remains standalone, value-driven, and integrates UX requirements where applicable.

Do I need a complete Game Design Document to generate agile stories for my project?▼

You need GDD and architecture notes to generate agile stories effectively. The Skill consolidates these inputs with UX considerations to create a structured set of epics and stories ready for planning.

How does the epic approval workflow work before creating user stories?▼

The epic approval workflow requires collaborative review to finalize epics before creating stories. This ensures epics driven by user value are explicitly approved, maintaining structure and consistency before story-level detailing begins.

Can I integrate UX requirements into epics for comprehensive game planning?▼

Yes, you can integrate UX requirements into epics for comprehensive game planning. The consolidation process incorporates UX-DRs directly into applicable epics alongside architecture and GDD inputs.

Why are my agile epics lacking clear acceptance criteria and traceability?▼

Agile epics lack clear acceptance criteria and traceability when requirements are not explicitly mapped. Using template-driven documentation enforces structure, ensuring every FR is traced to an epic with detailed story-level acceptance criteria.