Zum Hauptinhalt springen
Dieser Inhalt ist noch nicht in Ihrer Sprache verfügbar und wird auf Englisch angezeigt.

PM Post Mortem Facilitator

Skill Verifiziert Aktiv

Blameless incident and failure post-mortem generator using 5 Whys root cause analysis. Produces structured post-mortem documents with timeline, contributing factors, corrective actions, and lessons learned. Tracks MTTR and detection time metrics. Use when someone says "post-mortem", "postmortem", "incident review", "root cause analysis", "5 whys", "what happened", "outage review", "failure analysis", "RCA".

Zweck

To streamline and standardize the process of conducting blameless incident post-mortems, ensuring thorough analysis and actionable outcomes.

Funktionen

  • Generates blameless incident post-mortem documents
  • Utilizes 5 Whys for root cause analysis
  • Includes structured sections for timeline, contributing factors, and corrective actions
  • Tracks key incident metrics (MTTR, detection time)
  • Adapts to company/personal context via `domain-context.md` and `personal-context.md`

Anwendungsfälle

  • When an incident requires a formal post-mortem review.
  • To establish a consistent process for analyzing failures and identifying systemic causes.
  • To generate structured documentation for incident follow-up and prevention.
  • When needing to track and improve MTTR and detection times.

Nicht-Ziele

  • Assigning blame to individuals for incidents.
  • Performing real-time incident response or mitigation.
  • Generating generic incident reports without user-provided context.

Workflow

  1. Clarify incident details (what happened, impact, timeline)
  2. Generate post-mortem document template
  3. Fill in metadata, metrics, executive summary, customer impact
  4. Construct incident timeline
  5. Perform 5 Whys root cause analysis
  6. Identify contributing factors, what went well, and what went poorly
  7. Define corrective actions with owners and deadlines
  8. Document lessons learned
  9. Conduct domain-specific compliance checks if applicable
  10. Determine output delivery method (chat, file, Notion)

Praktiken

  • Blameless analysis
  • Root cause identification
  • Actionable corrective planning
  • Metric tracking

Voraussetzungen

  • Access to the `marfoerst/the-pragmatic-pm` plugin
  • Ability to provide incident details and context
  • Optional: Customized `domain-context.md` and `personal-context.md` files for tailored output

Installation

Zuerst Marketplace hinzufügen

/plugin marketplace add marfoerst/the-pragmatic-pm
/plugin install the-pragmatic-pm@the-pragmatic-pm

Qualitätspunktzahl

Verifiziert
99 /100
Analysiert about 24 hours ago

Vertrauenssignale

Letzter Commit29 days ago
Sterne6
LizenzMIT
Status
Quellcode ansehen

Ähnliche Erweiterungen

Conduct Post Mortem

99

Conduct a blameless post-mortem analysis after an incident. Build timeline reconstruction, identify contributing factors, and generate actionable improvements. Focus on systemic issues rather than individual blame. Use after any production incident or service degradation, following a near-miss, when investigating recurring issues, or to share systemic learnings across teams.

Skill
pjt222

Teach Guidance

100

Guide a person in becoming a better teacher and explainer. AI coaches content structuring, audience calibration, explanation clarity, Socratic questioning technique, feedback interpretation, and reflective practice for technical presentations, documentation, and mentoring. Use when a person needs to present technical content and wants preparation coaching, wants to write better documentation or tutorials, struggles to explain concepts across expertise levels, is mentoring a colleague, or is preparing for a talk or knowledge-sharing session.

Skill
pjt222

Prepare Inspection Readiness

100

Prepare an organisation for regulatory inspection by assessing readiness against agency-specific focus areas (FDA, EMA, MHRA). Covers warning letter and 483 theme analysis, mock inspection protocols, document bundle preparation, inspection logistics, and response template creation. Use when a regulatory inspection has been announced or is anticipated, when a periodic self-assessment is due, when new systems have been implemented since the last inspection, or after a significant audit finding that may attract regulatory attention.

Skill
pjt222

External Context

100

Invoke parallel document-specialist agents for external web searches and documentation lookup

Skill
Yeachan-Heo

Deepinit

100

Deep codebase initialization with hierarchical AGENTS.md documentation

Skill
Yeachan-Heo

Readme I18n

100

Nutzen Sie dies, wenn der Benutzer eine Repository-README übersetzen, ein Repository mehrsprachig machen, Dokumentationen lokalisieren, einen Sprachumschalter hinzufügen, die README internationalisieren oder lokalisierte README-Varianten in einem GitHub-ähnlichen Repository aktualisieren möchte.

Skill
xixu-me