bv

Automate Beads project triage and planning using .beads/beads.jsonl graph metrics.

1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/trungtnm/claude-code-utils --skill bv-trungtnm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bv
Source: https://github.com/trungtnm/claude-code-utils/tree/main/plugins/skills/bv
Command: npx skills add https://github.com/trungtnm/claude-code-utils --skill bv-trungtnm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Beads teams face challenges in triage and planning due to large issue graphs; BV provides a graph-aware engine to surface priorities and drive deterministic execution plans.

Core Features & Use Cases

  • Graph metrics (PageRank, betweenness, cycles, and more) to reveal blockers and critical paths.
  • Automated planning and robot-style guidance to coordinate multiple agents on complex features.
  • Use Case: In a Beads project with dozens of issues, BV highlights top bottlenecks and suggests the next work item.

Quick Start

Run BV in robot mode to triage issues and surface bottlenecks with graph metrics.

Frequently Asked Questions about bv

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prioritize issues in a Beads project using a dependency graph?

To prioritize issues in a Beads project using a dependency graph, you can apply graph metrics like PageRank and betweenness to surface critical bottlenecks and identify the most impactful work items. BV automates this analysis directly from your .beads/beads.jsonl data.

What are graph metrics like PageRank and betweenness used for in issue triage?

Graph metrics like PageRank and betweenness in issue triage are used to reveal blockers and critical paths within large dependency graphs. They mathematically identify high-impact issues and bottlenecks that delay overall project progress.

Can I automate action plans for multiple agents working on Beads repositories?

Yes, you can automate action plans for multiple agents working on Beads repositories by running the engine in robot mode. This generates deterministic, robot-guided execution plans to coordinate complex features across multiple agents.

Does this triage tool require a specific file format to analyze Beads issue graphs?

Yes, this triage tool requires the .beads/beads.jsonl file format to analyze Beads issue graphs. It specifically parses these dependency graphs to calculate graph metrics and output deterministic recommendations for your project.

What is the best way to identify bottlenecks in a large Beads dependency graph?

The best way to identify bottlenecks in a large Beads dependency graph is to calculate cycle detection and betweenness metrics. These graph algorithms highlight the specific issues causing circular dependencies and blocking downstream work.

Why are my automated Beads project recommendations not deterministic across multiple runs?

If your automated Beads project recommendations are not deterministic, ensure you are using the built-in robot-mode commands correctly. The engine is designed to output consistent, deterministic recommendations based on the static .beads/beads.jsonl graph structure.