Jira Epic

When to Use

Use this skill when creating Jira epics for:

• Large features spanning multiple components
• New views/pages in the application
• Major refactoring initiatives
• Features requiring API + UI + SDK work

Epic Template

# {Epic Title}

**Figma:** {figma link if available}

## Feature Overview

{2-3 paragraph description of what this feature does and why it's needed}

## Requirements

### {Section 1: Major Functionality Area}

#### {Subsection}
- Requirement 1
- Requirement 2
- Requirement 3

#### {Another Subsection}
- Requirement 1
- Requirement 2

### {Section 2: Another Major Area}

#### {Subsection}
- Requirement 1
- Requirement 2

## Technical Considerations

### Performance
- {Performance requirement 1}
- {Performance requirement 2}

### Data Integration
- {Data source}
- {Integration points}

### UI Components
- {Component 1}
- {Component 2}

## Implementation Checklist

- [ ] {Major deliverable 1}
- [ ] {Major deliverable 2}
- [ ] {Major deliverable 3}

## Diagrams

{Mermaid diagrams for architecture, flow, data model, etc.}

Epic Title Conventions

Format: [EPIC] Feature Name

Examples:

• [EPIC] Findings View
• [EPIC] Multi-tenant Support
• [EPIC] Compliance Dashboard Redesign
• [EPIC] GovCloud Support

Required Sections

1. Feature Overview

Brief but complete description of:

• What the feature does
• Who uses it
• Why it's needed

2. Requirements

Organized by functional area:

• Group related requirements together
• Use clear headers and subheaders
• Be specific and testable

3. Technical Considerations

Always include:

• Performance: Large dataset handling, pagination, caching
• Data Integration: Data sources, APIs, relationships
• UI Components: Reusable components, design system usage

4. Implementation Checklist

High-level deliverables that will become individual tasks:

• Each checkbox = potential Jira task
• Order by dependency (API before UI)
• Include testing milestones