Convert game design documents into structured epics and stories.
npx skills add https://github.com/igot-ai/os-twin --skill create-epics-igot-ai
Please help me install this Agent Skill. Skill: create-epics Source: https://github.com/igot-ai/os-twin/tree/main/.agents/skills/roles/game-designer/create-epics Command: npx skills add https://github.com/igot-ai/os-twin --skill create-epics-igot-ai
It converts a game's design document into structured epics and user stories that engineers can implement, ensuring alignment between design goals and development tasks.
Provide your GDD path (for example gdd.md) and run the create-epics skill to generate epics and stories.
High-intent search queries and answers about installing and using this skill.
To convert a game design document into actionable epics and stories, provide your GDD file path and run the skill to generate structured outputs. It transforms design artifacts like gdd.md into prioritized epics with clear dependencies, acceptance criteria, and a recommended sprint plan.
Generating agile sprint plans from a GDD involves parsing design requirements and grouping them into coherent development goals. This process outputs a structured markdown file containing epic definitions, sized user stories with acceptance criteria, and a recommended sprint schedule traceable to input artifacts.
Yes, epic generation works with game-brief.md files alongside other GDD artifacts. It processes these input documents to extract requirements, then outputs structured epics and actionable stories to the .output/planning/epics-and-stories.md file for engineering teams.
Yes, you can trace generated user stories back to specific game design requirements. The skill preserves traceability to input design artifacts, ensuring every generated epic and story maintains a clear link back to the original GDD sections for alignment verification.
Structuring game development requirements into epics with dependencies and size estimates requires parsing your GDD sections into coherent goals. The skill automates this by generating stories with acceptance criteria, dependency mapping, and sizing, outputting a complete prioritized backlog.
A key limitation when transforming a game design document into engineering tasks is the reliance on well-structured input artifacts like gdd.md. Without clearly defined requirements in the source GDD, the accuracy of generated dependency mapping, size estimates, and sprint plans may vary.
jfrometaStructure a Game Design Document with Pitch, Core Loop, Mechanics, Progression, Art Style, and Audio.
AcidicSoilBreak down epics into stories with estimates, dependencies, and sprint plans.
ConnectiveTCSPlan sprints with story estimation, capacity planning, and goal definition.
emcconnellBreak epics into traceable story markdown files with QA test cases.
