flow-next-deps

# Flow-Next Dependency Graph Visualize spec dependencies, blocking chains, and execution phases. ## Preamble flowctl is bundled with the plugin (not on PATH). Define once; subsequent blocks use `$FLOWCTL`: ```bash FLOWCTL="${DROID_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT}}/scripts/flowctl" ``` ## Setup ```bash $FLOWCTL detect --json | jq -e '.exists' >/dev/null && echo "OK: .flow/ exists" || echo "ERROR: run $FLOWCTL init" command -v jq >/dev/null 2>&1 && echo "OK: jq installed" || echo "ERROR: brew install jq" ``` ## Step 1: Gather Spec Data Build a consolidated view of all specs with their dependencies: ```bash # Get all spec IDs spec_ids=$($FLOWCTL specs --json | jq -r '.specs[].id') # For each spec, get full details including dependencies for id in $spec_ids; do $FLOWCTL show "$id" --json | jq -c '{ id: .id, title: .title, status: .status, plan_review: .plan_review_status, deps: (.depends_on_epics // []) }' done ``` ## Step 2: Identify Blocking Chains Determine which specs are ready vs blocked (pure jq, works on any shell): ```bash # Collect all spec data with deps specs_json=$($FLOWCTL specs --json | jq -r '.specs[].id' | while read id; do $FLOWCTL show "$id" --json | jq -c '{id: .id, title: .title, status: .status, deps: (.depends_on_epics // [])}' done | jq -s '.') # Compute blocking status echo "$specs_json" | jq -r ' # Build status lookup (map({(.id): .status}) | add // {}) as $status | # Check each non-done spec .[] | select...