skills.rest
Negentropy-Laby
Negentropy-LabyOFFICIAL
Explore all skills by this author →
GitHub

retrospective

Analyze sprint data to generate a structured retrospective markdown report.

3|Updated Jun 3, 2026
Search Tags:#retrospective#agile#velocity#sprint#milestone#action-items#team-improvement
One-click install
npx skills add https://github.com/Negentropy-Laby/Constitution-Driven-Development --skill retrospective-negentropy-laby
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retrospective
Source: https://github.com/Negentropy-Laby/Constitution-Driven-Development/tree/main/.agents/skills/retrospective
Command: npx skills add https://github.com/Negentropy-Laby/Constitution-Driven-Development --skill retrospective-negentropy-laby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sprint and milestone retrospectives are time-consuming and error-prone; this skill analyzes completed work, velocity, blockers, and patterns to produce actionable insights for the next iteration.

Core Features & Use Cases

  • Analyze planned vs actual work from sprint and milestone data to surface carryovers, unplanned work, and process improvements.
  • Compute velocity trends, blockers, and patterns to guide continuous improvement and better planning.
  • Generate a structured retrospective markdown that can be saved to production paths and memory snapshots for auditing.

Quick Start

Generate a retrospective for the current sprint and save the results as a markdown report.

Frequently Asked Questions about retrospective

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

FAQPage Schema
How do I generate an agile retrospective from sprint data?▼

This skill analyzes sprint data by evaluating planned versus actual work, velocity trends, and blockers to produce a structured retrospective markdown report for continuous improvement.

What is the best way to track sprint velocity and identify blockers?▼

Tracking sprint velocity and identifying blockers is done by computing velocity trends and analyzing patterns from your completed milestone data, surfacing actionable insights for better next iteration planning.

Do I need git history to run a sprint retrospective?▼

Yes, you need access to production artifacts including sprint plans, completed work data, git history, and a memory_bank for archiving to accurately evaluate actual work and generate the retrospective report.

Can I save retrospective reports to production paths for auditing?▼

Yes, the skill writes new structured retrospective markdown reports directly to production paths and memory snapshots for auditing and future reference during continuous improvement tracking.

How do I analyze planned vs actual work in a sprint?▼

Analyzing planned versus actual work involves evaluating sprint and milestone data to surface carryovers and unplanned work, then computing velocity trends and blockers to guide process improvements.

Related Skills

Explore More Product & Management Skills→
wsmanwsman
18

retrospective

Analyze sprint artifacts and git logs to generate retrospective reports.

Community
Advanced
officebeatsofficebeats
8

retrospective

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

Community
Intermediate
Fantasia1999Fantasia1999

scrum-master

Analyze sprint data with Python scripts for forecasting and health scoring.

Community
Advanced
wanghaishengwanghaisheng
10

retrospective

Generate sprint retrospectives from git logs and sprint plans.

Community
Advanced