work-items-to-jira

Name: work-items-to-jira
Author: testdouble

122stars12forks

How to install work-items-to-jira?

testdouble/han/work-items-to-jira

$npx -y skills add testdouble/han --skill work-items-to-jira

Installs into the current project.

Summary

Break a work-items.md file (produced by /plan-work-items) into independently-grabbable Jira tickets, one per slice, in a single Jira project. Use when you want to turn a work-items file into Jira tickets, publish work items as Jira issues, or create implementation tickets that ca

Files · 1

View on GitHub

SKILL.md

1	# Work Items to Jira Tickets
2
3	Take an already-broken-down `work-items.md` file (produced by `/plan-work-items`) and publish each slice as a Jira ticket in a single target project.
4
5	The breakdown work — drafting slices, assigning symbolic IDs, specifying dependencies, inventorying references — has already been done upstream. This skill's job is to validate the format, confirm the target, create one ticket per slice through the Atlassian MCP server, link the within-file dependencies, and place the tickets in the chosen column.
6
7	## Rules
8
9	- Every slice posts into one Jira project. This skill does not split work across repos or projects. A `work-items.md` that names multiple code repos still produces tickets in the single project you name; the repo prose is informational only.
10	- Dependencies are within-file only. Every SYM named in a `Depends on` line must resolve to another slice in the same file. A `Depends on` that names an unknown SYM is a format error to surface for repair.
11	- Symbolic-ID prefixes: accept whatever the input uses. Any uppercase prefix shape is valid (`W-N`, `V2-N`, `EV-N`, …); the prefix has no effect on Jira placement.
12	- Defaults: issue type `Story`, no assignee, reporter taken from the Atlassian MCP identity, and the project's initial status (Backlog). Each is overridable per run; nothing is assigned or moved unless asked.
13	- Parenting is optional and determines the child issue type. `--parent <KEY>` accepts an epic or a standard issue (a story, task, or bug). Under an epic, each item is a standard issue (default `Story`). Under a story (any standard issue), each item is a subtask (default the project's subtask issue type). You cannot parent under a subtask. `--epic <KEY>` is a deprecated alias for `--parent`; it resolves the same way regardless of the named issue's actual type.
14	- Every slice ticket MUST carry the reference artifacts an implementer needs — API/event contracts, design references, schema docs, runbooks, ADRs, coding standards. Tickets that consume an HTTP endpoint or event payload MUST reference the contract section that defines it. Full include/exclude list in [references/reference-artifact-inventory.md](./references/reference-artifact-inventory.md).
15	- NEVER include process artifacts in ticket descriptions. Excluded: iteration histories, decision logs, review findings, team findings, facilitation summaries, gap analyses, and anything under an `artifacts/` subfolder of the plan that is not a contract or design reference.
16	- No screenshot upload or image embedding. Design references are carried as links, not uploaded into Jira. See [references/jira-ticket-template.md](./references/jira-ticket-template.md).
17
18	## Process
19
20	### 0. Atlassian MCP preflight (hard requirement)
21
22	This skill cannot run without a configured and connected Atlassian MCP server. Confirm it is reachable by calling `mcp__claude_ai_Atlassian__getAccessibleAtlassianResources` to retrieve the cloud ID(s). If the tool is unavailable, the call errors, or it returns no accessible resources, stop immediately and tell the user the skill requires the Atlassian MCP server to be installed, configured, and authenticated. Do not fall back to any other publishing target.
23
24	If more than one site is accessible, note which are available; you will confirm the right one while resolving the project in Step 3.
25
26	### 1. Locate the work-items file
27
28	If the path is not provided, ask for it. The input is a single `work-items.md` produced by `/plan-work-items`. Read

People who liked this also viewed

6 picks

Type

work-items-to-jira

122stars12forks

View on GitHub

How to install work-items-to-jira?

testdouble/han/work-items-to-jira

$npx -y skills add testdouble/han --skill work-items-to-jira

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Work Items to Jira Tickets
2
3	Take an already-broken-down `work-items.md` file (produced by `/plan-work-items`) and publish each slice as a Jira ticket in a single target project.
4
5	The breakdown work — drafting slices, assigning symbolic IDs, specifying dependencies, inventorying references — has already been done upstream. This skill's job is to validate the format, confirm the target, create one ticket per slice through the Atlassian MCP server, link the within-file dependencies, and place the tickets in the chosen column.
6
7	## Rules
8
9	- Every slice posts into one Jira project. This skill does not split work across repos or projects. A `work-items.md` that names multiple code repos still produces tickets in the single project you name; the repo prose is informational only.
10	- Dependencies are within-file only. Every SYM named in a `Depends on` line must resolve to another slice in the same file. A `Depends on` that names an unknown SYM is a format error to surface for repair.
11	- Symbolic-ID prefixes: accept whatever the input uses. Any uppercase prefix shape is valid (`W-N`, `V2-N`, `EV-N`, …); the prefix has no effect on Jira placement.
12	- Defaults: issue type `Story`, no assignee, reporter taken from the Atlassian MCP identity, and the project's initial status (Backlog). Each is overridable per run; nothing is assigned or moved unless asked.
13	- Parenting is optional and determines the child issue type. `--parent <KEY>` accepts an epic or a standard issue (a story, task, or bug). Under an epic, each item is a standard issue (default `Story`). Under a story (any standard issue), each item is a subtask (default the project's subtask issue type). You cannot parent under a subtask. `--epic <KEY>` is a deprecated alias for `--parent`; it resolves the same way regardless of the named issue's actual type.
14	- Every slice ticket MUST carry the reference artifacts an implementer needs — API/event contracts, design references, schema docs, runbooks, ADRs, coding standards. Tickets that consume an HTTP endpoint or event payload MUST reference the contract section that defines it. Full include/exclude list in [references/reference-artifact-inventory.md](./references/reference-artifact-inventory.md).
15	- NEVER include process artifacts in ticket descriptions. Excluded: iteration histories, decision logs, review findings, team findings, facilitation summaries, gap analyses, and anything under an `artifacts/` subfolder of the plan that is not a contract or design reference.
16	- No screenshot upload or image embedding. Design references are carried as links, not uploaded into Jira. See [references/jira-ticket-template.md](./references/jira-ticket-template.md).
17
18	## Process
19
20	### 0. Atlassian MCP preflight (hard requirement)
21
22	This skill cannot run without a configured and connected Atlassian MCP server. Confirm it is reachable by calling `mcp__claude_ai_Atlassian__getAccessibleAtlassianResources` to retrieve the cloud ID(s). If the tool is unavailable, the call errors, or it returns no accessible resources, stop immediately and tell the user the skill requires the Atlassian MCP server to be installed, configured, and authenticated. Do not fall back to any other publishing target.
23
24	If more than one site is accessible, note which are available; you will confirm the right one while resolving the project in Step 3.
25
26	### 1. Locate the work-items file
27
28	If the path is not provided, ask for it. The input is a single `work-items.md` produced by `/plan-work-items`. Read

People who liked this also viewed

6 picks

Type