What problem does it solve? Teams often make significant technical decisions without documenting the reasoning, alternatives, and trade-offs, leaving future maintainers guessing why the system was built a certain way. This Skill produces a consistent, numbered Architecture Decision Record (ADR) for every major technical choice. ## Core Features & Use Cases - Automatic ADR numbering: Scans docs/architecture/ to determine the next ADR number so records stay sequential. - Structured ADR template: Generates a complete record covering status, context, constraints, decision, alternatives considered, consequences, performance implications, migration plan, and validation criteria. - Context gathering: Reads related code and existing ADRs, and asks clarifying questions when the title alone is insufficient. - Use Case: After deciding to replace a REST layer with an event-driven message bus, invoke the Skill to produce docs/architecture/adr-0007-event-driven-messaging.md capturing the rejected alternatives and migration plan. ## Quick Start Ask the assistant to create an architecture decision record for your chosen technical decision, providing a short title such as "adopt event-driven messaging".