jira_epic

Generate Jira epics for large features using Prowler's standard format.

Updated Nov 20, 2025
One-click install
npx skills add https://github.com/JFEspanolito/Template_FrontEnd_NextJS_JF --skill jira-epic-jfespanolito
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira_epic
Source: https://github.com/JFEspanolito/Template_FrontEnd_NextJS_JF/tree/main/AI/skills/curated/jira-epic
Command: npx skills add https://github.com/JFEspanolito/Template_FrontEnd_NextJS_JF --skill jira-epic-jfespanolito

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation of Jira epics for large features, ensuring consistency and adherence to Prowler's standard format.

Core Features & Use Cases

  • Epic Creation: Generates Jira epics for significant features, refactoring, or multi-component initiatives.
  • Standardized Template: Follows a predefined Markdown structure for epics, including overview, requirements, technical considerations, and checklists.
  • Use Case: When a new major feature like "User Profile Redesign" is planned, use this Skill to create a comprehensive epic in Jira, outlining all necessary requirements and technical details.

Quick Start

Use the jira_epic skill to create an epic titled "Onboarding Flow Improvement".

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 or initiative?

Jira epic creation for major features involves generating a standardized format with sections for overview, requirements, technical considerations, implementation checklists, and diagrams. This ensures consistency for large features, major refactoring, and cross-functional API, UI, and SDK work.

What should be included in a Jira epic for major refactoring?

A Jira epic for major refactoring should include a feature overview, requirements, technical considerations, an implementation checklist, and diagrams. Adhering to standard naming conventions ensures the refactoring scope is clearly tracked across API, UI, and SDK components.

When do I need to use a standardized template for Jira epics?

You need a standardized Jira epic template when planning new views, major refactoring, or cross-functional initiatives involving API, UI, and SDK components. It streamlines epic creation and ensures all necessary technical details and requirements are consistently documented.

Can I use this approach to create epics for cross-functional work involving APIs and UIs?

Yes, this approach supports creating epics specifically for cross-functional work involving API, UI, and SDK components. The generated epic includes comprehensive sections for technical considerations and implementation checklists to track these multi-component initiatives effectively.

What is the best way to document technical considerations in a Jira epic?

The best way to document technical considerations in a Jira epic is to use a predefined Markdown structure that includes dedicated sections for requirements, implementation checklists, and diagrams. This ensures all technical details for features and refactoring are clearly outlined.