What problem does it solve? Writing a full Game Design Document for every small change—like adjusting jump height or adding a parry window—wastes time, yet implementing changes with no written rationale causes confusion and contradictions. This Skill provides a middle path: a structured Quick Design Spec for changes too small for a full GDD but too meaningful to implement undocumented. ## Core Features & Use Cases - Change Classification: Categorizes requests as Tuning, Tweak, Addition, or New Small System, and redirects oversized changes to the full GDD pipeline. - Context Scanning: Reads existing GDDs, the systems index, and prior quick specs to avoid contradictions before drafting. - Tailored Spec Templates: Produces category-specific Markdown specs with tuning tables, design deltas, acceptance criteria, and GDD update flags, saved to design/quick-specs/. - Use Case: A designer wants to increase jump height from 5 to 6 units. The Skill classifies it as Tuning, checks the GDD's Tuning Knobs section, and writes a dated spec with old/new values, rationale, and testable acceptance criteria. ## Quick Start Use the quick-design skill to create a lightweight design spec for increasing enemy patrol speed by 10 percent.
