retro

Gather Git activity and backlog status to analyze session retrospectives.

14|6|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/tyevans/tackline --skill retro-tyevans
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/tyevans/tackline/tree/main/skills/teams/retro
Command: npx skills add https://github.com/tyevans/tackline --skill retro-tyevans

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of conducting retrospectives, transforming raw session data into actionable insights and durable learnings.

Core Features & Use Cases

  • Automated Data Gathering: Collects relevant information from Git history, backlog activity, and conversation context.
  • Structured Analysis: Evaluates session performance across velocity, quality, process, blockers, and discoveries.
  • Actionable Learning Extraction: Identifies specific "keep doing," "stop doing," and "try next time" items, sharpening them for implementation.
  • Memory Persistence: Updates project memory with durable insights and captures action items as tasks.
  • Use Case: After a complex development sprint, run this Skill to automatically generate a retrospective report, identify key learnings, and create tasks for process improvements.

Quick Start

Run the retro skill to analyze the current work session and capture learnings.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I automate a development session retrospective using Git history?

Automating a session retrospective involves gathering Git activity, backlog status, and conversation context to analyze velocity, quality, and blockers. The process extracts actionable learnings and updates persistent memory with durable insights.

What is the best way to extract action items from a recent work session?

Extracting action items from a work session requires analyzing conversation context and Git history to identify specific improvements. The process sharpens findings into keep doing, stop doing, and try next time categories for implementation.

How does automated session analysis evaluate process improvement opportunities?

Automated session analysis evaluates process improvements by assessing velocity, quality, blockers, and discoveries from development activity. It identifies patterns and generates actionable recommendations to enhance future workflow efficiency.

Can I persist retrospective learnings across multiple development sprints?

Persisting retrospective learnings across sprints is supported by updating persistent memory with durable insights. This enables historical retro tracking and team learning health assessment to monitor long-term progress.

Does automated retrospective analysis work without additional dependencies?

Automated retrospective analysis operates without additional dependencies, functioning independently. It gathers Git history and conversation context natively to generate structured reports and optional tasks for identified action items.

When should I run an automated retrospective analysis on my backlog?

Run automated retrospective analysis after completing complex development sessions or sprints. It captures conversation context and backlog status to evaluate performance, ensuring learnings are preserved while they remain fresh.