reflection

Extract generalizable lessons from completed work via memory_store.

4|Updated Feb 1, 2026

Search Tags:#learning #retrospective #improvement #reflection #root-cause #lessons #memory_store

Ready to run

npx skills add https://github.com/mkalkere/agent-coordinator --skill reflection-mkalkere

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reflection
Source: https://github.com/mkalkere/agent-coordinator/tree/main/.os/skills/meta/reflection
Command: npx skills add https://github.com/mkalkere/agent-coordinator --skill reflection-mkalkere

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extracts insights from completed work to drive continuous improvement by turning experiences into repeatable learnings.

Core Features & Use Cases

Automated retrospective analysis to identify successes and failures and surface actionable lessons.
Root-cause classification and structured recommendations for process improvement.
Persistence of learnings via memory_store with tagging for retrieval in future projects.

Quick Start

Invoke the reflection skill on your latest project using the gathered evidence to generate actionable lessons.

Frequently Asked Questions about reflection

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

FAQPage Schema

How do I conduct a post-project retrospective to extract actionable lessons?▼

A post-project retrospective extracts actionable lessons by gathering evidence from completed work, identifying root causes of outcomes, and formulating structured recommendations to improve future performance. Learnings are then tagged and persisted via memory_store for retrieval in future projects.

What is root-cause analysis in after-action reviews and how does it improve future sprints?▼

Root-cause analysis in after-action reviews identifies the underlying factors driving successes and failures in completed sprints. By classifying these root causes, teams generate structured recommendations that turn experiences into repeatable learnings and drive continuous process improvement.

Can I use retrospective analysis for both team and individual project evaluations?▼

Yes, retrospective analysis applies to post-project evaluations, sprint reviews, and after-action assessments across both teams and individual projects. It gathers evidence and identifies root causes to surface actionable lessons regardless of the project scale or context.

What is the best way to store lessons learned from completed work for future retrieval?▼

The best way to store lessons learned is persisting them via memory_store with tagging for retrieval. This ensures that actionable lessons extracted from retrospectives are saved and can be accessed to drive continuous improvement in future projects.

How do I turn past project failures and successes into process improvements?▼

Turning past project outcomes into process improvements requires gathering evidence from completed work, identifying root causes of failures and successes, and formulating generalizable, actionable lessons. These lessons are persisted via memory_store to guide future performance.