unity-adr

Document Unity architecture decisions with context, options, and rationale.

1|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/muddyrain/valley-mas --skill unity-adr-muddyrain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unity-adr
Source: https://github.com/muddyrain/valley-mas/tree/main/.codex/skills/unity-skills/skills/adr
Command: npx skills add https://github.com/muddyrain/valley-mas --skill unity-adr-muddyrain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unity ADR helps teams capture architecture decisions for Unity projects, ensuring trade-offs and design choices are documented for future reference.

Core Features & Use Cases

  • ADR-style decision records for Unity projects to compare options and lock design choices
  • Context, options, chosen option, rationale, consequences, and revisit triggers are captured
  • Use during design reviews, feature planning, and refactoring to align stakeholders

Quick Start

Draft an ADR for a Unity design decision by outlining the context, options, and chosen solution.

Frequently Asked Questions about unity-adr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document architecture decisions for a Unity project?

An Architecture Decision Record (ADR) for Unity captures the problem context, evaluated options, chosen solution, rationale, consequences, and revisit triggers to lock design choices during reviews.

What is the best way to track design trade-offs during Unity refactoring?

Tracking design trade-offs during Unity refactoring is best handled by drafting an ADR that outlines the context, available options, and chosen solution, ensuring future reference and stakeholder alignment.

When do I need an architecture decision record in software engineering?

You need an architecture decision record in software engineering during design reviews, feature planning, or refactoring when multiple approaches exist, allowing you to document options and capture trade-offs effectively.

How do I capture context and rationale for Unity design choices?

To capture context and rationale for Unity design choices, draft a record that explicitly outlines the problem context, decision options, chosen option, consequences, and revisit triggers for future reference.

Can I use ADRs to align stakeholders during Unity feature planning?

Yes, you can use ADRs to align stakeholders during Unity feature planning by documenting the problem context, available options, chosen option, and rationale, ensuring everyone understands the design choices.