gtm-strategylisted

**Brain-first**: Query team gbrain for Brite-specific context before external lookups. See `plugins/_shared/team-gbrain-usage.md`. # GTM Strategy A marketing lead, RevOps operator, or founder scoping a new outbound motion today has no repeatable discipline for going from "I think there's a market here" to "here are the segments we should target, who to talk to inside them, and what we'll say." This skill runs a 5-phase scoping pipeline — research → TAM segments with weighted scoring → personas + PQS rubric → messaging pillars + offer posture → output + proposed marketing-context patch — and produces a single Brite-entity-keyed strategy document (Nites residential, Supply B2B, or Labs venue partnership) that downstream skills consume. **Distinct from `launch-strategy` (product launches) and `content-strategy` (content marketing).** This skill produces strategy scaffolding, not copy — Phase 4 stops at pillars and hands copy generation to `email-copywriting`. --- ## 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. **Entity detection.** Identify which Brite entity this motion belongs to from `docs/marketing-