What problem does it solve? Engineering decisions and their rationale are often lost, forcing future developers and AI agents to re-debate settled questions or guess why the codebase looks the way it does. This Skill provides templates and rules for capturing the why behind decisions through ADRs, inline comments, API docs, READMEs, and changelogs. ## Core Features & Use Cases - Architecture Decision Records (ADRs): A complete template with status lifecycle (Proposed → Accepted → Superseded/Deprecated), alternatives analysis, and consequences, stored in docs/decisions/ with sequential numbering. - Inline Documentation Rules: Clear guidance on commenting the why rather than the what, documenting known gotchas, and avoiding TODOs and commented-out code. - API & Project Documentation: Patterns for TSDoc-style function documentation, OpenAPI/Swagger specs, README structure, and changelog maintenance. - Use Case: After choosing PostgreSQL over MongoDB for a new service, use this Skill to write ADR-001 capturing the context, rejected alternatives, and consequences so future engineers never re-litigate the decision. ## Quick Start Ask the agent to write an ADR documenting the architectural decision you just made, including the context, alternatives considered, and consequences.
