closing-checklist

Update corporate transaction closing checklist item statuses and blocking risks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill solves the problem of tracking and maintaining a deal closing checklist so teams always know what is still pending and what is blocking closing.

Core Features & Use Cases

  • Self-updating closing checklist: Initializes from the purchase agreement and ingests pre-closing findings from diligence so the checklist stays current.
  • Status-by-item visibility: Updates item status and last-updated timestamps, and reports what is blocking vs. on track.
  • Critical-path focus: Estimates time-to-complete per blocking item to surface items at risk and highlight those most likely to push the close date.
  • Matter-aware outputs: Uses the practice-level or active matter CLAUDE context and reads/writes to the correct deal/matter folder.

Quick Start

Ask the skill to show the current closing checklist status and what’s blocking for your deal code.

Frequently Asked Questions about closing-checklist

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

FAQPage Schema
What is a closing checklist for corporate transactions and why do I need to track conditions precedent?

A closing checklist tracks conditions precedent, closing deliverables, and deadline-bound covenants to identify what blocks a deal from closing. Monitoring these items ensures legal teams resolve pending requirements before the target close date.

How do I generate a critical path status report showing what is blocking a deal closing?

To generate a blocking status report, ingest purchase agreement terms and diligence findings into a checklist YAML. The system reconciles item statuses and produces a report estimating time-to-complete for each pending item to highlight critical path risks.

Can I reconcile diligence findings with an existing corporate transaction closing checklist?

Yes, you can reconcile diligence findings by ingesting pre-closing deliverables into an existing checklist. The system updates item statuses and last-updated timestamps while mapping findings to matching conditions precedent and covenants.

What is the best way to track due-date risk across closing deliverables and covenants with deadlines?

The best way to track due-date risk is using a self-updating checklist that estimates time-to-complete per blocking item. This surfaces items at risk of pushing the close date and highlights critical path deliverables for stakeholder reporting.

Does this closing checklist skill require a specific deal folder or matter context to initialize?

Yes, initialization requires reading the checklist YAML from a configured corporate deals folder. The skill uses practice-level or active matter context to read and write data to the correct deal directory for matter-aware status reporting.