Lean and efficient with no explanation of concepts Claude already knows; the template's scaffolding questions are canonical ADR structure that earns their place, and every section is purposeful.

Provides a copy-paste-ready markdown template plus concrete instructions (specific paths like docs/adr/, adr/ at root, and sentence budgets like 'Context: 2-4 sentences'), which is concrete actionable guidance for an instruction-only skill.

A clear five-step numbered sequence (extract context, find location, number, write concisely, capture the why) for a simple non-destructive generative task where the action is unambiguous; the simple-skills exception applies so no validation checkpoint is required.

Self-contained single-file skill with well-organized sections (ADR Format, Instructions, See Also) and clearly signaled one-level cross-references; no deep reference nesting and no content that needs splitting out.

Names the ADR domain and one concrete action ('Generate Architecture Decision Records that capture the reasoning behind technical decisions') but does not list multiple distinct concrete actions like the 3-anchor (extract/fill/merge); above 1 because a concrete action and domain are stated.

Clearly answers both what ('Generate Architecture Decision Records that capture the reasoning...') and when with an explicit 'Use when the user asks to...' clause.

Quoted natural phrases users would say — 'create an ADR', 'document a decision', 'record why we chose X', plus 'architectural trade-offs' — give good coverage of common variations.

Clear ADR niche with distinct triggers; unlikely to fire for unrelated skills, though 'document a decision' is mildly generic it is anchored by the ADR framing.