Help us improve
Share bugs, ideas, or general feedback.
From text-visualizations
Run daily product ops standup using bv insights for prioritization and health checks
npx claudepluginhub tjboudreaux/cc-plugin-text-visualizationsHow this command is triggered — by the user, by Claude, or both
Slash command
/text-visualizations:ops-standup --verboseThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Daily Ops Standup Run a structured daily standup using bd/bv for graph-aware prioritization and health monitoring. ## Arguments: $ARGUMENTS ## Standup Agenda ### 1. Health Check First, verify the environment and get graph health metrics: **Alert conditions:** - `cycle_count > 0`: Circular dependencies need resolution - `critical_path_length > 10`: Deep dependency chain may bottleneck ### 2. What's Blocked Identify issues that cannot proceed: **Action**: For each blocked issue, either: - Resolve the blocker - Re-prioritize the blocker - Remove the dependency if it's not actual...
/standupGenerates brief operational standup report: task counts, 2-3 key in-progress items, blockers, progress signal, and next recommended command from project state files.
/statusSummarizes project state, backlog health, and next work items. Also supports per-feature and backlog-only subcommands.
/project-statusGenerates intelligent project status overview with progress metrics, blockers, risks, visualizations, predictions, recommendations, and historical context. Supports focus arguments like sprint, blocked, team.
/daily-standupOrchestrates daily brief, experiment monitoring, and feedback scan into a concise standup summary with top insights, action items, and watch list.
/standup-notesGenerates daily standup notes from Git commits, Jira tickets, Obsidian vault, and calendar events. Uses optional arguments for focused context.
/standup-reportGenerates daily standup reports from git activity, Linear tasks, and GitHub PRs. Outputs in Markdown, Slack, Email, or team rollup formats.
Share bugs, ideas, or general feedback.
Run a structured daily standup using bd/bv for graph-aware prioritization and health monitoring.
First, verify the environment and get graph health metrics:
# Verify tools
command -v bd && command -v bv || echo "ERROR: bd or bv not installed"
# Database health
bd info --json | jq '{
project: .project,
total_issues: .total_issues,
daemon_status: .daemon_status
}'
# Graph health
bv --robot-insights --json | jq '{
critical_path_length: .critical_path.length,
cycle_count: (.cycles | length),
top_pagerank: [.top_pagerank[:3] | .[].id]
}'
Alert conditions:
cycle_count > 0: Circular dependencies need resolutioncritical_path_length > 10: Deep dependency chain may bottleneckIdentify issues that cannot proceed:
# Blocked issues
bd blocked --json | jq '.[] | {id, title, blocked_by: .blocked_by}'
# If cycles exist, show them
bv --robot-insights --json | jq 'if .cycles | length > 0 then .cycles else "No cycles" end'
Action: For each blocked issue, either:
Issues that can be worked immediately:
# Ready work sorted by priority
bd ready --json | jq '.[0:10] | .[] | {id, title, priority, type}'
Get graph-aware prioritization with reasoning:
# AI-assisted priority recommendations
bv --robot-priority --json | jq '.recommendations[:5] | .[] | {
id,
title,
reasoning,
confidence
}'
Use this when:
How many agents/streams can work simultaneously:
# Execution plan
PLAN=$(bv --robot-plan --json)
# Number of parallel tracks
echo "$PLAN" | jq '.parallel_tracks | length'
# First item in each track (can start immediately)
echo "$PLAN" | jq '[.parallel_tracks[] | .[0]] | .[] | {id, title}'
For multi-agent setups:
Check what's currently being worked on:
# In-progress issues
bd list --status in_progress --json | jq '.[] | {
id,
title,
assignee,
notes: (.notes | split("\n")[0])
}'
Stale in-progress check:
# Issues in-progress for >3 days without notes update
bd list --status in_progress --json | jq '[.[] | select(
(.updated_at | fromdateiso8601) < (now - 259200)
)] | .[] | {id, title, days_stale: ((now - (.updated_at | fromdateiso8601)) / 86400 | floor)}'
Quick velocity check:
# Closed in last 24 hours
bv --robot-diff --diff-since "1 day ago" --json | jq '{
closed: [.closed_issues[].id],
opened: [.new_issues[].id],
velocity_ratio: ((.closed_issues | length) / ((.new_issues | length) + 0.001))
}'
Based on all the above, recommend today's focus:
# Top 3 priorities for today
echo "=== TODAY'S FOCUS ==="
# 1. Any blockers to resolve?
BLOCKED=$(bd blocked --json | jq 'length')
if [ "$BLOCKED" -gt 0 ]; then
echo "1. RESOLVE BLOCKERS ($BLOCKED issues blocked)"
bd blocked --json | jq -r '.[0] | " → Unblock: \(.id) - \(.title)"'
fi
# 2. Top priority from graph analysis
TOP=$(bv --robot-priority --json | jq -r '.recommendations[0]')
echo "2. TOP PRIORITY: $(echo "$TOP" | jq -r '.id') - $(echo "$TOP" | jq -r '.title')"
echo " Reasoning: $(echo "$TOP" | jq -r '.reasoning')"
# 3. Quick wins (low effort, unblocks others)
echo "3. QUICK WINS (unblocks most):"
bv --robot-plan --json | jq -r '[.unblocks | to_entries | sort_by(.value | length) | reverse | .[0:3] | .[]] | " → \(.key): unblocks \(.value | length) issues"'
Generate a standup summary in this format:
## Standup Summary - [DATE]
### Health
- Total Issues: [N]
- Critical Path: [N] deep
- Cycles: [N] (action required if >0)
### Capacity
- Blocked: [N] issues
- Ready: [N] issues
- Parallel Tracks: [N]
- In-Progress: [N]
### Yesterday
- Closed: [N]
- Opened: [N]
- Velocity: [ratio]
### Today's Focus
1. [Top priority with reasoning]
2. [Second priority]
3. [Quick win that unblocks most]
### Actions Required
- [ ] [Any blockers to resolve]
- [ ] [Any stale in-progress to check]
- [ ] [Any cycles to break]
Add to your shell profile or Agent Mail session init:
# ~/.zshrc or session init
alias standup="factory /ops-standup"
After running standup, copy the summary to team channel.
# Run at 9am daily, save to file
0 9 * * * cd /path/to/project && factory /ops-standup > .standup-$(date +%Y%m%d).md
If --verbose is passed, include additional details:
# Full insights dump
bv --robot-insights --json
# Full execution plan
bv --robot-plan --json
# All in-progress with full notes
bd list --status in_progress --json