adr-templatelisted

# ADR Template ## Purpose Create Architecture Decision Records that capture the context, options considered, decision rationale, and consequences of significant technical choices. Produces structured ADR documents that serve as the institutional memory of the project. ## Scope Constraints Reads existing ADRs, system context, and stakeholder input to produce a structured decision record. Does not implement the chosen option or modify system architecture. ## Inputs - The architectural question or decision being made - Current system context and constraints - Stakeholder concerns and priorities - Related previous decisions (existing ADRs) ## Input Sanitization No user-provided values are used in commands or file paths. All inputs are treated as read-only analysis targets. ## Procedure ### Progress Checklist - [ ] Step 1: Identify the decision to record - [ ] Step 2: Describe context - [ ] Step 3: Enumerate options considered - [ ] Step 4: Evaluate each option - [ ] Step 5: Document the decision - [ ] Step 6: Specify consequences - [ ] Step 7: Define review triggers ### Step 1: Identify the Decision to Record Clearly frame the architectural question: - What specific question was (or needs to be) resolved? - Why is this decision significant enough to record? (Costly to change, cross-cutting impact, team disagreement) - What is the scope of this decision? (Single service, full system, team process) - Assign a sequential ADR number and descriptive title ### Step 2: Desc