jira-epic

Create Jira epics with standardized templates and title conventions.

Updated Aug 8, 2025
One-click install
npx skills add https://github.com/Albarracin-sg/MIS-DOTFILES --skill jira-epic-albarracin-sg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-epic
Source: https://github.com/Albarracin-sg/MIS-DOTFILES/tree/main/tools/opencode/skill/jira-epic
Command: npx skills add https://github.com/Albarracin-sg/MIS-DOTFILES --skill jira-epic-albarracin-sg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps product teams quickly plan and communicate large-scale work by generating Jira epics that follow a consistent format, ensuring alignment across stakeholders.

Core Features & Use Cases

  • Epic Template: Provides a standard Epic Template with sections for Feature Overview, Requirements, Technical Considerations, and Implementation Checklist to ensure comprehensive planning.
  • Conventions & Titleing: Enforces Epic Title conventions like [EPIC] Prefix to maintain consistency across the backlog.
  • Task Splitting: Guides splitting epics into actionable tasks and linking them to dependent work.
  • Diagrams: Supports Mermaid diagrams for architecture or data flow within the epic description.
  • Figma Integration: Includes guidance for linking Figma designs and UI specs when available.
  • Output Guidelines: Prescribes how to structure content for Jira UI or MCP integration.

Quick Start

Provide a Jira epic titled with the [EPIC] prefix and fill in the Feature Overview, Requirements, Technical Considerations, and Implementation Checklist using the Epic Template.

Frequently Asked Questions about jira-epic

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create Jira epics for large features using a standardized template?

To create Jira epics for large features, use a standardized Epic Template containing Feature Overview, Requirements, Technical Considerations, and Implementation Checklist sections to ensure comprehensive planning and stakeholder alignment.

What is the best way to structure epic titles and requirements for Jira backlog management?

The best way to structure epic titles for Jira backlog management is enforcing an [EPIC] prefix convention, then filling in structured requirements and implementation checklists to maintain consistency across large-scale initiatives.

Can I include architecture diagrams and Figma links within a Jira epic description?

Yes, you can include Mermaid diagrams for architecture or data flow visualization, and add integration guidance for linking Figma designs and UI specs directly within the Jira epic description.

How do I split a large feature epic into actionable tasks in Jira?

To split a large feature epic into actionable tasks in Jira, follow task splitting guidance to break down the multi-component initiative and link the resulting tasks to their dependent work items.

Do I need specific Jira UI or MCP integration settings to output structured epic content?

No specific integration setup is strictly required to plan the content, but the skill prescribes output guidelines for structuring content so it can be directly pasted into the Jira UI or sent via MCP integration.

When should I use a dedicated epic template instead of manually writing Jira issues?

You should use a dedicated epic template instead of manual entry when planning large-scale work or multi-component initiatives, ensuring consistent formatting, technical considerations, and stakeholder alignment across the backlog.