Menu

Individual skill

retro

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", "振り返り", "レトロスペクティブ", "weekly report", "/atk:retro".

plugins/atk/skills/retro/SKILL.md

Read pinned source

Source commit 55481d2e4ae3cec8e2050c160303c751bbf20173

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Local scripts
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
12
Repository last updated
Nov 6, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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.