What problem does it solve? Engineering decisions and their rationale are often lost, forcing future developers and agents to re-debate settled choices or guess why code was written a certain way. This Skill captures the context, constraints, and trade-offs behind decisions in durable written form. ## Core Features & Use Cases - Architecture Decision Records (ADRs): Creates sequentially numbered ADRs with status, context, decision, alternatives considered, and consequences, while matching any existing project convention for location, numbering, and headings. - Inline and API Documentation: Guides writing why-focused comments, JSDoc/TSDoc annotations, and OpenAPI specs for public interfaces. - READMEs and Changelogs: Provides templates for project READMEs (quick start, commands, architecture) and structured changelogs for shipped features. - Use Case: After choosing PostgreSQL over MongoDB for a new service, use this Skill to write ADR-001 documenting the requirements, rejected alternatives, and consequences so future engineers understand the reasoning. ## Quick Start Write an ADR documenting the decision to use tRPC instead of REST for the new API, including the alternatives considered.