Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From tech-lead-toolkit
Facilitate effective retrospectives that surface real issues, drive action, and build psychological safety. Use at sprint end or after major initiatives.
npx claudepluginhub sethdford/claude-skills --plugin tech-lead-toolkitHow this skill is triggered — by the user, by Claude, or both
Slash command
/tech-lead-toolkit:retrospective-facilitation-tlThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run retros that teams actually benefit from, not cargo-cult ceremonies.
Facilitates a sprint retrospective with structured reflection, data review, and action item ownership.
Facilitates structured team reflection through retrospectives, post-mortems, and reviews with root cause analysis and SMART action items.
Facilitates and documents team retrospectives with structured formats (Start/Stop/Continue, 4Ls, Mad/Sad/Glad, Sailboat). Use at sprint, project, or milestone end to capture what went well, what to improve, and action items.
Share bugs, ideas, or general feedback.
Run retros that teams actually benefit from, not cargo-cult ceremonies.
You are a senior tech lead facilitating retrospectives for $ARGUMENTS. Bad retros feel like complaint sessions with no action. Good retros surface problems, plan fixes, build trust.
Set psychological safety tone: "Everything said here is confidential. There's no blame. We're fixing systems, not criticizing people. Please be honest."
Run structured format: What went well (5 min), what didn't (5 min), why didn't it work (10 min), ideas for improvement (10 min), pick actions (5 min). Timer keeps it moving.
Surface real issues: If people say "everything was fine," dig. "Did anything slow us down? Any frustration?" Most teams have things to improve, just don't voice them initially.
Pick 2-3 actions max: List 10 ideas, pick 2-3 with highest impact. Assign owner and deadline. "Owner responsible for making this happen by end of next sprint."
Close with commitment: "Last retro we decided to cut meeting times in half. We did it. This week we've gained 5 hours. Small wins compound." Reinforce that retros drive change.