retro

Extract structured learnings and retro summaries from project artifacts.

418|40|Updated Nov 5, 2025
One-click install
npx skills add https://github.com/boshu2/agentops --skill retro-boshu2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/boshu2/agentops/tree/main/skills/retro
Command: npx skills add https://github.com/boshu2/agentops --skill retro-boshu2

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams capture and organize learnings from completed work to feed the knowledge flywheel, reducing repeated mistakes and speeding future delivery.

Core Features & Use Cases

  • Automated extraction of learnings from retrospectives, post-mortems, and project artifacts (plans, research, commits, feedback).
  • Generation of structured outputs: .agents/learnings/YYYY-MM-DD-<topic>.md and .agents/retros/YYYY-MM-DD-<topic>.md, enabling tracking and indexing.
  • Context gathering and indexing to support cross-project knowledge transfer and faster onboarding in future sessions.

Quick Start

Run a retrospective on the latest sprint by invoking the retro workflow and point the system at relevant artifacts (plans, research, commits). Then review generated learnings and retros.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I extract actionable learnings from a sprint retrospective?

You can automate a post-mortem by pointing the analysis workflow at relevant project artifacts such as plans, research, and commits. It processes these inputs to produce structured learnings and retrospective summaries, storing them as dated markdown files in the .agents directory.

Can I use retrospective analysis for release reviews and cross-project knowledge transfer?

Yes, retrospective analysis applies to release reviews and post-mortems to support cross-project knowledge transfer. By indexing generated learnings and summaries, it enables faster onboarding and context gathering for future software engineering sessions.

What is the best way to organize project post-mortems and prevent repeated mistakes?

The best way to organize post-mortems and prevent repeated mistakes is to generate structured, dated markdown files for learnings and retros. Storing these artifacts under .agents/learnings and .agents/retros enables tracking, indexing, and continuous knowledge flywheel integration.

Do I need specific dependencies to run retrospective analysis on my software projects?

No specific dependencies are required to run retrospective analysis on software projects. The process operates directly on existing project artifacts and feedback, optionally integrating vibe results when available, to produce structured learnings without external tooling.

Why does my retrospective summary fail to capture actionable insights from project artifacts?

A retrospective summary may fail to capture actionable insights if the provided project artifacts lack sufficient detail or context. Ensure you include comprehensive plans, research, commits, and feedback so the analysis can effectively distill structured learnings into the .agents directory.