design-iteration-tracker

Track design changes by logging each decision with its rationale, data source, and impact. This prevents circular design by detecting previously rejected states and building institutional memory to stop repeated mistakes.

Log game design decisions by specifying the change, the rationale, and the data source. This maintains institutional memory by recording parameter version history and generating summary reports of design iterations.

Yes, revert warnings identify when a proposed change mirrors a previously rejected design. This prevents rework and player frustration by alerting the team if a similar change was tried and reverted in a previous version.

Map cascading game design changes through impact chain tracking. This records how a single adjustment, like combat speed, impacts different game systems to prevent unintended consequences and circular design patterns.

Yes, iteration tracking maintains a parameter version history timeline. It tracks how key design values evolve over time by logging changes and their rationale to prevent losing track of decisions.