retro

Collect git commits, diffs, and TODOs to generate a dated Markdown retro entry.

1|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/manastalukdar/ai-devstudio --skill retro-manastalukdar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/manastalukdar/ai-devstudio/tree/main/skills/retro
Command: npx skills add https://github.com/manastalukdar/ai-devstudio --skill retro-manastalukdar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly retrospectives are tedious and error-prone; this skill gathers data from the last week, distills outcomes, and produces a structured retro entry with concrete actions.

Core Features & Use Cases

  • Automatically assemble week-in-review data from git activity, diffs, and TODOs.
  • Generate a dated retro entry that lists shipped items, blockers, and patterns to carry forward.
  • Create concrete, actionable tasks for the next sprint or week, saved to a standard location.

Quick Start

Generate a dated retro entry for this week documenting shipped items, blockers, patterns to carry forward, and one concrete next-week change.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I generate a weekly retrospective from git commits and diffs?▼

To generate a weekly retrospective from git commits and diffs, the skill automatically collects your past week's development activity, distills outcomes, and produces a formal retro entry with concrete action items.

What is the best way to document sprint blockers and shipped items?▼

The best way to document sprint blockers and shipped items is using a structured retrospective. This skill guides you through four retro questions to surface what shipped, what slowed down, and patterns to carry forward, saving a dated Markdown file.

Can I create actionable next-week tasks from my development activity?▼

Yes, you can create actionable next-week tasks from your development activity. The skill summarizes your week's commits, diffs, and TODOs to publish a compact action-item checklist for the upcoming sprint.

Does the retrospective skill handle weeks with no git activity?▼

Yes, the retrospective skill handles weeks with no git activity. It incorporates specific safeguards for inactive weeks to ensure the retro entry process completes smoothly without manual intervention.

How do I save a dated retro entry for my agile team?▼

You save a dated retro entry for your agile team by running this skill, which automatically generates a formal Markdown file. This file documents shipped items, blockers, and one concrete change to implement next week.