Collect a factual retrospective from each task-owned agent and safely dismiss the team after successful work. Use during wrap-up of a completed, green multi-agent task or when explicitly requested.
Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Know which skills are safe — weekly.
SSkills DirectorySkills Directory
Is that skill safe to install?
Are you the author of Team Retrospective?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/oleg-koval-team-retrospective-agent-skills)
---
name: team-retrospective
description: Collect a factual retrospective from each task-owned agent and safely dismiss the team after successful work. Use during wrap-up of a completed, green multi-agent task or when explicitly requested.
license: MIT
compatibility: Codex, Claude Code, and other agent environments with delegation controls.
metadata:
author: Oleg Koval
tags:
- agents
- retrospective
- delegation
- cleanup
---
# Team retrospective
Run after a multi-agent task is complete and its applicable checks are green,
before dismissing its agents. Explicit user instructions to retain agents or
finish early take precedence. Do not spawn agents solely to run this skill.
1. Identify agents, tabs, and sessions owned by this task using the environment's
actual inventory and recorded ownership. Preserve other tasks and sessions.
2. Ask each reachable agent for a concise factual report: what went wrong, failed
approaches, tool or coordination problems, resolutions, and unresolved items.
Ask them to distinguish direct observation from inference. A clean report may
say no issues. Do not request new implementation or speculative findings.
3. Collect each response, or label it unavailable with the reason. Preserve useful
findings and a concise summary in an appropriate task artifact; avoid secrets,
unnecessary transcripts, and public disclosure. Report recurring issues and
unresolved items to the user. Claims remain reports until independently verified.
4. Confirm work and required handoffs are preserved. Dismiss the task-owned agents
and close only their task-owned tabs or panes when safe; verify the result.
Follow the environment's skill and safety rules. Never stop a shared server or
close another task's session. Respect explicit instructions to keep agents.
5. If work is blocked, unfinished, or still active, preserve the agents and report
the blocker instead of treating the task as green. If the environment cannot
contact or dismiss an agent, report the limitation; never claim it was dismissed.
