Analyze session logs to compare planned versus actual outcomes and extract reusable patterns.
npx skills add https://github.com/iadr-dev/colab --skill retrospective-iadr-dev
Please help me install this Agent Skill. Skill: retrospective Source: https://github.com/iadr-dev/colab/tree/main/skills/retrospective Command: npx skills add https://github.com/iadr-dev/colab --skill retrospective-iadr-dev
This Skill prevents teams and solo agents from repeating the same mistakes by turning post-session results into reusable knowledge and updated memory.
Run the retrospective learning loop after a significant session (over 30 minutes) so it analyzes the latest session, updates memory files, and writes any new draft skills to .ohc/skills/.
High-intent search queries and answers about installing and using this skill.
Session analysis converts coding session logs into reusable workflow improvements by diffing planned versus actual outcomes and extracting debugging patterns. It parses log files to identify variances and distills recurring solutions into draft skills.
Session analysis for post-coding retrospectives is the process of parsing session logs to compare intended plans with actual results. It identifies failures, variances, and tool-use patterns to update project memory and promote newly discovered skills.
Extract reusable debugging patterns from a long coding session by running a retrospective analysis after sessions exceeding 30 minutes. The process compares planned versus actual outcomes, identifies variances, and distills recurring tactics into draft skills.
Session analysis requires parsing .ohc/state/sessions/*/log.jsonl files to update project memory. It uses these structured logs to compare planned and actual outcomes, then writes updates to .ohc/PROJECT.md and ~/.ohc/USER.md memory files.
You can promote newly discovered skills from session outcomes by running a retrospective analysis that extracts reusable patterns. The process optionally creates draft skills in .ohc/skills/ for later promotion based on identified workflow improvements and debugging tactics.
Run retrospective analysis after significant coding sessions exceeding 30 minutes to ensure sufficient variance and learning data. This timing allows the session analysis to accurately compare planned versus actual outcomes and extract meaningful workflow improvements.
ai-native-campValidate Claude Code session execution against SKILL.md definitions from debug logs.
steven715Extract reusable patterns from Claude Code session transcripts into learned skills.
iadr-devNormalize PRDs, RFCs, diagrams, and wiki exports into a repo-grounded intake index.
TheMattBermanAnalyze Google Ads budgets to identify misallocations and generate reallocation drafts.
