retrospective-agent

Extract actionable learnings from completed tracks and update knowledge base files.

2|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/AhmedElhadarey/Gilfoyle --skill retrospective-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retrospective-agent
Source: https://github.com/AhmedElhadarey/Gilfoyle/tree/main/skills/knowledge/retrospective-agent
Command: npx skills add https://github.com/AhmedElhadarey/Gilfoyle --skill retrospective-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The retrospective agent automatically analyzes completed tracks to extract actionable learnings, identify patterns, and drive improvements to the knowledge base and future workflows.

Core Features & Use Cases

  • Extracts learnings from track execution (plan, metadata, commits, and spec) to feed knowledge bases.
  • Updates conductor/knowledge/patterns.md with newly discovered solutions and error patterns.
  • Proposes skill updates when workflow improvements are identified and keeps a retrospective trail for audits.

Quick Start

After a track completes, run the retrospective to extract learnings and update 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 extract learnings from completed tracks to update a knowledge base?

Track retrospective analysis automatically identifies and records actionable learnings from completed track execution data, including plans, metadata, commits, and specs. It extracts patterns and error signatures to update knowledge bases and accelerate future deliveries.

What is the best way to automate error tracking and pattern extraction after a workflow finishes?

Automating error tracking and pattern extraction post-workflow involves analyzing completed tracks to identify recurring error signatures and update knowledge base files. This approach systematically captures actionable learnings to prevent similar issues in future runs.

How do I generate retrospective artifacts for audits using track metadata and commits?

Generate retrospective artifacts for audits by running a post-track analysis across metadata, commits, and specs. This creates a retrospective trail that records actionable learnings and error signatures, satisfying compliance requirements for workflow audits.

Can I use a retrospective agent to propose workflow improvements based on past execution?

Yes, a retrospective agent can propose workflow improvements by analyzing completed tracks to identify actionable learnings and patterns. It updates knowledge base files and suggests skill updates when workflow bottlenecks or inefficiencies are identified.

Do I need specific dependencies to run a post-track retrospective analysis?

No specific dependencies are required to run a post-track retrospective analysis. The process works directly on completed track artifacts including plans, metadata, commits, and specs to extract patterns without external tool installations.