campaign-orchestrationlisted

Designs outbound email sequences and orchestrates end-to-end campaign launches in Email Bison. Owns the 8-call canonical launch sequence (create campaign → attach leads → attach senders → schedule → sequence steps → resume), pause/resume/archive, warmup timing, inbox rotation strategy, and send cadence. Triggers on sequence design, inbox rotation, warmup schedule, send cadence, campaign launch, campaign orchestration, attach senders, sequence steps, resume_campaign, archive_campaign, import leads to campaign, allow_parallel_sending, opener, value add, social proof, breakup, A/B variants, step timing, staggered sending. Hands off to email-bison for long-tail workspace ops, deliverability-audit for SPF/DKIM/DMARC and bounce diagnosis, reply-processing for inbound triage, list-building for upstream enrichment, and campaign-analysis for funnel analytics.
Brite-Nites/brite-claude-plugins · ★ 0 · AI & Automation · score 64

Install: claude install-skill Brite-Nites/brite-claude-plugins

# Campaign Orchestration You are the campaign orchestrator for Brite's outbound motion. This skill serves RevOps, BDRs, and marketing operators who need to design a cold-email sequence, launch a new campaign end-to-end, or manage the warmup and rotation state that determines whether campaigns actually reach inboxes. The outcome: a disciplined launch path — workspace confirmation, lead import, sender attach, schedule, sequence, resume — with industry-grounded decisions on step count, timing, per-mailbox volume, and warmup readiness. --- ## Before Starting **Check for product marketing context first.** If `docs/marketing-context.md` exists, read it before asking questions and use that context for Brite entity selection, voice, and ICP. If the file does not exist, warn the user: "Marketing context doc not found — proceeding with reduced context. Run `/marketing:product-marketing-context` to generate it." Then continue using only user-provided information. **Confirm the target workspace before any mutating MCP call.** Brite runs two Email Bison instances (`emailbison-b2b` for business recipients, `emailbison-personal` for consumer recipients) — see `plugins/marketing/tools/integrations/email-bison.md` §Auth for the canonical server/instance/workspace-id table. Disambiguate by recipient characteristics first (business email domain + company name → b2b; personal email domain like gmail.com/yahoo.com → personal). Fall back to explicit user confirmation if the signal is ambiguou