tdd-to-jira-tickets

To convert a markdown Technical Design Document into Jira tickets, this Skill parses TDD files and automates ticket creation via the Jira REST API. It establishes explicit 'Blocks' dependency links between tasks and updates the original markdown with the newly generated Jira keys.

Yes, you can automate Jira ticket creation and dependency linking directly from TDD markdown files. The Skill extracts ticket metadata like type, parent, labels, priority, and story points, then uses the Jira REST API to create tickets and define inter-ticket dependencies.

The best way to break down a feature design document into granular Jira tasks is to use this Skill to parse structured markdown into individual tickets. It automatically defines metadata such as parent epics, labels, and story points, preparing the breakdown for sprint planning.

Yes, this automated ticket creation process supports idempotent processing for Jira REST API requests. Idempotency ensures that running the Skill multiple times on the same TDD markdown file does not create duplicate tickets, safely updating existing entries instead.

You need a structured markdown format that specifies ticket metadata such as type, parent, labels, priority, story points, and explicit dependencies. The Skill parses these TDD specifications to generate the corresponding Jira tickets and establish the required 'Blocks' relationships.