---
name: gather-requirements
description: Interactive requirements gathering that asks detailed questions, validates responses, and produces actionable technical specifications.
isolation: worktree
---

# gather-requirements

Interactive requirements gathering that asks detailed questions, validates responses, and produces actionable technical specifications.

## Usage

Ask me to gather requirements for any feature. I'll conduct a structured interview and create a comprehensive requirements document.

## Interactive Question Flow

### 1. Business Context

```
Q1: What problem are you solving?
Q2: Who experiences this problem?
Q3: What's the current workaround?
Q4: What's the business impact?
Q5: Success metrics?
```

### 2. User Analysis

```
Q6: Primary user personas?
Q7: User technical skill level?
Q8: Device types they use?
Q9: Languages they speak?
Q10: Accessibility needs?
```

### 3. Functional Requirements

```
Q11: Core features needed?
Q12: User actions/workflows?
Q13: Data inputs required?
Q14: Expected outputs?
Q15: Error scenarios?
```

### 4. Technical Constraints

```
Q16: Existing systems to integrate?
Q17: Performance requirements?
Q18: Data volume estimates?
Q19: Response time needs?
Q20: Concurrent user load?
```

### 5. Security & Compliance

```
Q21: Sensitive data types?
Q22: Authentication method?
Q23: Authorization levels?
Q24: Audit requirements?
Q25: Compliance standards?
```

### 6. UI/UX Preferences

```
Q26: Visual style preference?
Q27: Similar products you like?
Q28: Brand guidelines?
Q29: Mobile-first or desktop?
Q30: Dark mode support?
```

## Automatic Actions After Gathering

1. **Validate Requirements**
   - Check for conflicts
   - Identify missing info
   - Assess feasibility
   - Estimate complexity

2. **Generate Specifications**
   - Technical architecture
   - Database schema
   - API endpoints
   - Component hierarchy
   - Test scenarios

3. **Create Artifacts**
   - User stories
   - Acceptance criteria
   - Technical design doc
   - Risk assessment
   - Timeline estimate

## Example Session

```
Me: "I'll gather requirements for your feature. Let's start:

**What problem are you solving?**"

You: "Patients forget appointments"

Me: "**Who experiences this problem most?**"

You: "Elderly patients and busy parents"

[... continues through all questions ...]

Me: "Based on your requirements, here's what I'll build:

## Appointment Reminder System

### Technical Specification
- WhatsApp integration for notifications
- Automated reminder scheduler
- Multi-language support (AR/EN)
- Configurable reminder timing
- Confirmation tracking

### Implementation Plan
1. WhatsApp Business API setup
2. Cron job for scheduling
3. Message template system
4. Response handler
5. Analytics dashboard

### Estimated Timeline: 2 weeks
### Risk Level: Low
### Complexity: Medium

Shall I proceed with implementation?"
```

## Smart Features

- **Adaptive Questions**: Skips irrelevant questions based on previous answers
- **Validation**: Ensures answers are complete and consistent
- **Context Awareness**: References existing project patterns
- **Memory Integration**: Recalls similar requirements from past
- **Auto-documentation**: Generates all necessary docs

## Output Format

```markdown
# [Feature Name] Requirements

## Executive Summary

[Brief overview]

## User Stories

- As a [persona], I want [action], so that [benefit]

## Technical Requirements

- Architecture: [details]
- Database: [schema]
- APIs: [endpoints]
- Security: [measures]

## Acceptance Criteria

- [ ] Criterion 1
- [ ] Criterion 2

## Timeline & Resources

- Duration: [estimate]
- Team: [needs]
- Dependencies: [list]
```

## Success Metrics

- All questions answered
- No conflicting requirements
- Technical feasibility confirmed
- Clear implementation path
- Stakeholder alignment
