Verified:GitHub

retrospective

Document lessons learned from completed interactions into structured YAML payloads.

90|16|Updated Mar 21, 2026

Search Tags:#workflow #retrospective #postmortem #knowledge-management #process-improvement #lessons-learned #procedural-memory

Ready to run

npx skills add https://github.com/WingedGuardian/GENesis-AGI --skill retrospective-wingedguardian

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/WingedGuardian/GENesis-AGI/tree/main/src/genesis/skills/retrospective
Command: npx skills add https://github.com/WingedGuardian/GENesis-AGI --skill retrospective-wingedguardian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture and codify lessons learned after a completed interaction to improve future performance and avoid repeating mistakes.

Core Features & Use Cases

Structured post-mortems: Reconstruct timelines, identify outcomes, and derive concrete improvements.
Procedural memory updates: Generate actionable changes to procedures and observations to inform future work.
Cross-project learning: Apply insights across teams and tasks to reduce repeating issues.

Quick Start

Provide a retrospective analysis for the most recent completed task to extract actionable lessons and update procedural memory.

Frequently Asked Questions about retrospective

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

FAQPage Schema

How do I document lessons learned after completing a multi-step task?▼

To document lessons learned, you run a retrospective analysis that identifies outcomes, surprises, and patterns from the completed task, generating structured YAML procedure updates and observations to store in procedural memory.

What is the best way to run a structured post-mortem for process improvement?▼

A structured post-mortem reconstructs the task timeline, identifies concrete outcomes and surprises, and derives actionable procedure updates and observations to refine workflows and inform future performance.

How does procedural memory capture work for cross-project knowledge management?▼

Procedural memory capture works by generating a structured YAML payload containing the subject, date, outcome, lessons, and procedure updates from a completed interaction to codify knowledge for cross-project learning.

Can I use this retrospective approach after any completed conversation or project phase?▼

Yes, you can apply retrospective analysis after any completed multi-step task, conversation, or project phase to extract actionable lessons and update procedural memory for future work.

What specific data format is produced when capturing lessons learned?▼

Capturing lessons learned produces a structured YAML payload containing fields for subject, date, outcome, surprises, lessons, procedure updates, and observations to be stored in procedural memory.

When should I avoid using a retrospective for workflow improvement?▼

Retrospectives are designed for completed interactions; you should avoid using them during ongoing tasks, as the process requires a finished timeline to reconstruct events, identify surprises, and derive concrete improvements.