skills.rest
lithiumtoast
lithiumtoastCOMMUNITY
Explore all skills by this author →
GitHub

retrospective

Guide Agile retrospectives through Derby–Larsen's five stages and save actions to Markdown.

1|1|Updated Feb 15, 2026
Search Tags:#documentation#retrospective#agile#sprint#project-management#continuous-improvement#team-process
One-click install
npx skills add https://github.com/lithiumtoast/hearthportal --skill retrospective-lithiumtoast
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/lithiumtoast/hearthportal/tree/main/.claude/skills/retrospective
Command: npx skills add https://github.com/lithiumtoast/hearthportal --skill retrospective-lithiumtoast

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides teams through a structured Agile retrospective, turning reflections into actionable improvements and preserving the results for future reference.

Core Features & Use Cases

  • 5-stage Derby–Larsen process guides the team through scope, setup, data gathering, insights, and actions.
  • Survival check cross-references the previous retro to ensure real progress.
  • Actionable outputs generate 1–3 concrete actions with owners and deadlines persisted to docs/software/retrospectives.
  • Standardized artifacts store the narrative and the results for cross-reference.

Quick Start

Initiate a retrospective for the current cycle and persist the result to docs/software/retrospectives/ with a UTC timestamped filename.

Frequently Asked Questions about retrospective

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

FAQPage Schema
How do I run an agile retrospective that produces concrete action items?▼

An agile retrospective guides teams through Derby–Larsen's five stages—scope, setup, data gathering, insights, and actions—ending with 1–3 concrete action items that have assigned owners and deadlines.

What is the Derby-Larsen retrospective model for sprint reviews?▼

The Derby-Larsen retrospective model structures sprint reviews into five stages: setting the scope, gathering data, generating insights, deciding on actions, and closing, ensuring continuous improvement.

How do I save and document sprint retrospective results in markdown?▼

Save sprint retrospective results as standardized Markdown files in a directory like docs/software/retrospectives using a UTC timestamped filename, preserving the narrative and action items for future cross-reference.

Can I use a structured retrospective process for post-incident reviews?▼

Yes, a structured retrospective process applies to various team cycles including post-incident reviews, sprints, and feature releases, adapting the five-stage framework to analyze incidents and prevent recurrence.

How do I check if previous retrospective action items were completed?▼

Perform a survival check by cross-referencing the previous retrospective's saved Markdown file to validate that prior action items had owners, deadlines, and were actually executed before starting a new cycle.

Do I need dedicated project-management software to track continuous improvement actions?▼

No, you do not need dedicated project-management software if you validate that continuous improvement actions have clear owners and deadlines, persisting them as standardized Markdown artifacts for team tracking.

Related Skills

Explore More Software Engineering Skills→
bowiemaxbowiemax

retro

Facilitate structured sprint retrospectives and generate prioritized action items.

Community
Intermediate
phurynphuryn
25.0k

retro

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

Community
Intermediate
bacocobacoco

project-manager

Guide Agile software projects with sprint planning, estimation, and risk management.

Community
Intermediate
cpliakascpliakas
4

facilitate-retrospective

Facilitate structured retrospectives using the Derby-Larsen five-phase framework.

Community
Advanced