skills.rest
drvoss
drvossCOMMUNITY
Explore all skills by this author →
GitHub

sprint-retro

Generate a markdown sprint retrospective report from Copilot CLI session history and Git metrics.

42|9|Updated Mar 16, 2026
Search Tags:#automation#git#metrics#retrospective#sprint#copilot-cli
One-click install
npx skills add https://github.com/drvoss/everything-copilot-cli --skill sprint-retro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sprint-retro
Source: https://github.com/drvoss/everything-copilot-cli/tree/main/skills/workflow/sprint-retro
Command: npx skills add https://github.com/drvoss/everything-copilot-cli --skill sprint-retro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often conduct sprint retrospectives based on memory or vague impressions, missing concrete data from their development activity.

Core Features & Use Cases

  • Session History Retrieval: Uses /chronicle to collect detailed Copilot CLI session timelines.
  • Git Metrics Analysis: Extracts commit counts, churned files, PR cycle times, and other repository statistics.
  • Automated Report Generation: Produces a structured markdown retro that includes shipped work, velocity analysis, friction points, and owner‑assigned action items.
  • Use Case: Run at the end of each sprint to create a factual, data‑driven retrospective for software engineering teams.

Quick Start

Ask Copilot to run a sprint retrospective for the past two weeks, summarizing /chronicle data and git metrics into a markdown report with actionable items.

Frequently Asked Questions about sprint-retro

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

FAQPage Schema
How do I generate a data-driven sprint retrospective using Git metrics?▼

To generate a data-driven sprint retrospective, this Skill analyzes Git log data and Copilot CLI session history to produce a structured markdown report summarizing shipped features, velocity, and friction points.

What is needed to automate sprint retrospective reporting with Copilot CLI?▼

Automating sprint retrospective reporting requires access to `/chronicle` output for session timelines and Git log data; the optional GitHub CLI can also provide PR information to enrich the analysis.

Can I use GitHub CLI data to add PR cycle times to my sprint retrospective?▼

Yes, you can use GitHub CLI data to add PR cycle times to your sprint retrospective; the Skill optionally integrates GitHub CLI information alongside Git log data to create a factual retrospective.

How do I extract owner-assigned action items from recent Git commits?▼

You can extract owner-assigned action items from recent Git commits by running this Skill at the end of a sprint; it analyzes commit counts, churned files, and session history to assign concrete follow-ups.

Does sprint retrospective automation work without GitHub CLI access?▼

Yes, sprint retrospective automation works without GitHub CLI access, but you must provide `/chronicle` output and Git log data to generate the markdown report with velocity analysis and action items.

Related Skills

Explore More Software Engineering Skills→
rajbosrajbos
100

copilot-log-analysis

Parse Copilot session logs to extract token and model usage data.

Community
Advanced
officebeatsofficebeats
8

retrospective

Analyze sprint data and team feedback to generate prioritized action items.

Community
Intermediate
aporto-techaporto-tech

gstack-plan-devex-review

Review developer experience plans with scoring and competitive analysis.

Official
Advanced
autostay-krautostay-kr
1

retro

Facilitate structured sprint retrospectives and generate prioritized action plans.

Official
Intermediate