create-adr

An architecture decision record (ADR) captures significant technical choices, module dependencies, and consequences. You need ADRs when planning a new MVP or formalizing implementation decisions to align your team on system design tradeoffs before development begins.

To generate architecture decision records, provide a PRD or feature idea to define system structure, module boundaries, data models, and interface contracts. This process outputs implementation-ready ADRs complete with diagrams and testing strategy for technical planning.

Yes, ADR generation applies to both simple and multi-area projects. It prepares environment variables, mandatory testing strategy, and Context7 references so an AI developer agent can execute implementation preparation without guessing module dependencies or interface contracts.

The best way to document rejected alternatives is by capturing significant technical choices and their consequences directly within the architecture decision record. This formalizes system design tradeoffs and establishes explicit review triggers for team alignment.

You do not strictly need a PRD to create architecture decision records, as a standard feature description is sufficient. However, PRD-backed planning provides deeper context for defining data models, interface contracts, and module boundaries accurately.