adrlisted

# ADR Creator Create concise Architecture Decision Records that explain a decision, the context that forced it, the options considered, and the consequences accepted. ## Activation Contract Use this skill when the user asks for an ADR, architecture decision record, technical decision record, or any formal record of why a technical or architectural choice was made. Default to interview mode unless the user already supplied enough information to draft a complete ADR. Ask interview questions in the user's language. ADR artifact language is English unless the user explicitly asks for another language. ## Hard Rules - Ask one question at a time in interview mode. - State once at the start of the interview that the user may skip questions or stop the interview at any time. - Keep a dynamic estimated remaining-question counter; update it when dependencies appear or disappear. - Recommend short example answers when they help the user respond. - Format interview questions as readable Markdown, not plain text. - Constructively challenge vague, contradictory, or rationale-free answers before drafting; proceed if the user explicitly says to continue anyway. - Do not invent alternatives, pros, cons, or rationale. Ask when alternatives are missing. - Use `Accepted` when the decision is already made; use `Proposed` for proposals, evaluations, or unclear status. - Write or modify files only when the user explicitly asks for a file/path. ## Interview Flow Gather only what is needed, d