valec3/agents.md/jira-epic
Claude Code and agent skill by valec3/agents.md
- community
Checking that the SKILL.md file is still in the repository.
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.
Install
npx vskill@latest install valec3/agents.md/jira-epicSKILL.md
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 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
Data Flow Diagrams
State Diagrams
Entity Relationship Diagrams
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:
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
Checklist Before Submitting
- ✅ Title follows
[EPIC] Feature Nameformat - ✅ 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
backticksfor 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
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*** itemfor bullets (same)** subitemfor nested bullets
After creating the epic, update the description with:
Linking Tasks to Epic
When creating child tasks, use the epic key as parent:
Workflow Transitions
MCP Commands Sequence
- Create epic:
- Update Work Item Description:
- Create child tasks:
- Assign and transition:
Keywords
jira, epic, feature, initiative, prowler, large feature
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingREFERENCES/GentlemanProgramming/skill/jira-epic/SKILL.md
Popularity
- 7-day trend score
- 0
Refreshed 19 Mar 2026, 8 months ago.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/valec3/agents.md/jira-epic)