retrospective

Generate sprint retrospectives by analyzing plans, commits, and TODO trends.

70|42|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/tranhieutt/software_development_department --skill retrospective-tranhieutt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/tranhieutt/software_development_department/tree/main/.claude/skills/retrospective
Command: npx skills add https://github.com/tranhieutt/software_development_department --skill retrospective-tranhieutt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams spend too much time manually reconciling plans, commits, and blockers to understand what happened during a sprint or milestone, leaving action items vague and unresolved.

Core Features & Use Cases

  • Plan vs. reality analysis: Read sprint plans or milestone definitions, then scan git history and task tracking to see what finished, what drifted, and what was added or dropped.
  • Metric-rich reporting: Compile completion rates, velocity trends, blocker timelines, estimation accuracy, technical debt counts, and carryover tasks to surface systemic opportunities for improvement.
  • Actionable follow-up: Cross-check previous retrospectives, confirm action item status, and generate a new retrospective document with focused action items, blockers, and process improvements for the next iteration.

Quick Start

Ask the retrospective skill for sprint-4 to compare planned deliverables with git history, highlight blockers, and suggest action items.

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 commits and sprint plans?

To generate a sprint retrospective, the skill reads sprint plans and git history to compare planned deliverables with completed work, tracking velocity trends and surfacing blockers for each iteration.

What metrics are included in an automated milestone retrospective?

An automated milestone retrospective compiles completion rates, velocity trends, blocker timelines, estimation accuracy, technical debt counts, and carryover tasks to surface systemic opportunities for improvement.

Can I track technical debt and blockers across multiple sprints?

Yes, you can track technical debt and blockers across multiple sprints by cross-checking previous retrospectives to confirm action item status and analyzing technical debt markers and blocker timelines for each iteration.

How do I compare planned versus completed work for a sprint?

Comparing planned versus completed work involves reading sprint plans or milestone definitions, then scanning git history and task tracking to identify what finished, what drifted, and what was added or dropped during the iteration.

What's the best way to follow up on action items from previous retrospectives?

The best way to follow up on action items is cross-checking previous retrospectives to confirm action item status, then generating a new retrospective document with focused action items, blockers, and process improvements for the next iteration.

Does generating a retrospective require manual reconciliation of commits and plans?

Generating a retrospective does not require manual reconciliation; the skill automatically reads sprint plans, git logs, and previous retrospectives to compare planned deliverables with completed work and surface blockers.