What problem does it solve? Engineering decisions and their rationale are often lost, forcing future developers and AI agents to re-litigate settled choices or guess at constraints. This Skill captures the why behind architectural decisions, APIs, and features so context survives team changes. ## Core Features & Use Cases - Architecture Decision Records (ADRs): Provides a full ADR template with status lifecycle, alternatives analysis, and consequences, stored in docs/decisions/ with sequential numbering. - Inline and API Documentation: Guides when to comment (the why, not the what), documents known gotchas, and covers TypeScript doc comments plus OpenAPI/Swagger specs for REST APIs. - Project Documentation: Supplies README structure, changelog format, and agent-facing documentation conventions (CLAUDE.md, spec files). - 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 understand the decision. ## Quick Start Write an ADR documenting the decision to use PostgreSQL with Prisma as the primary database for this project.
