jira-create-epic-from-plan

Create Jira epics and child tickets from markdown or OpenSpec plans.

154|28|Updated Aug 31, 2018
One-click install
npx skills add https://github.com/commercetools/ui-kit --skill jira-create-epic-from-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-create-epic-from-plan
Source: https://github.com/commercetools/ui-kit/tree/main/.agents/skills/jira-create-epic-from-plan
Command: npx skills add https://github.com/commercetools/ui-kit --skill jira-create-epic-from-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the manual, error-prone process of translating project plans into a structured Jira epic, individual tickets, and explicit dependency links so teams can move from planning to execution faster and with fewer mistakes.

Core Features & Use Cases

  • Create a concise epic description and suggest multiple epic name options that follow project naming conventions, then create the epic in Jira.
  • Parse markdown or OpenSpec plans into discrete tickets with issue types, labels, phase-aware summaries, and acceptance criteria, then batch-create those tickets via the MCP Jira tool.
  • Produce an executable shell script that uses the Jira REST API to create predecessor/successor links (and optionally clean them up), and update the original plan with actual Jira keys and a dependency table.
  • Use Case: Prepare a phased migration or feature rollout plan, preview all tickets and dependencies for stakeholder approval, then create the epic and tickets and run the link script to finalize dependencies.

Quick Start

Use the skill on a plan file path to preview the epic and ticket breakdown and then create the epic and tickets in Jira after explicit approval.

Frequently Asked Questions about jira-create-epic-from-plan

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

FAQPage Schema
How do I create Jira epics and tickets from a markdown project plan?

Creating Jira epics from a markdown plan involves parsing the file to extract phases and tickets, generating markdown descriptions, and batch-creating issues via the Jira MCP tool. This Skill automates that workflow and requires explicit approval before writing any changes to Jira.

Can I automatically set up predecessor and successor dependency links between Jira tickets?

Yes, you can set up predecessor and successor dependency links by running an executable shell script generated by this Skill. The script uses the Jira REST API to create the links between batch-created issues and optionally clean them up, allowing you to finalize dependencies after ticket creation.

Does this Jira automation work with OpenSpec proposals?

Yes, this Jira automation works with OpenSpec proposals by parsing them into discrete tickets with issue types, labels, and acceptance criteria. It extracts the necessary project management data from the OpenSpec format to batch-create issues and map dependency relationships in Jira.

What is the best way to batch-create Jira issues from a phased rollout plan?

The best way to batch-create Jira issues from a phased rollout plan is to use this Skill to preview the epic and ticket breakdown for stakeholder approval. Once approved, it calls the Jira MCP tool to batch-create the issues with phase-aware summaries and then updates the original plan with actual Jira keys.

Do I need explicit approval before this Skill creates issues in Jira?

Yes, explicit user approval is required before any Jira changes are made. The Skill previews the epic and ticket breakdown for stakeholder review, and only proceeds to call the Jira MCP tool to batch-create issues and generate the dependency link script after receiving your confirmation.