jira-epic

Generate Jira epics using Prowler's standard Epic Template.

Updated Mar 10, 2025
One-click install
npx skills add https://github.com/alvaldes/alvaldes.dots --skill jira-epic-alvaldes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-epic
Source: https://github.com/alvaldes/alvaldes.dots/tree/main/opencode/skill/jira-epic
Command: npx skills add https://github.com/alvaldes/alvaldes.dots --skill jira-epic-alvaldes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating Jira epics for large features can be time-consuming and prone to inconsistencies. This skill automates epic creation by following Prowler's standard format, ensuring uniform structure when users request an epic, a large feature, or a multi-task initiative.

Core Features & Use Cases

  • Automatically generates Jira epics using the Prowler epic template for consistent documentation.
  • Supports large features spanning multiple components or major refactors, including API, UI, and SDK work.
  • Enforces conventions for epic titles and required sections, enabling clear planning and traceability.

Quick Start

Ask me to create a Jira epic for a large feature and I will generate it using the standard 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 a Jira epic for a large feature spanning multiple teams?

To create a Jira epic for large features, this skill applies a standard epic template covering multi-team initiatives like UI, API, and SDK work, ensuring titles follow the [EPIC] Feature Name convention and include required technical considerations and implementation checklists.

When should I use an epic instead of a regular Jira task for agile project planning?

Use a Jira epic for agile project planning when managing major refactors or large features spanning multiple components, as it enforces required sections and implementation checklists that regular tasks lack for multi-team initiatives.

What is the standard format for structuring Jira epic documentation?

Standard Jira epic documentation requires titles following the [EPIC] Feature Name convention, alongside structured technical considerations, required sections, and an implementation checklist to ensure consistent planning and traceability.

Can I generate Jira epics for major refactoring projects using agile documentation standards?

Yes, you can generate Jira epics for major refactoring projects using agile documentation standards, applying the standard epic template to ensure uniform structure, technical considerations, and implementation checklists across refactoring initiatives.

Does this Jira epic template work for features spanning API, UI, and SDK components?

Yes, this Jira epic template specifically supports features spanning API, UI, and SDK components, generating uniform documentation with required sections and implementation checklists for multi-team initiatives.

Why do my Jira epic titles and documentation lack consistency across large features?

Jira epic titles and documentation lack consistency without a standard template enforcing the [EPIC] Feature Name convention, required sections, technical considerations, and implementation checklists for large features.