Architecture Decision Record (ADR) Series Generator

You are a technical writer and architect. Generate Architecture Decision Records (ADRs) for the following project decisions:

**Project:** [PROJECT_DESCRIPTION — e.g., "B2B SaaS platform for invoice management"]
**Decisions to document:** [LIST_DECISIONS — e.g., "1. Choose Next.js over Remix, 2. Use PostgreSQL over MongoDB, 3. Implement CQRS for reporting, 4. Choose Stripe over custom billing"]

For each decision, write an ADR following this template:

---
**ADR-[NUMBER]: [DECISION_TITLE]**

**Status:** [Accepted / Proposed / Deprecated / Superseded by ADR-X]
**Date:** [DATE]
**Deciders:** [ROLES — e.g., "Engineering Lead, Backend Team, CTO"]

**Context**
- Business requirement driving this decision (2-3 sentences)
- Technical constraints and non-functional requirements
- Team capabilities and experience relevant to this choice

**Options Considered**
For each option:
| Criteria | Option A | Option B | Option C |
|----------|----------|----------|----------|
| [Criteria 1] | Rating + note | Rating + note | Rating + note |

- **Option A: [NAME]** — Pros, cons, and effort estimate
- **Option B: [NAME]** — Pros, cons, and effort estimate
- **Option C: [NAME]** — Pros, cons, and effort estimate

**Decision**
We chose [OPTION] because [REASONING in 2-3 sentences linking back to context and criteria].

**Consequences**
- **Positive:** [What this enables]
- **Negative:** [What trade-offs we accept]
- **Risks:** [What could go wrong and mitigation]

**Follow-up Actions**
- [ ] [Action items resulting from this decision]
---

Also generate:
- **ADR index page** — table of all ADRs with status and one-line summary
- **ADR template** — blank template for the team to use for future decisions
- **Decision log changelog** — format for tracking when ADRs are updated or superseded