retrospective

Generate sprint or milestone retrospectives from git logs and project plans.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/CarlosQ96/robot-crawler --skill retrospective-carlosq96
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/CarlosQ96/robot-crawler/tree/main/.agents/skills/retrospective
Command: npx skills add https://github.com/CarlosQ96/robot-crawler --skill retrospective-carlosq96

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often spend excessive time manually gathering sprint or milestone data, analyzing velocity, and drafting retrospectives, leading to delayed insights and missed improvement opportunities.

Core Features & Use Cases

  • Argument parsing to distinguish sprint numbers from milestone names.
  • Data loading from git logs, sprint plans, and milestone definitions.
  • Completion analysis including task status, unplanned work, and technical debt trends.
  • Retrospective generation with metrics tables, action items, and process improvements.
  • Save & update existing retrospective files, archiving previous versions when needed.
  • Use case: During a sprint review, run the skill to automatically compile a comprehensive retrospective that highlights what went well, blockers, and next‑step actions.

Quick Start

Ask the retrospective skill to create a sprint 7 retrospective.

Frequently Asked Questions about retrospective

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

FAQPage Schema
How do I generate a sprint retrospective from git logs and project plan files?

To generate a sprint retrospective, the skill analyzes git logs, sprint plans, and milestone definitions to compile task status, velocity, and blockers into a markdown document with actionable insights for the next iteration.

Can I automatically analyze sprint velocity and blockers for a milestone assessment?

Yes, you can automatically analyze sprint velocity and blockers during a milestone assessment by parsing milestone names, loading project data, and generating metrics tables with action items and process improvements.

What is the best way to automate drafting a sprint review with technical debt trends?

Automating a sprint review involves loading completed work data to identify technical debt trends and unplanned work, then generating a retrospective with metrics tables and next-step actions.

Do I need to manually save and update retrospective markdown documents?

No, the skill automatically saves and updates retrospective markdown documents, archiving previous versions when needed, so you do not need to manage files manually.

Does the retrospective skill work with both sprint numbers and milestone names?

Yes, the retrospective skill works with both sprint numbers and milestone names through argument parsing, allowing you to distinguish between a specific sprint and a broader milestone assessment.

What limitations exist when generating retrospectives from project plan files?

The main limitation is that the skill requires access to git logs, project plan files, and read/write permissions for markdown documents to successfully generate a retrospective and archive previous versions.