unity-adr

Use an Architecture Decision Record that captures the decision, context, options considered, chosen option, rationale, consequences, and revisit triggers. This Skill generates that structure for Unity-specific trade-offs like Coroutine vs UniTask or asmdef splitting.

A Unity ADR should include the decision statement, the context that forced the choice, the options considered, the chosen option, why it won, its consequences, and conditions that would trigger revisiting it. Keep it short and focused on architecture-affecting choices.

Write an ADR when the choice may be revisited later or when multiple plausible options exist, such as event-driven communication vs direct references. Skip it for routine implementation details that do not affect architecture direction.

No, it is documentation-only. It produces the ADR text and does not execute REST calls or alter project files, so it can be loaded under any operating mode including Approval, Auto, or Bypass.

ADRs only help if kept short and limited to decisions that materially affect code generation or architecture. Recording every minor choice creates noise, and an ADR cannot enforce that future code follows the documented decision.