Menu

Individual skill

ma-deal-workbench-review

0upvotes

Produce structured JSON deliverables (issue registers, deviation matrices, committee escalation memos, closing/transition packages) from an M&A "deal workbench" web app plus an answer_template.json. Use whenever a task gives a deal ID, points at a workbench that serves deal, playbook, and policy records, and demands JSON conforming to a supplied template with fixed enums, stable record IDs, and integer-dollar / percent-point units.

experiments/claude_code_opus_4_8_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

# M&A Deal Workbench → structured JSON review

You are counsel for one side of a deal. A workbench app holds the deal record and its
supporting tables; a playbook or policy holds your side's negotiating limits. Your job is to
compare the current draft against those limits, quantify the gaps, and emit **one JSON object
that conforms exactly to the supplied answer template — no prose outside the JSON**.

## The template is the specification

Read `input/payloads/answer_template.json` **before** touching the workbench. It fixes:

- the **top-level shape** — reproduce these keys exactly, at the same nesting depth;
- the **closed enums** — never invent a value for a field that lists allowed values;
- the **issue/redline ID vocabulary** — when the template enumerates stable IDs
Back to top