Dolt-backed issue tracker for multi-session work with dependencies and conversation compaction survival.
Works with
Persists task context across conversation compaction and multiple sessions using a local Dolt database, with atomic claim-and-start workflow to prevent race conditions
Tracks task dependencies, blockers, and discovery relationships; use bd ready to surface unblocked work and bd show <id> --long to recover full context after compaction
Essential commands: bd create , bd ready
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionbeadsExecute the skills CLI command in your project's root directory to begin installation:
Fetches beads from steveyegge/beads and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate beads. Access via /beads in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
2
total installs
2
this week
20.3K
GitHub stars
0
upvotes
Run in your terminal
2
installs
2
this week
20.3K
stars
Graph-based issue tracker that survives conversation compaction. Provides persistent memory for multi-session work with complex dependencies.
Decision test: "Will I need this context in 2 weeks?" YES = bd, NO = TodoWrite.
| bd (persistent) | TodoWrite (ephemeral) |
|---|---|
| Multi-session, dependencies, compaction survival | Single-session linear tasks |
| Dolt-backed team sync | Conversation-scoped |
See BOUNDARIES.md for detailed comparison.
bd --version # Requires v0.60.0+
BEADS_DIR + --stealth for git-free operation)bd init run once (humans do this, not agents)Run bd prime for AI-optimized workflow context (auto-loaded by hooks).
Run bd <command> --help for specific command usage.
Essential commands: bd ready, bd create, bd show, bd update, bd close, bd dolt push
bd ready — Find unblocked workbd show <id> — Get full contextbd update <id> --claim — Claim and start work atomicallybd close <id> --reason "..." — Complete taskbd dolt push — Push to Dolt remote (if configured)Append --json to any command for structured output. Use bd show <id> --long for extended metadata. Status icons: ○ open ◐ in_progress ● blocked ✓ closed ❄ deferred.
| Error | Fix |
|---|---|
database not found |
bd init <prefix> in project root |
not in a git repository |
git init first |
disk I/O error (522) |
Move .beads/ off cloud-synced filesystem |
| Status updates lag | Use server mode: bd dolt start |
See TROUBLESHOOTING.md for full details.
Track a multi-session feature:
bd create "OAuth integration" -t epic -p 1 --json
bd create "Token storage" -t task --deps blocks:oauth-id --json
bd ready --json # Shows unblocked work
bd update <id> --claim --json # Claim and start
bd close <id> --reason "Implemented with refresh tokens" --json
Recover after compaction: bd list --status in_progress --json then bd show <id> --long
Discover work mid-task: bd create "Found bug" -t bug -p 1 --deps discovered-from:<current-id> --json
| Feature | CLI | Resource |
|---|---|---|
| Molecules (templates) | bd mol --help |
MOLECULES.md |
| Chemistry (pour/wisp) | bd pour, bd wisp |
CHEMISTRY_PATTERNS.md |
| Agent beads | bd agent --help |
AGENTS.md |
| Async gates | bd gate --help |
ASYNC_GATES.md |
| Worktrees | bd worktree --help |
WORKTREES.md |
| Category | Files |
|---|---|
| Getting Started | BOUNDARIES.md, CLI_REFERENCE.md, WORKFLOWS.md |
| Core Concepts | DEPENDENCIES.md, ISSUE_CREATION.md, PATTERNS.md |
| Resilience | RESUMABILITY.md, TROUBLESHOOTING.md |
| Advanced | MOLECULES.md, CHEMISTRY_PATTERNS.md, AGENTS.md, ASYNC_GATES.md, WORKTREES.md |
| Reference | STATIC_DATA.md, INTEGRATION_PATTERNS.md |
If bd --version reports newer than 0.60.0, this skill may be stale. Run bd prime for current CLI guidance — it auto-updates with each bd release and is the canonical source of truth (ADR-0001).
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
I recommend beads for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
beads reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added beads from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Registry listing for beads matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: beads is the kind of skill you can hand to a new teammate without a long onboarding doc.
Keeps context tight: beads is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for beads matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: beads is focused, and the summary matches what you get after install.
beads is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: beads is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 57