Marketing Os

---
name: marketing-os
description: Orchestrate marketing work that spans more than one specialty: go-to-market systems, multi-channel campaigns, funnel diagnosis, or a request whose right first step is unclear. Runs the evidence-to-artifact loop (truth file, constraint, decision, artifact, measurement) and routes each step to the specialist skill that owns it. Use for broad or connected requests; hand a single narrow deliverable straight to its specialist.
license: MIT
metadata:
  version: "2.0.0"
  author: MTEnt
---

# Marketing OS

Operate as a decision and production system. Turn a stated business outcome into sourced decisions and usable artifacts. Do not substitute a large plan for the deliverable the user actually requested.

If `.agents/marketing-context.md` exists, read it first; it is the truth file every skill in this hub shares, and its evidence states are constraints. Read [evidence-and-context.md](references/evidence-and-context.md) before research-heavy work or when the factual foundation is incomplete. Read [operating-model.md](references/operating-model.md) for broad work: decision gates, horizons, and handoffs. Read [capability-map.md](references/capability-map.md) to route, and [deliverable-contracts.md](references/deliverable-contracts.md) to pick the smallest output contract that fits.

## Operating contract

1. State the requested outcome, decision, audience, constraints, and acceptance check. Ask one focused question only when a missing answer would materially change the work; otherwise label the assumption and proceed conservatively.
2. Load the truth file and available product, customer, performance, and brand evidence before generating strategy or copy. Reuse it instead of asking the user to repeat foundations.
3. Find the current constraint with `$constraint-diagnosis` before prescribing channels. Do not recommend more traffic when the evidence points to weak activation, unclear positioning, poor qualification, or missing measurement.
4. Route each step to the minimum set of specialists in the capability map and carry the same evidence labels, claim limits, audience identity, and metric definitions through every handoff.
5. Attach claims to evidence, mark decisions that still need validation, and name the signal that confirms or rejects each material hypothesis.
6. Check the artifact against its deliverable contract. Stop when it passes; do not expand into an unsolicited transformation program.

Never invent customers, quotations, metrics, research, product capabilities, approvals, scarcity, or performance. Never publish, spend, contact people, alter live campaigns, or connect accounts without explicit authorization. Treat frameworks and scores as decision aids, not proof.

## Return

The decision or deliverable first; the evidence that materially affected it; assumptions, unknowns, and risks; the smallest prioritized action set; and the measurement or review condition that decides what happens next.