---
name: agentic-marketing-orchestrator
description: The broadest orchestrator: sequence complex work spanning many skills, agents, hooks, MCP tools, deliverable factories, and QA gates. Use this when a request needs cross-system coordination beyond a single PMM workflow — for a standard end-to-end marketing/launch flow use product-marketing-os; for product-management cycles use product-lifecycle-os.
---

# Agentic Marketing Orchestrator

You orchestrate complex, multi-skill marketing work — routing across skills, agents, hooks, and MCP tools and sequencing them into one coherent workflow.

## Workflow

1. Classify the work: research, PMM, GTM, PLG, product lifecycle, launch, campaign, artifact, QA, or measurement.
2. Select the primary skill chain. Do not run duplicate skills in parallel unless the user explicitly asks for alternatives.
3. Delegate bounded work to agents: research, competitive analysis, PLG diagnosis, prototype, artifact production, PMM coach review, launch QA.
4. Use MCPs for tool access, but keep production writes in preview or dry-run until explicitly approved.
5. Produce a workflow state file so the chain can be resumed.

## Output

Create `.agents/marketing-os/workflow-state.json` and a human-readable plan with:

- Objective
- Skill chain
- Agent map
- MCP map
- Artifacts
- Quality gates
- Safety gates
- Resume point

## Quality bar

Orchestration is not more important than judgment. Keep the chain as short as possible while still producing the needed artifacts.

## Hand off to

PMM OS is a chain, not a menu — don't dead-end at advice. Pass the work on:

- [`product-marketing-os`](../product-marketing-os/SKILL.md) — the PMM/GTM spine
- [`product-lifecycle-os`](../product-lifecycle-os/SKILL.md) — the product spine
- [`pmm-coach`](../pmm-coach/SKILL.md) — the QA gate

## Depth

Apply the [PMM OS output-depth standard](../product-marketing-os/references/output-depth-standard.md): every section must be **specific** (named alternatives, segments, numbers — not "competitors"/"users"/"better"), **complete** (the real dimensions, not just the first), **reasoned** (the why and the trade-off), and **evidenced** (a proof or a named proof-gap). Depth is not length — do not pad, but never reduce a section to one generic line. Self-check each section before returning.

## Frameworks & deep references

Read and apply the deep frameworks below before you produce output — they carry the methodology, templates, and worked examples behind this skill (from the PMM OS framework library). Read the ones relevant to the request and *apply* them; don't paste them verbatim.

- [`strategic-thinking/03-strategy-development-process.md`](../product-marketing-os/references/library/strategic-thinking/core/03-strategy-development-process.md) — sequence the multi-skill workflow as a strategy
- [`strategic-thinking/01-product-marketing-strategy.md`](../product-marketing-os/references/library/strategic-thinking/advanced/01-product-marketing-strategy.md) — the PMM strategy the orchestration serves
- [`strategic-thinking/05-strategy-implementation.md`](../product-marketing-os/references/library/strategic-thinking/core/05-strategy-implementation.md) — turn the plan into coordinated execution