What problem does it solve? Unity projects often revisit technical choices without a record of why a particular approach was chosen, leading to repeated debates and inconsistent architecture. This Skill captures architecture decisions in a structured ADR format so the reasoning behind each choice is preserved. ## Core Features & Use Cases - Structured ADR Output: Produces a consistent record covering Decision, Context, Options considered, Chosen option, Rationale, Consequences, and Revisit triggers. - Unity-Specific Decision Support: Covers common Unity tradeoffs such as Coroutine vs UniTask, direct references vs event-driven communication, ScriptableObject config vs in-scene authoring, and MonoBehaviour vs pure C# services. - Use Case: When deciding whether to split game code into multiple asmdef assemblies, use this Skill to compare the options, weigh compile-time and dependency tradeoffs, and lock in the decision with documented rationale. ## Quick Start Ask the assistant to record an ADR comparing Coroutine and UniTask for your Unity project's async logic.
