pmo-retrospective

Capture portfolio-level lessons learned and produce retrospective artifacts.

205|26|Updated Oct 30, 2025

Search Tags:#retrospective #lessons learned #process-improvement #knowledge-sharing

Ready to run

npx skills add https://github.com/LerianStudio/ring --skill pmo-retrospective

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pmo-retrospective
Source: https://github.com/LerianStudio/ring/tree/main/pmo-team/skills/pmo-retrospective
Command: npx skills add https://github.com/LerianStudio/ring --skill pmo-retrospective

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Portfolio retrospective skill for capturing lessons learned, process improvements, and organizational learning across completed projects.

Core Features & Use Cases

Retrospective context, data collection, reflection
Pattern analysis and action planning
Knowledge sharing and templates

Quick Start

Run PMO retrospective gates to collect data and produce retro artifacts.

Frequently Asked Questions about pmo-retrospective

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

FAQPage Schema

How do I capture lessons learned from completed projects across my portfolio?▼

Portfolio retrospectives systematically capture lessons learned by collecting project data, facilitating structured reflection, identifying patterns, and planning actions. This Skill gates the retrospective process with templated outputs (retro-context.md, retro-data.md, retro-reflection.md, retro-patterns.md, retro-actions.md, lessons-learned.md) that integrate into your PMO knowledge base for organizational learning.

When should I run a portfolio retrospective for process improvement?▼

Run portfolio retrospectives at project closure, during quarterly or annual portfolio reviews, or across thematic groups of completed projects. The structured process—context, data collection, reflection, pattern analysis, and action planning—surfaces process improvements and enables knowledge sharing across teams.

What outputs does a retrospective produce and how do I use them?▼

Retrospectives produce six templated artifacts: retro-context.md (background), retro-data.md (collected facts), retro-reflection.md (insights), retro-patterns.md (themes), retro-actions.md (improvements), and lessons-learned.md (summary). These integrate into your PMO knowledge base to drive organizational learning and inform future project decisions.

Can I use retrospectives to identify patterns across multiple projects?▼

Yes. Portfolio retrospectives analyze patterns across completed projects by consolidating data, facilitating reflection on shared outcomes, and identifying recurring themes. Pattern analysis surfaces systemic opportunities for process improvement that individual project reviews might miss.

Does this retrospective process work for different review cadences?▼

Yes. The gated retrospective process applies to project closures, quarterly reviews, annual portfolio assessments, and thematic retrospectives. The structured methodology—context, data collection, reflection, pattern analysis, and action planning—scales across different review schedules and project groupings.