solo-retro

Analyze pipeline runs to identify failure patterns and efficiency gaps.

18|2|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/fortunto2/solo-factory --skill solo-retro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: solo-retro
Source: https://github.com/fortunto2/solo-factory/tree/main/skills/retro
Command: npx skills add https://github.com/fortunto2/solo-factory --skill solo-retro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-pipeline retrospectives are time-consuming and prone to miss recurring issues, leaving teams without a clear plan to improve.

Core Features & Use Cases

  • Parses pipeline logs, progress artifacts, and git history to surface actionable insights about efficiency, stability, and quality.
  • Generates a structured retro report with per-track metrics, recurring failure patterns, and concrete patch recommendations.
  • Produces patch-ready guidance and documentation updates to improve future runs.

Quick Start

Run the retro skill after a pipeline completes to generate a concise evaluation and patch plan.

Frequently Asked Questions about solo-retro

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

FAQPage Schema
How do I automate post-pipeline retrospectives to identify failure patterns?

Yes, you can analyze pipeline runs across multiple tracks, platforms, and stacks to identify failure patterns and efficiency gaps. The retrospective process parses logs, progress artifacts, and git history to deliver both qualitative and quantitative insights.

What is the best way to generate patch recommendations from pipeline logs?

Generate patch recommendations by analyzing pipeline runs to identify failure patterns and efficiency gaps. The process parses pipeline logs, progress artifacts, and git history to produce patch-ready guidance and documentation updates for future runs.

How do I produce per-track metrics from pipeline runs for a retro report?

Produce per-track metrics by applying post-pipeline retrospectives across multiple tracks, platforms, and stacks. The analysis parses pipeline logs, progress artifacts, and git history to generate a structured retro report with actionable insights about stability and quality.

Can I analyze pipeline efficiency gaps across different platforms and stacks?

Yes, you can analyze pipeline efficiency gaps across multiple platforms and stacks. The retrospective process parses pipeline logs, progress artifacts, and git history to deliver both qualitative and quantitative insights for per-track metrics.

When do I need to run an automated pipeline retrospective?

Run an automated pipeline retrospective after a pipeline completes to generate a concise evaluation and patch plan. This surfaces actionable insights about efficiency, stability, and quality without the time-consuming manual review process.