New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Jira Epic

by Gentleman-Programming in Gentleman-Programming/Gentleman-Skills

Creates Jira epics for large features following Prowler's standard format.

Apache-2.0Auto-check passedDevelopment

Install Jira Epic

skills CLI
$ npx skills add Gentleman-Programming/Gentleman-Skills --skill jira-epic -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Gentleman-Programming/Gentleman-Skills jira-epic --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Gentleman-Programming/Gentleman-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/curated/jira-epic .claude/skills/jira-epic && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
jira-epic
GitHub stars
658
Token cost
~1.9k tokens
SKILL.md length
500 words
Files
1
Skills in repo
24
Repo updated
First seen
Licence
Apache-2.0

At a glance

Creates Jira epics for large features following Prowler's standard format.

  • Works in 4 steps: Feature Overview → Requirements → Technical Considerations → …
  • Asks to create an epic
  • SKILL.md covers When to Use, Epic Template, Epic Title Conventions and Required Sections, plus 8 more sections
  • Reaches figma.com

What it does

Jira Epic is an agent skill from Gentleman-Programming/Gentleman-Skills. 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.

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Diagrams and User stories. It works with Jira and Figma. The repository describes itself as: Community-driven AI agent skills for Claude Code, OpenCode, and other AI assistants. Curated patterns and community contributions. The licence is Apache-2.0.

When your agent uses it

  • Asks to create an epic
  • Multi-task initiative

Example prompts

  • “Use the jira-epic skill to create Jira epics for large features following Prowler's standard format”
  • “/jira-epic”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Feature Overview
  2. Requirements
  3. Technical Considerations
  4. Implementation Checklist

What it can do on your machine

Read from SKILL.md and the folder at commit c8036a3. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are mermaid, markdown and json).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • figma.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Jira Epic loads about 1.9k tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 500 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~42
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Gentleman-Programming/Gentleman-Skills at commit c8036a3, republished under its Apache-2.0 licence (© Gentleman-Programming). 500 words, ~1,868 tokens.

