Technical Decision Documentation Review

D

Daniel Okoye

@daniel-okoye

·

Reflect on ADR quality to improve decision documentation.

3 copies0 forks
Share this prompt:
I wrote this Architecture Decision Record. Help me reflect on its quality:

My ADR:
{{adr_content}}

Decision Context:
{{decision_context}}

Stakeholders:
{{stakeholders}}

Reflect on the ADR quality:

1. CONTEXT COMPLETENESS
   - Did I capture all relevant constraints?
   - Is the problem statement clear to future readers?
   - What context will be lost over time?

2. OPTION FAIRNESS
   - Did I present alternatives objectively?
   - Did I strawman any options?
   - What options did I not consider?

3. REASONING CLARITY
   - Is my reasoning traceable and logical?
   - Will future engineers understand why?
   - What implicit knowledge did I assume?

4. CONSEQUENCE HONESTY
   - Did I acknowledge real downsides?
   - Am I being honest about risks?
   - What negative consequences did I downplay?

5. REVISED ADR
   Rewrite the ADR to:
   - Provide complete context
   - Present fair alternatives
   - Show clear reasoning
   - Honestly state consequences
   - Be useful to engineers 2 years from now

Details

Category

Coding

Use Cases

ADR quality improvementDecision documentation refinementKnowledge preservation enhancement

Works Best With

claude-opus-4.5gpt-5.2gemini-2.0-flash
Created Updated Shared

Related Prompts

Create your own prompt vault and start sharing