// Master technical decision-making, architecture choices, technology evaluation, technical roadmaps, and technical strategy for engineering teams. Use when making architectural decisions or evaluating technologies.
| name | technical-decision-making |
| description | Master technical decision-making, architecture choices, technology evaluation, technical roadmaps, and technical strategy for engineering teams. Use when making architectural decisions or evaluating technologies. |
Effective technical decisions balance multiple factors: team capability, business goals, scalability, cost, and risk.
# ADR-001: [Title]
Date: [Date]
Status: [Proposed/Accepted/Deprecated]
## Context
[Explain the issue requiring decision]
[Background and constraints]
## Options Considered
### Option A: [Description]
- Pros: ...
- Cons: ...
- Effort: ...
- Risk: ...
### Option B: [Description]
- Pros: ...
- Cons: ...
- Effort: ...
- Risk: ...
## Decision
[Chosen option and why]
[Trade-offs accepted]
## Consequences
[Positive outcomes]
[Negative outcomes]
[Future implications]
Criteria Weight Decision
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Team expertise 30% ★★☆
Ecosystem maturity 25% ★★★
Community support 15% ★★★
Performance 20% ★★☆
Cost 10% ★★★
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Total Score ★★★
Recommendation: [Based on scores]
Build vs. Buy
Monolith vs. Microservices
Caching Strategy