Is the Issue To Beads skill free?

Yes. The skill itself is free from jbdamask/john-claude-skills. SkillProof publishes the install command and an independent test verdict at no cost.

What is the Issue To Beads SkillProof Score?

7.6/10 — installs cleanly 3/5, triggers reliably 5/5, output vs. baseline 7/10, docs & honesty 4/5.

How do I install Issue To Beads?

Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.

Can I use Issue To Beads with Cursor, Copilot, Gemini CLI, Codex or other AI tools?

The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.

Issue To Beads

Turns a GitHub issue into a filed Beads epic/task tree with verifiable acceptance criteria.

by jbdamask · jbdamask/john-claude-skills

Works with setup

Install — copy the command Download source ↗

Test report

Verdict: Works with setup
Score: 7.6/10
Tested: Jul 15, 2026
Environment: Claude Code 2.x (agent harness)
Upstream re-checked: Aug 10, 2026 · 3598635

The breakdown quality itself is genuinely good — on a real open issue it correctly demoted the 'package tracking' sub-feature to non-blocking P2 because the issue text called it optional, and gave every task a concrete pass/fail acceptance criterion instead of the naive baseline's 'test it works.' But Phase 3 and Phase 7 call sibling skills (beads-planner:plan-only, beads-planner:git-push-and-tag) that a standard single-folder 'cp -r issue-to-beads' install would leave behind, and bd (Beads CLI) isn't installed by default, so the filing/handoff phases couldn't be executed for real.

Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works

Installs cleanly 3/5
Triggers reliably 5/5
Output vs. baseline 7/10
Docs & honesty 4/5

What Issue To Beads does

A 7-phase workflow that fetches a GitHub issue via gh, branches/worktrees it, runs a plan-only exploration, then decomposes the plan into a Beads (bd) epic with tasks/sub-tasks carrying objectively verifiable acceptance criteria and dependency links, refining up to 5 passes before handoff. Triggers on 'break down issue X', 'convert this to beads', or a GitHub issue URL with intent to make it trackable — but it hard-requires the bd CLI, an initialized Beads project, and two sibling skills (plan-only, git-push-and-tag) from the same beads-planner plugin.

How to install Issue To Beads

git clone https://github.com/jbdamask/john-claude-skills
cd john-claude-skills
mkdir -p ~/.claude/skills
cp -r plugins/beads-planner/skills/issue-to-beads ~/.claude/skills/issue-to-beads

Skills live in ~/.claude/skills/ (global) or .claude/skills/ (per-project). Restart Claude Code after installing.

Commands — how to trigger Issue To Beads

/issue-to-beads Turns a GitHub issue into a filed Beads epic/task tree with verifiable acceptance criteria.

It also activates on plain-language prompts like these:

break down this github issue into a beads epic with acceptance criteria
convert issue number four into trackable beads tasks with dependencies
turn this feature request into a filed epic with verifiable subtasks

Frequently asked questions

Is the Issue To Beads skill free?: Yes. The skill itself is free from jbdamask/john-claude-skills. SkillProof publishes the install command and an independent test verdict at no cost.
Does Issue To Beads work with Claude Code?: We tested it with Claude Code 2.x (agent harness) on Jul 15, 2026. Verdict: Works with setup. The breakdown quality itself is genuinely good — on a real open issue it correctly demoted the 'package tracking' sub-feature to non-blocking P2 because the issue text called it optional, and gave every task a concrete pass/fail acceptance criterion instead of the naive baseline's 'test it works.' But Phase 3 and Phase 7 call sibling skills (beads-planner:plan-only, beads-planner:git-push-and-tag) that a standard single-folder 'cp -r issue-to-beads' install would leave behind, and bd (Beads CLI) isn't installed by default, so the filing/handoff phases couldn't be executed for real.
What is the Issue To Beads SkillProof Score?: 7.6/10 — installs cleanly 3/5, triggers reliably 5/5, output vs. baseline 7/10, docs & honesty 4/5.
How do I install Issue To Beads?: Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
Can I use Issue To Beads with Cursor, Copilot, Gemini CLI, Codex or other AI tools?: The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.