preflight-campaign

Preflight a campaign

Run the bundled checker over a campaign and report what would go wrong. The checker is deterministic and read-only: it inspects, and it cannot activate, edit, or send anything.

Do this first: figure out what you were given

The user will arrive with one of four things. Identify which, then follow that path. Do not ask a long questionnaire — collect what is needed and go.

What you have	Path
File paths, or an uploaded file	A. Files
A lead list or copy pasted into chat	B. Pasted
Only a description in conversation	C. Described
Nothing yet	D. Nothing

Everything ends the same way: build a campaign file and a leads CSV in a scratch directory, run the checker, and report the result in plain language.

A. Files

Confirm the paths exist, then run it. A campaign file and a leads file are required; the rest are optional and their absence is reported honestly.

"${CLAUDE_PLUGIN_ROOT}/bin/preflight" check \
  --campaign <campaign.yaml> \
  --leads <leads.csv> \
  --suppressions <suppressions.csv> \
  --evidence <evidence.json> \
  --config <preflight.yaml>

If the user uploaded a file, it is already on disk — use the path Cowork gives you. If they only have a lead list and no campaign file, treat it as path C for the campaign half: ask about the sequence and build the campaign file.

B. Pasted

Write what was pasted into a scratch directory, then run path A.

1. Create a working directory: mktemp -d.
2. If they pasted a lead list: write it to leads.csv. Add a header row if it is missing — read references/input-formats.md for the accepted column names, which are generous (Email/E-Mail Address/work_email all resolve).
3. If they pasted campaign copy: build campaign.yaml around it using the template in references/input-formats.md.
4. Fill any gap by asking, or by following path C.

Never paste contact data back into the conversation unedited. The checker redacts mailboxes by default; keep it that way.