tdd-to-jira-tickets

Name: tdd-to-jira-tickets
Availability: InStock
Author: jonball4

Convert markdown Technical Design Documents into structured Jira tickets with dependency links.

1|Updated Jan 27, 2026

Search Tags:#automation #tdd #dependency management #project planning #jira #ticket creation

Ready to run

npx skills add https://github.com/jonball4/claude-dev-skills --skill tdd-to-jira-tickets

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd-to-jira-tickets
Source: https://github.com/jonball4/claude-dev-skills/tree/main/skills/tdd-to-jira-tickets
Command: npx skills add https://github.com/jonball4/claude-dev-skills --skill tdd-to-jira-tickets

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, mistletoe, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of Jira tickets and dependency links from Technical Design Document (TDD) markdown specifications, streamlining project planning and ensuring accurate task breakdown.

Core Features & Use Cases

Automated Ticket Creation: Generates Jira tickets directly from structured markdown.
Dependency Linking: Automatically establishes 'Blocks' relationships between tickets based on TDD specifications.
Use Case: Convert a detailed TDD for a new feature into a set of Jira tickets, complete with parent epics, labels, priorities, and explicit dependencies, ready for sprint planning.

Quick Start

Use the tdd-to-jira-tickets skill to convert the TDD document located at '/path/to/your/tdd-tickets.md' into Jira tickets.

Frequently Asked Questions about tdd-to-jira-tickets

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

FAQPage Schema

How do I convert a markdown Technical Design Document into Jira tickets with dependencies?▼

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.

Can I automate Jira ticket creation and dependency linking from a TDD markdown file?▼

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.

What is the best way to break down a feature design document into granular Jira tasks for sprint planning?▼

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.

Does this automated ticket creation process support idempotent processing for Jira REST API requests?▼

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.

What markdown structure do I need to define parent epics, story points, and inter-ticket dependencies?▼

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.