retro

Generates weekly engineering retrospectives from commit history, work patterns, and code quality metrics.

Updated Aug 9, 2026
One-click install
npx skills add https://github.com/raghavbadhwar/rstack --skill retro-raghavbadhwar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/raghavbadhwar/rstack/tree/main/retro
Command: npx skills add https://github.com/raghavbadhwar/rstack --skill retro-raghavbadhwar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering teams often lose track of what shipped each week and lack a structured way to review contributions, spot trends, and capture learnings. This Skill automates the weekly retrospective by analyzing commit history, work patterns, and code quality metrics with persistent history and trend tracking. ## Core Features & Use Cases - Automated retro generation: Analyzes commit history, work patterns, and code quality metrics to produce a weekly engineering retrospective. - Team-aware breakdowns: Breaks down per-person contributions with praise and growth areas for each team member. - Persistent history and trends: Loads prior retros, recent timeline events, and learnings from the local gstack project store to track trends over time. - Use Case: At the end of a sprint, ask for a weekly retro to get a summary of what shipped, per-person contribution highlights, and trend comparisons against previous retros. ## Quick Start Ask your agent to run the weekly retro to summarize what the team shipped this week with per-person contributions and trends.

Frequently Asked Questions about retro

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a weekly engineering retrospective automatically?

Invoke the retro skill with a phrase like "weekly retro" or "what did we ship". It analyzes commit history, work patterns, and code quality metrics, then produces a structured retrospective with per-person breakdowns.

What data does an automated engineering retro analyze?

It analyzes git commit history, work patterns, and code quality metrics. It also loads prior retros, recent timeline events, and learnings from the local gstack project directory to provide trend context.

Can a retrospective break down contributions per team member?

Yes, the retro is team-aware and breaks down per-person contributions. It highlights praise-worthy work and identifies growth areas for each contributor based on their commits and activity.

Does the retro skill track trends across multiple weeks?

Yes, it maintains persistent history by reading prior retro files stored under the project's gstack directory. This lets it compare the current week against previous retros and surface trends over time.

When should I run an engineering retrospective skill?

Run it at the end of a work week or sprint, or whenever asked "what did we ship". It can also be proactively suggested at the end of a sprint when proactive skill suggestions are enabled.