retrospective

Convert incident timelines and postmortem reports into owner-assigned, time-boxed improvement actions.

1|Updated Mar 17, 2026

Search Tags:#retrospective #agile #postmortem #action-items #continuous-improvement #team-feedback

Ready to run

npx skills add https://github.com/yknothing/prodcraft --skill retrospective-yknothing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/yknothing/prodcraft/tree/main/skills/08-evolution/retrospective
Command: npx skills add https://github.com/yknothing/prodcraft --skill retrospective-yknothing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Retrospective turns evidence from postmortems, incident reports, and sprint reviews into a small set of concrete improvements with owners and deadlines, closing the feedback loop and guiding the next cycle.

Core Features & Use Cases

Transform operational data into actionable improvement actions that feed intake and planning.
Define 3-5 specific improvements with owners and timeboxed deadlines for accountability.
Link insights to downstream skills (intake, planning) to ensure follow-through across the lifecycle.
Use case: after a sprint or incident, capture what worked, what didn't, and a concrete plan to improve the next cycle.

Quick Start

Schedule a retrospective at the end of a sprint and generate 3-5 concrete improvement actions with owners and deadlines.

Frequently Asked Questions about retrospective

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

FAQPage Schema

How do I turn postmortem reports into actionable improvement items?▼

Run a retrospective workflow that transforms incident timelines and postmortem reports into 3-5 owner-assigned, time-boxed improvement actions, closing the feedback loop with concrete accountability for the next cycle.

What is the best way to assign owners and deadlines for agile sprint retrospective action items?▼

Use a structured retrospective process that defines 3-5 specific improvements with assigned owners and timeboxed deadlines, ensuring actionable follow-through and team accountability.

Can I use this for incident reviews and continuous improvement rituals?▼

Yes, this applies to agile teams conducting sprint retrospectives, incident reviews, and continuous improvement rituals. It requires clear input-output contracts and a defined quality gate to ensure actionable follow-through.

How do I ensure retrospective findings actually feed into intake and planning?▼

Link retrospective insights to downstream skills like intake and planning to ensure follow-through across the lifecycle, transforming operational data into actionable improvement actions that guide the next cycle.

How many action items should a sprint retrospective generate?▼

A sprint retrospective should generate 3-5 specific improvement actions. Keeping the set small ensures owners can realistically complete the timeboxed deadlines and maintain continuous improvement momentum.