Slash Command

/retrospective

Quantitative retrospective of PM engagement — metrics-driven review of the entire PM planning engagement

Install

Run in your terminal

npx claudepluginhub javimontano/mao-pm-apex

Command Content

Other plugins with /retrospective

/retrospective

Facilitates and documents a team retrospective using the iterate-retrospective skill, following its instructions and TEMPLATE.md output format.

pm-skills

122

/retrospective

Cross-session learning synthesis. Finds patterns, resolves contradictions, promotes insights. Triggers: retrospective, reflect, patterns, learnings, synthesis.

ReadBashGrep+1

kernel

/retrospective

Run a post-sprint retrospective with Auditor and Researcher agents to verify quality and process

code

/retrospective

Sprint retrospective facilitator with structured formats for continuous improvement

aeo-agile-tools

/retrospective

bmad/bmm/workflows/

Run after epic completion to review overall success, extract lessons learned, and explore if new information emerged that might impact the next epic

bmad-system

/retrospective

Sprint retrospective — review completed cycle, facilitate retro discussion, post status update

workflows

Stats

Stars0

Forks0

Last CommitMar 28, 2026

Actions

View Source View Plugin View on GitHub View README

PROTOCOL

Engagement Metrics — deliverables produced, total effort, cycle time per deliverable, rework rate. [DOC]

Quality Assessment — per deliverable: excellence score, audit findings, stakeholder feedback. [DOC] [INFERENCIA]

Process Effectiveness — what worked well, what could improve, what to avoid. [INFERENCIA]

Tool Effectiveness — which APEX capabilities were most/least valuable. [INFERENCIA]

Recommendations — for future PM engagements: process improvements, skill gaps, template improvements. [INFERENCIA]

Client Value — estimated value delivered: time saved, quality improved, risks identified. [INFERENCIA] [SUPUESTO]

PMO-APEX · ENGAGEMENT RETROSPECTIVE · NL-HP v3.0

ROLE

Engagement Analyst — activates apex-engagement-retro as primary skill. Quantitative review of the PM planning process itself.

AUTO-DETECTION PROTOCOL

Project root: Use current working directory.
Engagement data: Load all deliverables, session logs, changelog from project/.
Quality data: Load audit results if available.

PROTOCOL

Engagement Metrics — deliverables produced, total effort, cycle time per deliverable, rework rate. [DOC]
Quality Assessment — per deliverable: excellence score, audit findings, stakeholder feedback. [DOC] [INFERENCIA]
Process Effectiveness — what worked well, what could improve, what to avoid. [INFERENCIA]
Tool Effectiveness — which APEX capabilities were most/least valuable. [INFERENCIA]
Recommendations — for future PM engagements: process improvements, skill gaps, template improvements. [INFERENCIA]
Client Value — estimated value delivered: time saved, quality improved, risks identified. [INFERENCIA] [SUPUESTO]

OUTPUT CONFIGURATION

Language: Spanish (Latin American)
Format: Markdown-excellence (tables, metrics, evidence tags)
Tagline: "PMO-APEX — Project Management Excellence, potenciado por inteligencia agentica."

CONSTRAINTS

Retrospective must be data-driven, not anecdotal.
Honest assessment — do not inflate value metrics.
Recommendations must be specific and actionable.