jira-epic

Generate a standardized Jira epic template with requirements and implementation checklist.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/himuraxkenji/dotfiles-nix --skill jira-epic-himuraxkenji
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-epic
Source: https://github.com/himuraxkenji/dotfiles-nix/tree/main/opencode/skill/jira-epic
Command: npx skills add https://github.com/himuraxkenji/dotfiles-nix --skill jira-epic-himuraxkenji

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Jira epics for large features spanning multiple components are often inconsistently defined, making planning and cross-team coordination difficult. This skill standardizes epic creation by providing a reusable template and guidance.

Core Features & Use Cases

  • Epic Template: Provides a complete Jira epic structure including title, overview, requirements, technical considerations, and an implementation checklist.
  • Standard Naming & Conventions: Enforces the [EPIC] Feature Name convention to improve searchability and governance.
  • Output for Task Splitting: Produces a structured epic that downstream tasks can be generated from, with optional diagrams and Figma integration guidance.

Quick Start

Prompt me to generate a Jira epic using this template, and I will return the full structured epic ready for Jira import.

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 standardized Jira epic template for large features?

To create a standardized Jira epic template, generate a structured epic with Feature Overview, Requirements, Technical Considerations, and an Implementation Checklist. This ensures consistent naming conventions and cross-team coordination for multi-component features.

What sections should a Jira epic include for multi-team initiatives?

A Jira epic for multi-team initiatives should include Feature Overview, Requirements, Technical Considerations, and an Implementation Checklist. Optional diagrams and Figma links can be integrated to provide additional context for cross-team coordination.

Can I use this epic template for major refactors spanning API, UI, and SDK work?

Yes, this epic template is applicable to major refactors requiring API, UI, and SDK work. It generates a ready-to-import epic structure that standardizes planning across multiple components and teams.

What is the best way to structure Jira epics for cross-team coordination?

The best way to structure Jira epics for cross-team coordination is to enforce a standard naming convention like [EPIC] Feature Name. This improves searchability and governance while producing a structured epic for downstream task generation.

How do I split downstream tasks from a structured Jira epic?

To split downstream tasks from a structured Jira epic, use the generated Implementation Checklist and Requirements sections. This structured output provides the foundation for generating granular tasks across multiple components.