Architecture Decision Record
Writes an ADR with context, alternatives and consequences for a decision.
Install
npx skills add Donchitos/Claude-Code-Game-Studios --skill architecture-decision -g -a claude-code -y- Repository
- Donchitos/Claude-Code-Game-Studios32.1k
- Category
- Engineering
- Updated
- 17d ago
- License
- MIT
- Context cost
- Mediumabout 1,578 tokens
- Runs scripts
- No, instructions only
What it does
Create an ADR documenting a technical decision: context, alternatives considered, consequences.
!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys review_mode,automation,workflow,docs.density,team.size
Resolved above, use as-is; --review overrides review_mode. No block →
defaults in .claude/docs/config-resolution.md.
Architecture Decision
When this skill is invoked:
0. Parse Arguments, Detect Retrofit / Acceptance Mode
See .claude/docs/director-gates.md for the full check pattern. Individual gate definitions live in .claude/docs/director-gates/[gate-id].md, the spawned agent reads its own gate file; do not read it in the parent session.
Every AskUserQuestion call follows .claude/docs/automation-modes.md
(collaborative asks always · guided major-only · autonomous logs and proceeds;
automation_always_ask categories always prompt).
team.size: which agents validate this ADR (orthogonal to review_mode/workflow).
individual(default):technical-director(TD-ADR) + the engine-specialist.smallandstudio: the same two. This skill spawns no engine sub-specialist and no adversarial reviewer at any size.
docs.density, it controls the depth of the ADR's prose sections, not
which sections the skeleton emits (that is fixed). modes.rigor sets it
alongside workflow; set docs.density explicitly to vary ADR verbosity alone:
terse (the default, via rigor: minimal) = decision + alternatives as bullets, one line of rationale each;
balanced = paragraph per section with light rationale (rigor: standard); thorough =
full prose with trade-offs and worked rationale in Decision, Alternatives, and
Consequences. Apply it to the prose sections; the Engine Compatibility, ADR
Dependencies, and GDD Requirements tables are structural and stay whole at every
density.
