retro

The 'retro' skill is designed to facilitate weekly engineering retrospectives by providing a comprehensive analysis of a team's development activities. It examines commit history, work patterns, and code quality metrics over time, helping teams gain insights into their workflow, individual contributions, and overall code health. By tracking persistent history and trends, it allows teams to monitor improvements, identify bottlenecks, and maintain accountability across projects, ensuring continuous progress and a culture of reflection and growth.

This skill offers several key features. It breaks down contributions on a per-person basis, highlighting both areas of praise and opportunities for growth, which supports constructive feedback and team development. 'Retro' can be invoked through specific prompts like 'weekly retro,' 'what did we ship,' or 'engineering retrospective.' Additionally, it can proactively suggest retrospectives at the end of a work week or sprint, although this proactive behavior can be disabled according to user preference. Telemetry and analytics tracking are built-in, allowing users to monitor skill usage while maintaining privacy.

The 'retro' skill is ideal for engineering managers, team leads, and development teams seeking structured reflection on their work. It is particularly useful at the end of sprints or work weeks for evaluating productivity, reviewing code quality, and fostering team growth. By consolidating insights from commit history and work patterns, it helps teams make data-driven decisions, enhance collaboration, and improve overall development efficiency. This makes it a practical tool for teams of all sizes aiming to maintain consistent delivery standards and support continuous improvement.