cheat-retro

Automate iterative retrospectives after each bug fix to update K/RW forecasts.

12|Updated May 29, 2026
One-click install
npx skills add https://github.com/Jason5330/ai-self-eval --skill cheat-retro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cheat-retro
Source: https://github.com/Jason5330/ai-self-eval/tree/main/skills/cheat-retro
Command: npx skills add https://github.com/Jason5330/ai-self-eval --skill cheat-retro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Iterative retrospectives after each bug fix prevent uncalibrated forecasts and promote concrete learning from outcomes.

Core Features & Use Cases

  • Phase-driven retro workflow for bug-fix cycles (Phase 0–Phase 5) to structure reflections and decisions.
  • Immutable forecast sections with appended retrospectives to preserve history while updating learnings.
  • Continuous calibration of K/RW targets after each iteration and automatic logging of insights for future cycles.

Quick Start

Run a retro immediately after every bug fix to log results and update K/RW.

Frequently Asked Questions about cheat-retro

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

FAQPage Schema
How do I automate retrospectives after a bug fix to lock in learning?

Automating retrospectives after a bug fix uses a phase-driven workflow to structure reflections and log insights. This process ensures concrete learning from outcomes and updates K/RW targets for future development cycles.

What is the best way to calibrate forecasts during an iterative development cycle?

Calibrating forecasts during an iterative development cycle requires continuous updates to K/RW targets after each bug fix. Logging iterative analyses ensures predictions remain immutable while appending new retrospective learnings.

How does a phase-driven retro workflow structure bug-fix reflections?

A phase-driven retro workflow structures bug-fix reflections across Phase 0 to Phase 5. This framework organizes iterative analyses and decisions to prevent uncalibrated forecasts and promote concrete learning from outcomes.

Can I preserve historical predictions while appending new retrospective insights?

You can preserve historical predictions by maintaining immutable forecast sections. Retrospectives are appended to these sections, allowing you to log iterative analyses and update learnings without altering original K/RW forecasts.

When do I need to run a retro to calibrate K/RW targets?

You need to run a retro immediately after every bug fix to calibrate K/RW targets. This rapid feedback loop updates predictions and automatically logs insights for future iterative development cycles.