write-retro SKILL.md skillA
write-retro from atman-33/workhub is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add atman-33/workhub/write-retro@git:20260720.f88c2b0Pins git:20260720.f88c2b0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- atman-33/workhub
- Path
plugins/team-ops/skills/write-retro/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260720.f88c2b0, committed Jul 20, 2026
- Size
- 1,158 bytes
- Repository stars
- 3
- License
- MIT
Facilitate and record a sprint retrospective (KPT) with follow-up on the previous retro's action items. Use at sprint end when the user wants a retrospective, KPT, or team improvement discussion.
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
# Write a retrospective Facilitate a KPT (Keep / Problem / Try) anchored on sprint facts, and keep action items accountable across sprints. ## Steps 1. Resolve the sprint (default: latest). Read `review.md` if present, `progress-history.jsonl`, and the **previous** sprint's `retro.md`. 2. **Follow up first**: list the previous retro's Try/action items and ask which happened — carry unfinished ones forward explicitly. 3. **Facilitate KPT**: propose seed observations from the data (velocity swings, items stuck in `doing`, scope changes), then collect the team's Keep / Problem / Try. Push each Try to be actionable (owner + when). 4. **Write `sprints/<id>/retro.md`** (team content language): KPT table, action items with owners, previous-retro follow-up results. 5. If a Try is a durable process rule, propose promoting it to `knowledge/rules/` via `team-kb-save`. Append an activity-log line.
Read the whole file at its exact version.
How to install
mdr add atman-33/workhub/write-retro@sha256:bb7e1c851e19c415The line at the top of this page pins the label git:20260720.f88c2b0, 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_ej26tdwztq2bnsyg)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jul 20, 2026.
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 (1158 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
atman-33/workhub · 3 stars · license MIT · pushed 2026-10-15 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ej26tdwztq2bnsyg GET https://markdownregistry.com/api/v1/resolve?ref=atman-33/workhub/write-retro GET https://markdownregistry.com/api/v1/blob/bb7e1c851e19c415e85d742886f22406809d1c4242bdc0432f3d12fca9d18cb8
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.