pmo-retrospective

Capture portfolio-level lessons learned and process improvement opportunities into structured reports.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/withmartian-sandbox-darkside/ghrc-y-3126672651424eddb640ecc81321a665 --skill pmo-retrospective-withmartian-sandbox-darkside
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pmo-retrospective
Source: https://github.com/withmartian-sandbox-darkside/ghrc-y-3126672651424eddb640ecc81321a665/tree/main/pmo-team/skills/pmo-retrospective
Command: npx skills add https://github.com/withmartian-sandbox-darkside/ghrc-y-3126672651424eddb640ecc81321a665 --skill pmo-retrospective-withmartian-sandbox-darkside

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishes a repeatable, PMO-level retrospective process to capture lessons learned, identify systemic patterns, and convert findings into tracked improvement actions so organizations stop repeating mistakes and improve delivery across projects.

Core Features & Use Cases

  • Retrospective Types: Supports project closure retrospectives, quarterly/annual portfolio reviews, and thematic retrospectives for recurring patterns.
  • Gated Workflow: Structured gates for context setting, data collection, reflection, pattern analysis, action planning, and knowledge sharing with prescribed outputs and templates.
  • Governance & Safety: Includes blocker criteria, anti-rationalization guidance, pressure-resistance responses, and required ownership to ensure follow-through.
  • Use Case: During a quarterly portfolio review, aggregate final project metrics, run cross-project pattern analysis, and produce a lessons-learned report with prioritized actions and owners for PMO governance.

Quick Start

Conduct a portfolio retrospective for the recent quarter by gathering project metrics, running the reflection and pattern analysis gates, and producing a Lessons Learned report saved to docs/pmo/{date}/lessons-learned.md.

Frequently Asked Questions about pmo-retrospective

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

FAQPage Schema
How do I conduct a portfolio retrospective to capture lessons learned across multiple projects?

Conduct a portfolio retrospective by gathering final project metrics, running reflection and pattern analysis gates, and producing a structured lessons-learned report with prioritized actions and owners saved to your PMO documentation.

What is the best way to identify systemic patterns during a quarterly portfolio review?

The best way to identify systemic patterns during a quarterly portfolio review is to aggregate final project metrics and run cross-project pattern analysis to convert recurring findings into tracked improvement actions.

How do I ensure action planning and follow-through after a project closure retrospective?

Ensure action planning follow-through by applying governance criteria that require specific ownership and success criteria for each improvement action identified during the project closure retrospective.

Can I use this approach for thematic retrospectives targeting recurring project issues?

Yes, you can use this structured approach for thematic retrospectives to analyze recurring patterns across projects, utilizing guided gates for data collection, reflection, and knowledge sharing to resolve systemic issues.

What structured outputs should a PMO lessons-learned report include?

A PMO lessons-learned report should include structured outputs such as project context, collected data, reflection insights, pattern analysis, action plans, and defined success criteria with assigned owners.

Does this retrospective process include anti-rationalization guidance to prevent biased reflection?

Yes, the retrospective process includes anti-rationalization guidance, blocker criteria, and pressure-resistance responses to ensure objective pattern analysis and prevent biased reflection during portfolio reviews.