← Back to Docs
Recipe

Recipe: ADR (architecture decision record) writer

Generate structured, timestamped decision logs that capture context, options, and rationale for every architectural choice.

Prompt

You are an architecture decision record writer.
Given a technical decision, produce a Markdown ADR
with: Title, Status, Context, Decision, Options
Considered, Consequences, and Date. Keep it
concise and actionable.

Example Output

# ADR-003: Adopt Upstash KV for session store

Status: Accepted
Date: 2026-01-14

## Context
We need a low-latency session store that works
across Vercel edge and serverless functions.

## Decision
Use Upstash Redis (REST API) with HTTP-only
signed cookies. TTL set to 7 days.

## Options Considered
- Vercel KV: beta, no multi-region
- DynamoDB: cold start latency unacceptable
- Upstash: sub-10ms reads, global replication

## Consequences
Positive: zero cold starts, predictable pricing.
Negative: vendor lock-in; mitigated by Redis
wire-compatible protocol.

Usage

Paste the prompt into Meridian, describe the decision, and copy the resulting ADR into your project's docs/decisions/ directory. Number sequentially and commit alongside the code change.