Loading...
Guides you through structuring and writing a clear, concise Architecture Decision Record (ADR) to document significant technical decisions for posterity.
An Architecture Decision Record (ADR) is a document that captures important architectural decisions made along with their context and consequences. ADRs help teams understand why certain technical choices were made, document trade-offs, and provide historical context for future decision-making.
Architecture Decision Record (ADR) Drafter provides practical benefits for engineering teams, including improved efficiency, better code quality, and streamlined workflows. The key advantages include:
Act as a Principal Engineer who champions clear, asynchronous communication. I need to write an Architecture Decision Record (ADR) for a recent technical decision my team made. Your task is to help me draft it. I will describe the decision in my own words. You will then format my description into a standard ADR template. You must ask me clarifying questions if any section is unclear. The ADR template you will use is: 1. **Title:** A short, descriptive title for the decision. 2. **Status:** (Proposed, Accepted, Deprecated, Superseded) 3. **Context:** What is the problem or issue that this decision addresses? What is the background? 4. **Decision:** What is the change that we are proposing or have decided on? 5. **Consequences:** What are the results of this decision? What are the positive outcomes? What are the trade-offs or risks? What new problems might this decision introduce? 6. **Options Considered:** What other options were considered, and why were they rejected? Let's begin. --- MY DESCRIPTION OF THE DECISION --- [Your description here]
Get access to enhanced versions, advanced examples, and premium support for this prompt.
Loading revision history...
Apply what you learned with these prompts and patterns
Acts as a critical Red Team consultant to pressure-test your product strategy, identify hidden assumptions, uncover potential weaknesses, and validate market fit before presenting to executives or committing resources.
Comprehensive system design review with scalability and reliability analysis
Assess and prioritize technical debt in your codebase
Deep dive into prompt engineering with our comprehensive masterclass covering all patterns and techniques.
Prompt Engineering Masterclass: Complete Guide for Developers