create-gdd

Generate a structured Game Design Document from a game brief.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/igot-ai/os-twin --skill create-gdd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-gdd
Source: https://github.com/igot-ai/os-twin/tree/main/.agents/skills/roles/game-designer/create-gdd
Command: npx skills add https://github.com/igot-ai/os-twin --skill create-gdd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating a high-quality Game Design Document from a game brief is often manual, time-consuming, and prone to inconsistency across sections. This workflow automates extracting pillars from the brief, scaffolding the standard GDD structure, and aligning all sections to the defined pillars for a cohesive design document.

Core Features & Use Cases

  • Prerequisite loading and pillar extraction: Reads project context and the game brief to determine pillars.
  • GDD scaffolding: Generates sections for Game Overview, Core Mechanics, Game Modes & Progression, UI/UX, Monetization, Audio & Visual Direction, and Technical Requirements.
  • Pillar-driven design: Maps mechanics and sections to defined pillars, ensuring alignment throughout the document.
  • Output generation: Writes the final GDD to .output/design/gdd.md and supports iterative refinement.

Quick Start

Provide a game brief or ensure .output/design/game-brief.md exists, then run the GDD workflow to generate .output/design/gdd.md.

Frequently Asked Questions about create-gdd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a Game Design Document from a brief automatically?

Generating a Game Design Document from a brief involves reading your project context, extracting core pillars, and scaffolding sections like mechanics and progression. This process maps game mechanics to defined pillars and outputs the structured document to gdd.md.

What sections should a complete Game Design Document include?

A complete Game Design Document should include Game Overview, Core Mechanics, Game Modes & Progression, UI/UX, Monetization, Audio & Visual Direction, and Technical Requirements. These sections ensure comprehensive coverage of game design pillars.

How do I keep my game design pillars aligned with core mechanics?

To keep game design pillars aligned with core mechanics, use a pillar-driven design approach. This extracts pillars from your game brief and explicitly maps mechanics and subsequent GDD sections to them, ensuring cohesive alignment throughout the document.

Do I need an existing game brief to start writing a GDD?

Yes, you need an existing game brief to start writing a GDD. The workflow requires loading prerequisites from project context or a game-brief.md file to extract pillars and scaffold the remaining Game Design Document sections.

Can I iteratively refine a Game Design Document after generation?

Yes, you can iteratively refine a Game Design Document after generation. After writing the initial GDD to the output directory, the workflow supports iterative refinement to continuously adjust mechanics, progression, and technical constraints.