What problem does it solve? Engineering decisions and their rationale are often lost, forcing future developers and AI agents to re-debate settled choices or guess why code was written a certain way. This Skill captures the context, constraints, and trade-offs behind decisions in durable written form. ## Core Features & Use Cases - Architecture Decision Records (ADRs): Creates 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: Guides writing comments that explain why rather than what, plus typed docstrings and OpenAPI specs for public APIs. - Project Documentation: Provides templates for READMEs, changelogs, and agent-facing context files like CLAUDE.md. - 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 future contributors understand the rationale. ## Quick Start Ask your agent to write an ADR documenting the architectural decision you just made, following the conventions already present in the repository.
