retro

Generate weekly engineering retrospectives from local project activity and team contributions.

1|Updated May 27, 2026

Search Tags:#engineering #project-history #retrospectives #retro #team-performance #gstack

Ready to run

npx skills add https://github.com/mi179/claude-skills --skill retro-mi179

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/mi179/claude-skills/tree/main/user/gstack/retro
Command: npx skills add https://github.com/mi179/claude-skills --skill retro-mi179

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives help teams review past work, surface contributions, and identify growth opportunities with persistent history and trend tracking across sprints.

Core Features & Use Cases

Break down per-person contributions with praise and growth areas.
Analyze commit history, timelines, and learnings to surface actionable insights for the team.
Maintain a persistent backlog of retrospectives to track progress over time.

Quick Start

Ask the retro skill to generate a weekly retrospective for the current sprint.

Frequently Asked Questions about retro

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

FAQPage Schema

How do I generate a structured weekly engineering retrospective for my team?▼

To generate a weekly engineering retrospective, the skill analyzes project activity, commit history, and team contributions to produce per-person praise and growth areas. It requires local retrospective files stored under the gstack projects directory to render historical context.

What is the best way to track engineering team performance and growth areas across sprints?▼

Tracking engineering team performance across sprints requires analyzing persistent retrospective history and timelines. This skill maintains a persistent backlog of retrospectives to track progress over time, surfacing actionable insights and per-person contributions from prior project activity.

How do I analyze commit history and timelines to surface actionable insights for a sprint review?▼

Analyzing commit history and timelines for sprint reviews involves reading prior retros and learnings files to extract per-person contributions. The skill processes this local project data to highlight individual praise and identify specific growth areas for the team.

Do I need a specific local directory structure to store project retrospectives?▼

Yes, storing project retrospectives requires a specific local directory structure. You need local retrospectives stored under the gstack projects path for the repository slug, which the skill reads to render historical context and track performance trends.

Can I review individual and team performance contributions from prior project sprints?▼

Yes, you can review individual and team performance contributions from prior sprints. The skill reads stored retrospective history and timeline files to break down per-person contributions, providing a comprehensive overview of past project activity and growth opportunities.

What limitations exist when tracking engineering retrospective trends over time?▼

A key limitation for tracking retrospective trends is the dependency on local history files. If prior retros, timelines, or learnings files are missing from the gstack projects directory, the skill cannot render full historical context or accurately track long-term team performance.