hs-retro

Conduct structured GTM retrospectives anchored to OKRs with root cause analysis.

5|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/stefanoskarakasis/Product-Marketing-Skills --skill hs-retro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hs-retro
Source: https://github.com/stefanoskarakasis/Product-Marketing-Skills/tree/main/pmm-execution/skills/retro
Command: npx skills add https://github.com/stefanoskarakasis/Product-Marketing-Skills --skill hs-retro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps product marketing teams conduct structured, GTM-focused retrospectives, ensuring that post-launch reviews and other sessions yield actionable insights and decisions that improve future outcomes.

Core Features & Use Cases

  • Structured Retrospectives: Guides teams through a structured process to diagnose root causes and make actionable decisions.
  • OKR Anchoring: Ensures that the retro is anchored to specific OKRs, providing a clear link to business goals.
  • Brain Learning: Incorporates learnings from past sessions to improve future outcomes and provide more relevant insights.
  • Use Case: After a product launch, use this Skill to review the cycle, identify areas that went well and areas that need improvement, and make decisions to improve the next cycle.

Quick Start

Run a structured GTM retrospective on the Q2 product launch using the 'hs-retro' skill.

Frequently Asked Questions about hs-retro

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I conduct a product marketing retrospective tied to GTM outcomes?

A product marketing retrospective evaluates GTM outcomes by anchoring sessions to OKRs and diagnosing root causes. This automates the structured review process, turning post-launch data into actionable decisions for future cycle improvements.

What is the best way to structure a GTM retrospective around OKRs?

Structuring a GTM retrospective around OKRs involves linking session data directly to business goals. This approach ensures post-launch reviews focus on specific objective outcomes, applying root cause analysis to identify areas needing improvement.

Do I need a product-marketing-context to run a GTM retrospective?

Yes, a product-marketing-context is required for accurate diagnosis during the retrospective. Providing this context ensures the structured review yields relevant insights and actionable decisions for improving future product launches.

How does pre-mortem risk assessment integrate into a product launch retrospective?

Pre-mortem risk assessment integrates into a retrospective by evaluating anticipated risks against actual session outcomes. This combination helps GTM teams diagnose root causes accurately and make informed decisions to improve future product launches.

Can past GTM session data be used to improve future product marketing retrospectives?

Yes, past session data is incorporated through brain learning to improve future product marketing retrospectives. This mechanism uses historical GTM insights to provide more relevant outcomes and actionable decisions for subsequent cycles.