skills.rest
Yassimba
YassimbaCOMMUNITY
Explore all skills by this author →
GitHub

ticket-overview

Generates read-only roadmap and dependency graph views from Beads ticket data.

9|Updated Jul 17, 2026
Search Tags:#mermaid#beads#dependency analysis#roadmap#issue tracking#bv#ticket graph
One-click install
npx skills add https://github.com/Yassimba/loom --skill ticket-overview-yassimba
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ticket-overview
Source: https://github.com/Yassimba/loom/tree/main/skills/ticket-overview
Command: npx skills add https://github.com/Yassimba/loom --skill ticket-overview-yassimba

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams using Beads for issue tracking struggle to see the big picture across many tickets: what to work on next, how open work maps to product goals, and how dependencies block progress. This Skill turns raw ticket graph data into a clear product map without modifying any tracker state. ## Core Features & Use Cases - Next Ticket Preview: Identifies the next actionable ticket via BV robot commands and grounds an approach by skimming the affected code. - Roadmap View: Maps open tickets into product workstreams with Mermaid timeline and dependency flowcharts, bottlenecks, and independent tracks. - Complete Graph View: Renders the full open and closed ticket graph including parent hierarchies, blocking DAGs, and related edges. - Use Case: A developer returning from vacation asks what the team is building and what is blocked; the Skill produces a roadmap with workstream phases, dependency flowcharts, and the next actionable ticket. ## Quick Start Use the ticket-overview skill to explain the complete ticket graph and its main workstreams.

Frequently Asked Questions about ticket-overview

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

FAQPage Schema
How do I see the next actionable ticket in Beads?▼

Run bv --robot-next to get BV's pick, then read it with br show <id> --json. If BV returns nothing, br ready --json shows the ready frontier, distinguishing an empty frontier from ready epics.

How to generate a roadmap from Beads tickets?▼

Run bv --robot-triage, --robot-graph, --robot-plan, and --robot-insights plus br list --json, then group tickets into product workstreams by intent and dependencies. Render phases as a Mermaid timeline and relationships as Mermaid flowcharts.

Does ticket-overview modify my Beads issue tracker?▼

No, the Skill is strictly read-only and leaves the graph unchanged. It only runs query commands like br list, br show, and bv robot commands, and confirms tracker state was unchanged at the end.

What tools are required for Beads ticket graph analysis?▼

You need the br CLI and a .beads directory for all views; roadmap and graph views additionally require the bv tool. The Skill reports a missing prerequisite and stops rather than failing midway.

Why should I avoid running bare bv in the terminal?▼

Running bare bv opens an interactive TUI that blocks scripted workflows. Always use the robot flags such as bv --robot-next or bv --robot-graph --graph-format=json for machine-readable output.

Related Skills

Explore More Product & Management Skills→
sidereal-iosidereal-io
15

beads-sdd-orchestrator

Orchestrate Spec-Driven Development workflows and manage cycles with the Beads framework.

Official
Advanced
aditriokaaditrioka

next-change

Identify and claim the next OpenSpec change for the nearyou-id project.

Community
Advanced
anthropicsanthropics
23.4k

roadmap-update

Update, create, and reprioritize product roadmaps using RICE and MoSCoW frameworks.

Official
Advanced
DicklesworthstoneDicklesworthstone
1.1k

br

Manage dependency-aware issues in a local SQLite and JSONL issue tracker via the br CLI.

Community
Intermediate