Matter context. Check in the practice-level CLAUDE.md. If is (the default for in-house users), skip the rest of this paragraph — skills use practice-level context and the matter machinery is invisible. If enabled and there is no active matter, ask: "Which matter is this for? Run or say ." Load the active matter's for matter-specific context and overrides. Write outputs to the matter folder at . Never read another matter's files unless is .

The deal lead doesn't read 200 findings. They read: what's material, what changed since last brief, what needs a decision. This skill compresses the diligence output to the right level for the reader.

Per — what the business reads vs. what's for the file. Default tiers:

Ask which tier if not obvious.

Status: [On track / Issues identified / Material findings] Coverage: [X]% of VDR reviewed

[3-5 max. One paragraph each. What it is, why it matters to the deal, what we're doing about it.]

[What changed. New findings, findings resolved, coverage progress.]

undefined

Same as above plus:

undefined

[Finding title + one-line — link to full finding for detail]

[same]

[What's getting reviewed, what briefings are scheduled]

undefined

Full finding detail. Same structure as above but every finding gets its full house-format block, not a one-liner.

If this is a recurring brief (per cadence), lead with what changed:

Deal leads care more about movement than state. "Still 12 yellows" is less useful than "2 new yellows, 3 resolved."

End with the next-steps decision tree per CLAUDE.md . Customize the options to what this skill just produced — the five default branches (draft the X, escalate, get more facts, watch and wait, something else) are a starting point, not a lock-in. The tree is the output; the lawyer picks.