← ClaudeAtlas

retrolisted

Facilitates a structured GTM retrospective for cross-functional squads, anchored to OKRs and launch outcomes, that ends in root causes and decisions rather than venting. Use for post-launch reviews, GTM cycle debriefs, and sprint retrospectives where you need to fix what broke structurally before the next cycle.
stefanoskarakasis/Product-Marketing-Skills · ★ 13 · AI & Automation · score 86
Install: claude install-skill stefanoskarakasis/Product-Marketing-Skills
# retro — GTM Retrospective Engine for PMMs Runs a structured retrospective for cross-functional squads that produces OKR-linked decisions. Not a feelings circle. A diagnostic system. --- ## Trigger - **When:** Post-launch review, GTM cycle debrief, sprint retrospective with a PMM lens, or any cross-functional session where decisions are needed, not just discussion. - **Not for:** Pre-launch risk analysis → use `pre-mortem`. OKR setting for the next quarter → use `pmm-okrs`. Campaign briefing after a retro surfaces a messaging gap → use `gaccs-brief`. Competitive root cause analysis → no dedicated skill yet. - **Example prompts:** - "Run a retro on our Q2 product launch" - "We missed our pipeline KR — let's debrief" - "What went wrong with the enterprise campaign?" - "Facilitate our post-launch review for the analytics dashboard" - "Our last sprint ended badly — help us figure out why" --- ## Inputs - **Args:** Cycle name or launch name (required). Free format — one sentence minimum. - **Defaults:** If no cycle named, run intake before proceeding. Never generate a retro output without a named cycle and at least one OKR to anchor to. - **Context keys:** - `/foundation/brain.md` — optional but recommended. Load Section 2 (ICP), Section 3 (Alternatives & Positioning) and Section 7 (Strategy: priorities, launches with tier, quarterly goals) silently if present. - `/context/meta-patterns.md` — optional; recurring patterns the user has logged from all skills.