design

Convert unstructured game feature ideas into player-focused design documents.

10|2|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/tykisgod/quick-question --skill design-tykisgod
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design
Source: https://github.com/tykisgod/quick-question/tree/main/skills/design
Command: npx skills add https://github.com/tykisgod/quick-question --skill design-tykisgod

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about design

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

FAQPage Schema
How do I turn rough game ideas into structured design documents?

To turn rough game ideas into structured design documents, you input unstructured feature one-liners or drafts to generate formal, player-focused feature documentation ready for technical planning and pre-implementation alignment.

How do I generate a game design document without implementation jargon?

Generating a game design document without implementation jargon requires enforcing player-first language, automatically filtering out class names, component terms, and system references to ensure the output remains player-facing.

Does this game design documentation workflow support Unity, Godot, and Unreal?

Yes, this game design documentation workflow supports Unity, Godot, Unreal, and S&box projects by standardizing feature documentation and passing pre-handoff validation checks for implementability.

How do I validate a game design document before handing it to engineering?

Validating a game design document before engineering handoff involves running mandatory self-reviews, post-design reviews, and contradiction checks to catch gaps and inconsistencies in the feature documentation.

What is the best way to flesh out a game concept for the qq pipeline?

The best way to flesh out a game concept for the qq pipeline is converting one-liner feature ideas into vetted, formatted design documents that satisfy pre-handoff validation checks without manual formatting.