retro

Validate improvement systems and calculate recurrence rate and MTTR metrics.

2|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/ka2kama/ringiflow --skill retro-ka2kama
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/ka2kama/ringiflow/tree/main/.claude/skills/retro
Command: npx skills add https://github.com/ka2kama/ringiflow --skill retro-ka2kama

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you systematically evaluate the effectiveness of your improvement cycles, analyze project health trends, and identify areas for operational enhancement from an SRE perspective.

Core Features & Use Cases

  • Improvement System Validation: Analyzes improvement records to verify the functionality of your feedback loop.
  • Project Health Trend Analysis: Tracks key metrics across Discovery, Delivery, and Sustainability to identify shifts.
  • SRE Perspective: Focuses on metrics like recurrence rate, MTTR, toil, and error budget to optimize operations.
  • Use Case: Run this Skill weekly to get a report on how well your team's improvement efforts are working, identify recurring issues, and ensure a healthy balance between new feature development and maintenance.

Quick Start

Run the retro skill to perform a full analysis of your improvement cycle and project health.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I analyze the effectiveness of my project's improvement cycle?

Project health trend analysis tracks key metrics across Discovery, Delivery, and Sustainability to identify shifts. It processes historical assessment reports to detect recurring issues and ensure a healthy balance between feature development and maintenance.

How do I track project health trends across development phases?

Project health trend analysis tracks key metrics across Discovery, Delivery, and Sustainability to identify shifts. It compares assessment reports to detect recurring issues and ensure a healthy balance between feature development and maintenance.

Can I calculate SRE metrics like MTTR and recurrence rate for operational improvements?

You should run the retrospective analysis weekly to get a report on how well your team's improvement efforts are working. Regular execution helps identify recurring issues early and tracks the effectiveness of your improvement cycle over time.

What is the best way to validate if our feedback loop is functioning correctly?

To validate a feedback loop, analyze improvement records to verify its functionality. This Skill systematically evaluates improvement records to confirm your improvement system is actively capturing and resolving operational issues.

How often should I run a retrospective analysis to monitor improvement efforts?

Run retrospective analysis weekly to report on team improvement efforts and identify recurring issues. Regular execution tracks improvement cycle effectiveness and ensures a healthy balance between new feature development and maintenance.

Does evaluating an improvement system require specific SRE metrics?

Evaluating an improvement system benefits from SRE metrics like recurrence rate, MTTR, toil, and error budget. This Skill focuses on these operational metrics to optimize enhancements and systematically assess project health trends.