What problem does it solve? Architectural decisions and their rationale are often lost, forcing teams and AI agents to re-debate settled choices and leaving public APIs undocumented. This Skill captures the why behind .NET technical decisions in durable, structured documentation. ## Core Features & Use Cases - Architecture Decision Records (ADRs): Provides a numbered ADR template (Context, Decision, Alternatives Considered, Consequences) stored in docs/adr/, with a PROPOSED → ACCEPTED → SUPERSEDED lifecycle. - API Documentation: Covers XML doc comments with <summary>, <remarks>, and <exception> tags, plus OpenAPI/Swagger metadata for ASP.NET Core Minimal APIs. - README & Changelog Templates: Supplies README structures with dotnet CLI commands, global.json notes, and changelog guidance tied to NuGet versioning (MinVer, Nerdbank.GitVersioning). - Use Case: After choosing PostgreSQL with EF Core over Dapper and MongoDB, use this Skill to write ADR-001 documenting the alternatives considered and consequences, so future engineers never re-litigate the decision. ## Quick Start Ask the agent to write an ADR documenting your recent architectural decision, such as choosing EF Core over Dapper for your data layer.