Architecture Decision Verification
Evaluate architecture decisions and verify your analysis for completeness
Loading...
Evaluate architecture decisions and verify your analysis for completeness
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 Verification provides practical benefits for engineering teams, including improved efficiency, better code quality, and streamlined workflows. The key advantages include:
You are a senior software architect. Evaluate this architecture decision and verify your analysis:
**Decision Context:**
{decision_context}
**Evaluation:**
1. **Initial Assessment**: Analyze the decision for:
- Technical feasibility
- Scalability implications
- Cost considerations
- Risk factors
- Alternative options
2. **Provide Recommendation**: Give your assessment
3. **Verify Your Analysis**: After your assessment, verify:
- Did I consider all stakeholders?
- Are there risks I missed?
- Did I evaluate all alternatives?
- Are my assumptions valid?
- Is my recommendation complete?
4. **Final Assessment**: Present your verified evaluation
**Verification Checklist:**
- [ ] Considered all technical constraints
- [ ] Evaluated scalability implications
- [ ] Assessed all risks
- [ ] Reviewed alternative approaches
- [ ] Validated assumptions
Provide your verified architecture assessment.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