closing-checklist

Maintain a living closing checklist with blockers and critical-path days-to-close.

183|37|Updated May 15, 2026
One-click install
npx skills add https://github.com/zhou210712/claude-for-legal-ZH --skill closing-checklist-zhou210712
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: closing-checklist
Source: https://github.com/zhou210712/claude-for-legal-ZH/tree/main/corporate-legal/skills/closing-checklist
Command: npx skills add https://github.com/zhou210712/claude-for-legal-ZH --skill closing-checklist-zhou210712

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents deal closing surprises by maintaining a living closing checklist that surfaces what is blocking, what is critical path, and how many days remain until closing.

Core Features & Use Cases

  • Checklist self-updating from diligence: Converts extracted diligence handoffs (consents, board/shareholder actions, regulatory filings, releases/terminations, escrow/withholding, and closing deliverables) into deduplicated checklist items while preserving upstream fields and severity rules.
  • Agreement-driven initialization: Builds initial checklist entries by extracting conditions precedent, closing deliverables, and contractual cutoff commitments from the signed share purchase agreement, with explicit sourcing to the exact provisions.
  • Status reporting and dashboard-ready outputs: Updates specific items with user-provided status notes and produces a structured “what is blocking” report grouping risks by severity and highlighting critical path items.

Quick Start

Use /corporate-legal:closing-checklist to retrieve the current closing checklist status and a table of blockers with critical path focus for the deal.

Frequently Asked Questions about closing-checklist

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

FAQPage Schema
How do I track M&A closing conditions precedent and identify what is blocking the deal?

Track M&A closing conditions precedent by maintaining a living closing checklist that extracts contractual cutoff commitments from the signed share purchase agreement. It surfaces blocking items and critical-path deliverables with days-to-close to prevent closing surprises.

What is the best way to generate a closing status report showing deal blockers by severity?

Generate a closing status report by updating your per-deal checklist data with status notes. This produces a structured blocker report grouping risks by severity and highlighting critical-path items requiring immediate attention before closing.

Can I auto-update a closing checklist from contract diligence outputs?

Yes, you can auto-update a closing checklist from contract diligence outputs. The system ingests diligence handoffs like consents, regulatory filings, and releases, converting them into deduplicated checklist items while preserving upstream fields and severity rules.

How do I initialize a closing checklist from a share purchase agreement?

Initialize a closing checklist from a share purchase agreement by extracting conditions precedent, closing deliverables, and contractual cutoff commitments. Each entry includes explicit sourcing to the exact provisions within the signed agreement.

Does closing checklist tracking work for managing critical path items with days-to-close deadlines?

Closing checklist tracking works for managing critical path items by calculating days-to-close and highlighting time-sensitive deliverables. It reads and updates per-deal YAML data, supporting item status updates via an optional item-id argument.

What limitations exist when updating individual checklist items during deal compliance tracking?

Deal compliance tracking requires reading and updating per-deal YAML checklist data files. Status updates to specific items depend on an optional item-id argument, meaning bulk updates or non-YAML data formats are not supported by this workflow.