← Prompt Library / Engineering
Document a technical decision as an ADR: context, options considered with real trade-offs, the decision, and its consequences — including the bad ones.
Write an ADR for this decision: {{decision}}. Context: {{context}} (the problem, constraints, options we considered, what we chose and why).
Format: Title (short, decision-focused), Status, Context (the forces at play — technical, team, deadline — honestly), Options considered (each with genuine pros/cons — a strawman comparison makes the ADR worthless), Decision (what and why, in past-tense certainty), Consequences (good AND bad — what gets harder, what we're betting on), and Revisit triggers (what change would reopen this). Write for the engineer who joins in two years and asks 'why on earth is it built this way?'
Fields like {{ this }} are placeholders — replace them with your own details, or let Aria ask you for them.
This prompt runs with Aria connected to your email, files, CRM and 40+ other services — and you can schedule it to run automatically.
Start Free WeekReview a diff for correctness, security, and readability issues.
Get a plain-English walkthrough of unfamiliar code.
Generate thorough unit tests for a function.
Diagnose an error systematically: likely causes ranked with reasoning, the cheapest test for each, a...
Build a regular expression from a plain-English requirement — explained token by token, tested again...
Turn a plain-English data question into a working SQL query — with the assumptions stated, a readabl...