skills.rest
ShaheerKhawaja
ShaheerKhawajaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

productionos-retro

Summarize shipped work, failures, and improvement opportunities from recent code changes.

8|Updated Mar 17, 2026
Search Tags:#patterns#retrospective#code-review#process-improvement#retro
One-click install
npx skills add https://github.com/ShaheerKhawaja/ProductionOS --skill productionos-retro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: productionos-retro
Source: https://github.com/ShaheerKhawaja/ProductionOS/tree/main/codex-skills/productionos-retro
Command: npx skills add https://github.com/ShaheerKhawaja/ProductionOS --skill productionos-retro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Retrospective workflow that summarizes what shipped, what broke, and what should improve next. It helps teams reflect on recent work and convert insights into concrete improvements.

Core Features & Use Cases

  • Summarizes wins, misses, and repeated pain points across recent commits and artifacts.
  • Connects patterns to concrete improvements in processes or code.
  • Supports time-windowed and scoped retrospectives for targeted improvements.

Quick Start

Run the productionos-retro workflow on your latest changes to generate a concise retrospective and actionable improvements.

Frequently Asked Questions about productionos-retro

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

FAQPage Schema
How do I generate a retrospective from recent code changes and commits?▼

To generate a retrospective from recent code changes, run the workflow on your latest commits and artifacts. It summarizes shipped work, failures, and improvement opportunities into a structured report with wins, misses, and patterns.

Can I scope a code review retrospective to a specific time window?▼

Yes, you can scope a code review retrospective to a specific time window. The workflow supports time-windowed and scoped retrospectives to target specific improvement areas and analyze relevant changes.

What is the best way to identify repeated pain points in our development process?▼

The best way to identify repeated pain points is by summarizing recent wins and misses across commits. The workflow connects recurring patterns in code changes to concrete process improvements and backlog recommendations.

Does automated retrospective software require any dependencies to analyze failures?▼

No dependencies are required to analyze failures with this automated retrospective software. It directly processes recent commits and artifacts to produce a structured summary of misses and improvement opportunities.

How do I turn process improvement insights into actionable backlog items?▼

To turn process improvement insights into actionable backlog items, review the structured retrospective output. It provides concrete, backlog-worthy recommendations derived from patterns found in recent code changes and failures.

Related Skills

Explore More Software Engineering Skills→
ShaheerKhawajaShaheerKhawaja
8

retro

Analyze commit history and artifacts to generate structured retrospective reports.

Community
Advanced
arch-teamarch-team
73

pace-analyst

Analyze development iteration metrics and generate retrospective reports from historical project data.

Community
Advanced
bomberoxenviosdosruedasbomberoxenviosdosruedas

agency-feedback-synthesizer

Analyze user feedback from surveys, interviews, and social media to identify patterns and pain points.

Community
Advanced
serejarisserejaris
215

cc-analytics

Analyze Claude Code history and Git data into weekly HTML reports.

Community
Intermediate