---
name: connector-flow
description: |
  Routes ANY connector request into the gated three-phase flow (Research → Build →
  Validate) — never author connector YAML without it. Triggers: "build a [provider]
  connector", "create a connector for [provider]", "make an integration for [provider]",
  "research [provider]'s API", "validate the [provider] connector", "take [provider] from
  scratch to done". Determines the right entry point (/connector:full by default, or a
  single phase) and follows its command file exactly.
---

# Connector flow router

This skill only routes. It does not do research, build, or validation work itself, and it
does not duplicate any of that content — the command files own it.

Default to the full flow. Use a single phase only when the user's request names just that
phase (e.g. "research X's API" → research only).

| Request maps to | Command file |
|---|---|
| Full flow (default) | `${CLAUDE_PLUGIN_ROOT}/commands/connector-full.md` |
| Research only | `${CLAUDE_PLUGIN_ROOT}/commands/connector-research.md` |
| Build only | `${CLAUDE_PLUGIN_ROOT}/commands/connector-build.md` |
| Validate only | `${CLAUDE_PLUGIN_ROOT}/commands/connector-validate.md` |

Read the matched command file and follow it exactly as if the command had been invoked —
**in this session, yourself**. Never hand the flow to a subagent or background agent: a
delegated run rebuilds all context from zero and measured at roughly double the cost.