retro SKILL.md skillA
retro from stefanoskarakasis/product-marketing-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add stefanoskarakasis/product-marketing-skills/retro@v1.4.0Pins v1.4.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- stefanoskarakasis/product-marketing-skills
- Path
pmm-execution/skills/retro/SKILL.md- Versions recorded
- 5
- Latest version
- v1.4.0, committed Oct 19, 2026
- First version recorded
- Sep 11, 2026
- Size
- 14,092 bytes
- Repository stars
- 7
- License
- MIT
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.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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:** …
Read the whole file at its exact version.
How to install
mdr add stefanoskarakasis/product-marketing-skills/retro@sha256:04526dae9a1f9066The line at the top of this page pins the label v1.4.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_tb3ryfw3mfyhbopp)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 11, 2026 and Oct 19, 2026, about one every 9 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.4.0 latest | 2026-10-19 | f2a0167 | 14,092 B | A | view · diff |
| v1.4.0 | 2026-10-11 | 5b18188 | 14,219 B | A | view · diff |
| v1.4.0 | 2026-10-05 | fc09ef3 | 14,162 B | A | view · diff |
| v1.4.0 | 2026-10-04 | f4b739f | 14,077 B | A | view · diff |
| v1.4.0 | 2026-09-11 | 3e95f56 | 13,697 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (14092 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
stefanoskarakasis/product-marketing-skills · 7 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_tb3ryfw3mfyhbopp GET https://markdownregistry.com/api/v1/resolve?ref=stefanoskarakasis/product-marketing-skills/retro GET https://markdownregistry.com/api/v1/blob/04526dae9a1f90664de129aaf190154193855816d8421654a4fdcedca855fb71
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from stefanoskarakasis/product-marketing-skills
Every file in stefanoskarakasis/product-marketing-skills