Game PRD Builder

A skill for turning game concepts, prototypes, and brainstorm notes into production-ready PRDs for video games.

What It Solves

Generic PRD workflows often fail on game projects in predictable ways:

• They describe the game like a software product instead of a playable system.
• They keep mechanics at the fantasy layer and skip triggers, state, resolution, and tuning knobs.
• They blur immutable core rules with optional expansion systems.
• They omit replayability, build identity, balance risks, and MVP boundaries.

game-prd-builder is designed to prevent those failures.

Best Fit

Use this skill when you need to turn any of the following into a complete game PRD:

• a rough game idea
• a brainstorm session
• a prototype ruleset
• a pitch with partial mechanics
• an existing design doc that is too vague to implement

It works best for systemic games such as roguelikes, deckbuilders, board-builders, auto-battlers, strategy games, and other content-scalable designs.

Core Principles

• Preserve the user's non-negotiable gameplay foundation.
• Translate mechanics into codeable systems.
• Separate immutable rules from expandable systems.
• Write MVP scope before long-term expansion.
• Document balance risks and unwinnable states explicitly.
• Favor system interactions over disconnected feature lists.

Skill Structure

• SKILL.md: main skill instructions and trigger conditions.
• agents/openai.yaml: UI metadata.
• references/prd-template.md: game-specific PRD structure.
• references/design-checklist.md: final review checklist.
• examples/example-prompts.md: example prompts for real usage.
• testing/red-baseline.json: baseline failure modes this skill is meant to address.
• README.zh-CN.md: Chinese documentation for distribution.

Example Prompt

Use $game-prd-builder to turn this roguelike board-building concept into a full PRD without changing the immutable core loop.

Output Expectations

A good result should:

• define the core loop and run structure clearly
• preserve fixed rules stated by the designer
• specify major systems in implementable terms
• include progression, difficulty, replayability, and expansion hooks where relevant
• flag balance risks, dominant strategies, and dead-state risks
• separate MVP from future scope

Recommended Publish Targets

• GitHub: best default choice for source distribution, versioning, issues, and discoverability.
• MCP Market or similar skill directories: useful after GitHub, once the repository is stable and documented.
• Personal site or design blog: useful only as a secondary mirror or showcase.

Minimal Release Checklist

• Ensure SKILL.md is final.
• Keep the English skill files concise and ASCII-safe where possible.
• Include this README and the Chinese documentation.
• Validate the skill folder before release.
• Add a license before publishing publicly.
• Include at least 3 to 5 example prompts.