Systems Design Doc
A design document for one game system — economy, combat, or crafting — specifying the rules an engineer needs to implement it without daily designer input.
A systems design document describes one game system in enough detail for implementation. Where a GDD describes all systems at a high level and a feature spec describes a single feature, a systems design doc goes deep on the rules, variables, ranges, and interactions for a specific system: the economy (currency sources, sinks, and exchange rates), the progression system (level curves, unlock gates, pacing), or the combat system (damage formula, status effects, interaction matrix).
A good systems design doc is quantitative. It does not say “enemies should feel challenging but fair” — it specifies the damage formula, the hitpoints by enemy type, the difficulty scaling function. The numbers might change, but having them stated forces the design to be concrete and makes later changes traceable to a decision.
Systems design docs are among the most valuable documents to keep in version control. Balance changes — the most common source of live-game patches — are changes to the variables in the systems design doc. Being able to diff two versions of the economy doc is worth more than any amount of spreadsheet cell-by-cell comparison.
How it works in Gameframe
Gameframe’s document editor handles balance tables, structured specs, and mixed prose-plus-table formats natively. The diff view shows cell-level changes in spreadsheets alongside prose changes in text sections — so a balance patch that changes fifty numbers shows exactly which numbers changed.
Gameframe’s Specialist Reviews include an Economy Designer and Systems Designer personality that review the doc for internal consistency: do the currency sources and sinks balance? Does the progression curve match the stated pacing intent?
See Gameframe’s features or start a free trial to bring your systems docs into version control.