retro

Analyze sprint completion data to generate retrospective documents with metrics and action items.

Updated May 11, 2026
One-click install
npx skills add https://github.com/webn77/opennexus --skill retro-webn77
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/webn77/opennexus/tree/main/skills/retro
Command: npx skills add https://github.com/webn77/opennexus --skill retro-webn77

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of comprehensive sprint retrospective documents, simplifying team review processes and fostering continuous improvement.

Core Features & Use Cases

  • Automated Report Generation: Calculates completion rates and identifies issues based on sprint data.
  • KPT Analysis: Derives keep, problem, and try items from input patterns to facilitate team reflection.
  • Next Action Planning: Translates problem areas into actionable items with assigned responsibilities and deadlines.
  • Use Case: During sprint closure, teams input completed and pending tasks, and the Skill produces an organized retrospective document highlighting successes and areas for improvement.

Quick Start

Provide sprint ID and completion details; the Skill will generate a retrospective report automatically.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I automate sprint retrospective report generation from completion data?

Automating sprint retrospective report generation requires inputting sprint IDs and task completion details to produce a structured document with success metrics, identified problems, and future action items.

Can I use KPT analysis to identify problems and action items in agile team reviews?

KPT analysis for agile team reviews derives keep, problem, and try items from input patterns, translating problem areas into actionable items with assigned responsibilities and deadlines for continuous improvement.

What is a sprint retrospective and when do I need a structured document for it?

A sprint retrospective is a team review process needed during sprint closure to evaluate completion rates, identify issues from sprint data, and plan actionable improvements for upcoming sprints.

Does this agile retrospective tool work for project managers tracking sprint metrics?

Agile retrospective tools for project managers process sprint completion details to calculate metrics, identify issues, and generate organized documents highlighting successes and areas for team improvement.

How to plan next action items with assigned responsibilities after a sprint review?

Planning next action items after a sprint review involves translating identified problem areas into actionable tasks with assigned responsibilities and deadlines, supporting structured planning for upcoming sprints.

What is the best way to evaluate sprint success metrics and pending tasks?

Evaluating sprint success metrics and pending tasks requires processing completion data to calculate rates, identify issues, and derive insights for comprehensive team reflection and continuous improvement.