quick-design

To write a design spec for small game changes without a full GDD, you can generate a lightweight quick spec that includes acceptance criteria and approval-gated update instructions. This prevents small tweaks from stalling behind heavyweight documentation.

You can classify game design changes into Tuning, Tweak, Addition, or New Small System categories to keep scope appropriate. This classification prevents runaway work by ensuring the spec targets the correct subsystem level.

You need a quick spec when handling tuning adjustments or small additions that are too meaningful for chat-only decisions but too small for full GDD authoring. It provides an implementation-ready rationale without heavyweight overhead.

You check existing GDD context by scanning relevant GDDs and prior quick specs before drafting a balance tuning spec. This context scanning reduces contradictions and ensures your changes target the right subsystem.

You generate acceptance criteria for small gameplay behavior changes by drafting a quick design spec that defines the expected outcomes. The spec is filed into the design quick-specs output path for implementation tracking.

The best way to document a new small system with limited scope is producing a lightweight quick spec with acceptance criteria. This approach includes optional explicit prompts for GDD updates when the system eventually requires broader integration.