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 documentation. ## 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 API docs with parameters, return values, and thrown errors, including OpenAPI specs for REST endpoints. - READMEs and Changelogs: Provides templates for project READMEs covering quick start, commands, and architecture, plus structured changelogs for shipped features. - Use Case: After choosing PostgreSQL over MongoDB for a new service, use this Skill to write an ADR documenting the alternatives considered 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 alternatives you considered and why they were rejected.
