jira-create

Create Jira Epics and Sub-tasks from Epic documents via Jira MCP workflows.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ryu-qqq/conventionHub --skill jira-create-ryu-qqq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: jira-create
Source: https://github.com/ryu-qqq/conventionHub/tree/main/.claude/skills/jira-create
Command: npx skills add https://github.com/ryu-qqq/conventionHub --skill jira-create-ryu-qqq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Epic 문서를 기반으로 Jira Epic + Sub-task를 일괄 생성합니다. Jira MCP 기반 워크플로우를 활용해 운영합니다.

Core Features & Use Cases

  • Epic 문서를 기반으로 Jira Epic과 Sub-task를 일괄 생성합니다.
  • Jira MCP 기반 워크플로우와 연동하여 추적성을 확보합니다.
  • --dry-run 옵션으로 실제 등록 없이 미리 확인이 가능합니다.
  • Epic 문서에 Jira ID를 자동으로 주석으로 추가합니다.

Quick Start

Use the jira-create skill to generate Jira Epics and Sub-tasks from the most recent epic document.

Frequently Asked Questions about jira-create

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

FAQPage Schema
How do I bulk create Jira Epics with Sub-tasks from a project document?▼

You can bulk create Jira Epics and Sub-tasks from a project document by using this Skill to parse Epic documents and automate Jira registration via Jira MCP workflows. It processes the document structure to generate corresponding Jira issues and nested sub-tasks in one operation.

Can I preview Jira issue creation before committing changes?▼

Yes, you can preview Jira issue creation before committing changes by running the command with the --dry-run option. This validates the Epic document parsing and displays the proposed Jira Epics and Sub-tasks without actually creating any issues in Jira.

How do I assign Jira Sub-tasks to specific users and sprints during bulk import?▼

You can assign Jira Sub-tasks to specific users and sprints during bulk import by passing command-line options like --assignee user, --sprint N, and --priority P. These parameters scope the automatically generated Jira issues to the correct project members and sprint cycles.

Does Jira MCP workflow integration add Jira IDs back to the source Epic document?▼

Jira MCP workflow integration automatically adds the generated Jira IDs back to the source Epic document as annotations. This ensures full traceability between your initial project planning document and the newly created Jira Epics and Sub-tasks.

Can I skip Sub-task generation and only create Jira Epics from a document?▼

Yes, you can skip Sub-task generation and only create Jira Epics by including the --no-subtasks command-line option. This restricts the bulk creation workflow to top-level Epic issues, omitting all downstream nested tasks from the Jira MCP registration process.