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.