retrospective

Automate structured team retrospectives and generate typed action items.

18|4|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/botminter/botminter --skill retrospective-botminter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/botminter/botminter/tree/main/profiles/scrum/roles/chief-of-staff/coding-agent/skills/retrospective
Command: npx skills add https://github.com/botminter/botminter --skill retrospective-botminter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides teams through a structured retrospective process and produces a prioritized action-item summary, reducing ambiguity and improving continuous improvement.

Core Features & Use Cases

  • Structured retrospective flow: define scope, collect data, synthesize insights, and generate an action plan.
  • Data-driven analysis: derives patterns from completed work on the project board to inform improvements.
  • Outputting retro documents: writes a markdown retro summary to agreements/retros/ with references to examined issues.

Quick Start

Run a retrospective for the current sprint and generate the retro document at agreements/retros/NNNN-<title>.md.

Frequently Asked Questions about retrospective

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

FAQPage Schema
How do I automate a sprint retrospective and generate action items?

Automate a sprint retrospective by defining the scope, collecting completed work data, synthesizing insights, and generating typed action items. The Skill outputs a retro summary with references to examined issues.

What is the best way to structure a milestone review for continuous improvement?

Structure a milestone review using a defined flow: scope definition, data collection, insight synthesis, and an action plan. This structured retrospective process reduces ambiguity and drives continuous improvement.

Can I use retrospective data from a project board to identify team pain points?

Yes, you can use retrospective data from a project board. The Skill derives patterns from completed work to identify pain points and inform improvements for the team.

How are retrospective summaries and agreements documented?

Retrospective summaries are documented as markdown files written to agreements/retros/. The document includes typed action items and references to the examined issues from the project board.

Does the retrospective process work for any time-boxed period or just sprints?

The retrospective process works for any time-boxed period. It applies to sprint retrospectives, milestone reviews, or any defined timeframe to collect data and generate an action plan.

What are the limitations of automating team retrospectives?

Automating team retrospectives relies on reading scope from operators or todo requests and completed project board data. It requires structured input to accurately identify pain points and generate improvements.