game-design-doc

Generate quick design specs for small game changes with acceptance criteria.

Updated Jul 22, 2025
One-click install
npx skills add https://github.com/MichaelSolati/mkai --skill game-design-doc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: game-design-doc
Source: https://github.com/MichaelSolati/mkai/tree/main/profiles/game-dev/skills/game-design-doc
Command: npx skills add https://github.com/MichaelSolati/mkai --skill game-design-doc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing full Game Design Documents (GDDs) for small, low-risk changes like balance tweaks or minor mechanic adjustments wastes valuable development time. This skill removes that overhead by providing a fast, structured workflow to create concise, actionable design specs for small changes in minutes.

Core Features & Use Cases

  • Intelligent Change Classification: Automatically categorizes changes into tuning, tweaks, additions, or new small systems to apply the correct spec template and avoid over-documentation.
  • Context-Aware Drafting: Scans existing GDDs and prior quick specs to ensure new specs align with established game systems and avoid contradictions.
  • Structured, Implementation-Ready Output: Generates formatted quick design specs with clear change rationale, testable acceptance criteria, and GDD cross-references for seamless handoff to development teams.
  • Real-World Use Case: For example, if you want to increase a character's jump height by 1 unit to improve platforming feel, this skill will generate a complete spec with old/new values, rationale, and test criteria without requiring a full GDD rewrite.

Quick Start

Use the game-design-doc skill to create a quick design spec for increasing the player's jump height by 1 unit.

Frequently Asked Questions about game-design-doc

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

FAQPage Schema
How do I document minor game design changes without writing a full GDD?

You can document minor game design changes without a full GDD by generating a lightweight quick spec that captures change rationale, testable acceptance criteria, and GDD cross-references for seamless implementation handoff.

What is a quick design spec used for in game development?

A quick design spec is used for low-risk game development changes like balance tuning, minor mechanic tweaks, or small system additions with implementation timelines under one week, avoiding unnecessary documentation overhead.

How do I create a balance tuning spec for a small mechanic tweak?

Create a balance tuning spec for a small mechanic tweak by categorizing the change, scanning existing GDDs for context, and outputting a structured spec with old/new values, rationale, and testable acceptance criteria.

Can I use quick specs for new micro-features instead of updating the full game design document?

Yes, you can use quick specs for standalone micro-features and small system additions instead of updating the full game design document, provided the implementation timeline remains under one week.

When should I avoid using lightweight design specs and write a full GDD instead?

You should avoid lightweight design specs and write a full GDD when changes exceed a one-week implementation timeline, involve high-risk core systems, or require comprehensive documentation beyond balance tuning and minor mechanic tweaks.