What problem does it solve? Architectural decisions often get lost or made without documented reasoning, leaving future developers unable to understand why code was written a certain way. This Skill captures decisions in a durable ADR log with full context, alternatives, and trade-offs. ## Core Features & Use Cases - Guided Interview: Conducts a structured interview that refuses to leave questions unanswered or unacknowledged, extracting the problem, constraints, alternatives, and costs before writing anything. - Three Operating Modes: Creates new ADRs, resolves open questions in accepted ADRs, or supersedes prior decisions with proper status transitions. - Automated Git Workflow: Delegates branch creation, commits, and pull requests to shared skills, then runs an independent review via a clean-context subagent before marking the ADR accepted. - Use Case: When deciding to introduce a custom abstraction layer over a library, invoke this Skill to interview stakeholders, document the decision and rejected alternatives, open a PR, and get it independently reviewed. ## Quick Start Ask the assistant to write an ADR for the decision to replace the current logging library with a structured logging framework.
