# Create Epic Task

Break down validated concepts into focused epics with coordinated implementation stories.

## Purpose

Transform concepts from Laboratory experimentation or Gauntlet validation into actionable epics that can be implemented systematically.

## When to Use This Task

**Use this task when:**
- Concept requires 2-5 coordinated stories to complete
- Multiple features or components need integration
- Some design and planning work is needed
- Implementation spans multiple development sessions

**Use create-story when:**
- Single focused change can be completed in one session
- Follows existing patterns exactly
- Minimal integration complexity

## Process

### Step 1: Concept Analysis

**Concept Context:**
- [ ] Validated concept clearly understood
- [ ] User value proposition identified  
- [ ] Success metrics defined
- [ ] Integration requirements assessed

**Implementation Scope:**
- [ ] Core features identified
- [ ] Technical approach outlined
- [ ] Dependencies and integration points mapped
- [ ] Risk assessment completed

### Step 2: Epic Creation (Agile/Scrum Format)

#### Epic Title
{{Concept Name}} - {{Brief Value Description}}

#### Epic Statement (Agile Format)
```
As a [user type],
I need [high-level capability or outcome],
So that [significant business value or user benefit].
```

**Epic:** As a {{user type}}, I need {{high-level capability}}, so that {{significant business value}}.

#### Epic Details (Scrum Framework)

**Epic ID:** {{unique identifier}}
**Initiative:** {{broader business initiative this supports}}
**Epic Owner:** {{responsible stakeholder}}
**Target Release:** {{planned release version/date}}
**Story Point Estimate:** {{total estimated complexity}}

**Concept Background:**
- **Origin:** {{Laboratory session, Gauntlet validation, strategic initiative}}
- **User Problem:** {{specific problem being solved}}
- **Business Objective:** {{measurable business goal}}
- **Success Metrics:** {{how success will be measured}}

**Epic Scope:**
- **In Scope:** {{what this epic includes}}
- **Out of Scope:** {{what this epic explicitly does not include}}
- **Assumptions:** {{key assumptions being made}}
- **Constraints:** {{technical, business, or resource constraints}}

#### User Stories Breakdown (Agile Format)

**Sprint Planning:** Stories prioritized and estimated for sprint inclusion

1. **Story 1 (Priority: High):** 
   - **Title:** {{Foundation story title}}
   - **Story:** As a {{user}}, I want {{foundation capability}}, so that {{enables other features}}.
   - **Story Points:** {{1, 2, 3, 5, 8, 13}}
   - **Sprint:** {{target sprint number}}

2. **Story 2 (Priority: High):**
   - **Title:** {{Primary feature story title}}
   - **Story:** As a {{user}}, I want {{primary capability}}, so that {{core user value}}.
   - **Story Points:** {{1, 2, 3, 5, 8, 13}}
   - **Sprint:** {{target sprint number}}

3. **Story 3 (Priority: Medium):**
   - **Title:** {{Secondary feature story title}}
   - **Story:** As a {{user}}, I want {{secondary capability}}, so that {{additional value}}.
   - **Story Points:** {{1, 2, 3, 5, 8, 13}}
   - **Sprint:** {{target sprint number}}

4. **Story 4 (Priority: Medium):**
   - **Title:** {{Integration story title}}
   - **Story:** As a {{user}}, I want {{integration capability}}, so that {{seamless experience}}.
   - **Story Points:** {{1, 2, 3, 5, 8, 13}}
   - **Sprint:** {{target sprint number}}

5. **Story 5 (Priority: Low):**
   - **Title:** {{Enhancement story title}}
   - **Story:** As a {{user}}, I want {{enhancement capability}}, so that {{improved experience}}.
   - **Story Points:** {{1, 2, 3, 5, 8, 13}}
   - **Sprint:** {{target sprint number}}

#### Success Metrics

- **User Adoption:** {{how to measure user engagement}}
- **Business Impact:** {{relevant business metrics}}
- **Technical Performance:** {{performance benchmarks}}
- **Quality Standards:** {{quality and reliability measures}}

#### Risk Management

- **Primary Risk:** {{main implementation or adoption risk}}
- **Mitigation:** {{how risk will be addressed}}
- **Success Indicators:** {{early signals of success/failure}}
- **Pivot Options:** {{alternative approaches if needed}}

#### Definition of Done

- [ ] All stories completed with acceptance criteria met
- [ ] User testing validates concept effectiveness
- [ ] Integration points working smoothly
- [ ] Performance meets established benchmarks
- [ ] Documentation and training materials created
- [ ] Success metrics baseline established

### Step 3: Story Sequencing

**Implementation Order:**
1. {{Foundation work that enables other stories}}
2. {{Core user value - MVP functionality}}
3. {{Enhancement and integration work}}
4. {{Polish and optimization}}

**Dependencies:**
- Story dependencies clearly identified
- Blocking relationships documented
- Parallel development opportunities noted

### Step 4: Epic Validation

**Scope Check:**
- [ ] Epic delivers clear user value
- [ ] Stories are logically sequenced
- [ ] Implementation approach is feasible
- [ ] Resource requirements are reasonable

**Integration Assessment:**
- [ ] Integration points identified and planned
- [ ] Technical dependencies understood
- [ ] Risk mitigation strategies defined
- [ ] Success metrics are measurable

## Output
- Complete epic specification
- Story breakdown with dependencies
- Implementation timeline estimate
- Risk assessment and mitigation plan