data-vision-runbook
description (verbatim frontmatter)
The durable "why + where we are" document for .coworkers-analytics's multi-connector Fivetran data-infra initiative — why this repo is building its own connector-backed data layer, what "done" looks like for the rollout, and the exact current state of every connector (registry row counts, which are fivetran-debug-verified, which are real vs. best-guess schemas, which are wired to live data vs. zero-row skeleton). Use when the user asks "what's the data vision", "where are we on Fivetran connectors", "why are we building this", "what's done vs. not done on the connector rollout", "which connectors are verified", "recap the data-infra state", or wants to know current registry numbers before deciding what to build next. Trigger on "data vision", "connector rollout state", "fivetran status", "connector registry", "coworkers-analytics data layer". Do NOT use this for breaking the rollout into atomic tasks/tickets — that's `plugins/cwc-product-management/skills/fivetran-rollout-decomposition`. Do NOT use this to execute code changes, write connector.py files, edit schema.ts, or run migrations — that's `plugins/cwc-engineering/skills/engineering-playbook`, which hands off to cwc-deploy with the exact phrase "ready for cwc-deploy" once code is written. This skill only states and maintains the vision and the ground-truth snapshot; it does not plan tasks and does not touch a keyboard.
summary
The durable "why + where we are" document for .coworkers-analytics's multi-connector Fivetran data-infra initiative — why this repo is building its own connector-backed data layer, what "done" looks like for the rollout, and the exact current state of every connector (registry row counts, which a...
source
plugins/cwc-analytics-engineering/skills/data-vision-runbook/SKILL.md
provenance
created 2026-07-10 18:13:13 · JSON