retrospective

Solid

Post-interaction retrospective analysis — use after completing a significant task, conversation, or phase to extract lessons, identify process improvements, and update procedures

AI & Automation 77 stars 13 forks Updated today MIT

Install

View on GitHub

Quality Score: 88/100

Stars 20%
63
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
70
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Retrospective ## Purpose Analyze a completed interaction or task to extract lessons, identify process improvements, and update procedural memory. ## When to Use - After a multi-step task completes (success or failure). - After a user interaction that revealed a gap or surprise. - After an obstacle was resolved (capture the resolution pattern). - Scheduled: end of each active work session. ## Workflow 1. **Reconstruct timeline** — What happened, in what order? What was the goal? 2. **Identify outcomes** — Did it succeed? Partially? What was the quality? 3. **Extract surprises** — What was unexpected? What assumptions broke? 4. **Find patterns** — Does this match any existing procedural knowledge? Does it contradict any? 5. **Derive lessons** — Concrete, actionable learnings (not vague platitudes). 6. **Update memory** — Write observations, update procedures if warranted, flag contradictions for user review. ## Output Format ```yaml subject: <what was analyzed> date: <YYYY-MM-DD> outcome: success | partial | failure surprises: - <unexpected finding> lessons: - <concrete actionable lesson> procedure_updates: - procedure: <name> change: <what to update> observations: - <observation to store> ``` ## References - `src/genesis/learning/procedural/` — Procedure CRUD for updates - `src/genesis/learning/observation_writer.py` — Writing observations

Details

Author
WingedGuardian
Repository
WingedGuardian/GENesis-AGI
Created
2 months ago
Last Updated
today
Language
Python
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category