| name | filing-breakdown-tasks |
| description | Turn a tech breakdown's tasks.md into Jira ticket drafts — an epic parent plus one child story/task per task entry, each a real ticket with acceptance criteria and mapped Blocked-by/Depends-on links — then hand off to filing-jira-tickets to file them. |
| when_to_use | Use only when starting from a finished tasks.md (a tech breakdown's task decomposition) to create a set of new Jira tickets — phrasings like "create the tickets from tasks.md", "make Jira tickets for these tasks", "file the epic and stories", "turn this breakdown into Jira tickets". Also use when a tech breakdown in bitwarden/tech-breakdowns hands off a finished tasks.md. Do not use to edit or update an existing ticket's fields such as description, acceptance criteria, status, or labels (there's no tasks.md involved); to read or research existing issues (that is researching-jira-issues); or to move, organize, or otherwise manage breakdown files and folders. |
| allowed-tools | Read, Glob, Skill(bitwarden-atlassian-tools:filing-jira-tickets), mcp__plugin_bitwarden-atlassian-tools_bitwarden-atlassian__get_issue |
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.
