Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →donchitos/architecture-decision
Creates an Architecture Decision Record (ADR) documenting a significant technical decision, its context, alternatives considered, and consequences. Every major technical choice should have an ADR.
Passed 16 of 19 test cases with the skill, and 9 of 19 without it.
and 7 more in the full report
8 fixed8 passed either way2 still failing1 broke4 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
All prerequisite ADRs in our project registry are now written and documented. What specific next step option should be added to the closing interactive menu?
| Checked | Without skill | With skill |
|---|---|---|
| Displays an option to start writing game design documents using the design system tool. | Missed | Passed |
The instructions your model reads when the skill loads.
!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.
When this skill is invoked:
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.small and studio: 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.
workflow (see .claude/docs/workflow-modes.md):
full — all ADRs on the required ADR list must be completed.standard — critical ADRs only (Foundation-layer systems).minimal — not required. Can still be run voluntarily.If the argument starts with retrofit followed by a file path
Read references/0-retrofit.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
test cases passed, vs 9 / 19 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.