From tech-lead-toolkit
Run retrospective that surfaces improvements without blame.
How this command is triggered — by the user, by Claude, or both
Slash command
/tech-lead-toolkit:facilitate-retro sprint/quarter team size known issuesThe summary Claude sees in its command listing — used to decide when to auto-load this command
Chain these steps: 1. Use the `retrospective-facilitation-tl` skill to plan retro structure and safe environment 2. Use the `team-charter` skill (if needed) to establish psychological safety norms 3. Synthesize into retro outcomes with clear actions, owners, and next steps After completion, suggest: - How to follow up on action items between retros - How to measure if improvements are working - How to celebrate progress
Chain these steps:
retrospective-facilitation-tl skill to plan retro structure and safe environmentteam-charter skill (if needed) to establish psychological safety normsAfter completion, suggest:
npx claudepluginhub sethdford/claude-skills --plugin tech-lead-toolkit/retroFacilitates agile retrospective for a sprint or period with optional focus, invoking agile-coach agent to generate improvement insights and action items.
/retroFacilitates agile retrospectives by capturing sprint learnings, surfacing past insights, and compounding team knowledge over time.
/flow-retrospective-cycleOrchestrates structured retrospective cycles for retrospectives, producing feedback summaries, prioritized action items with owners, pattern analysis, and improvement metrics.
/sprintManages sprint lifecycle: plans sprints with capacity estimation and story selection, facilitates structured retrospectives, generates release notes from context.
/retrospective-analyzerAnalyzes sprint retrospectives from Linear and GitHub data, generating metrics tables, performance trends, pattern recognition, and discussion topics for team facilitation.