Ai Retro Brief
Use when the user asks to synthesize, summarize, or analyze the AI session retro log — recurring friction in AI-assisted work, patterns across AI sessions, or prep for a team retrospective (e.g. "what patterns are in our AI retros", "prep the AI retro summary for Friday"). Companion to ai-session-retro, which writes the entries this skill reads.
Install
$ agentstack add skill-teamretrohq-teamretro-skills-ai-retro-brief ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-teamretrohq-teamretro-skills-ai-retro-brief) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
AI Retro Brief
Read the team's AI session retro entries and surface recurring patterns as an actionable one-page brief for their retrospective. The audience is humans walking into a retro — they need ranked patterns, evidence, and proposed actions, not a restatement of every entry.
Input
Read every file in docs/ai-retros/entries/ (sorted by the date in the filename). Each entry carries a **Skill:** version stamp — parse each according to its stamp and note any resulting gaps rather than guessing. Legacy format: if a single docs/ai-retros/retro-log.md exists (v1.1 wrote one append-only file, entries under ## YYYY-MM-DD — summary headings), parse its entries too.
If there are fewer than 3 entries, say so and give only a light summary — pattern claims need repetition to mean anything.
Multi-repo rollup: if asked for patterns across several repos, read each repo's docs/ai-retros/entries/ and attribute every theme to its repo(s) in the brief.
The brief
Exactly this structure:
# AI Collaboration Retro Brief — , sessions
## Recurring friction
## Root-cause distribution
## Were suggested fixes adopted?
## Top 3 recommended actions
## Trend
Rules
- Every claim traces to specific dated entries. No pattern claims from a single occurrence.
- Do not soften findings: if most friction traces to briefing quality, say that; if most traces to agent error, say that too.
- Root-cause counts use the fixed vocabulary as-is; if an entry contains an out-of-vocabulary label, flag it rather than silently reclassifying.
- Exclude backfilled entries from the "were fixes adopted?" analysis (they weren't written in sequence), but include their friction in counts.
- Keep it to one page. The brief feeds a conversation; it doesn't replace one.
Save as docs/ai-retros/briefs/brief-YYYY-MM-DD.md (dated, so successive briefs accumulate), stamp it with ai-retro-brief v, commit it, and present it to the user.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: TeamRetroHQ
- Source: TeamRetroHQ/teamretro-skills
- License: MIT
- Homepage: https://www.teamretro.com
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.