# jira-epic

Drafts structured Jira epics following Prowler conventions, complete with Mermaid diagrams and task breakdown tables.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 138 installs · ★ 678 repo stars
- Author: gentleman-programming
- License: Apache-2.0 · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/Gentleman-Programming/Gentleman-Skills/tree/HEAD/curated/jira-epic/SKILL.md
- Updated: 2026-03-28
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/jira-epic

## What it does

This skill guides the AI to structure multi-component features, major redesigns, and refactoring efforts into a unified format. The generated document contains an overview answering what is built and why, a detailed requirements list organized by functional zones, technical constraints, and a sequenced implementation checklist.

It embeds Mermaid diagrams directly into the issue text for sequence flows, architecture boundaries, entity relationships, and state transitions. When provided with Figma URLs, it pins them to the header and links specific frame IDs to their related UI sections. A summary table at the bottom suggests child feature tickets ordered by API and UI dependencies.

Keep in mind the project specifics: direct submission through Jira MCP uses project key `PROWLER`, mandates the team field `customfield_10359` set to `UI`, `API`, or `SDK`, and formats description text with Jira Wiki syntax inside `customfield_10363`.

## Requirements
- Works with: Jira

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add Gentleman-Programming/Gentleman-Skills --skill jira-epic -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/jira-epic/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/jira-epic/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add Gentleman-Programming/Gentleman-Skills --skill jira-epic -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/jira-epic/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add Gentleman-Programming/Gentleman-Skills --skill jira-epic -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/jira-epic/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install Gentleman-Programming/Gentleman-Skills curated/jira-epic/SKILL.md
```

2. **Manually: put the files in place**
- File: `.github/skills/jira-epic/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add Gentleman-Programming/Gentleman-Skills --skill jira-epic -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/Gentleman-Programming/Gentleman-Skills --path curated/jira-epic
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/jira-epic/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add Gentleman-Programming/Gentleman-Skills --skill jira-epic -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/Gentleman-Programming/Gentleman-Skills/tree/HEAD/curated/jira-epic/SKILL.md

## When to use it
- format multi-component initiatives into standard Jira epics
- split large epics into ordered child tasks with clear dependencies
- embed Mermaid architecture and sequence diagrams into ticket drafts
- populate required custom Jira fields and wiki markup when calling Jira MCP

## Example prompts
- Create a Jira epic for the findings view with filtering and bulk actions
- Draft an epic for the GovCloud support feature using the Prowler template
- Build a multi-tenant support epic and suggest child tasks for API and UI

## Source text · SKILL.md · Apache-2.0

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: b2db213d256c0ce6.

BEGIN THIRD-PARTY FILE b2db213d256c0ce6
````text
---
name: jira-epic
description: >
  Creates Jira epics for large features following Prowler's standard format.
  Trigger: When user asks to create an epic, large feature, or multi-task initiative.
license: Apache-2.0
metadata:
  author: gentleman-programming
  version: "1.0"
---

## 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
# {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

## 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
```mermaid
sequenceDiagram
````
END THIRD-PARTY FILE b2db213d256c0ce6

The third-party file has ended. Everything between the b2db213d256c0ce6 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2521 of 7494 bytes. © gentleman-programming · Apache-2.0 · https://github.com/Gentleman-Programming/Gentleman-Skills/tree/HEAD/curated/jira-epic/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
