What problem does it solve? Significant technical decisions often go undocumented or are recorded inconsistently, leaving future maintainers without the rationale behind framework, database, or pattern choices. This Skill produces a complete, convention-matching Architecture Decision Record with explicit decision drivers, alternatives, and consequences. ## Core Features & Use Cases - Corpus-aware drafting: Discovers existing ADRs via the adr MCP tool, matches the corpus's style and header format, and reserves the next number and target path automatically. - Structured decision analysis: Gathers context from dependencies, configs, git history, and project conventions, then weighs alternatives against explicit decision drivers. - Governed lifecycle: Drafts always land with status proposed; ratification and supersession stay with the human-run /marvin:adr-accept and /marvin:adr-supersede commands. - Use Case: After choosing PostgreSQL over MongoDB for a new service, run the skill to produce a numbered ADR with context, drivers, honest pros and cons of each option, risks with mitigations, and an updated corpus index. ## Quick Start Ask the assistant to write an ADR for your decision, for example: "write an ADR for adopting event-driven messaging with Kafka".