jira-to-beads

Break down Jira tickets into feature and task beads with dependencies.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/jordanfbrown/dotfiles --skill jira-to-beads
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-to-beads
Source: https://github.com/jordanfbrown/dotfiles/tree/main/claude/dot-claude/skills/jira-to-beads
Command: npx skills add https://github.com/jordanfbrown/dotfiles --skill jira-to-beads

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Jira tickets often need to be translated into actionable work units that teams can implement with clear ownership and dependencies. This skill breaks a Jira issue into a feature bead and multiple task beads, establishing parent-child relationships and explicit sequencing to guide agent work.

Core Features & Use Cases

  • Breaks a Jira ticket into a feature bead (parent) and task beads (children) linked via --parent.
  • Establishes dependencies to enforce sequential work and clear handoffs.
  • Works with the bd beads workflow and the ralph.sh script to materialize tasks and track progress.

Quick Start

Create a feature bead using the Jira ticket ID, add task beads with proper --parent links and dependencies, and verify the bead structure with the r command.

Frequently Asked Questions about jira-to-beads

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

FAQPage Schema
How do I break Jira tickets into parent-child task hierarchies?

To break Jira tickets into parent-child task hierarchies, this skill creates a feature bead as the parent and multiple task beads as children. It uses explicit --parent relationships to establish dependencies and clear task ordering for engineering teams.

What is a bead hierarchy for Jira work items?

A bead hierarchy for Jira work items is a structured breakdown where a feature bead acts as the parent and task beads act as children. It translates Jira issues into actionable units with dependencies to guide agent work and track progress.

Do I need jira-cli installed to create task beads from Jira issues?

You need jira-cli authenticated in ~/.netrc to create task beads from Jira issues. Additionally, you must have bd beads installed and an initialized bead repository to use the bd beads tooling and the ralph.sh script.

How do I establish sequential dependencies when breaking down Jira tickets?

To establish sequential dependencies when breaking down Jira tickets, add task beads with proper --parent links and explicit dependency definitions. This enforces sequential work and creates clear handoffs between the generated task beads.

What's the best way to track Jira ticket progress using beads?

The best way to track Jira ticket progress using beads is by materializing tasks with the ralph.sh script and verifying the bead structure with the r command. This workflow integrates bd beads tooling to monitor the parent-child task hierarchy.