What problem does it solve?
Game developers and designers often have unstructured feature ideas, one-liners, or rough drafts but lack a standardized process to convert them into formal, player-focused game design documents, leading to misalignment between design intent and technical implementation.
Core Features & Use Cases
- Structured Design Doc Generation: Converts rough inputs (one-liners, feature discussions, rough drafts) into complete, formatted game design documents ready for the technical planning phase.
- Player-First Language Enforcement: Automatically filters out implementation jargon (like class names, component terms, or system references) to ensure all content is written in player-facing language.
- Built-in Validation & Review: Includes mandatory self-review, post-design review, and contradiction checks to catch gaps and inconsistencies before handoff to engineering teams.
- Use Case: A developer with a rough idea for a "crew hunger and fatigue" system can input their one-liner and get a full, vetted design document ready for the /qq:plan pipeline without manual formatting or jargon cleanup.
Quick Start
Use the design skill to turn your one-liner game feature idea into a structured, player-focused design document ready for the technical planning phase.