retro

Capture a retrospective with What worked, What failed, and What to change next time.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/jukqaz/stack-pilot --skill retro-jukqaz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/jukqaz/stack-pilot/tree/main/addons/stackpilot-dev-kit/claude/skills/retro
Command: npx skills add https://github.com/jukqaz/stack-pilot --skill retro-jukqaz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture a lightweight retrospective after completing work to identify what went well, what didn’t, and actionable improvements.

Core Features & Use Cases

  • Structured recap prompts for What worked, What failed, and What to change next time.
  • Quick reference to deeper guidance at ../../RETRO.md for more context.
  • Lightweight and repeatable: run after each task or sprint to build an improvements history.

Quick Start

Run this skill after you finish a task to generate a concise retrospective covering what worked, what failed, and what to change next time.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I document a post-work retrospective after completing a task?

This Skill facilitates capturing a lightweight post-work retrospective by requiring entries for what worked, what failed, and what to change next time. It provides structured recap prompts to document task outcomes and actionable improvements consistently.

What is a lightweight retrospective and when should I run one?

A lightweight retrospective is a concise post-work review identifying what went well and what to improve. You should run this retrospective after completing each task or sprint to build a repeatable team-learning and process-improvement history.

Can I use this retrospective template for sprint post-mortem reviews?

Yes, this retrospective Skill applies to post-work review scenarios including sprint post-mortems. It documents what worked, what failed, and what to change next time, making it suitable for both individual tasks and sprint-level team-learning reviews.

What is the best way to capture team learning from a completed project?

The best way to capture team learning is running a structured retrospective covering what worked, what failed, and what to change next time. This Skill generates concise post-work documentation to build a repeatable improvements history for process improvement.

Do I need any dependencies to run this retrospective documentation process?

No, you do not need any dependencies to run this retrospective documentation process. The Skill operates independently with no required components, though it references an external RETRO.md file for deeper retrospective context and guidance if needed.