jira-epic

Create Jira epics with [EPIC] titles and structured sections.

Updated Feb 5, 2025
One-click install
npx skills add https://github.com/CrisGO0510/My-Linux-Dotfiles --skill jira-epic-crisgo0510
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-epic
Source: https://github.com/CrisGO0510/My-Linux-Dotfiles/tree/main/.config/opencode/skill/jira-epic
Command: npx skills add https://github.com/CrisGO0510/My-Linux-Dotfiles --skill jira-epic-crisgo0510

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the creation of Jira epics to organize large features and multi-component initiatives, reducing manual planning overhead and ensuring consistent epic structure.

Core Features & Use Cases

  • Epic templating: Generates a structured epic with sections for overview, requirements, and technical considerations.
  • Conformance to conventions: Applies the [EPIC] title format and standard fields for traceability.
  • Use Case: When starting a major feature that touches API, UI, and SDK work, you can generate a ready-to-use epic and a task breakdown.

Quick Start

Use the epic creation prompts to generate a Jira epic titled "[EPIC] {Feature Name}" with sections for Feature Overview, Requirements, and Technical Considerations.

Frequently Asked Questions about jira-epic

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

FAQPage Schema
How do I create a Jira epic for a multi-component feature?

To create a Jira epic for a multi-component feature, use this skill to automatically generate a structured epic following the [EPIC] title convention with sections for Feature Overview, Requirements, and Technical Considerations.

What is the standard format for structuring large feature work in Jira epics?

The standard format for Jira epics includes an enforced [EPIC] title prefix and a template containing sections for Feature Overview, Requirements, Technical Considerations, and a Mermaid diagram block to ensure consistent traceability.

How do I plan cross-team initiatives like API changes and refactors in Jira?

Plan cross-team initiatives by generating a Jira epic that consolidates API changes and refactors into a structured template, enabling organized cross-team planning and reducing manual project management overhead.

Can I include Mermaid diagrams in my Jira epic template?

Yes, you can include Mermaid diagrams in your Jira epic template, as the skill supports a dedicated Mermaid diagram block within the Technical Considerations section for visual technical planning.

Does this skill enforce specific naming conventions for Jira project management?

Yes, the skill enforces the [EPIC] title naming convention for project management, ensuring that all large features and multi-component initiatives maintain consistent traceability across cross-team planning workflows.

What is the best way to break down large features into actionable Jira tasks?

The best way to break down large features is to generate a ready-to-use Jira epic with standardized sections for requirements and technical considerations, which then supports a detailed task breakdown for multi-component work.