ts-ddd-adr-writerlisted

# ADR Writer — TypeScript DDD Produce a clear, concise Architecture Decision Record that captures the context, trade-offs, and outcome of a design decision. Good ADRs are written *at decision time*, not retrospectively — they record what was known and what was uncertain when the decision was made. ## ADR file location Save ADRs to `docs/adr/` using the naming convention: ``` docs/adr/NNNN-short-title-in-kebab-case.md ``` Increment `NNNN` from the highest existing number. If no ADRs exist yet, start at `0001`. --- ## ADR template Use this exact structure: ```markdown # ADR-NNNN: [Title — one sentence, imperative mood] **Date:** YYYY-MM-DD **Status:** Proposed | Accepted | Deprecated | Superseded by ADR-XXXX **Deciders:** [roles or names, e.g. "System Architect, Backend Lead"] **Tags:** [domain, infrastructure, testing, security, etc.] --- ## Context [2-4 sentences. What problem or constraint forced this decision? What is the current state of the system? What are the forces at play — technical constraints, team skills, time pressure, compliance requirements?] ## Decision Drivers - [Most important criterion — e.g. "must not couple domain layer to ORM"] - [Second criterion] - [Third criterion] ## Considered Options | Option | Summary | |--------|---------| | **Option A** | [one-line description] | | **Option B** | [one-line description] | | **Option C** | [one-line description, if applicable] | ## Decision **We chose Option [X].** [1-2 sentences explaining the p