jira-epic

Create Jira epics with standardized sections and MCP-compatible fields.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/giruclawbot/giru-backup --skill jira-epic-giruclawbot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-epic
Source: https://github.com/giruclawbot/giru-backup/tree/main/skills/jira-epic
Command: npx skills add https://github.com/giruclawbot/giru-backup --skill jira-epic-giruclawbot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes ambiguity and manual formatting when creating large Jira epics by providing a consistent, Prowler-standard template and step-by-step guidance so teams can quickly produce comprehensive, actionable epics.

Core Features & Use Cases

  • Standardized epic template with sections for Feature Overview, Requirements, Technical Considerations, Implementation Checklist, and Diagrams.
  • Guidance for splitting epics into child tasks, naming conventions, task dependencies, and suggested task tables to accelerate backlog planning.
  • Jira MCP integration details and required custom fields to create and update epics programmatically for projects that require specific team and work-item fields.
  • Use Case: Product and engineering teams drafting a new multi-component feature (API + UI + SDK) or a major refactor can use this Skill to produce a ready-to-import epic and its child tasks.

Quick Start

Ask the assistant to "Create an epic titled '[EPIC] Feature Name' with a two-paragraph overview, organized requirements, technical considerations, an implementation checklist, mermaid diagrams, and suggested child tasks."

Frequently Asked Questions about jira-epic

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

FAQPage Schema
How do I create standardized Jira epics for multi-component features?

Jira epics for multi-component features are created using a standardized template that includes feature overview, organized requirements, technical considerations, implementation checklists, and mermaid diagrams. This ensures large initiatives like API, UI, and SDK work are comprehensive and ready for backlog planning.

What is the best way to structure a Jira epic for a major refactor?

Structuring a Jira epic for a major refactor involves using a standard template with sections for feature overview, requirements, technical considerations, an implementation checklist, and mermaid diagrams. This removes manual formatting ambiguity and provides step-by-step guidance for engineering teams.

How does Jira MCP integration handle custom fields for epic creation?

Jira MCP integration handles custom fields by producing epics with MCP-compatible Jira fields, including required team custom fields. This allows teams to programmatically create and update epics for projects that require specific work-item configurations.

Can I use this approach to split epics into child tasks with dependencies?

Yes, you can split epics into child tasks with dependencies. The standardized template provides guidance on naming conventions, task dependencies, and suggested task tables to accelerate backlog planning for multi-task initiatives.

When do I need a standardized template for Jira task creation?

You need a standardized template for Jira task creation when drafting large features such as new views, major refactors, multi-component initiatives, and combined API, UI, and SDK work. It removes ambiguity and manual formatting to quickly produce comprehensive, actionable epics.