closing

What problem does it solve?

Closeouts often lack structure, leaving retros and lessons undocumented and handoffs unclear. This skill provides a guided framework to capture insights, secure sign-offs, and facilitate knowledge transfer at project end.

Core Features & Use Cases

• Structured retrospectives formats (Start/Stop/Continue, Mad/Sad/Glad, 4Ls, Sailboat) to capture concrete improvements.
• Formal closeout activities including sign-off, knowledge transfer sessions, runbooks, archival documentation, and benefits realization tracking.
• Standardized templates and references to ensure consistent lessons learned exploration and project handoff.

Quick Start

Trigger a closeout by running a retrospective and a lessons-learned session, then complete the closeout checklist and publish the lessons.