retro

retro is a skill for Claude Code from stefanoskarakasis/Product-Marketing-Skills. It costs 66 tokens per session (3,389 once invoked), scanned A, original, MIT.

A structured review for a product launch, marketing cycle, or team sprint that connects what happened to OKRs, the measurable goals used to track progress. It focuses on causes, decisions, and follow-up actions.

In plain words
What is it for?
Use it to examine missed targets, diagnose launch or campaign problems, and agree on actions after a cross-functional team review.
Why use it?
It turns a post-launch discussion into an evidence-based review instead of a general conversation about what went wrong.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions .claude-plugin.

Part of the pmm-execution plugin — 8 skills, 8 commands shipped together

Good fit Use it to examine missed targets, diagnose launch or campaign problems, and agree on actions after a cross-functional team review.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/stefanoskarakasis/product-marketing-skills/retro
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add stefanoskarakasis/Product-Marketing-Skills --skill retro
Clone the repo
git clone --depth 1 https://github.com/stefanoskarakasis/Product-Marketing-Skills

Made for: Claude Code.

Or install pmm-execution, the plugin that ships this one along with the rest of its 8 skills, 8 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for retro

README.md
[![agentmods](https://agentmods.dev/badge/skills/stefanoskarakasis/product-marketing-skills/retro/github.svg)](https://agentmods.dev/skills/stefanoskarakasis/product-marketing-skills/retro)
Your own site
<a href="https://agentmods.dev/skills/stefanoskarakasis/product-marketing-skills/retro"><img src="https://agentmods.dev/badge/skills/stefanoskarakasis/product-marketing-skills/retro/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for retro

Your own site · 80×15
<a href="https://agentmods.dev/skills/stefanoskarakasis/product-marketing-skills/retro"><img src="https://agentmods.dev/badge/skills/stefanoskarakasis/product-marketing-skills/retro.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,389 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00066 $0.03389
Opus 5.5 $0.00026 $0.01356
Sonnet 5.5 $0.00013 $0.00678
Haiku 4.5 $0.00007 $0.00339

Measured 11d ago against content hash 04526dae9a1f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

retro scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

pmm-execution/skills/retro/SKILL.md · 295 lines

How it starts

The opening of the file, as written. The whole thing — 295 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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.

Connectors (Optional)

Connector What it adds
~~project tracker Launch tasks and outcomes
~~knowledge base Launch docs and OKRs
~~team chat Launch threads
~~calendar Retro scheduling and attendees

No connectors? Paste the material and I'll work from that. The output has the same shape. Pulled facts are drafts: each is tagged with category, tool and date, and nothing is written until you confirm.


Pre-flight

Before anything else, check /foundation/brain.md.

Read the full file on GitHub · 295 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago Changed · -3 lines · -19 tokens per session 04526dae9a1f
  2. 19d ago Changed eceee3b5d5fb
  3. 24d ago Changed · +2 lines 0c13a9642ca2
  4. 26d ago Changed · +12 lines a8268401f311
  5. 1mo ago Changed · +2 lines f34f0a0647a5
  6. 1mo ago Changed · -1 lines 5c37dbd5aa5a
  7. 2mo ago First seen · 283 lines · 85 tokens per session scan A 948071a77f94

Subscribe to this mod's changes

retro is a skill published in the GitHub repository stefanoskarakasis/Product-Marketing-Skills (8 stars, last pushed 3d ago), licensed MIT. It adds 66 tokens to every session and 3,389 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

report

A way to export a chat card or reply as a standalone HTML report, meaning a file that can open in a browser without the chat application. It preserves the card template, including right-to-left Persian or left-to-right English layouts.

smk-labs/claude-plugins · 57 tokens

k8s-rightsize

Right-size Kubernetes CPU and memory requests from Prometheus usage (p95 CPU, p98 memory over 7 days), size the node count, tune KEDA autoscaling. Use when asked to rightsize workloads, cut node cost, or "how many nodes do we need".

smk-labs/claude-plugins · 62 tokens

owasp-security

Deep OWASP reference: Top 10 2025, ASVS 5.0, secure patterns, per-language quirks, LLM Top 10 and agentic AI security. Use for an in-depth security review, auth work, or hardening an LLM or agent app. For the everyday baseline use secure-coding.

smk-labs/claude-plugins · 72 tokens

fig

One self-contained HTML file holding a looping animated SVG, for ideas that move: flows, loops, retries, queues, fan-outs. Use when the user says "fig" or a diagram would be better animated.

smk-labs/claude-plugins · 45 tokens

brand

A project-specific visual identity for chat cards and saved reports, using the project's colors, logo, and fonts. It finds these details in the repository or asks the user for them, then stores the result in a committable `.readable/` folder.

smk-labs/claude-plugins · 64 tokens

workspace-rules

A set of guidelines for deciding which rules belong in a repository's workspace instructions and which should be enforced by its build or checks.

smk-labs/claude-plugins · 83 tokens