unity-adr

Use an Architecture Decision Record (ADR) that captures the decision, context, options considered, chosen option, rationale, consequences, and revisit triggers. This Skill generates that structure for Unity-specific choices like async patterns or assembly layout.

The choice depends on your project's async needs, and this Skill helps you weigh both options and record the outcome. It produces an ADR comparing tradeoffs so the decision and its reasoning are preserved for the team.

Write an ADR when multiple plausible options exist or the choice may be revisited later, such as event-driven vs direct references or one assembly vs multiple asmdefs. Only record decisions that materially affect code generation or architecture direction.

No, it is documentation-only and generates no code changes. It loads freely under any operating mode including Approval, Auto, or Bypass, since it only produces decision records.

ADRs add overhead when applied to trivial choices, so they should stay short and cover only decisions affecting architecture direction. Minor implementation details that can be easily reversed do not need a formal record.