decide

You log architecture decision records by writing a markdown file under docs/decisions/NNNN-slug.md, which enforces ADR structure, numbering, and slug generation for consistent traceability across your team.

The best way to prevent relitigating past technical decisions is to log ADRs into a searchable brain, storing reference markdown files so team members can search past decisions before making new recommendations.

Yes, you can auto-detect decisions from prompts to create ADRs. The system logs them with source metadata for traceability, or you can manually invoke a write workflow to refine stubs.

You search past decisions by querying the logged ADR history in the brain before making load-bearing recommendations, preserving context and alignment with previous team choices.

No, this ADR logging tool requires no external dependencies to write markdown files. It generates structured decision details and corresponding markdown files directly under your docs/decisions directory.

A manually created architecture decision record uses a structured format capturing title, body, and decision details, automatically enforcing numbering and slug generation to maintain consistent traceability.