Skip to content
Get packs

Architecture Decision Records

Guides the agent through writing a formal ADR documenting a technical decision and its alternatives

Source Download skill
Repository
Donchitos/Claude-Code-Game-Studios
Stars
32,965
Licence
MIT
Files
8 files

What it does

When you ask the agent to record a technical decision, it walks you through the context, the options you considered, and the consequences, then writes an Architecture Decision Record (a standard numbered markdown document) into your project's docs/architecture folder. It can also retrofit an ADR for a decision already made in existing code, or mark an existing ADR as accepted. It is built for game-studio workflows, so it also reads engine context and can spawn review agents such as a technical director to check the decision.

Great for

  • Developers and tech leads who want decisions written down in a consistent format
  • Teams using the Claude Code Game Studios setup who need ADRs linked to design docs
  • Anyone documenting an architecture choice that was made in code but never recorded

Skip it if

  • Quick one-off coding questions, since the skill produces a full formal document and asks many questions first (it is overhead for small choices)
  • Projects without a docs/architecture convention, since it expects that folder and an ADR numbering scheme; the reason is it will create files in unexpected places otherwise
  • Teams that want the agent to decide architecture on its own, since it is designed to collaborate and leave the decision in Proposed status until a human accepts it

Try asking

  • “/architecture-decision event-system-architecture”
  • “/architecture-decision retrofit src/physics/collision.cs”
  • “/architecture-decision accept ADR-0003”
  • “/architecture-decision physics-engine-choice --review lean”
Step-by-step guide: how to use Architecture Decision RecordsInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 8 original files, the MIT licence and an attribution note.

    architecture-decision.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip architecture-decision.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip architecture-decision.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Give a short, specific title such as physics-engine-choice so the generated file name is clear
  • Run /architecture-review in a fresh session afterwards, as the skill instructs, so the review is independent
  • Set workflow or docs.density in your config to control how long the generated ADRs are

What's inside

  • CONTRACT.md
  • references/0-accept.md
  • references/0-retrofit.md
  • references/1-engine-context.md
  • references/3-gather-context.md
  • references/4-decide.md
  • references/5-generate.md
  • SKILL.md

Redistributed unmodified from Donchitos/Claude-Code-Game-Studios under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.