What problem does it solve? Engineering decisions lose their context over time, leaving future developers and AI agents unable to understand why code was built a certain way. This Skill captures the reasoning behind architectural choices, API designs, and feature changes so that knowledge persists beyond the original author's memory. ## Core Features & Use Cases - Architecture Decision Records (ADRs): Provides a structured template with context, decision, alternatives considered, and consequences, stored in docs/decisions/ with sequential numbering and a proposed-to-accepted lifecycle. - Inline and API Documentation: Guides writing comments that explain why rather than what, JSDoc-style function documentation, and OpenAPI/Swagger specs for REST endpoints. - README and Changelog Standards: Defines a README structure covering quick start, commands, and architecture, plus a changelog format 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 the team never re-litigates the decision. ## Quick Start Write an ADR documenting the decision to use FastAPI for the backend, including the alternatives considered and their trade-offs.
