fivetran-rollout-decomposition
description (verbatim frontmatter)
Decompose the coworkers/ Fivetran multi-connector data-storage project (Slack, cloudflare-analytics, github, gmail connectors + connector_registry/connector_runs/source_tables in coworkers/data-infra) into atomic tasks with subtasks, and own the one green-light approval gate before any task is handed to cwc-engineering for implementation. Use when the user asks to "decompose the fivetran rollout", "break down the connector project", "what tasks are next", "what's the next atomic task for fivetran", "plan the connector rollout", "greenlight the next connector task", or asks for the task/subtask breakdown of wiring Slack or cloudflare-analytics to real data. Do NOT use for narrating why this project exists or keeping the registry-counts/ doc-provenance story current (cwc-analytics-engineering's data-vision-runbook skill owns the vision narrative) and do NOT use for writing connector/schema/API code yourself (cwc-engineering's engineering-playbook owns implementation) — this skill's job ends the moment a task is approved and hands off.
summary
Decompose the coworkers/ Fivetran multi-connector data-storage project (Slack, cloudflare-analytics, github, gmail connectors + connector_registry/connector_runs/source_tables in coworkers/data-infra) into atomic tasks with subtasks, and own the one green-light approval gate before any task is ha...
source
plugins/cwc-product-management/skills/fivetran-rollout-decomposition/SKILL.md
provenance
created 2026-07-10 18:13:13 · JSON