ops-standup

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:

# 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 resolution
• critical_path_length > 10: Deep dependency chain may bottleneck

2. What's Blocked

Identify 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:

• Resolve the blocker
• Re-prioritize the blocker
• Remove the dependency if it's not actually blocking

3. What's Ready

Issues that can be worked immediately:

# Ready work sorted by priority
bd ready --json | jq '.[0:10] | .[] | {id, title, priority, type}'

4. Priority Recommendations

Get graph-aware prioritization with reasoning:

# AI-assisted priority recommendations
bv --robot-priority --json | jq '.recommendations[:5] | .[] | {
  id,
  title,
  reasoning,
  confidence
}'

Use this when:

• Multiple issues seem equally important
• Unsure what to work on next
• Need to justify prioritization decisions

5. Parallel Capacity

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}'