game-gdd-author

Guides section-by-section authoring of game design documents with pillar validation and scope tiering.

Updated Aug 11, 2026
One-click install
npx skills add https://github.com/zerox-core/AI_Game --skill game-gdd-author-zerox-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: game-gdd-author
Source: https://github.com/zerox-core/AI_Game/tree/main/.continue/skills/game-gdd-author
Command: npx skills add https://github.com/zerox-core/AI_Game --skill game-gdd-author-zerox-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a game design document from a blank template is intimidating, and self-written GDDs often contain orphan features, internal contradictions, and unscoped ambition. This Skill turns GDD creation into a guided, Socratic workflow that asks the right questions, enforces design pillar alignment, and assigns scope tiers to every feature. ## Core Features & Use Cases - 10-Section Guided Process: Walks through elevator pitch and pillars, core loops, mechanics with MDA tagging, progression, economy, narrative, art, audio, and technical architecture in dependency order. - Pillar Validation & Contradiction Detection: Every feature must justify itself against established design pillars, and cross-section contradictions are flagged immediately. - Scope Tier Marking: Every mechanic and system receives a T1 (Must-Ship), T2 (Launch Target), or T3 (Post-Launch) tier to prevent scope creep. - Use Case: A solo developer with a validated game concept says "help me write my GDD" and is guided through each section with targeted questions, good/bad entry examples, and honest scope feedback. ## Quick Start Ask the assistant to help you write a game design document for your game concept, starting with your elevator pitch and three design pillars.

Frequently Asked Questions about game-gdd-author

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

FAQPage Schema
How do I write a game design document from scratch?

Start with an elevator pitch and three falsifiable design pillars, then define your 30-second, 5-minute, and 30-minute gameplay loops. This Skill guides you section by section with targeted questions, validating every feature against your pillars before moving on.

What sections should a game design document include?

This workflow covers 10 sections: elevator pitch and pillars, core loop, mechanics and systems, progression and meta, economy and resources, narrative and setting, art direction, audio direction, and technical architecture. Each section builds on the previous ones.

How do I prevent scope creep in my game design?

Assign every feature a scope tier: T1 (Must-Ship), T2 (Launch Target), or T3 (Post-Launch). The Skill requires a tier for every mechanic and gives honest feedback when a described project exceeds realistic team capacity.

What is MDA tagging in game design?

MDA tagging maps each mechanic to the aesthetic it serves: Sensation, Fantasy, Narrative, Challenge, Fellowship, Discovery, Expression, or Submission. The Skill requires every mechanic to identify its target aesthetic before it can be included in the GDD.

When should I not use this GDD authoring workflow?

Do not use it for reviewing an existing GDD (use a design review skill instead) or for designing individual game systems in depth. It is specifically for creating a new structured document from a concept.