quick-design

To create a quick design spec for small game mechanics changes, you provide a brief description of the change and rationale. The tool generates a lightweight markdown spec with acceptance criteria, classifying the change as tuning, tweak, addition, or new small system.

You need a quick spec instead of full game design documentation for small, low-risk gameplay or system changes with clear scope boundaries. It handles tuning, small tweaks, and standalone system additions without requiring full GDD authoring overhead.

To ensure balancing tweaks remain consistent with your existing game design document, the quick spec process scans relevant GDD material and prior quick specs for the same system. It checks appropriate data sources for tuning changes before generating the final spec.

Yes, you can use quick specs for tuning changes and new small standalone systems. The tool classifies your request into tuning, tweak, addition, or new small system categories, applying a matching spec format with clear scope boundaries for each type.

The best way to document acceptance criteria for small gameplay additions is generating a quick design spec. It produces an implementation-ready output that embeds directly into story files, defining clear acceptance criteria and any required data updates.

A limitation of using a quick spec for game system changes is it only applies to small, low-risk modifications with clear scope boundaries. It is not designed for complex feature expansions that require comprehensive full GDD authoring and extensive story integration.