jira-epic

Create Jira epics for large features using a standard template.

Updated Apr 9, 2025
One-click install
npx skills add https://github.com/D4nitrix13/dotfiles-tmp --skill jira-epic-d4nitrix13
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-epic
Source: https://github.com/D4nitrix13/dotfiles-tmp/tree/main/.config/opencode/skill/jira-epic
Command: npx skills add https://github.com/D4nitrix13/dotfiles-tmp --skill jira-epic-d4nitrix13

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Large features spanning multiple components often suffer from scope creep and misalignment between teams. This skill standardizes Jira epic creation by enforcing a consistent template and workflow, improving clarity, ownership, and traceability across initiatives.

Core Features & Use Cases

  • Generates Jira epics following the [EPIC] format with a structured feature overview, requirements, and technical considerations.
  • Provides templates for cross-team work involving API, UI, and SDK efforts, ensuring consistent documentation and handoffs.
  • Supports large-scale initiatives such as new views/pages and major refactors that require multi-component coordination.

Quick Start

To create an epic for a large feature, ask to generate a Jira epic following the provided conventions and fill in the epic template and diagrams as needed.

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 spanning multiple components?

To create Jira epics for large features, this skill automates epic generation by enforcing a standard template covering feature overviews, requirements, technical considerations, and implementation checklists for cross-team coordination.

What should a Jira epic template include for cross-team API and UI work?

A Jira epic template for cross-team API and UI work should include a feature overview, requirements sections, technical considerations, implementation checklists, diagrams, and task splitting guidance to ensure consistent documentation and handoffs.

When do I need a standardized Jira epic workflow for project management?

You need a standardized Jira epic workflow when managing large-scale initiatives like new views, major refactors, or API, UI, and SDK efforts that require multi-component coordination to prevent scope creep and team misalignment.

Can I use this approach for major refactors and new view initiatives in Jira?

Yes, this approach supports large-scale initiatives including major refactors and new views or pages by applying a consistent epic format that improves clarity, ownership, and traceability across multiple teams.

What is the best way to structure Jira epics to prevent scope creep?

The best way to structure Jira epics to prevent scope creep is to enforce a consistent template with defined requirements, technical considerations, and task splitting guidance, ensuring clear ownership and traceability across initiatives.