beads-bv
Made by JeffGraph-aware task triage with bv and br. Use when prioritizing work, finding bottlenecks, tracking dependencies, or managing local issues across projects.
Works With
Quality and Utility come from canonical skill metadata. Community ratings appear separately as stars when subscriber reviews exist.
Subscribe to download
Public previews are available, but downloads, CLI sync, and premium content require an active subscription.
Sign In to Subscribe- Full skill content with deterministic versioning
- CLI sync + local search index
- Access to Jeffrey’s premium library
Save to your account
Saved skills live in your cloud list. Run jsm sync on each machine to pull them locally.
What's New with this Skill
1Updates, enhancements, and release notes for this skill.
New: bv, graph-aware triage that picks your next bead by PageRank and finds your bottleneck by betweenness
Your backlog is a directed graph, not a list. bv treats it that way: PageRank surfaces the bead that everything else depends on, betweenness centrality finds the bead that blocks multiple paths, slack measures the buffer before a delay cascades, and k-core shows structural core membership. --robot-triage packages the result into one JSON response an agent can act on. Never run bare bv: it launches a TUI and blocks the terminal.
- --robot-triage is the mega-command: one JSON payload with recommendations, quick wins, blockers to clear, and project health. Designed to be the first call an agent makes at the start of a session
- --robot-next for the single top pick with the claim command pre-built; --robot-plan for parallel-execution tracks with unblocks lists an entire swarm can split across
- Graph metrics instead of gut feel: PageRank for downstream weight, betweenness for bottlenecks, articulation points for cut vertices, slack for critical-path buffer, k-core for structural core membership
- --robot-priority flags priority misalignments with confidence scores: beads whose priority field disagrees with where they sit in the dependency graph
- --robot-label-health and --robot-label-flow segment the graph by label so you can spot a domain (auth, billing, ingest) that's structurally struggling rather than just busy
- Never run bare bv in an agent context; TUI mode blocks the terminal. Always bv --robot-*
The single most important rule: never run bare bv in an agent context. It launches an interactive TUI and blocks the terminal indefinitely. The agent variant is bv --robot-triage: a single command that returns a quick reference, recommendations, quick wins, blockers to clear, and project health as JSON. From there, --robot-next returns the one top-ranked bead with the claim command pre-built, and --robot-plan returns the parallel-execution tracks with their unblocks lists so a swarm can fan out without stepping on each other.