closing-checklist

Synchronize purchase agreement conditions and diligence findings into a live closing checklist.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents deals from missing closing by maintaining a live checklist of conditions precedent, closing deliverables, and pre-closing covenants, then telling you exactly what is blocking progress.

Core Features & Use Cases

  • Self-updating deal checklist: Initializes from the purchase agreement and ingests new diligence “closing action” findings to append missing items.
  • Status governance with identifiers: Supports explicit item status updates (by item ID) and tracks last-updated timestamps.
  • Blocking-focused reporting: Produces a “what’s blocking” status view with at-risk prioritization based on estimated time-to-complete versus due dates.
  • Critical-path prioritization: Separates blocking items by whether slips would likely push the close date, not just by marked “blocking” status.
  • Matter-aware outputs and guardrails: Uses the practice-level matter context (when enabled) and includes a certification gate before any “ready to close” assertion.

Quick Start

Ask the skill to produce the latest “what’s blocking” closing checklist status for the current 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 conditions precedent and see what is blocking deal closing?

A closing checklist tracks conditions precedent and closing deliverables by synchronizing purchase agreement text with diligence findings, then reporting critical-path prioritization and at-risk items blocking deal close.

How does a closing checklist ingest diligence findings to update deal status?

The checklist ingests diligence findings by appending new closing action items to the existing checklist state, synchronizing conditions precedent and pre-closing covenants with the purchase agreement to maintain live deal status.

Can I update specific closing checklist items by ID and track their status?

Yes, you can update specific closing checklist items by their item ID to change status, which automatically tracks last-updated timestamps to maintain accurate deal closing progress governance.

What is the best way to prioritize blocking items on a critical path for deal closing?

The best way to prioritize blocking items is using a closing checklist that separates critical-path items by whether slips would likely push the close date, comparing estimated time-to-complete versus due dates for at-risk prioritization.

Does the closing checklist provide a ready to close certification?

No, the closing checklist does not make closing certifications or draft documents; it includes a certification gate before any ready to close assertion and generates structured status outputs without legally certifying the deal.

When do I need a live closing checklist for matter context deal workflows?

You need a live closing checklist for matter context deal workflows when tracking conditions precedent, closing deliverables, and pre-closing covenants across multiple operation modes including initialize, ingest, update, and report to prevent missing closing.