adrlisted

# Architecture Decision Record (ADR) When this skill is activated, create an ADR file that documents a significant architectural decision. ADRs are short, durable records that explain *why* a decision was made — not just what was decided. ## Clarifying Questions Before writing the ADR, you **must always** ask question 1 first — never skip it, never infer it from context. Wait for the answer before continuing. 1. **[Always ask]** What is the exact decision being documented? State it in one sentence. Once you have the answer to question 1, ask the remaining questions. Skip any already clearly answered by the user's response. 2. What forced this decision — what was the situation, constraint, or requirement that made it necessary? 3. Which alternatives were seriously considered (not strawmen)? What made each one worth evaluating? 4. Why was each alternative rejected in favor of the chosen option? 5. What are the most significant trade-offs or risks of the chosen option? 6. What is the current status — Proposed, Accepted, or other? 7. Are there related ADRs this connects to or supersedes? ## Steps 1. Use the answers above to understand the decision; fill remaining gaps from conversation context 2. Determine the next ADR number by checking if an `adr/` or `docs/adr/` folder exists and what ADRs already exist there 3. Write the ADR with full context, considered alternatives, and honest consequences 4. Link it to any related ADRs if they exist ## Output Create a file at `do