10 actions in 4 pieces of software · ranked by words, meaning and measured trust · 616 ms
- beads-operator
Distributed git-backed graph issue tracker for AI agents. Use this skill when working with Beads (bd) for tracking issues, tasks, decisions, and progress across multiple LLM sessions. Triggers include: setup/configuration of Beads, creating or managing issues/tasks/epics, session handoffs, tracking
- beads-operator
- 2beadsfound in code, not yet checkedno passport yet
MCP serverpeterkc-io/beads
- claim
Atomically claim an issue for work (assignee + in_progress in one CAS-style operation).
- ready
Find issues with no blocking dependencies that are ready to work on.
- reopen
Reopen one or more closed issues. Sets status to
- context
Manage workspace context for beads operations.
- comment
Add a comment to an issue.
- show
Show detailed information about a specific issue including dependencies and dependents.
- update
Update an existing issue.
- claim
- beads
Track issues with bd/br, triage with bv, and convert plans to beads.
- beads
- ralph-tui-create-beads
Convert PRDs to beads for ralph-tui execution. Creates an epic with child beads for each user story. Use when you have a PRD and want to use ralph-tui with beads as the task source. Triggers on: create beads, convert prd to beads, beads for ralph, ralph beads.
- ralph-tui-create-beads
Labels are the instruments' verdict and are never changed by ranking. Agents and robots get this same answer as JSON at /api/v1/find?q=…&answer=1 and through the MCP server.