Individual skill
ma-deal-workbench-json
Analyze M&A deal workbench records and draft transaction terms to produce structured JSON outputs such as seller issue registers, buyer SPA deviation matrices, committee escalation packages, closing readiness packages, transition reviews, consent/blocker schedules, cap-table economics allocations, and playbook or policy comparison summaries. Use when the task provides a deal workbench, a deal ID, and an answer template requiring precise legal/business issue classification, quantified deal metrics, stable source IDs, and JSON-only output.
experiments/codex_gpt5_5_xhigh/reports/skills/task_group_020/reflect-3/reflect-3_attempt_01/SKILL.md
Source commit 5082a777379156a048881e94940d640702e5e09a
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 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.
- agent Repository topic
- ai Repository topic
- benchmark Repository topic
- llm Repository topic
- self-evolving Repository topic
- self-learning Repository topic
- skills Repository topic
- legal Derived category
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 JSON
## Workflow
1. Read the prompt and answer template before fetching data. Identify the deal ID, client side, transaction type, requested work product, required ordering, enums, units, rounding rules, and required fields.
2. Gather the complete workbench record set made available for the deal: deal summary, current draft terms, playbook rules or policy thresholds, risk estimates, employees, consents, material contracts, regulatory records, diligence findings, benchmarks, notes, documents, and cap table when economics or holder allocation is requested.
3. Do not assume that similarly named projects or generic records apply. Use only records tied to the requested deal ID.
4. Use read-only cross-table querying only when the prompt makes it available and only to verify source records, joins, or completeness.
5. Build the output directly from the template. Keep enum strings exact, preserve required object nesting, include every required field, and return valid JSON only.
## Issue Selection
- Use only current draft terms unless the prompt asks for historical context. Exclude stale terms, in-policy distractors, and categories with no current draft term unless the prompt or client position requires a missing affirmative provision.
- Include missing required terms when the surrounding records show a protection is needed, such as regulatory clearance, required consents, employee service credit/PTO, escrow support, transition services, tax allocation, transfer taxes, governing law/forum, IP/domain transition, or outside-date protection.