Closing Checklist

Closing Checklist

Purpose

Build and maintain a structured transaction closing checklist that captures every condition precedent, closing deliverable, and pre-closing covenant drawn from the transaction agreement. The skill can initialize a checklist from the agreement, fold in items surfaced by diligence, update item status, and produce a blocking and critical-path summary. It produces draft legal work product for attorney review — not legal advice and not a closing certification.

Use When

• A deal team needs to initialize a closing checklist from a purchase agreement, merger agreement, or financing document.
• Diligence findings have surfaced pre-closing action items — consents, regulatory filings, board or shareholder approvals, releases, or escrow mechanics — that must be tracked to closing.
• The team needs to update the status of existing checklist items and surface what remains open.
• A deal is approaching signing or closing and the team wants a consolidated view of open conditions and deliverables for attorney review.
• The user asks for a "closing checklist," "conditions checklist," "pre-closing action list," or equivalent.

Required Inputs

• The transaction agreement (purchase agreement, merger agreement, financing document, or equivalent) — required to initialize the checklist or verify item sourcing. Do not reconstruct or paraphrase conditions from memory or a description alone.
• Deal context — deal name, transaction structure (e.g., stock purchase, asset purchase, merger, or financing [CONFIRM: structure]), and parties. If any of these are missing, ask for them before proceeding.
• Operating mode — one of: initialize (build from the agreement), add (fold in diligence items), update (revise item status), or status report (surface blocking items and critical path).
• Diligence findings — required only for add mode; a list or memo of findings that carry pre-closing action items.
• Existing checklist — required for update and status report modes; provide the current checklist to be updated.
• Optional: the practice group's practice-profiles/corporate.md if it has been populated and is loaded alongside this skill. If present, the skill uses its Standard Positions and Escalation Thresholds tables to benchmark the output and to gate escalation. If absent, the skill proceeds without practice-profile benchmarking and asks the user to supply standing positions inline if needed.