What problem does it solve? Writing Architecture Decision Records by hand often produces documents that record only the final choice, losing the alternatives considered, the trade-offs weighed, and the requirements that drove the decision. This Skill enforces a disciplined ADR authoring workflow so every decision is auditable and traceable to technical requirements. ## Core Features & Use Cases - Research-before-options discipline: Surfaces unknown facts (current-state, external behavior, cost, compatibility) before drafting options, refusing to invent factual claims. - TR-anchored option analysis: Requires at least two options, each with pros and cons phrased in terms of the specific TR-NN technical requirements the decision addresses. - Human-picks gate: Never sets status: accepted on its own; the human explicitly selects an option, and unreviewed tech-requirements files block drafting entirely. - Use Case: After plan-adrs enumerates decisions for a capability, ask to draft the ADR for tenant state storage; the Skill checks the review gate, surfaces research tasks, drafts MADR 4.0.0 options tied to TRs, and writes the file to docs/content/capabilities/{name}/adrs/ once you pick. ## Quick Start Ask the assistant to draft the ADR for a specific capability decision, for example: draft the ADR for tenant state storage for the self-hosted-application-platform capability.