Sprint Retro
Runs a structured team retrospective, turning raw notes or discussion into wins, issues, and committed action items.
Before & after
Same prompt, same agent — the only difference is the skill.
You could do a retro by asking the team to discuss what went well, what didn't, and what to improve. You might want to ask everyone for their thoughts on blockers, wins, and ideas. You could gather feedback through a survey or have a meeting where people share. I'd recommend documenting the discussion and pulling out action items. How many people are on your team, and do you have a format you usually follow?
SPRINT RETRO: Sprint 27 (July 22-26) WHAT WENT WELL (Kept items) • Code review velocity improved 18% (avg 2h → 1.3h turnaround) • Fixed 4 high-priority bugs proactively before launch • New Slack bot reduced meeting spam by 30% WHAT DIDN'T (Pain points) • Feature creep: Added 3 unplanned items mid-sprint; 2 rolled to Sprint 28 • Dependency chain on backend blocked frontend for 2 days • One environment outage; unclear who owns incident comms ACTION ITEMS (Assigned owner, due next sprint) 1. Set intake gate: Product can NOT add mid-sprint items without dropping equivalent scope (Chen) 2. Daily backend standup: 15min sync to unblock dependencies (James) 3. Create incident commander runbook and on-call escalation (Priya) METRIC Story points completed: 34/38 (89% — acceptable given dependencies) Next sprint focus: Reduce dependencies by pairing across teams
About this skill
name: retro description: Use when Structured Claude skill that gives Claude a repeatable workflow for retro.
Retro
One of 337+ skills in the original author's multi-agent claude-skills mega-collection (~19k GitHub stars). Packages the Retro workflow with its own instructions and validation so outputs stay consistent.
What you get
- Public GitHub repo (alirezarezvani/claude-skills)
- the retro skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.
Customize your output
- Fork the repo and adapt the skill's instructions and references to your workflow.
Example output
Activates automatically when your request matches Retro; chains with the other skills, agents, and commands in the collection.
Best for
Creators, builders, and teams using Claude Code.
SKILL.md preview
---
name: retro
description: Use this skill when a team needs a structured retrospective covering what went well, what did not, and concrete action items for the next cycle.
version: 1.0.0
category: AI Agents / Development
author: AgentVolt
license: proprietary
tags:
- ai-agents
- development
---
# Retro
Runs a structured team retrospective, turning raw notes or discussion into wins, issues, and committed action items.
## When to use
… (sign up to view the full skill)More ai & agents skills
View all AI & Agents skills →Skill Status Report
Scan every skill in a project and report which pass validation, which are stale, and which lack required metadata.
Skills Scaffolder
Scaffold a new skills directory — folder structure, metadata, a baseline validation pass — with the right conventions from day one.
Research Bundle
Run a multi-step research task as one pipeline: gather sources, extract findings, validate consistency, emit one structured bundle.
Workspace Admin
Administer a Cowork or Claude workspace — settings, access, configuration — with every change scoped and verified.