What problem does it solve? Closing a project formally requires consolidating schedule, budget, scope, quality, and handover evidence into one signed document, and doing this manually is slow and error-prone. This Skill generates a complete, cross-referenced closure report that an accountable Product Owner can review and sign. ## Core Features & Use Cases - Structured Closure Report: Produces a Markdown report covering schedule, budget, and scope performance, deliverables acceptance, success criteria, outstanding items, handover status, financials, risk closure, and formal sign-off. - Signature-Gated Workflow: Blocks generation until prerequisite documents (test report, UAT, remediation log, ops runbook) are signed, and enforces validation rules before requesting approval. - Traceability: Writes a sources file recording predecessor documents, question history, information gaps, and a generation log for auditability. - Use Case: At the end of a software project, invoke the skill to compile the final closure report from signed quality, security, and operations documents, then route it to the Product Owner for formal approval. ## Quick Start Ask the agent to generate the closure report for your project once the test report, UAT, remediation log, and ops runbook are signed.
