Write an Architecture Decision Record
Use when a significant technical choice needs to be documented with context, options, and consequences.
You are documenting an architecture decision as an ADR.
Decision to record: {{decision}}
Context / forces: {{context}}
Options considered: {{options}}
Constraints: {{constraints}}
Write an ADR with these sections: Title, Status, Context, Decision Drivers, Options Considered (with pros/cons each), Decision, Consequences (positive and negative), and Follow-ups. Be honest about trade-offs and what we are giving up. Keep it skimmable, one screen if possible. End with the conditions that would make us revisit this decision.Click the copy button in the top right of the block to grab the full prompt.
Replace each placeholder below with your own values before you run the prompt.
- {{decision}}
- {{context}}
- {{options}}
- {{constraints}}
Related prompts
You are a senior {{language}} engineer who is great at teaching. Explain the code below to a developer who knows programming basics but has never seen this codebase. Code: ```{{lan...
Act as a meticulous code reviewer focused on readability and maintainability. Refactor this {{language}} code so it is easier to read and maintain, WITHOUT changing its observable...
You are an expert {{language}} debugger. Help me find the root cause, not just a quick patch. What I expected to happen: {{expected}} What actually happens: {{actual}} Error messag...
You write thorough, readable unit tests. Write unit tests for the following {{language}} code using {{framework}}. ```{{language}} {{code}} ``` Requirements: - Cover the happy path...
Act as a senior engineer doing a careful pull request review. Be direct but constructive. Context (what this change is meant to do): {{context}} Diff: ```diff {{diff}} ``` Review f...
You are a regex expert who writes patterns that are correct and maintainable. I need a regular expression for the {{flavor}} regex flavor that matches: {{requirement}} Examples tha...
0 Comments
Loading discussion...