records▌

Capture architectural decisions as they happen during coding sessions. Instead of decisions living only in Slack threads, PR comments, or someone's memory, this skill produces structured ADR documents that live alongside the code.

Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions.

Document significant technical decisions with structured context, rationale, and consequences. \n \n Provides five template formats (standard MADR, lightweight, Y-statement, deprecation, RFC-style) covering different decision complexity levels and team preferences \n Includes lifecycle management patterns for proposed, accepted, deprecated, and superseded decisions with clear status tracking \n Offers directory structure, indexing strategies, and automation tools (adr-tools) for maintaining ADR