issue-to-beads

Decompose GitHub issues into Beads epics, tasks, and sub-tasks with acceptance criteria.

29|2|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/jbdamask/john-claude-skills --skill issue-to-beads
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-to-beads
Source: https://github.com/jbdamask/john-claude-skills/tree/main/plugins/beads-planner/skills/issue-to-beads
Command: npx skills add https://github.com/jbdamask/john-claude-skills --skill issue-to-beads

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of converting complex GitHub issues into structured, actionable work items within the Beads project management system, ensuring clarity and trackability.

Core Features & Use Cases

  • Decomposition: Breaks down GitHub issues into epics, tasks, and sub-tasks.
  • Acceptance Criteria: Generates objectively verifiable acceptance criteria for each work item.
  • Dependency Mapping: Establishes clear dependencies between tasks.
  • Use Case: When a new feature request comes in as a GitHub issue, use this Skill to automatically create a detailed breakdown in Beads, complete with epics, tasks, and acceptance criteria, ready for the development team.

Quick Start

Use the issue-to-beads skill to decompose GitHub issue number 42.

Frequently Asked Questions about issue-to-beads

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

FAQPage Schema
How do I convert GitHub issues into Beads epics and tasks?

This Skill decomposes GitHub issues into structured Beads work items, generating epics, tasks, sub-tasks, and objectively verifiable acceptance criteria. It establishes clear dependency mappings between tasks to ensure software development teams have actionable work items.

What's the best way to break down a GitHub feature request into trackable sub-tasks?

Automated task decomposition breaks down a GitHub feature request into a detailed Beads hierarchy of epics and sub-tasks. It generates objectively verifiable acceptance criteria and maps dependencies between work items for clear trackability.

Do I need the gh CLI and bd CLI to sync issues from GitHub to Beads?

Yes, you need the gh CLI for GitHub interaction and the bd CLI for Beads management to sync issues. These command-line interfaces are required dependencies for the Skill to automatically read GitHub issues and create structured Beads work items.

Can I generate acceptance criteria automatically when converting GitHub issues to Beads?

Yes, the Skill generates objectively verifiable acceptance criteria automatically for each decomposed task and sub-task when converting GitHub issues to Beads. This ensures software development teams have clear trackability for every work item created.

Does this issue tracking workflow establish dependencies between decomposed tasks?

Yes, this issue tracking workflow establishes clear dependencies between tasks during decomposition. It maps relationships across the generated Beads epics, tasks, and sub-tasks to ensure proper execution order for software development teams.