voc-orchestratorlisted

# /voc-orchestrator — The Weekly Run One command, six phases. The intelligence lives in the individual skills; this is a coordinator that runs them in order and fails loudly instead of quietly. ## Arguments | Flag | Effect | |---|---| | `--window 30d` | Override the default window | | `--skip-sources chat,notes` | Skip named sources | | `--dry-run` | Pull, analyze and synthesize, but do not route or dispatch | | `--sources-only` | Stop after Phase 1 | **Use `--dry-run` for your first three runs.** Read the synthesis by hand and check whether the confirmed themes match what you already believe from talking to customers. If they do not, the problem is almost always upstream configuration, not the rule. --- ## Phase 0 — Preflight Before pulling anything, verify the setup and **print the result as a table**. Do not proceed silently past a broken connector. ``` Preflight config/thresholds.json ok context/product-context.md ok CALL_PROVIDER=gong credentials present Apify MCP connected CRM MCP NOT CONNECTED — signals will be tier U chat_channels 3 configured notes_source not configured — skipping VOC_OUTPUT_DIR=./outputs local, not synced ok ``` Check `VOC_OUTPUT_DIR` for the strings `Dropbox`, `Google Drive`, `OneDrive`, `iCloud`. If it is inside a synced folder, **warn before writing anything**. This pipeline writes customer conversations to disk. If few