skills.rest
aspelldenny
aspelldennyCOMMUNITY
Explore all skills by this author →
GitHub

retro

Analyze weekly shipping data to generate a structured project retrospective report.

Updated Apr 4, 2026
Search Tags:#retrospective#code-quality#velocity#risk#project-management#team-learning#retro
One-click install
npx skills add https://github.com/aspelldenny/sos-kit --skill retro-aspelldenny
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/aspelldenny/sos-kit/tree/main/skills/retro
Command: npx skills add https://github.com/aspelldenny/sos-kit --skill retro-aspelldenny

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly retrospectives help solo or small teams translate shipped work into actionable insights, preserving context and driving continuous improvement.

Core Features & Use Cases

  • Gather data from the past week or sprint to surface shipped work, changes, and context.
  • Analyze Shipping Velocity, code-quality signals, hotspots, and risks to guide action items.
  • Produce a structured retro report that records learnings and next-cycle improvements.
  • Use cases: end-of-week retro, project health check, post-ship review.

Quick Start

Run the retro skill for the current week to generate a concise, data-driven retrospective report.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I generate a data-driven project retrospective from weekly shipping data?▼

A data-driven project retrospective analyzes your weekly shipping data to summarize velocity, identify code-quality hotspots, surface risks, and record actionable learnings for the next development cycle.

What is a structured retro report and how does it track shipping velocity?▼

A structured retro report translates shipped work into actionable insights by measuring shipping velocity, highlighting code-quality hotspots, and documenting team learnings to drive continuous improvement.

Can I run a sprint retrospective for a small team or solo developer?▼

Yes, sprint retrospectives help solo or small teams translate shipped work into actionable insights, preserving project context and driving continuous improvement through a structured health check.

How do I identify code-quality hotspots and project risks at the end of a sprint?▼

You identify code-quality hotspots and risks by analyzing your past sprint's shipping data, which surfaces context and changes to guide actionable improvements for the next cycle.

What's the best way to summarize development velocity and team learnings after a ship?▼

The best way to summarize velocity and learnings is a post-ship review that gathers weekly data to produce a concise, structured report highlighting risks and next-cycle improvements.

When do I need a post-ship review and project health check?▼

You need a post-ship review at the end of a week or sprint to analyze shipping data, surface code-quality signals, and document learnings that guide actionable next steps.

Related Skills

Explore More Software Engineering Skills→
legotec73legotec73

gstack-openclaw-retro

Analyze weekly commit history and code quality metrics to generate team retrospectives.

Community
Advanced
tarunccettarunccet
5

retro

Converts team feedback and sprint metrics into a markdown retro with prioritized action items.

Community
Intermediate
OpenLaborOpenLabor
4

Sprint Planning

Plan development sprints with velocity-based scope and blocker tracking.

Official
Intermediate
theandyalvarez7-rubytheandyalvarez7-ruby

scrum-master

Forecasts velocity, scores sprint health, and analyzes retrospectives for Scrum teams.

Community
Advanced