sprint-retro

Generate evidence-backed sprint retrospectives from fragmented team activity data.

4|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/npow/claude-skills --skill sprint-retro-npow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-retro
Source: https://github.com/npow/claude-skills/tree/main/sprint-retro
Command: npx skills add https://github.com/npow/claude-skills --skill sprint-retro-npow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill replaces fragmented, manually assembled sprint summaries with an evidence-backed retrospective that consolidates team activity while protecting private and sensitive information.

Core Features & Use Cases

  • Multi-source activity gathering: Collects relevant work signals from GitHub, public Slack channels, Jira, Confluence, Google Docs, and CI/CD systems.
  • Privacy and attribution safeguards: Excludes DMs, private channels, restricted documents, sensitive content, individual blame, and work merely observed rather than authored or owned by the team.
  • Evidence-based reporting: Produces coverage metrics, shipped work, collaboration highlights, blockers, process gaps, action items, kudos, raw metrics, and a termination evidence file.
  • Use Case: Use this Skill to create a two-week retrospective for a resolved engineering team, clearly distinguishing complete reports from partial reports when source coverage is limited.

Quick Start

Run the sprint-retro skill for the specified team members or Slack alias and generate a privacy-filtered retrospective for the last 14 days.

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 sprint retrospective from GitHub, Slack, and Jira activity?

Generate a sprint retrospective by consolidating fragmented team activity signals from GitHub, Slack, Jira, Confluence, Google Docs, and CI/CD systems into a single evidence-backed report. The Skill aggregates contributions across these platforms for a specified time window, such as a two-week sprint.

Can I create a sprint review that excludes private Slack channels and restricted documents?

Yes, sprint reviews apply strict privacy gates that exclude DMs, private channels, restricted documents, and sensitive content. Attribution safeguards also prevent individual blame, filtering out work merely observed rather than authored or owned by the team.

What is evidence-based sprint reporting and how does it handle incomplete source coverage?

Evidence-based sprint reporting produces structured markdown output containing shipped work, blockers, and action items alongside an on-disk JSON evidence file. When source coverage is limited, it clearly distinguishes complete reports from partial reports using an honest termination label.

Does sprint retrospective reporting work for individual team members or only resolved engineering teams?

Sprint retrospective reporting applies to sprint reviews involving engineering teams, individual members, and Slack aliases. You can run the Skill for specific team members or a designated Slack alias to generate a retrospective for the last 14 days.

What metrics are included in a privacy-filtered sprint retrospective?

A privacy-filtered sprint retrospective includes coverage metrics, shipped work, collaboration highlights, blockers, process gaps, action items, kudos, and raw metrics. It consolidates public collaboration, documentation, and CI/CD activity while producing source coverage tracking.

Are there limitations when generating retrospectives from fragmented team activity data?

Limitations include strict privacy filtering that excludes DMs and restricted documents, which can result in partial reports when source coverage is limited. The Skill applies an honest termination label to distinguish complete reports from partial ones based on available evidence.