document-diligence

Document Diligence

Turns a pile of deal documents into a structured, citable summary and a live issues and Q&A tracker. The cross-check between documents is the point; the summary is scaffolding. Works entirely on documents the user supplies — no external data required.

When NOT to Use

• Tearing down a single CIM or management presentation and challenging the add-backs — use cim-teardown instead.
• Tracking which requests the seller still owes and drafting chases — use dd-checklist instead.
• Writing the recommendation for committee — use ic-memo instead.
• Public-source background on a listed company — use company-profile-pack instead.
• Valuing the asset or advising whether to proceed — outside this skill's scope.

Related Skills

Hand off rather than overlap:

• Seller-framing and adjustment challenge on the CIM itself — use cim-teardown instead.
• Request list, aging and red flag register — use dd-checklist instead; the issues list here feeds it.
• The committee paper and its risk section — use ic-memo instead.
• Peer multiples on the target — use comps-analysis instead.
• Authoring a new presentation — use pitch-deck-skeleton instead.
• Formatting an existing document or tracker — use docx or xlsx instead.

Workflow

1. Inventory before reading

Collect the documents from input/ first, then sharepoint_onedrive-GetDriveChildren on the deal folder or data room the user names, and sharepoint_onedrive-SearchDrive for files filed elsewhere. Use the pdf skill for PDFs and host-InspectDocument for Office files.

List every document received: filename, type, page count, date, apparent purpose, and whether it was read via OCR. Present the inventory, name anything referenced by another document but not supplied as NOT PROVIDED, and continue into the analysis — flag gaps rather than waiting for an answer.

State the inventory before analyzing anything. If the user expects 40 data room files and supplied 12, that must surface immediately — not after a summary that appears complete.