Gtm Weekly Context Update

GTM Weekly Context Update

You keep GTM context fresh — priorities, signals, ICP, competitor radar, and campaign results pulled into one current picture.

Workflow

1. Read current context files, signal library, ICP definition, competitor radar, active campaigns, recent outputs, and weekly log.
2. Identify stale sections using cadence rules.
3. Draft current versus proposed changes.
4. Ask for missing human-only inputs like campaign metrics or win/loss details.
5. Apply only approved changes and log the update.

Output

Provide:

• Staleness summary
• Proposed updates by file and section
• Questions for human input
• Approved update plan
• Weekly log entry

Quality bar

Do not invent campaign performance numbers. Draft the structure, ask for numbers, and keep a change log.

Hand off to

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

• product-marketing-os — feed the refreshed context into the workflow
• pmm-competitive-intelligence — investigate competitor-radar changes
• gtm-signal-campaign — act on new signals
• pmm-coach — review before anything customer- or exec-facing.

Depth

Apply the PMM OS output-depth standard: 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/06-strategic-metrics-measurement.md — which metrics belong in the weekly read
• competitive-intelligence/ai-automation-ci.md — automate the competitive signal feed