multi

Beads Issue Tracking Skill

> **Attribution**: [Beads](https://github.com/steveyegge/beads) by [Steve Yegge](https://github.com/steveyegge)

155 stars

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/beads/SKILL.md --create-dirs "https://raw.githubusercontent.com/maslennikov-ig/claude-code-orchestrator-kit/main/.claude/skills/beads/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/beads/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How Beads Issue Tracking Skill Compares

Feature / Agent	Beads Issue Tracking Skill	Standard Approach
Platform Support	multi	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

> **Attribution**: [Beads](https://github.com/steveyegge/beads) by [Steve Yegge](https://github.com/steveyegge)

Which AI agents support this skill?

This skill is compatible with multi.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Beads Issue Tracking Skill

> **Attribution**: [Beads](https://github.com/steveyegge/beads) by [Steve Yegge](https://github.com/steveyegge)

## Description

Beads is a git-backed, AI-native issue tracking system. This skill helps AI agents work with Beads effectively.

## When to Use

- Starting a new work session (bd prime → bd ready)
- Creating, updating, or closing issues
- Managing task dependencies
- Running workflow formulas
- Coordinating multi-session work

## Quick Reference

### Session Workflow

```bash
# START
bd prime                    # Inject context
bd ready                    # Find available work

# WORK
bd update ID --status in_progress  # Take task
# ... implement ...
bd close ID --reason "Done"        # Complete task
/push patch                        # Commit

# END (MANDATORY!)
bd sync
git push
```

### Issue Creation

```bash
# Basic
bd create "Title" -t type -p priority

# With files (auto-labels)
bd create "Fix button" --files src/components/Button.tsx

# Emergent work
bd create "Found bug" -t bug --deps discovered-from:current-id
```

### Types & Priorities

| Type | When |
|------|------|
| feature | New functionality |
| bug | Bug fix |
| chore | Tech debt, config |
| docs | Documentation |
| test | Tests |
| epic | Group of tasks |

| Priority | Meaning |
|----------|---------|
| 0 | Critical (blocks release) |
| 1 | Critical |
| 2 | High |
| 3 | Medium (default) |
| 4 | Low / backlog |

### Formulas (Workflows)

```bash
bd formula list                                    # List all
bd mol wisp exploration --vars "question=How?"    # Ephemeral
bd mol pour bigfeature --vars "feature_name=auth" # Persistent
bd mol squash WISP_ID                             # Save result
bd mol burn WISP_ID                               # Discard
```

## Resources

See `resources/` for detailed guides:
- COMMANDS_QUICKREF.md - Command cheat sheet
- DECISION_MATRIX.md - When to use what
- WORKFLOWS.md - Common workflows
- SPECKIT_BRIDGE.md - Integration with Spec-kit

## Integration with Spec-kit

For large features (>1 day):
1. `/speckit.specify` → requirements
2. `/speckit.plan` → design
3. `/speckit.tasks` → task breakdown
4. `/speckit.tobeads` → import to Beads
5. `bd ready` → work with Beads

## Links

- [Beads GitHub](https://github.com/steveyegge/beads)
- [CLI Reference](https://github.com/steveyegge/beads/blob/main/docs/CLI_REFERENCE.md)