Phase 3: Feature ideation from ticket analysis

Tinker

Home Epics Phase 3: Feature ideation from ticket analysisEdit

Cancel

Title *

Project *

Description

Implement Phase 3: Researcher analyzes user workflows and proposes feature/UX improvements.

## Ticket Content Analysis

**Find user pain points:**
```ruby
# Search tickets for friction patterns
search_tickets("struggle to find")
search_tickets("hard to use")
search_tickets("confusing")
search_tickets("takes too long")
search_tickets("wish I could")

# Find manual work patterns
search_tickets("manually")
search_tickets("copy paste")
search_tickets("repeated")
```

**Pattern extraction:**
1. Read last 200 ticket descriptions
2. Find user complaints or frustrations
3. Group by similarity
3. If pattern appears 3+ times → feature proposal

## Feature Proposals

**Example UX improvement:**
```json
{
  "title": "One-click rebook from failed booking",
  "proposal_type": "feature",
  "reasoning": "12 tickets mentioned rebooking after failure is tedious: users must manually fill all details again. One-click rebook would preserve original details.",
  "confidence": "high",
  "priority": "medium",
  "metadata": {
    "pattern_frequency": 12,
    "effort_estimate": "4h",
    "value_estimate": "high",
    "evidence_links": [
      {"type": "ticket", "id": 300, "description": "Rebooking is tedious"},
      {"type": "ticket", "id": 312, "description": "Wish I could rebook easily"},
      {"type": "ticket", "id": 325, "description": "Rebook lost my details"}
    ]
  }
}
```

**Example new feature:**
```json
{
  "title": "Add booking calendar heatmap",
  "proposal_type": "feature",
  "reasoning": "8 tickets mention difficulty finding available slots. Calendar heatmap would show availability at a glance, reducing booking friction.",
  "confidence": "medium",
  "priority": "low",
  "metadata": {
    "pattern_frequency": 8,
    "effort_estimate": "8h",
    "value_estimate": "medium",
    "evidence_links": [
      {"type": "ticket", "id": 210, "description": "Hard to find slots"},
      {"type": "ticket", "id": 225, "description": "Availability unclear"}
    ]
  }
}
```

## Effort/Value Estimation

**Estimation rubric:**
```
Effort:
- trivial: <1h
- small: 1-4h
- medium: 4-8h
- large: 8-16h
- xlarge: >16h

Value:
- critical: fixes frequent pain, high impact
- high: significant improvement
- medium: nice to have
- low: minor polish
```

## Analysis Loop (Phase 3)

```
Every 2 hours:
1. Search tickets for pain point keywords
2. Read last 200 tickets (not just recent)
3. Find recurring user struggles
4. Group by similarity
5. Estimate effort/value
6. Generate feature/UX proposals
7. Store via create_proposal
```

## Acceptance Criteria
- [ ] Analyzes tickets for user pain points
- [ ] Proposes UX improvements
- [ ] Proposes new features
- [ ] Estimates effort and value
- [ ] Evidence links to source tickets