Individual skill

deal-workbench-ma-review

Prepare structured M&A deal-workbench JSON deliverables from a task prompt and answer template, including buyer or seller APA/SPA issue registers, closing and economics packages, committee escalation memoranda, carveout transition reviews, and deviation matrices. Use when Codex must gather deal records, draft terms, playbook or policy rules, consents, regulatory facts, employees, material contracts, benchmarks, risk estimates, diligence records, notes, and then return schema-conforming JSON with calculated amounts, priorities, blockers, and stable source IDs.

experiments/codex_gpt5_5_xhigh/reports/skills/task_group_020/reflect-3/reflect-3_attempt_03/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
121
Repository last updated
Oct 29, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Deal Workbench M&A Review

## Core Workflow

1. Read the user prompt and the provided answer template before drafting anything.
2. Treat the answer template as controlling. Preserve required top-level fields, enum spellings, stable issue/redline IDs, nullability, array names, and ordering instructions.
3. Gather only records for the target deal ID. Use the workbench UI, APIs, or allowed read-only query access named in the task prompt. Do not import facts from similarly named or adjacent projects.
4. Build a compact source map: deal economics, current draft terms, playbook or policy thresholds, consents, regulatory records, employees, material contracts, diligence findings, benchmarks, risk estimates, notes, and documents.
5. Compare current draft terms to the applicable playbook or policy. Exclude stale terms unless the template explicitly asks to list excluded distractors.
6. Add missing-required-term issues only when the prompt, template stable IDs, playbook/policy, or surrounding deal records show that an affirmative provision is needed.
7. Return only valid JSON. Do not include narrative outside the JSON.

## Template Fidelity