Filing Breakdown Tasks into Jira

This skill owns the tech-breakdown half of ticketing: turning a tasks.md decomposition into a parented set of ticket drafts. It does not file them. Once the drafts are ready it hands off to filing-jira-tickets, which reads the target project's create screen, previews each ticket, takes approval, and creates and links them through the Atlassian MCP write tools.

Tickets are read outside the breakdown's context, so translate each task entry into a ticket that stands on its own — never paste the decomposition label.

Step 1 — Build the ticket tree

Read tasks.md and its sibling breakdown.md. The pair lives in one breakdown folder (<team>/<JIRA-KEY>-<short-slug>/) in a bitwarden/tech-breakdowns checkout — Glob for it when the user gave no path, and ask which one when more than one matches. If breakdown.md is missing or names no epic key, ask for the key.

Establish the hierarchy before drafting any fields:

• The breakdown's epic is the parent. Take its key from breakdown.md. If no epic exists, ask whether to create one or attach children to an existing key — do not guess a key. Confirm the key is an Epic (get_issue, check issuetype) before parenting under it.
• Each task entry becomes one child — Story by default; Task or Bug only if the entry says so.
• For each child, capture its Blocked by and Depends on.

Completion criterion: an echoed tree — epic key, then the ordered children with type and parent — where the child count matches the task count in tasks.md.

Step 2 — Draft each child ticket