gtm-weekly-context-updatelisted

# 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`](../product-marketing-os/SKILL.md) — feed the refreshed context into the workflow - [`pmm-competitive-intelligence`](../pmm-competitive-intelligence/SKILL.md) — investigate competitor-radar changes - [`gtm-signal-campaign`](../gtm-signal-campaign/SKILL.md) — act on new signals - [`pmm-coach`](../pmm-coach/SKILL.md) — review before anything customer- or exec-facing. ## 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"/"