skills.rest
mayurpise
mayurpiseCOMMUNITY
Explore all skills by this author →
Website𝕏@mayurpiseGitHub

jira-create

Create Epic, Stories, and Sub-tasks in Jira from a jira-export.md file via MCP-Jira.

39|6|Updated Jan 21, 2026
Search Tags:#automation#jira#project-management#issue-creation#MCP-Jira#epic-story-subtask#jira-export
One-click install
npx skills add https://github.com/mayurpise/draft --skill jira-create
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jira-create
Source: https://github.com/mayurpise/draft/tree/main/skills/jira-create
Command: npx skills add https://github.com/mayurpise/draft --skill jira-create

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates turning a jira-export.md into actionable Jira issues (Epic, Stories, and Sub-tasks) by leveraging MCP-Jira, reducing manual entry and ensuring traceability from plan to delivery.

Core Features & Use Cases

  • Create Epic, Stories, and Sub-tasks from a Jira export file, preserving the mapping between Draft concepts and Jira entities.
  • Auto-generate jira-export.md if missing and apply it to an active track.
  • Operate within the Draft workflow by loading the current track and applying the export to Jira.

Quick Start

Use the jira-create skill to generate Jira issues from the active track's jira-export.md. If missing, first generate a preview with /draft:jira-preview, then run /draft:jira-create to create the issues.

Frequently Asked Questions about jira-create

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

FAQPage Schema
How do I create Jira issues from a markdown export file?▼

Creating Jira issues from a markdown export file uses MCP-Jira to map Draft concepts into Epics, Stories, and Sub-tasks. It reads the jira-export.md file and automatically generates the corresponding issues in your configured Jira project.

What is the best way to automate Jira Epic, Story, and Sub-task creation?▼

Automating Jira Epic, Story, and Sub-task creation is best handled by processing a structured jira-export.md file. This preserves the mapping between Draft concepts and Jira entities, reducing manual entry while ensuring traceability from plan to delivery.

Do I need MCP-Jira to generate Jira issues from a track export?▼

Yes, MCP-Jira is required to generate Jira issues from a track export. The skill relies on MCP-Jira tooling to issue the necessary MCP calls that create Epics, Stories, and Sub-tasks within your configured Jira project.

How do I create Jira issues if the jira-export.md file is missing?▼

Creating Jira issues when the jira-export.md file is missing requires auto-generating the export first. You can generate a preview using /draft:jira-preview, apply it to the active track, and then run /draft:jira-create to create the issues.

Can I map Draft concepts to Jira entities automatically?▼

Yes, you can map Draft concepts to Jira entities automatically. The skill processes the jira-export.md file and preserves the hierarchical mapping between Draft concepts and Jira entities when creating Epics, Stories, and Sub-tasks.

What are the limitations of using jira-export for issue creation?▼

The limitations of using jira-export for issue creation include requiring a configured Jira project for issuing MCP calls and dependency on MCP-Jira tooling. Without these prerequisites, the automated issue generation process cannot execute successfully.

Related Skills

Explore More Software Engineering Skills→
albertoiruruetaalbertoirurueta

create-jira-ticket

Draft and file a Jira ticket with project and issue type selection.

Community
Intermediate
mayurpisemayurpise
39

jira-preview

Generate a Jira export file from a track plan for review.

Community
Intermediate
lujihlujih
188

webnovel-write

Orchestrate webnovel writing workflows with drafting, review, and Git-backed backups.

Community
Advanced
k3sdtwk3sdtw

jira

Create Task, Bug, and Story issues in Jira from templates.

Community
Basic