x-create-jira-epic

Parse epic markdown files and create Jira Epics via MCP.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/edercnj/ia-dev-environment --skill x-create-jira-epic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: x-create-jira-epic
Source: https://github.com/edercnj/ia-dev-environment/tree/main/src/main/resources/claude/skills/x-create-jira-epic
Command: npx skills add https://github.com/edercnj/ia-dev-environment --skill x-create-jira-epic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables teams to convert locally authored epic markdown files into Jira Epics and keep the local file synchronized by writing the Jira key back into the source file.

Core Features & Use Cases

  • Parse a local epic file (epic-XXXX.md) to extract title, overview, status, and Jira key.
  • Create a Jira Epic via MCP using the discovered project and the extracted content.
  • Sync the Jira key back into the local epic file and use labels for bidirectional lookup.
  • Integrates with references/jira-field-mapping.md for field-to-Jira mappings.

Quick Start

Run the skill with the path to the local epic markdown file to create the Jira Epic and sync the Jira key back to the file.

Frequently Asked Questions about x-create-jira-epic

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

FAQPage Schema
How do I create Jira Epics from local markdown files?

To create Jira Epics from local markdown files, this Skill parses epic-XXXX.md content to extract the title and overview, creates the Jira Epic via MCP, and syncs the Jira key back into the source file.

How does bidirectional traceability work between local epic files and Jira?

Bidirectional traceability works by writing the generated Jira key back into your local markdown file and applying labels, ensuring you can trace the local epic document to the corresponding Jira Epic and vice versa.

Can I use frontmatter to drive Jira Epic creation from markdown?

Yes, you can use frontmatter-driven discovery to extract the title, status, and Jira key from your local markdown file before publishing the corresponding Jira Epic through the MCP integration.

Do I need a specific project setup to sync Jira keys to local epic files?

You need a chosen Jira project configured for MCP-based Epic creation, and the Skill uses references/jira-field-mapping.md to ensure local markdown content maps correctly to the corresponding Jira fields.

What is the best way to automate publishing local epics to Jira?

The best way to automate publishing local epics to Jira is running this Skill with the path to your local epic markdown file, which parses the content, creates the Jira Epic, and updates the file with the new Jira key automatically.

How to map local markdown fields to Jira Epic fields?

You map local markdown fields to Jira Epic fields by integrating with the references/jira-field-mapping.md component, which defines the field-to-Jira mappings used during MCP-based Epic creation.