skills.rest
anderson-0
anderson-0COMMUNITY
Explore all skills by this author →
GitHub

retrospective

Facilitate post-epic retrospective reviews to extract lessons and define improvement actions.

4|2|Updated Apr 1, 2026
Search Tags:#software development#retrospective#process improvement#team collaboration#lessons learned#epic review
One-click install
npx skills add https://github.com/anderson-0/mighty-powers --skill retrospective-anderson-0
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/anderson-0/mighty-powers/tree/main/skills/retrospective
Command: npx skills add https://github.com/anderson-0/mighty-powers --skill retrospective-anderson-0

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams avoid repeating mistakes by systematically reviewing completed epics, identifying lessons learned, and creating actionable improvements.

Core Features & Use Cases

  • Epic Review Facilitation: Guides structured retrospectives with project context, story analysis, and team discussion prompts.
  • Continuous Improvement Tracking: Compares previous commitments, technical debt, challenges, and outcomes to surface process improvements.
  • Use Case: After finishing a major software epic, use this Skill to analyze implementation notes, gather team insights, and prepare a retrospective document with concrete action items.

Quick Start

Use the retrospective skill to run a review of the completed epic and capture lessons learned, successes, challenges, and next steps.

Frequently Asked Questions about retrospective

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

FAQPage Schema
How do I run a retrospective for completed software epics?▼

To run a retrospective for completed software epics, you need to analyze implementation records and facilitate team discussions. This process extracts lessons learned from the epic review and defines actionable improvement steps for future development workflows.

What is the best way to extract lessons learned from a software development epic?▼

The best way to extract lessons learned from a software development epic is through structured post-epic retrospective reviews. By comparing previous commitments, technical debt, and challenges against actual outcomes, teams can systematically surface process improvements.

How does post-epic review help with continuous process improvement?▼

Post-epic review drives continuous process improvement by analyzing completed epics against previous commitments and technical debt. This helps teams avoid repeating mistakes by identifying specific challenges and generating a structured retrospective document with concrete action items.

What do I need to prepare for a team retrospective on a completed epic?▼

For a team retrospective on a completed epic, you need project configuration data and artifact discovery inputs like implementation records. Resolving workflow customization and gathering team discussion notes allows the generation of a structured retrospective document.

Can I use epic reviews to track and reduce technical debt?▼

Yes, you can use epic reviews to track and reduce technical debt. The retrospective process compares previous technical debt commitments against actual outcomes, surfacing challenges and defining actionable improvements to prevent recurring development issues.

Related Skills

Explore More Software Engineering Skills→
ncptuanncptuan

bmad-retrospective

Discover completed epics, validate story status, and synthesize retrospective lessons.

Community
Advanced
MichaelSolatiMichaelSolati

retrospective

Compile and analyze sprint retrospective data from project artifacts into structured reports.

Community
Advanced
zm2231zm2231

meeting-notes

Capture and synthesize meeting notes with action item and decision extraction.

Community
Advanced
Nir-BhayNir-Bhay
19

backlog-refinement-guide

Guide backlog refinement sessions using the DEEP framework and Planning Poker.

Community
Intermediate