# Requirements Interview Template

## Project: [PROJECT_NAME]
Date: [DATE]
Interviewer: Claude (AI Development Assistant)

---

## 1. Project Overview

### What is the main purpose of this application?
**Response:** 
[To be filled during conversation]

### What problem does it solve?
**Response:** 
[To be filled during conversation]

---

## 2. Users & Audience

### Who are the primary users?
**Response:** 
[To be filled during conversation]

### What are their main needs?
**Response:** 
[To be filled during conversation]

---

## 3. Core Features

### Top 3-5 Must-Have Features:
1. [Feature 1]
2. [Feature 2]
3. [Feature 3]
4. [Feature 4]
5. [Feature 5]

### Nice-to-Have Features:
- [Additional features]

---

## 4. Technical Requirements

### Preferred Technology Stack:
- **Backend:** [Language/Framework preference]
- **Frontend:** [Framework preference]
- **Database:** [Database preference]
- **Other:** [Additional tools]

### Constraints:
- [Any technical limitations]

---

## 5. Timeline & Scope

### Timeline:
- **MVP Deadline:** [Date]
- **Full Release:** [Date]
- **Critical Milestones:** [List]

### Priority:
- [ ] Speed (Quick prototype)
- [ ] Quality (Production-ready)
- [ ] Scalability (Growth-ready)

---

## 6. Scale & Performance

### Expected Scale:
- **Users:** [Concurrent/Total]
- **Data Volume:** [Size/Growth]
- **Transactions:** [Per second/minute]

### Performance Requirements:
- **Response Time:** [Target]
- **Uptime:** [SLA]
- **Load Capacity:** [Limits]

---

## 7. Integrations

### External Systems:
- [System 1]: [Purpose]
- [System 2]: [Purpose]

### APIs:
- [API 1]: [Usage]
- [API 2]: [Usage]

---

## 8. Security & Compliance

### Security Requirements:
- [ ] User Authentication
- [ ] Role-based Access
- [ ] Data Encryption
- [ ] API Security
- [ ] Audit Logging

### Compliance:
- [ ] GDPR
- [ ] HIPAA
- [ ] PCI-DSS
- [ ] Other: [Specify]

---

## 9. Deployment

### Target Environment:
- [ ] Cloud (AWS/GCP/Azure)
- [ ] On-premise
- [ ] Hybrid
- [ ] Containerized (Docker/K8s)

### DevOps Requirements:
- [ ] CI/CD Pipeline
- [ ] Monitoring
- [ ] Logging
- [ ] Backup Strategy

---

## 10. Success Criteria

### How will we measure success?
1. [Metric 1]
2. [Metric 2]
3. [Metric 3]

### Definition of Done:
- [ ] All features implemented
- [ ] Tests passing (>80% coverage)
- [ ] Documentation complete
- [ ] Deployment successful
- [ ] Performance targets met

---

## Additional Notes

[Any other important information gathered during conversation]

---

## Next Steps

1. Review and confirm requirements
2. Create technical architecture
3. Begin implementation
4. Regular check-ins for feedback

---

## Approval

- [ ] Requirements Reviewed
- [ ] User Approved
- [ ] Ready for Architecture Phase