work-items-to-jira

Convert work-items.md slices into Jira tickets within a single project.

198|19|Updated May 7, 2026
One-click install
npx skills add https://github.com/testdouble/han --skill work-items-to-jira
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work-items-to-jira
Source: https://github.com/testdouble/han/tree/main/han-atlassian/skills/work-items-to-jira
Command: npx skills add https://github.com/testdouble/han --skill work-items-to-jira

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Converts a single work-items.md file produced by /plan-work-items into a set of Jira tickets, one per slice, all within a single Jira project. This enables deterministic tracking, dependency hygiene, and clear artifact references without needing per-repo ticketing.

Core Features & Use Cases

  • Turn each slice in work-items.md into an independent Jira ticket in a single project.
  • Enforce intra-file dependencies by ensuring each "Depends on" reference resolves to another slice in the same file.
  • Support parenting semantics: epic-based grouping for standard issues or story-based subgrouping for subtasks, depending on the chosen parent.
  • Carry plan-level references and design constraints as ticket References; include API contracts, design references, ADRs, and coding standards as applicable.
  • Update slice headings with the created Jira key to support idempotent re-runs and easier dependency linking.
  • Requires an Atlassian MCP server for publishing and authentication.

Quick Start

Run the skill after preparing work-items.md to publish all slices as Jira tickets within the configured project using the MCP-connected Jira instance.

Frequently Asked Questions about work-items-to-jira

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

FAQPage Schema
How do I convert a markdown planning file into Jira tickets?

To convert a work-items.md file into Jira tickets, the skill parses each slice into an independent issue within a single configured Jira project. It validates headings and dependencies before creating the tickets.

How do I enforce intra-file dependencies when creating Jira issues from markdown?

To enforce dependencies when creating Jira issues, the skill validates that every "Depends on" reference in the markdown resolves to another slice in the same file. This ensures dependency hygiene before publishing.

Do I need an Atlassian MCP server to publish work items to Jira?

Yes, you need a configured Atlassian MCP server to authenticate and publish work items to Jira. The skill relies on this server connection to create tickets and update slice headings with Jira keys.

Can I group Jira tickets as subtasks under a parent story from a markdown file?

Yes, you can group Jira tickets as subtasks under a parent story or within an epic. The skill supports parenting semantics based on the chosen parent type when publishing slices from the markdown file.

How does publishing markdown slices to Jira handle plan-level references and ADRs?

Publishing markdown slices to Jira carries plan-level references, API contracts, and ADRs directly into the ticket References field. This preserves design constraints and coding standards for each issue.

What happens if I re-run the Jira ticket creation process on the same markdown file?

When you re-run the Jira ticket creation process, the skill updates slice headings with the created Jira key. This idempotent behavior supports re-runs and makes dependency linking easier without duplicating tickets.