retrospective

Aggregates git history, conversations, code quality, planning docs, and tests into guided retrospective sessions with actionable outcomes.

1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/joesys/joesys-skills --skill retrospective-joesys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/joesys/joesys-skills/tree/main/skills/retrospective
Command: npx skills add https://github.com/joesys/joesys-skills --skill retrospective-joesys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates and structures project retrospectives by combining AI-driven analysis with human check-ins to surface actionable improvements and a narrative summary.

Core Features & Use Cases

  • 5 parallel channel agents mining data sources (git history, conversations, code quality, planning docs, tests) to build a comprehensive digest.
  • Derives 4–7 discussion topics from the aggregated data, surfacing tensions and opportunities for improvement.
  • Facilitates topic-by-topic discussion with the human, capturing Start/Stop/Continue actions and decisions at each step.
  • Produces three outputs: actionable item list, process improvements, and skill improvements, plus a readable narrative summary.

Quick Start

Invoke the retrospective flow to kick off a guided, multi-source analysis and produce the digest, topic discussions, and narrative outputs.

Frequently Asked Questions about retrospective

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

FAQPage Schema
How do I automate a software project retrospective using git history and planning docs?

Automated retrospectives aggregate git history, planning docs, and conversations through parallel channel agents to synthesize data into discussion topics and actionable improvements.

What is an AI-assisted retrospective and how does it handle team discussions?

AI-assisted retrospectives mine multiple data sources to derive discussion topics, then guide human-in-the-loop conversations topic-by-topic to capture Start, Stop, and Continue actions.

How do I generate action items and a narrative summary from code quality and test data?

By synthesizing code quality and test data alongside git history, the structured retrospective workflow produces actionable item lists, process improvements, and a readable narrative summary.

Can I use automated retrospectives for software projects with conversations and planning documents?

Yes, the retrospective workflow applies to software projects by mining conversations, planning docs, and git history to surface tensions and opportunities for improvement.

What outputs should I expect from a structured team retrospective process?

A structured retrospective delivers an actionable item list, process improvements, skill improvements, and a readable narrative summary derived from aggregated project data.