Technical Feasibility Analysis

You are a technical architect evaluating the feasibility of a proposed solution.

**Proposal:** {proposal_description}

**Requirements:**
{requirements}

**Constraints:**
- Timeline: {timeline}
- Budget: {budget}
- Team: {team_composition}
- Existing Infrastructure: {current_infrastructure}

Conduct a thorough feasibility analysis:

**1. Technical Feasibility:**

**Architecture Assessment:**
- Proposed tech stack: [evaluate each component]
- Integration points: [identify challenges]
- Scalability considerations: [bottlenecks, limits]
- Security implications: [risks, mitigations]

**Technology Maturity:**
For each key technology:
| Technology | Maturity | Community | Risk Level | Alternative |
|------------|----------|-----------|------------|-------------|
| {tech1}    | Production-ready | Large | Low | {alt} |

**Technical Risks:**
| Risk | Probability | Impact | Mitigation |
|------|-------------|--------|------------|
| [specific risk] | High/Med/Low | High/Med/Low | [strategy] |

**2. Resource Feasibility:**

**Team Capability Gap Analysis:**
| Required Skill | Current Level | Gap | Training/Hiring Plan |
|----------------|---------------|-----|----------------------|

**Timeline Analysis:**
```
Phase 1: [Name] - [duration]
  ├─ Task 1: [time estimate]
  ├─ Task 2: [time estimate]
  └─ Buffer: [X%]

Phase 2: [Name] - [duration]
  ...

Total: [timeline] (requested) vs [realistic estimate]
```

**Is the timeline realistic?** [Yes/No + justification]

**Budget Breakdown:**
| Category | Estimated Cost | Notes |
|----------|----------------|-------|
| Infrastructure | ${amount} | [AWS/GCP/Azure, breakdown] |
| Licenses | ${amount} | [specific tools] |
| Team | ${amount} | [if hiring needed] |
| Contingency (20%) | ${amount} | |
| **Total** | **${total}** | vs. Budget: ${budget} |

**3. Alternative Approaches:**
Provide 2-3 alternatives:

**Approach A: [Name]**
- Description: [how it differs]
- Pros: [advantages over proposal]
- Cons: [disadvantages]
- Cost: [relative cost]
- Timeline: [relative timeline]
- Recommendation score: X/10

**Approach B: [Name]**
[Same structure]

**4. Recommendation:**
- **Verdict:** Go / No-Go / Go with Modifications
- **Justification:** [data-driven reasoning]
- **Conditions for Success:**
  1. [specific requirement]
  2. [specific requirement]
- **Major Risks to Monitor:**
  1. [risk + KPI to track]
  2. [risk + KPI to track]

**5. Decision Matrix:**
| Criteria | Weight | Proposal | Alt A | Alt B |
|----------|--------|----------|-------|-------|
| Technical Fit | 30% | 8/10 | 7/10 | 9/10 |
| Cost | 25% | ... | ... | ... |
| Timeline | 20% | ... | ... | ... |
| Risk | 15% | ... | ... | ... |
| Team Fit | 10% | ... | ... | ... |
| **Weighted Score** | | **X.X** | **Y.Y** | **Z.Z** |

**6. Next Steps:**
If proceeding:
- Immediate actions (Week 1)
- Proof of concept scope
- Key decisions needed
- Stakeholders to involve

Format with clear sections, tables, and data-driven analysis.