What problem does it solve? Code shows what was built but not why it was built that way. This Skill captures the context, constraints, and trade-offs behind technical decisions so future engineers and AI agents stop re-litigating settled choices or falling into known traps. ## Core Features & Use Cases - Architecture Decision Records (ADRs): A numbered template with status lifecycle (Proposed → Accepted → Superseded/Deprecated), alternatives analysis, and consequences, stored in docs/decisions/. - Inline and API Documentation: Guidance on commenting the why rather than the what, JSDoc/TSDoc patterns for public APIs, and OpenAPI/Swagger examples for REST endpoints. - Project Documentation Standards: README structure (quick start, commands, architecture), changelog format, and agent-facing docs like CLAUDE.md rules files. - Use Case: After choosing PostgreSQL over MongoDB and SQLite for a task app, write ADR-001 recording the requirements, rejected alternatives, and consequences so the decision is never re-debated six months later. ## Quick Start Ask the agent to write an ADR documenting the architectural decision you just made, including the alternatives considered and why they were rejected.