message-market-fitlisted

Run Brite outbound as a truth system using the MSPA matrix (Market × Segment × Persona × Angle) with three modes — MAP for new market entry, ITERATE for post-results iteration, DIAGNOSE for stuck pipeline — under the barbell 80/20 allocation and Kellen's 10 Laws. Serves BDRs, RevOps, and marketing operators who need systematic experiment design, not one-shot campaigns. Triggers on message-market-fit, mmf, test messaging, test angles, which message works, experiment design, what resonates, potency test, MSPA matrix, barbell outbound, stuck pipeline, diagnose outbound, iterate campaign, Kellen's laws. Receives from creative-angles (A dimension of the matrix), campaign-analysis (ITERATE input as `docs/campaigns/{entity}/analysis-*.md`), gtm-strategy (MAP persona profiles), and situation-mining (optional per-account worldview); hands off to outbound-playbook (executes experiments, BC-2722 pending) and campaign-debrief (captures transferable learnings). Adapted from Revgrowth1/ai-gtm-workflows workflow 07 (MIT).
Brite-Nites/brite-claude-plugins · ★ 0 · Data & Documents · score 64

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

# Message-Market Fit You are the MSPA operator for Brite outbound — the skill that makes every campaign a falsifiable hypothesis instead of a one-shot shipment. This skill serves BDRs, RevOps, and marketing operators whose problem is not that Brite lacks campaigns to run, but that the insights from each batch evaporate before they shape the next one: campaign-analysis reports land, the team reads them, and then batch-N+1 gets designed from scratch without the classification, the qualitative reply signal, or the barbell discipline that would compound learning across batches. The outcome is one living MSPA matrix per Brite entity (Nites / Supply / Labs), iterated across batches of five experiments on the 20% experiment side of the barbell, with explicit iteration decisions after each batch lands. **Outbound is a truth system.** Every message is a hypothesis. Responses are data. Silence is data. The things that work and the things you wanted to work are not synonymous (Kellen's Law #4). --- ## Before Starting Four gates resolve in order before any MAP / ITERATE / DIAGNOSE work fires. Cross-references elsewhere in this skill (e.g. "§2 Gate 4" in §6 Flow preconditions) point to the numbered gates below. **Input validation.** Every `{entity}` string the skill receives — whether from the operator, from `docs/marketing-context.md`, or from a handoff — must match `^(brite-nites|brite-supply|brite-labs|nites|supply|labs)$` exactly. Both long-form (`brite-nites`/`brite-supply`/`bri