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

markdown
1# {Epic Title}
2
3**Figma:** {figma link if available}
4
5## Feature Overview
6
7{2-3 paragraph description of what this feature does and why it's needed}
8
9## Requirements
10
11### {Section 1: Major Functionality Area}
12
13#### {Subsection}
14- Requirement 1
15- Requirement 2
16- Requirement 3
17
18#### {Another Subsection}
19- Requirement 1
20- Requirement 2
21
22### {Section 2: Another Major Area}
23
24#### {Subsection}
25- Requirement 1
26- Requirement 2
27
28## Technical Considerations
29
30### Performance
31- {Performance requirement 1}
32- {Performance requirement 2}
33
34### Data Integration
35- {Data source}
36- {Integration points}
37
38### UI Components
39- {Component 1}
40- {Component 2}
41
42## Implementation Checklist
43
44- [ ] {Major deliverable 1}
45- [ ] {Major deliverable 2}
46- [ ] {Major deliverable 3}
47
48## Diagrams
49
50{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
1graph TB
2    UI[UI Components] --> API[API Endpoints]
3    API --> SDK[Prowler SDK]
4    SDK --> Cloud[Cloud Providers]

Data Flow Diagrams

mermaid
1sequenceDiagram
2    User->>UI: Apply filters
3    UI->>API: GET /findings?filters
4    API->>DB: Query findings
5    DB-->>API: Results
6    API-->>UI: JSON response
7    UI-->>User: Render table

State Diagrams

mermaid
1stateDiagram-v2
2    [*] --> Pending
3    Pending --> InProgress: Start triage
4    InProgress --> Resolved: Mark resolved
5    InProgress --> Pending: Reset
6    Resolved --> [*]

Entity Relationship Diagrams

mermaid
1erDiagram
2    FINDING ||--o{ RESOURCE : affects
3    FINDING }|--|| CHECK : "belongs to"
4    RESOURCE }|--|| ACCOUNT : "belongs to"
5    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:

markdown
1## Related Tasks
2- Epic: [EPIC] Findings View
3- Blocked by: [task if any]
4- 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

markdown
1## Epic: [EPIC] {Title}
2
3{Full epic content following template}
4
5---
6
7## Suggested Tasks
8
9Based on this epic, create the following tasks:
10
11| # | Title | Component | Blocked By |
12|---|-------|-----------|------------|
13| 1 | [FEATURE] Task name | API | - |
14| 2 | [FEATURE] Task name | UI | Task 1 |
15| 3 | [FEATURE] Task name | UI | Task 2 |
16
17Would you like me to generate the full task descriptions?

Checklist Before Submitting

1. ✅ Title follows [EPIC] Feature Name format
2. ✅ Feature Overview explains what/who/why
3. ✅ Requirements are organized by functional area
4. ✅ Technical Considerations cover performance, data, UI
5. ✅ Implementation Checklist has high-level deliverables
6. ✅ Diagrams included where helpful (Mermaid format)
7. ✅ Figma links included if available
8. ✅ 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

Jira MCP Integration

CRITICAL: When creating epics via MCP, use these exact parameters:

Required Fields

json
1{
2  "project_key": "PROWLER",
3  "summary": "[EPIC] Feature name",
4  "issue_type": "Epic",
5  "additional_fields": {
6    "customfield_10359": {"value": "UI"}
7  }
8}

Team Field (REQUIRED)

The customfield_10359 (Team) field is REQUIRED. Options:

• "UI" - Frontend epics
• "API" - Backend epics
• "SDK" - Prowler SDK epics

Work Item Description Field

IMPORTANT: The project uses customfield_10363 (Work Item Description) instead of the standard description field for display in the UI.

CRITICAL: Use Jira Wiki markup, NOT Markdown:

• h2. instead of ##
• *text* for bold instead of **text**
• * item for bullets (same)
• ** subitem for nested bullets

After creating the epic, update the description with:

json
1{
2  "customfield_10363": "h2. Feature Overview\n\n{overview}\n\nh2. Requirements\n\n*{Section 1}*\n* {requirement 1}\n* {requirement 2}\n\n*{Section 2}*\n* {requirement 1}\n* {requirement 2}\n\nh2. Technical Considerations\n\n*Performance:*\n* {consideration 1}\n\n*Data Integration:*\n* {consideration 2}\n\nh2. Implementation Checklist\n\n* [ ] {deliverable 1}\n* [ ] {deliverable 2}\n* [ ] {deliverable 3}"
3}

Linking Tasks to Epic

When creating child tasks, use the epic key as parent:

json
1{
2  "additional_fields": {
3    "parent": "PROWLER-XXX"
4  }
5}

Workflow Transitions

Backlog (10037) → To Do (14) → In Progress (11) → Done (21)
                → Blocked (10)

MCP Commands Sequence

1. Create epic:

mcp__mcp-atlassian__jira_create_issue (issue_type: "Epic")

2. Update Work Item Description:

mcp__mcp-atlassian__jira_update_issue with customfield_10363

3. Create child tasks:

mcp__mcp-atlassian__jira_create_issue with parent: EPIC-KEY

4. Assign and transition:

mcp__mcp-atlassian__jira_update_issue (assignee)
mcp__mcp-atlassian__jira_transition_issue (status)

Keywords

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