skills.rest
SoyJuanMa
SoyJuanMaCOMMUNITY
Explore all skills by this author →
GitHub

jira-epic

Create Jira epics with standardized sections for multi-feature initiatives.

Updated Jul 10, 2025
Search Tags:#planning#agile#jira#workflows#epic#project-management
One-click install
npx skills add https://github.com/SoyJuanMa/Nvim_Back --skill jira-epic-soyjuanma
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jira-epic
Source: https://github.com/SoyJuanMa/Nvim_Back/tree/main/opencode/skill/jira-epic
Command: npx skills add https://github.com/SoyJuanMa/Nvim_Back --skill jira-epic-soyjuanma

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Epics spanning multiple features and teams often lead to planning misalignment; this skill automates the creation and structuring of Jira epics to align stakeholders and streamline workflows.

Core Features & Use Cases

  • Epic scaffolding: Create a standardized epic title, description, and sections following Prowler's conventions.
  • Consistent templates: Provide a reusable epic template with sections like Overview, Requirements, Technical Considerations, Implementation Checklist.
  • Stakeholder alignment: Helps product managers and engineers quickly generate a shared baseline for planning.
  • Use Case: When starting a multi-component initiative, generate a Jira epic that captures scope and linking issues.

Quick Start

Ask the assistant to generate a Jira epic with a standardized title, description, and templates for a multi-feature initiative.

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

To create a Jira epic for a multi-component initiative, generate a standardized title and structured sections including Overview, Requirements, Technical Considerations, and an Implementation Checklist to align stakeholders across API, UI, and SDK efforts.

What sections are needed for agile project planning of large features in Jira?▼

Agile project planning for large Jira features requires standardized sectioned content like Overview, Requirements, Technical Considerations, and an Implementation Checklist, often supplemented with Mermaid diagram guidance to map workflows.

When should I use a Jira epic for cross-cutting development efforts?▼

You should use a Jira epic for cross-cutting development efforts when a multi-feature initiative spans multiple components like API, UI, and SDK, requiring a shared baseline to prevent planning misalignment among teams.

What is the best way to structure epic requirements for engineering teams?▼

The best way to structure epic requirements for engineering teams is using a consistent template with standardized naming conventions, capturing scope through Technical Considerations and linking related issues in an Implementation Checklist.

Can I include Mermaid diagrams in Jira epic descriptions for project management?▼

Yes, you can include Mermaid diagrams in Jira epic descriptions to visually guide technical considerations and workflows for product managers and engineers during multi-feature initiative planning.

Related Skills

Explore More Product & Management Skills→
loianeloiane
50

epic-slicing-planning

Plan Epic-level architecture and vertical-slice roadmaps for large features.

Community
Advanced
SentioLabsSentioLabs
1

atlassian-spec-to-backlog

Convert Confluence specification documents into structured Jira backlogs with Epics and linked tickets.

Official
Intermediate
valec3valec3
1

jira-epic

Create Jira epics with standardized templates and Mermaid diagrams.

Community
Advanced
dtabordadtaborda

jira-epic

Generate Jira epics from feature briefs using standardized templates and conventions.

Community
Advanced