What problem does it solve? Architectural decisions often live in chat threads or tribal knowledge and get lost when teams change, making it impossible to understand why a system was built a certain way. This Skill produces formal Architecture Decision Records (ADRs) that capture context, options, trade-offs, and rationale in version control. ## Core Features & Use Cases - Structured ADR Template: Generates records with status, deciders, context, decision, alternatives with pros/cons, and consequences (positive, negative, neutral). - Decision Lifecycle Management: Supports statuses from Proposed through Accepted, Rejected, Superseded, and Deprecated, with an index structure for organizing ADRs in docs/adr/. - Common Patterns & Anti-Patterns: Includes templates for technology choices, architectural patterns, and build-vs-buy decisions, plus examples of vague or incomplete ADRs to avoid. - Use Case: Your team must choose between PostgreSQL, MySQL, and MongoDB for a payments system. Use this Skill to produce an ADR documenting requirements, cost estimates, trade-offs, and follow-up actions so future engineers understand the reasoning. ## Quick Start Ask the AI to write an ADR for choosing PostgreSQL over MySQL and MongoDB as the primary database, including context, alternatives, and consequences.