skills.rest
evanfang0054
evanfang0054COMMUNITY
Explore all skills by this author →
GitHub

retrospective

Analyze commit logs, system metrics, and team learnings to generate retrospective reports.

Updated Apr 1, 2026
Search Tags:#retrospective#performance analysis#team improvement#sprint review#engineering culture
One-click install
npx skills add https://github.com/evanfang0054/agent-harness --skill retrospective-evanfang0054
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/evanfang0054/agent-harness/tree/main/skills/retrospective
Command: npx skills add https://github.com/evanfang0054/agent-harness --skill retrospective-evanfang0054

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill facilitates a structured engineering retrospective process, enabling teams to systematically review their work, identify areas for improvement, and document actionable insights.

Core Features & Use Cases

  • Structured Review: Guides a review of recent engineering work, focusing on what went well, what didn't, and what to improve.
  • Data Collection: Automates data collection from commits, learnings, and system metrics.
  • Actionable Insights: Generates a report with patterns, learnings, and action items for future work.
  • Use Case: At the end of a sprint, use this Skill to analyze the team's performance, identify bottlenecks, and plan for future improvements.

Quick Start

Run the 'retrospective' skill to start a new review session for the last sprint.

Frequently Asked Questions about retrospective

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

FAQPage Schema
How do I automate sprint retrospective data collection from commit logs and system metrics?▼

Automating sprint retrospective data collection involves analyzing commit logs, system metrics, and team learnings to systematically review engineering work. This process identifies performance bottlenecks and generates actionable insights for future improvement.

What is a structured engineering retrospective and how does it improve team performance?▼

A structured engineering retrospective is a systematic review process focusing on what went well, what didn't, and what to improve. It enhances team performance by identifying work patterns, documenting learnings, and proposing actionable solutions.

Can I use this retrospective process to analyze system metrics and team learnings for a sprint review?▼

Yes, you can use this retrospective process to analyze system metrics and team learnings during a sprint review. It guides the evaluation of recent engineering work to identify issues and document actionable insights for future planning.

What's the best way to identify engineering bottlenecks and document action items at the end of a sprint?▼

The best way to identify engineering bottlenecks is to run an automated retrospective session analyzing commits and metrics. This generates a comprehensive report containing patterns, learnings, and specific action items for future work.

Do I need specific tools for commit analysis and system metrics collection to run a retrospective?▼

Yes, conducting an engineering retrospective requires tools for commit analysis, system metrics collection, and learning capture. These tools provide the necessary data to systematically review performance and propose solutions.

Related Skills

Explore More Software Engineering Skills→
sanskarbasnetsanskarbasnet
1

retro

Aggregate commit history, work patterns, and quality metrics into weekly retrospectives.

Community
Advanced
phurynphuryn
25.0k

retro

Facilitate structured sprint retrospectives and generate prioritized action items with owners and deadlines.

Community
Intermediate
SoSoBurnerSoSoBurner

retro

Generate weekly engineering retrospective reports from commit history and code quality metrics.

Community
Advanced
mahg-esmahg-es
3

retrospective

Facilitate structured sprint retrospectives and generate action plans.

Official
Intermediate