jira-to-beads

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.