create-architectural-decision-record

You can document architectural decisions by generating structured Architectural Decision Records (ADRs) that capture the problem statement, chosen decision, consequences, alternatives, and implementation notes in a standardized format.

The best way to create an AI-optimized ADR is to use a standardized format with YAML frontmatter and coded bullet points, ensuring precise language for machine readability while maintaining human reference clarity.

Structure an architectural decision record with specific sections for context, the chosen decision, positive and negative consequences, alternatives considered with rejection rationale, and implementation notes.

Architectural decision records should be saved in the /docs/adr/ directory using a sequential naming convention to ensure they are easily discoverable and properly organized.

You need to write an architectural decision record when a team makes a critical architectural choice, such as selecting a new database technology, to formally capture the problem, proposed solutions, and final decision.

Yes, you can generate a database selection ADR automatically by providing a title like 'Database Selection', and the system will output a fully structured document with YAML frontmatter and all required sections.