qbr

Identifies root causes and assigns accountability via 5-Why analysis and structured post-mortems.

7|1|Updated Apr 3, 2026

Search Tags:#retrospective #leadership #accountability #root-cause #qbr #5-why #improvement-plans

Ready to run

npx skills add https://github.com/baizhine999/leader-skills --skill qbr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qbr
Source: https://github.com/baizhine999/leader-skills/tree/main/codex/qbr
Command: npx skills add https://github.com/baizhine999/leader-skills --skill qbr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The QBR Retrospective Skill helps AI act as a leadership figure to perform a thorough post-mortem on problems or completed projects using a 5-Why root cause analysis, accountability, and concrete improvement commitments, surfacing clear next steps.

Core Features & Use Cases

3-part framework: root-cause analysis, accountability, and improvement commitments to drive closure.
Structured recap: outputs a formal recap that documents root cause, responsible owner, and actionable follow-ups.
Use Case: After a failed project or incident, run a QBR-style review to identify root causes, define ownership, and create a plan with deadlines.

Quick Start

Run a QBR-style retrospective on a recently completed project and generate a root-cause analysis, owner assignments, and three improvement actions with deadlines.

Frequently Asked Questions about qbr

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

FAQPage Schema

How do I conduct a 5-Why root-cause analysis for a failed project?▼

A structured post-mortem identifies root causes and assigns accountability for problems using 5-Why analysis. It applies to incidents, product launches, or completed initiatives to surface ownership and concrete improvements with actionable deadlines.

What is the best way to assign accountability after an incident post-mortem?▼

Assigning accountability after an incident post-mortem requires documenting the responsible owner alongside the root cause. This Skill outputs a formal recap that pairs identified root causes with responsible owners and actionable deadlines.

How do I create improvement plans with deadlines after a product launch review?▼

Creating improvement plans with deadlines after a product launch review involves translating root-cause findings into concrete commitments. This Skill generates a structured recap documenting root causes, responsible owners, and actionable deadlines.

Can I use a QBR-style retrospective for completed initiatives?▼

Yes, a QBR-style retrospective can be used for completed initiatives. It applies a 3-part framework of root-cause analysis, accountability, and improvement commitments to surface root causes and concrete next steps.