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

## Diagrams

Use Mermaid for:

### Architecture Diagrams
```mermaid
graph TB
    UI[UI Components] --> API[API Endpoints]
    API --> SDK[Prowler SDK]
    SDK --> Cloud[Cloud Providers]

Data Flow Diagrams

sequenceDiagram
    User->>UI: Apply filters
    UI->>API: GET /findings?filters
    API->>DB: Query findings
    DB-->>API: Results
    API-->>UI: JSON response
    UI-->>User: Render table

State Diagrams

stateDiagram-v2
    [*] --> Pending
    Pending --> InProgress: Start triage
    InProgress --> Resolved: Mark resolved
    InProgress --> Pending: Reset
    Resolved --> [*]

Entity Relationship Diagrams

erDiagram
    FINDING ||--o{ RESOURCE : affects
    FINDING }|--|| CHECK : "belongs to"
    RESOURCE }|--|| ACCOUNT : "belongs to"
    ACCOUNT }|--|| PROVIDER : "belongs to"

Splitting Epic into Tasks

After creating the epic, generate individual tasks using the jira-task skill:

Task Naming Pattern

From epic [EPIC] Findings View, create:

[FEATURE] Findings table with pagination (UI)
[FEATURE] Findings filters - provider and account (UI)
[FEATURE] Findings detail panel - Overview tab (UI)
[FEATURE] Findings detail panel - Resources tab (UI)
[FEATURE] Findings bulk actions - mute/suppress (API + UI)
[FEATURE] Findings search functionality (API + UI)

Task Dependencies

Always specify in each task:

## Related Tasks
- Epic: [EPIC] Findings View
- Blocked by: [task if any]
- Blocks: [task if any]

Figma Integration

When Figma links are provided:

Include main Figma link at top
Reference specific frames in relevant sections
Example: https://www.figma.com/design/xxx?node-id=1830-44712&m=dev

Output Format

## Epic: [EPIC] {Title}

{Full epic content following template}

---

## Suggested Tasks

Based on this epic, create the following tasks:

| # | Title | Component | Blocked By |
|---|-------|-----------|------------|
| 1 | [FEATURE] Task name | API | - |
| 2 | [FEATURE] Task name | UI | Task 1 |
| 3 | [FEATURE] Task name | UI | Task 2 |

Would you like me to generate the full task descriptions?

Checklist Before Submitting

✅ Title follows [EPIC] Feature Name format
✅ Feature Overview explains what/who/why
✅ Requirements are organized by functional area
✅ Technical Considerations cover performance, data, UI
✅ Implementation Checklist has high-level deliverables
✅ Diagrams included where helpful (Mermaid format)
✅ Figma links included if available
✅ Suggested tasks table provided at the end

Formatting Rules

CRITICAL: All output MUST be in Markdown format, ready to paste into Jira.

Use # for epic title, ## for main sections, ### for subsections
Use **bold** for emphasis
Use - [ ] for checkboxes in Implementation Checklist
Use ``` for code blocks and Mermaid diagrams
Use backticks for file paths, commands, and code references
Use tables for Suggested Tasks section
Use --- to separate epic from suggested tasks

Keywords

jira, epic, feature, initiative, prowler, large feature

jira-epic

When to Use

Epic Template