jira-epic

Create Jira epics with standardized titles, overviews, requirements, and Mermaid diagrams.

2|Updated Jul 29, 2025
One-click install
npx skills add https://github.com/kurojs/ender4-dots --skill jira-epic-kurojs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-epic
Source: https://github.com/kurojs/ender4-dots/tree/main/.config/opencode/skill/jira-epic
Command: npx skills add https://github.com/kurojs/ender4-dots --skill jira-epic-kurojs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Large feature work often lacks cohesive planning; this skill provides a standardized Jira Epic blueprint to organize multi-component initiatives.

Core Features & Use Cases

  • Epic Title conventions: Promotes consistent naming with the format [EPIC] Feature Name.
  • Structured content: Includes Feature Overview, Requirements, Technical Considerations, and Implementation Checklists.
  • Diagrams & Planning: Encourages Mermaid diagrams and data-flow reasoning for design clarity.

Quick Start

Generate a Jira epic using the Epic Title Conventions and populate the Feature Overview, Requirements, and Technical Considerations sections.

Frequently Asked Questions about jira-epic

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

FAQPage Schema
How do I structure a Jira epic for a large feature spanning multiple components?

To structure a Jira epic for large features, apply a standardized format containing Feature Overview, Requirements, Technical Considerations, and Implementation Checklists to ensure cohesive planning across multiple components.

What is the best way to write requirements for a Jira epic involving major refactors?

Writing requirements for major refactors involves detailing Technical Considerations alongside structured Feature Overview and Implementation Checklist sections to capture data-flow reasoning and ensure clear project management.

Can I include Mermaid diagrams and Figma references in my Jira epic planning?

Yes, you can include Mermaid diagrams and Figma references in Jira epic planning. Adding Mermaid diagrams provides data-flow reasoning and design clarity, while Figma references can be optionally attached for visual context.

Does this Jira epic format work for initiatives combining API and UI work?

Yes, this Jira epic format applies to initiatives combining API and UI work. It standardizes planning for new views, pages, major refactors, or any multi-component initiative requiring a cohesive Epic and implementation plan.

What naming conventions should I use for Jira epics managing agile project tasks?

For Jira epics managing agile tasks, promote consistent naming by using the format `[EPIC] Feature Name`. This standardizes large feature work and ensures cohesive planning across multi-component initiatives.