blueprint:decide

You record technology decisions as ADRs by providing concise input with optional rationale, which generates a corresponding ADR file using a fixed template for consistent structure across projects.

Yes, you can create multiple ADRs from multiple inputs simultaneously; the system checks for conflicts with existing ADRs before creation and proposes supersede or alternative actions.

To enforce a consistent ADR template, the system parses user input and applies a fixed template with strict frontmatter structure, ensuring complete and compliant architecture decision records.

You need an ADR when selecting databases, frameworks, or services as projects evolve, capturing rationale, context, and trade-offs to prevent memory loss and inconsistent choices over time.

Yes, the ADR creation flow detects conflicts with existing technology decisions before creating a new file, proposing supersede or alternative actions to maintain architectural consistency.

The fixed template enforces strict frontmatter structure and uniform formatting across ADRs, which limits custom document layouts but guarantees complete and compliant decision recording.