pipeline-retro

Automates milestone retrospectives by collecting inputs from PRs, GitHub issues, and retro documents.

4|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/johnrtipton/pipeline-skills --skill pipeline-retro-johnrtipton
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pipeline-retro
Source: https://github.com/johnrtipton/pipeline-skills/tree/main/skills/pipeline-retro
Command: npx skills add https://github.com/johnrtipton/pipeline-skills --skill pipeline-retro-johnrtipton

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill facilitates comprehensive milestone retrospectives, ensuring deferred findings are addressed and action items are tracked effectively.

Core Features & Use Cases

  • Milestone Retro Synthesis: Summarizes PR feedback and project learnings into cohesive reports.
  • Action Tracking & Issue Management: Maintains a unified table of improvement actions linked to GitHub issues.
  • Reconciliation & Audit: Scans various sources like PR comments, issues, and retro files to maintain consistency.
  • Use Case: At the end of a project milestone, automate the process of reviewing PRs, logging lessons learned, and creating issues for technical debt.

Quick Start

Run the skill to generate a milestone retrospective report and update the action tracker by providing the relevant pipeline state file.

Frequently Asked Questions about pipeline-retro

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

FAQPage Schema
How do I automate milestone retrospectives and track GitHub issues?

You can automate milestone retrospectives by synthesizing PR feedback and retro documentation into cohesive reports, while maintaining a unified action tracker linked to GitHub issues for systematic follow-up.

What is the best way to track deferred findings from project reviews?

Tracking deferred findings involves scanning PR comments, issues, and retro files for reconciliation, then logging lessons learned and creating issues for technical debt to maintain consistency across project reviews.

How does a milestone retro synthesis work with PR comments and documentation?

Milestone retro synthesis works by collecting feedback from multiple input sources like PR comments and retro files, then summarizing project learnings into a cohesive report to streamline workflow reviews.

Can I reconcile action items across PR comments and GitHub issues?

Yes, you can reconcile action items by scanning various sources like PR comments and GitHub issues to audit consistency, ensuring deferred findings from development processes are addressed in a unified action table.

Do I need a pipeline state file to generate a retrospective report?

Yes, you need to provide the relevant pipeline state file to run the process, which generates a milestone retrospective report and updates the action tracker with improvement actions.