create-adr

Document architecture decisions by creating an architecture decision record that captures the decision, context, evaluated alternatives, and consequences. This ensures significant design choices remain discoverable and actionable across codebases and project documentation.

The best way to structure an architecture decision record is using a standardized template that includes metadata, options analysis, and consequences. This approach generates concise drafts that record rationale for review and maintain consistency across project documentation.

Manage ADR numbering and lifecycle by ensuring unique numbering when writing files and updating superseded ADR frontmatter. This lifecycle management preserves content integrity while accurately marking the status of previous architecture decisions.

Yes, you can gather codebase context automatically by orchestrating document and codebase locators to surface related files and code areas. This context gathering identifies relevant information needed to evaluate alternatives and draft the architecture decision record.

You need to create an architecture decision record during research, planning, and implementation workflows when making significant architectural or design choices. Documenting these decisions ensures the rationale and consequences remain accessible for future software teams.