gdd-writer

Generate and maintain lean Game Design Documents for solo development projects.

3|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/gavinmcfall/agentic-config --skill gdd-writer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gdd-writer
Source: https://github.com/gavinmcfall/agentic-config/tree/main/config/skills/game-dev/gdd-writer
Command: npx skills add https://github.com/gavinmcfall/agentic-config --skill gdd-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps solo game developers create and maintain Game Design Documents (GDDs) that serve as a lean, living memory of their project, evolving with development rather than becoming outdated.

Core Features & Use Cases

  • Phased GDD Approach: Guides users through creating a Minimum Viable GDD before prototyping and expanding it afterward.
  • Design Pillar Integration: Emphasizes defining core feelings and experiences, not just features, to guide decisions.
  • Use Case: When starting a new indie game project, use this Skill to quickly draft a Vision Statement, Design Pillars, Core Loop, and Scope Definition before writing any code. Later, after a prototype confirms the core mechanics, expand the GDD with detailed Player Mechanics and Content Structure.

Quick Start

Use the gdd-writer skill to help me write the Vision Statement for my new game.

Frequently Asked Questions about gdd-writer

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

FAQPage Schema
How do I write a Game Design Document for a solo indie game project?

To write a Game Design Document for a solo project, start with a Minimum Viable GDD focusing on a Vision Statement, Design Pillars, Core Loop, and Scope Definition before prototyping. This keeps the document lean and acts as a memory aid rather than a rigid plan.

What is a lean Game Design Document and why use it for game development?

A lean Game Design Document is a living memory aid that evolves with your development progress. It prevents scope creep by enforcing length constraints and defining only what is necessary, ensuring the documentation stays relevant rather than becoming outdated.

When should I update my Game Design Document during game development?

You should update your Game Design Document after your prototype confirms core mechanics. This phased approach expands the initial pre-prototype hypothesis into a post-prototype plan by adding detailed Player Mechanics and Content Structure based on development evidence.

How do I prevent scope creep when defining game design pillars?

Prevent scope creep by defining specific Design Pillars and enforcing constraints on your Game Design Document length and content. Focus on core feelings and experiences alongside a strict Scope Definition to guide decisions without overloading the project with features.