What problem does it solve? Architectural decisions made during development get lost or re-litigated across sessions because there is no persistent, structured record of why a choice was made. This Skill maintains a durable, immutable log of Architecture Decision Records (ADRs) under docs/adr/ so settled decisions stay settled. ## Core Features & Use Cases - File new ADRs: Creates numbered ADR files from a template with status, date, context, decision, and consequences, and appends them to the index. - Supersede instead of edit: Replaces outdated decisions by filing a new ADR and marking the old one as superseded, preserving the historical record. - Audit and index refresh: Reports stale proposals, orphan ADRs, and broken epic references, and rebuilds the docs/adr/README.md index table. - Use Case: After deciding to adopt PostgreSQL over SQLite in a design discussion, invoke this Skill to file ADR-0007 capturing the context, alternatives, and consequences, with the index updated automatically. ## Quick Start Ask Claude to file an ADR documenting the architectural decision you just made, including the context, the decision, and its consequences.