quick-design

To write a design spec for small game tweaks, you need a lightweight specification document that classifies changes into tuning, tweaks, additions, or new small systems. This generates a markdown quick-design spec file with tables, acceptance criteria, and optional GDD update prompts.

You need a quick design specification when handling minor game tweaks, tuning adjustments, or new small systems that require under a week of implementation. It prevents delays and inconsistencies caused by forcing full GDD creation for small scale changes.

You generate a markdown design spec by invoking the tool with a brief description of your change. It scans existing GDDs, system indexes, and quick specs for context, then drafts a complete markdown file with tables, acceptance criteria, and handoff instructions.

Quick design specs support minor game changes classified into four categories: tuning, tweaks, additions, and new small system adjustments. These changes must be scoped to require under a week of implementation.

Yes, the generated markdown quick-design spec includes appropriate sections, acceptance criteria, and optional GDD update prompts. It also handles file creation, naming, and handoff instructions for further validation.

No, this lightweight specification approach is explicitly designed for minor game tweaks and new small system adjustments requiring under a week of implementation. Major overhauls require a full Game Design Document instead.