retro

Score knowledge system effectiveness across five dimensions using work artifacts and logs.

11|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/anticorrelator/lore --skill retro-anticorrelator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/anticorrelator/lore/tree/main/skills/retro
Command: npx skills add https://github.com/anticorrelator/lore --skill retro-anticorrelator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you objectively assess how well your knowledge system supported a specific work cycle, identifying areas for improvement in knowledge capture, delivery, and retrieval.

Core Features & Use Cases

  • Multi-dimensional Scoring: Evaluates knowledge delivery, retrieval quality, knowledge gaps, plan-knowledge alignment, and overall impact.
  • Evidence-Based Analysis: Gathers data from work item artifacts, session logs, and retrieval metrics.
  • Protocol Evolution: Mandates concrete improvements to the knowledge system protocol with each use.
  • Use Case: After completing a complex feature implementation, use this Skill to understand if the documented principles and past learnings were effectively used, if crucial information was missing, and how the system could be improved for future tasks.

Quick Start

Evaluate the knowledge system's performance for the work item 'feature-x'.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I evaluate knowledge management system effectiveness after a development cycle?

You evaluate knowledge system effectiveness by scoring five dimensions: delivery, retrieval quality, gap analysis, plan-alignment, and overall delta. It analyzes work item artifacts, session logs, and retrieval metrics to measure performance and drive protocol evolution.

What is a knowledge system retrospective and when do I need one?

A knowledge system retrospective objectively assesses how well your documented principles supported a specific work cycle. You need one after completing complex feature implementations to identify missing information and improve future knowledge retrieval.

How do I perform a gap analysis on my technical documentation and session logs?

Perform a gap analysis by parsing markdown, JSON, and CSV files from work item artifacts and session logs. This identifies missing knowledge, scores retrieval quality, and highlights areas for protocol evolution.

Can I use shell commands to gather metrics for a knowledge system evaluation?

Yes, you can use shell commands to gather data and execute journal entries for a knowledge system evaluation. The system requires parsing markdown, JSON, and CSV files alongside shell execution to score retrieval quality and plan-alignment.

What's the best way to align documented knowledge with project plans during a retrospective?

The best way to align documented knowledge with project plans is to analyze work item artifacts against plan-alignment metrics. This evidence-based approach scores delivery and mandates concrete protocol improvements for future tasks.