Create Jira Epic

Create Jira epics with scope, acceptance criteria, and parent feature linkage.

112|305|Updated Oct 10, 2025
One-click install
npx skills add https://github.com/openshift-eng/ai-helpers --skill create-jira-epic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Create Jira Epic
Source: https://github.com/openshift-eng/ai-helpers/tree/main/plugins/jira/skills/create-epic
Command: npx skills add https://github.com/openshift-eng/ai-helpers --skill create-jira-epic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the guesswork and inconsistency in creating well-structured Jira epics, ensuring proper scope definition and parent linking from the start.

Core Features & Use Cases

  • Interactive Epic Creation: Guides users through defining objectives, scope, acceptance criteria, and timeframe.
  • Project-Specific Conventions: Automatically applies field mappings and requirements for specific Jira projects.
  • Use Case: When your team needs to create a multi-cluster metrics aggregation epic for ROSA HCP, this Skill ensures proper component assignment, epic name field population, and parent feature linking.

Quick Start

Use the Create Jira Epic skill to create a new epic in the CNTRLPLANE project for multi-cluster observability with parent feature CNTRLPLANE-100.

Frequently Asked Questions about Create Jira Epic

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a well-structured epic in Jira with proper parent linking?

Creating a Jira epic requires defining the epic name, summary, description, acceptance criteria, and timeframe, then linking it to a parent feature. This Skill guides you through each field to ensure consistency with your project's standards and guarantees parent-feature linkage for compatibility across Jira configurations.

What fields are mandatory when creating a Jira epic?

The epic name field is mandatory. Beyond that, this Skill enforces description and acceptance criteria alignment with your project standards, ensures timeboxing is set, and requires explicit parent-feature linkage to maintain proper work structure.

Can I automate epic creation across multiple Jira projects with different field requirements?

Yes. This Skill applies project-specific field mappings and requirements automatically, so epics created in different Jira server projects follow their respective conventions without manual configuration of scope, naming, or parent linking.

How do I ensure my team's epics follow project standards for scope and acceptance criteria?

This Skill enforces mandatory fields and aligns epic descriptions and acceptance criteria with your project standards during creation. It guides teams through defining objectives, scope, and acceptance criteria interactively to eliminate inconsistency.

What's the best way to structure work when creating multi-cluster observability epics in Jira?

Use this Skill to create epics with correct component assignment, proper epic name population, and parent feature linking from the start. This ensures multi-cluster metrics aggregation work is scoped consistently and tracked within your feature hierarchy.

Do I need to manually link epics to parent features, or is that handled automatically?

This Skill guarantees parent-feature linkage as part of epic creation, enforcing explicit parent linking for compatibility. You specify the parent feature during the guided creation process rather than linking afterward.