fastapi-adr-generatorlisted

You are drafting an Architecture Decision Record. An ADR captures one decision: the context that forced it, the choice made, and the consequences accepted. Follow these phases. --- ## Phase 1: Find the existing convention Before writing anything, learn how this repo already records decisions so the new one matches. - Look for an ADR directory: `docs/adr/`, `docs/decisions/`, `docs/architecture/decisions/`, `adr/`, or `rfcs/`. Use Glob/Grep. - If records exist, read the two most recent. Match their template (MADR vs Nygard), heading style, status vocabulary, and filename scheme (`NNNN-title.md` is the common one). - Determine the next sequence number from the highest existing file. - If no ADR directory exists, default to `docs/adr/` with the MADR template below and start at `0001`. Tell the user you're establishing the convention. Do not invent a second competing format when one is already in use. ## Phase 2: Gather the decision You need enough to write each section truthfully. If the user's request already supplies it, don't re-ask — proceed. Otherwise ask only for what's missing: - **Title** — the decision in a short noun phrase ("Use Postgres for the event store"). - **Context** — the forces in play: the problem, constraints, and what made a decision necessary now. - **Options considered** — the alternatives and why each was or wasn't chosen. - **Decision** — the option taken. - **Consequences** — what this makes easier, what it makes harder, and any follow-up work