What problem does it solve? Code shows what was built but not why it was built that way. This Skill captures the reasoning behind architectural decisions, public API changes, and design trade-offs so future engineers and AI agents can understand the codebase without re-litigating settled choices. ## Core Features & Use Cases - Architecture Decision Records (ADRs): Create 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: Write why-focused comments, JSDoc/TSDoc annotations, and OpenAPI specifications for public interfaces. - Project Documentation: Structure READMEs with quick start and commands, and maintain 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-debated. ## Quick Start Write an ADR documenting the decision to use tRPC instead of REST for the new API, following the existing docs/decisions convention.
