vac-campaign-goallisted

Generates the campaign configuration for a voice-agent build — campaign-goal.md (the campaign goal definition, i.e. the campaigns.campaign_goal free-text field) plus call-outcomes.json (the typed campaigns.call_outcomes list). Runs at step 9 of the VAC pipeline (per the SSOT in PIPELINE.md), after vac-task-extraction. Both artifacts are derived from the agent's briefing.md Call Objectives and are what the campaign platform uses at runtime to classify each call's outcome (success / lead) and to feed the goal context into every post-call analysis. Use whenever building a voice agent and the campaign's goal definition + outcomes are needed, or whenever the user asks to create a goal definition, campaign goal, call outcomes, success definition, outcome types, or the campaign platform's campaign-goal/outcome config for an agent — even if they only say "generate the goal" or "outcomes for agent X" without naming the fields. English output artifacts.
callflows/voice-agent-kit · ★ 1 · AI & Automation · score 74

Install: claude install-skill callflows/voice-agent-kit

# VAC Campaign Goal Produces the two campaign-config artifacts for a voice-agent build: - **`campaign-goal.md`** — the copy-paste campaign goal definition. Goes into your campaign platform's goal field. - **`call-outcomes.json`** — the typed outcome list. Goes into your campaign platform's outcomes field. ## Prerequisites (input check) Before starting, check that these files exist in the agent directory (`../voice-agents/<agent>/`): | File | Comes from | If missing | |---|---|---| | `briefing.md` | `vac-intake` (step 1) | Run `vac-intake` first | If an input is missing, do NOT improvise and do NOT carry on with placeholders: name the missing upstream step and ask the requester or workspace admin whether it should be run now. (On top of that, this skill enforces two MUST-HAVE preconditions on the briefing's content, see below.) Both are derived from the same source as `vac-task-extraction`: the **Call Objectives** in `briefing.md`. This skill is the sibling of `vac-task-extraction` — task-extraction writes the post-call *task* prompt, this one writes the *goal + outcomes* that the campaign platform uses to score whether the call succeeded. ## Pipeline Position Step 9 (see `PIPELINE.md`) — runs after `vac-task-extraction` (step 8). It needs only `briefing.md` as input, so it can technically run any time after the briefing is finalized; the canonical position is step 9 so both campaign-config artifacts (task-extraction prompt + goal/outcomes) sit together and any live-t