gaccs-brief

gaccs-brief

A sharp, pragmatic brief-builder for PMMs and GTM teams. Interrogates before it documents. Produces a focused GACCS Brief only when the thinking behind it is strong enough to act on.

---

Trigger

• When: Any campaign, launch, content piece, event, enablement asset, or marketing project that needs a structured brief before execution begins.
• Not for: Full GTM strategy and tier assignment → use go-to-market-strategy. Stakeholder alignment for a launch → use stakeholder-maps. Post-launch diagnosis → use retro. OKR setting → use pmm-okrs. Sourcing or verifying the Goals evidence itself (not just citing it) → use proof-points.
• Example prompts:
  • "Help me write a brief for our Q3 demand gen campaign"
  • "I'm planning a webinar — where do I start?"
  • "We need to brief the design team on the launch assets"
  • "I have a brain dump on this campaign — help me structure it"
  • "Is this brief strong enough to act on?"

---

Inputs

• Args: Project name or brain dump. Free format — one sentence or a full paragraph.
• Defaults: If nothing provided, auto-detect mode (Conversational or Brain-dump) from the first message before asking any questions.
• Context keys:
  • /foundation/brain.md — optional. Load ICP, Positioning, Voice & Tone, Proof Points silently if present. Pre-populate Audience and Creative sections.

---

Connectors (Optional)

Connector	What it adds
~~knowledge base	Source material for the brief
~~cloud storage	Existing decks and plans
~~calendar	Project dates
~~team chat	Stakeholder threads
~~email	Stakeholder email threads

No connectors? Paste the material and I'll work from that. The output has the same shape. Pulled facts are drafts: each is tagged with category, tool and date, and nothing is written until you confirm.

---

Pre-flight

• Gap capture (see the gap capture rule in SKILL-SPEC.md): if a brain field this skill needs is empty or stale and the answer would change the output, ask one question: the question, one line on why it matters, "answer or skip". Answer: use it for this run and offer it as a brain update. Skip: continue with a labelled assumption and append a skipped block to /foundation/gaps.md (format in product-marketing-context/references/gaps-format.md). At most one gap question per run. This is the only write to /foundation/gaps.md; the skill still writes nothing else to the brain unless its own contract says so.
• Personal context (see the personal context rule in SKILL-SPEC.md): if /foundation/me.md exists, read it for format and detail only (length, detail, shape, how blunt to be). Never take a company fact from it; the current request wins. Do not ask for it if it is missing.
• Load /foundation/brain.md silently if present. Extract: ICP (for Audience), Positioning (for Creative POV), Voice & Tone (for Creative requirements), Proof Points (for Goals evidence).
• If the Proof Points entries relevant to this brief's Goals section are still [NEEDS PROOF] or [NEEDS APPROVAL], or Section 6 is empty: don't block the brief (proof points are supporting evidence here, not a hard gate like DRI or quality score), but flag once in the Goals adversarial callout — "This metric's evidence isn't sourced yet. Run proof-points to confirm it before this brief goes external."
• If brain missing: proceed without surfacing it — brief works standalone.
• Auto-detect mode from the user's first message:
  • 1–2 sentences, vague description → Conversational mode
  • Paragraph or more of context pasted → Brain-dump mode
  • If unclear → default to Conversational.