aped-retro

Generates actionable improvement plans from Jepira-style epic retrospective analysis and prior METR evidence.

2|Updated Mar 12, 2026

Search Tags:#documentation #process improvement #lessons learned #readiness assessment #epic #retro #delivery analysis

Ready to run

npx skills add https://github.com/yabafre/aped-claude --skill aped-retro

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aped-retro
Source: https://github.com/yabafre/aped-claude/tree/main/src/templates/skills/aped-retro
Command: npx skills add https://github.com/yabafre/aped-claude --skill aped-retro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill captures what went well and what didn’t during an epic retrospective, then converts those insights into owned, time-bound action items that unblock the next epic.

Core Features & Use Cases

Post-epic analysis across stories: reviews story development and review patterns to surface systemic gaps and recurring failures.
Continuity with prior retros: audits what was promised last time and checks evidence of completion to prevent repeating the same mistakes.
Next-epic readiness & planning guardrails: previews the next epic’s dependencies and adds a readiness assessment and critical path before moving forward.

Quick Start

Run the retro for your last fully completed epic by invoking aped-retro.

Frequently Asked Questions about aped-retro

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

FAQPage Schema

How do I run an epic retrospective after shipping stories?▼

An epic retrospective synthesizes story-level lessons into actionable improvements after an epic finishes shipping. It reviews development patterns, audits prior retro promises, and persists lessons to your output directory.

What is the best way to turn lessons learned into next-epic readiness?▼

The best way to turn lessons learned into next-epic readiness is by capturing what went well and what didn't, then converting insights into owned, time-bound action items that unblock the next epic.

Can I target a specific epic number when doing a retrospective?▼

Yes, you can optionally target a specific epic number when running a retrospective. The tool reads project configuration and state to analyze the specified epic's story outputs and prior retro evidence.

How does a retrospective check if prior lessons learned were actually applied?▼

A retrospective checks continuity by auditing what was promised last time and checking evidence of completion. This prevents repeating systemic gaps and recurring failures across subsequent epics.

Do I need to run APED scripts before starting a delivery analysis retro?▼

Yes, you need to check enablement via APED scripts before starting a delivery analysis retro. This verifies your environment so the tool can read project config and persist retro artifacts correctly.

When do I need a readiness assessment before moving to the next epic?▼

You need a readiness assessment when an epic has finished shipping and you are preparing to move forward. It previews the next epic's dependencies and adds critical path planning guardrails.