retrospective-agent

Generate retrospective reports from completed track execution data.

371|38|Updated Feb 17, 2026

Search Tags:#automation #learning #patterns #retrospective #errors #knowledge-base #track-analysis

Ready to run

npx skills add https://github.com/Ibrahim-3d/conductor-orchestrator-superpowers --skill retrospective-agent-ibrahim-3d

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: retrospective-agent
Source: https://github.com/Ibrahim-3d/conductor-orchestrator-superpowers/tree/main/skills/knowledge/retrospective-agent
Command: npx skills add https://github.com/Ibrahim-3d/conductor-orchestrator-superpowers --skill retrospective-agent-ibrahim-3d

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically extracts and aggregates learnings from completed tracks to continuously improve future executions and knowledge bases.

Core Features & Use Cases

Extracts learnings from track execution, updates conductor/knowledge/patterns.md with new patterns, and logs new error patterns in conductor/knowledge/errors.json.
Analyzes inputs from track plan, metadata, commits, and spec to generate actionable retrospectives for the team.
Supports continuous improvement by proposing skill and workflow updates based on retrospective findings.

Quick Start

Trigger the retrospective agent after a track completes to generate insights and updates to the knowledge base.

Frequently Asked Questions about retrospective-agent

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

FAQPage Schema

How do I automate retrospective analysis for completed development tracks?▼

Automating retrospective analysis requires reading track metadata, commits, and spec files to extract execution learnings. This agent processes those inputs to generate actionable insights, logging new patterns and errors into a shared knowledge base for continuous improvement.

How does automated post-track analysis capture errors and improvement opportunities?▼

Automated post-track analysis captures errors by evaluating track plans and commit history against execution metadata. It identifies recurring failures and improvement opportunities, writing structured error logs and actionable retrospective documents to inform future development cycles.

Can I use automated retrospective analysis for QA sprints and evaluation loops?▼

Automated retrospective analysis applies directly to QA sprints and evaluation loops. By reading track plans and execution metadata, it extracts patterns and errors from these cycles to support continuous improvement and update knowledge bases.

What is the best way to extract learnings from completed tracks into a knowledge base?▼

The best way to extract learnings is to analyze track commits and specifications automatically. This approach aggregates execution patterns and errors, updating knowledge base files to continuously improve future executions without manual review overhead.

What files do I need to run an automated retrospective on a development track?▼

Running an automated retrospective requires track plan, metadata, commits, and spec files. The agent reads these specific inputs to generate a retrospective document and update the knowledge base with new patterns and error logs.