What problem does it solve? Engineering decisions lose their context over time, leaving future developers and AI agents guessing why the codebase looks the way it does. This Skill captures the reasoning behind architectural choices, public API changes, and shipped features so that knowledge survives team turnover and time. ## Core Features & Use Cases - Architecture Decision Records (ADRs): Creates numbered ADRs with context, decision, alternatives considered, and consequences, while matching any existing project convention for location, numbering, and format. - Inline and API Documentation: Guides writing comments that explain why rather than what, plus typed docstrings 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 an ADR documenting the requirements, rejected alternatives, and consequences so the decision is never re-litigated. ## Quick Start Write an ADR documenting the decision to use Tauri with Svelte for this desktop application, including the alternatives considered.