Download SKILL.mdSave it as .claude/skills/jira-epic/SKILL.md (or your agent's skills folder).
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
metadata.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
    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
mermaid
stateDiagram-v2
    [*] --> Pending
    Pending --> InProgress: Start triage
    InProgress --> Resolved: Mark resolved
    InProgress --> Pending: Reset
    Resolved --> [*]
Entity Relationship Diagrams
mermaid
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:

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

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

  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
Show full SKILL.md (196 more words)Show less

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
{
  "project_key": "PROWLER",
  "summary": "[EPIC] Feature name",
  "issue_type": "Epic",
  "additional_fields": {
    "customfield_10359": {"value": "UI"}
  }
}
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
{
  "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}"
}
Linking Tasks to Epic

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

json
{
  "additional_fields": {
    "parent": "PROWLER-XXX"
  }
}
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")
  1. Update Work Item Description:
mcp__mcp-atlassian__jira_update_issue with customfield_10363
  1. Create child tasks:
mcp__mcp-atlassian__jira_create_issue with parent: EPIC-KEY
  1. 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

© Gentleman-Programming, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in curated/jira-epic of Gentleman-Programming/Gentleman-Skills.

Open the folder on GitHubat commit c8036a3

Compare with similar skills

Jira Epic next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Jira Epic compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Jira Epic this skillGentleman-Programming/Gentleman-Skills658—~1.9kAutomated safety check: PassApache-2.0
Improve Codebase ArchitectureTwiTech-LAB/devchain101—~3kAutomated safety check: PassMIT
Architecture DiagramMathews-Tom/armory328—~4.8kAutomated safety check: PassMIT
Create Workflow Diagramgooseworks-ai/goose-skills1.2k1 repos~4.6kAutomated safety check: PassMIT
UX Flowsgenkovich/sdd171—~2kAutomated safety check: PassMIT
Status Update Generatorborghei/Claude-Skills886—~1.9kAutomated safety check: PassMIT

Similar skills

  • Improve Codebase Architecture

    TwiTech-LAB/devchain

    Plan architecture improvements and refactoring for a codebase: scan for deepening opportunities (shallow modules, leaky seams, low-leverage interfaces), present candidates as a markdown report with…

    101 GitHub stars~3k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Architecture Diagram

    Mathews-Tom/armory

    Generate architecture diagrams as fully editable SVG with native AWS, Azure, and GCP icons for cloud diagrams, or hand-drawn generic icons for everything else.

    328 GitHub stars~4.8k tokensUpdated 3 days ago
    DevelopmentAuto-check passed

  • Create Workflow Diagram

    gooseworks-ai/goose-skills

    Create FigJam/Miro-style workflow diagrams as high-quality PNG images from plain-text workflow descriptions.

    1.2k GitHub starsUsed in 1 repo~4.6k tokens
    DevelopmentAuto-check passed

  • UX Flows

    genkovich/sdd

    A skill your agent uses to derive the user flows of a UI-touching feature after the spec is clarified — one mermaid flowchart per UI-touching §4 user story (happy + alt/error branches from §5 ACs)…

    171 GitHub stars~2k tokensUpdated 1 mo ago
    Product & Project ManagementAuto-check passed

  • Status Update Generator

    borghei/Claude-Skills

    Generate weekly executive status updates from Jira/Linear data exports.

    886 GitHub stars~1.9k tokensUpdated 2 days ago
    Writing & ContentAuto-check passed

  • Acceptance Criteria Check

    shopsys/shopsys

    Checks a pull request against the acceptance criteria of its Jira issue by driving the deployed review environment with Playwright.

    350 GitHub stars~1k tokensUpdated today
    Product & Project ManagementAuto-check passed

More from Gentleman-Programming/Gentleman-Skills

All 24 skills in this repo

  • Elixir Antipatterns

    Gentleman-Programming/Gentleman-Skills

    Core catalog of 8 critical Elixir/Phoenix anti-patterns covering error handling, separation of concerns, Ecto queries, and testing.

    658 GitHub stars~2.1k tokensUpdated 6 mo ago
    Auto-check passed

  • Skill Creator

    Gentleman-Programming/Gentleman-Skills

    Creates new AI agent skills following the Agent Skills spec.

    658 GitHub stars~1.1k tokensUpdated 6 mo ago
    Auto-check: notes

  • AI SDK 5

    Gentleman-Programming/Gentleman-Skills

    Vercel AI SDK 5 patterns. An agent skill from Gentleman-Programming/Gentleman-Skills.

    658 GitHub stars~1.4k tokensUpdated 6 mo ago
    Auto-check passed

  • Angular Architecture

    Gentleman-Programming/Gentleman-Skills

    Angular architecture: Scope Rule, project structure, file naming, style guide.

    658 GitHub stars~823 tokensUpdated 6 mo ago
    Auto-check passed

  • Angular Core

    Gentleman-Programming/Gentleman-Skills

    Angular core patterns: standalone components, signals, inject, control flow, zoneless.

    658 GitHub stars~1.1k tokensUpdated 6 mo ago
    Auto-check passed

  • Angular Forms

    Gentleman-Programming/Gentleman-Skills

    Angular forms: Signal Forms (experimental) and Reactive Forms.

    658 GitHub stars~687 tokensUpdated 6 mo ago
    Auto-check passed

Works with

Categories

Questions about Jira Epic

What does Jira Epic do?

Creates Jira epics for large features following Prowler's standard format. Jira Epic is an agent skill from Gentleman-Programming/Gentleman-Skills. Creates Jira epics for large features following Prowler's standard format.

When should I use Jira Epic?

Jira Epic fits situations like: asks to create an epic; multi-task initiative.

How do I install Jira Epic in Claude Code?

Run `npx skills add Gentleman-Programming/Gentleman-Skills --skill jira-epic -a claude-code`. Or copy the skill folder (curated/jira-epic in Gentleman-Programming/Gentleman-Skills) into .claude/skills/jira-epic in your project. Claude Code loads it when a task matches its description.

How do I install Jira Epic in Codex?

Run `npx skills add Gentleman-Programming/Gentleman-Skills --skill jira-epic -a codex`. Or copy the skill folder (curated/jira-epic in Gentleman-Programming/Gentleman-Skills) into .agents/skills/jira-epic in your project. Codex loads it when a task matches its description.

Can I use Jira Epic in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Gentleman-Programming/Gentleman-Skills --skill jira-epic -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/jira-epic, .gemini/skills/jira-epic, .github/skills/jira-epic and .opencode/skills/jira-epic in your project.

What does Jira Epic need to run?

SKILL.md names no scripts, command-line tools or credentials: Jira Epic is instructions for the agent only.

Does Jira Epic access the network?

SKILL.md names 1 domain. In commands or code: figma.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Jira Epic safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Jira Epic use?

Jira Epic is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Jira Epic use?

About 1.9k tokens (SKILL.md is roughly 7.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Jira Epic?

Skills that share tags, products or a category with Jira Epic: Improve Codebase Architecture (TwiTech-LAB/devchain, 101 stars), Architecture Diagram (Mathews-Tom/armory, 328 stars), Create Workflow Diagram (gooseworks-ai/goose-skills, 1.2k stars) and UX Flows (genkovich/sdd, 171 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Jira Epic?

Gentleman-Programming (a GitHub organization) maintains it in Gentleman-Programming/Gentleman-Skills, which has 658 GitHub stars. The repository holds 24 skills in this directory. The repository was last updated on March 28, 2026.

Source: Gentleman-Programming/Gentleman-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.