Verified:GitHub

closeout-report

Generate a compliant project closeout report as a .docx with baseline vs actuals and sign-offs.

Updated Apr 19, 2026

Search Tags:#project-management #document-generation #stakeholder-signoff #closeout #variance-reporting #delivery-closure

Ready to run

npx skills add https://github.com/kenmulford/PMSkills --skill closeout-report

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: closeout-report
Source: https://github.com/kenmulford/PMSkills/tree/main/skills/closeout-report
Command: npx skills add https://github.com/kenmulford/PMSkills --skill closeout-report

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python-docx, and includes scripts (resource) components.

What problem does it solve?

Automates the creation of disciplined, audit-ready closeout reports that avoid fabrications and enforce sign-off discipline.

Core Features & Use Cases

Baseline-vs-actual comparison for scope, schedule, and cost
Deliverables acceptance log with explicit status and sign-offs
Open items, known defects, and contract/vendor closure tracking
Formal sign-off block with guardrails to prevent fabricated signatures
Generates a .docx handover document suitable for operations

Quick Start

Describe your project and run the script to render a drafted closeout report.

Frequently Asked Questions about closeout-report

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

FAQPage Schema

How do I generate a project closeout report with baseline vs actuals for scope, schedule, and cost?▼

Project closeout reports capture baseline vs actuals for scope, schedule, and cost alongside deliverables acceptance and formal sign-offs. This Skill generates a compliant .docx document using python-docx to ensure audit-ready delivery closure without fabricated data.

What is the best way to track deliverables acceptance and vendor closure in a formal document?▼

Deliverables acceptance and vendor closure are tracked within the generated closeout report's structured sections. The Skill captures explicit status, open items, and contract closure details, rendering them into a .docx document suitable for stakeholder sign-off.

Do I need python-docx installed to create closeout reports?▼

You need the python-docx library installed to render closeout reports as .docx files. The Skill executes the create_closeout_report.py script which depends on this library to generate the compliant project handover document.

How does the closeout report handle missing project data during generation?▼

Missing project data is handled by inserting [TBD] placeholders during report generation. The Skill enforces a no-fabrication rule, ensuring the closeout report remains compliant and requires users to fill gaps before formal stakeholder sign-off.

Can I use this for stakeholder sign-off on project deliverables?▼

Yes, the closeout report includes a formal sign-off block designed for stakeholder approval. It enforces explicit sign-offs and uses guardrails to prevent fabricated signatures, ensuring compliant delivery closure for project deliverables.