retro SKILL.md skillA
retro from lamngockhuong/aiteamkit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add lamngockhuong/aiteamkit/retro@git:20261029.cb16052Pins git:20261029.cb16052 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- lamngockhuong/aiteamkit
- Path
plugins/atk/skills/retro/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261029.cb16052, committed Oct 29, 2026
- First version recorded
- Oct 1, 2026
- Size
- 6,616 bytes
- Repository stars
- 12
- License
- MIT
Run a sprint retrospective on evidence rather than memory, and write the status report that goes up: what the data says about the sprint, what the team says, the few actions worth taking with an owner each, and whether last retro's actions actually happened. Use at the end of a sprint, a milestone, or a phase, and when a status report is due to a PM or a client. Triggers on: "retro", "retrospective", "họp retro", "tổng kết sprint", "sprint review", "status report", "振り返り", "レトロスペクティブ…
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
# Retrospective and Status Report (`atk:retro`) Brings facts to a retrospective so the discussion is not a memory contest, and produces the report a PM or client reads. Its strongest habit is checking the previous retro first: a team that never closes its actions does not need another list of actions. ## Scope Handles: gathering sprint evidence from git, the tracker, and CI, checking the previous retro's actions, structuring the discussion, capturing what the team says, and writing both the retro record and the status report. Does NOT handle: running the meeting for the team, deciding priority for the next sprint, which the PM does in sprint planning, or performance evaluation of individuals, which this skill never produces. ## Roles PM or a rotating facilitator runs the session. The whole team contributes. Each action gets one named owner. See `shared/team-roles.md`. ## Invocation ```bash /atk:retro <sprint> # Evidence, discussion structure, and record for a sprint /atk:retro 2026-09-01..2026-09-15 # Use an explicit date range /atk:retro --data-only # Gather the evidence pack before the meeting …
Read the whole file at its exact version.
How to install
mdr add lamngockhuong/aiteamkit/retro@sha256:22e5a0687d6f11eaThe line at the top of this page pins the label git:20261029.cb16052, 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_dr43gdtrucohp4vy)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Oct 1, 2026 and Oct 29, 2026, about one every 14 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261029.cb16052 latest | 2026-10-29 | cb16052 | 6,616 B | A | view · diff |
| git:20261014.03c655e | 2026-10-14 | 03c655e | 6,595 B | A | view · diff |
| git:20261001.ed02384 | 2026-10-01 | ed02384 | 6,388 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 (6616 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
lamngockhuong/aiteamkit · 12 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_dr43gdtrucohp4vy GET https://markdownregistry.com/api/v1/resolve?ref=lamngockhuong/aiteamkit/retro GET https://markdownregistry.com/api/v1/blob/22e5a0687d6f11eab1d89e8f75f0409c455b864c3b1d9bcc3ab305548aecd60c
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 lamngockhuong/aiteamkit
Every file in lamngockhuong/aiteamkit