retro SKILL.md skillA
retro from qa-aman/claude-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add qa-aman/claude-skills/retro@git:20261019.be4abccPins git:20261019.be4abcc in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- qa-aman/claude-skills
- Path
skills/by-role/marketing/retro/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261019.be4abcc, committed Oct 19, 2026
- First version recorded
- May 4, 2026
- Size
- 13,719 bytes
- Repository stars
- 21
- License
- MIT
Capture learnings from a campaign, launch, sprint, or initiative using Five Whys (Taiichi Ohno, Toyota Production System) for root cause analysis and Start-Stop-Continue for action planning. Append reusable insights to knowledge/learnings.md so future runs of the OS get smarter. Use when the user asks for a retro, retrospective, post-mortem, "what did we learn", "campaign wrap-up", "lessons learned", or after a campaign or launch ends. Critical feedback loop that makes the OS compound over time.
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 Captures structured learnings and persists them. The OS gets smarter every time this runs. Built on Five Whys (Taiichi Ohno) for root cause analysis and Start-Stop-Continue for action planning. The combination prevents "surface retros" - where the team identifies symptoms but repeats the same mistakes with different details. ## Frameworks ### Five Whys - Taiichi Ohno, Toyota Production System When something goes wrong - or unexpectedly right - ask "why?" five times. Each answer becomes the basis for the next "why." The goal is the root cause, not the symptom. Marketing example: - Campaign missed pipeline target by 40%. Why? - Lead quality was poor. Why? - We targeted too broadly. Why? - We hadn't updated our ICP definition. Why? - No one owns ICP maintenance. Why? - There's no process for reviewing ICP after each cycle. - **Root cause: missing process, not bad execution.** Without Five Whys, the team would have concluded "lead quality was poor" and changed the ad creative. The problem would repeat. **Five Whys applies to wins too.** An unexpected outperformance has a root cause. Understanding it is how you replicate it, not just celebrate it. …
Read the whole file at its exact version.
How to install
mdr add qa-aman/claude-skills/retro@sha256:e28acf987e0e6fb9The line at the top of this page pins the label git:20261019.be4abcc, 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_3bgot5ce4dwv6mrp)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between May 4, 2026 and Oct 19, 2026, about one every 84 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261019.be4abcc latest | 2026-10-19 | be4abcc | 13,719 B | A | view · diff |
| git:20260808.7dfb5c7 | 2026-08-08 | 7dfb5c7 | 13,637 B | A | view · diff |
| git:20260504.0d54b6b | 2026-05-04 | 0d54b6b | 8,850 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 (13719 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
qa-aman/claude-skills · 21 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3bgot5ce4dwv6mrp GET https://markdownregistry.com/api/v1/resolve?ref=qa-aman/claude-skills/retro GET https://markdownregistry.com/api/v1/blob/e28acf987e0e6fb9f6a6f3b6069644e39aac4659014f225012002c31f494f646
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 qa-aman/claude-skills
Every file in qa-aman/claude-skills