| name | material-contract-schedule |
| title | $corporate-legal:material-contract-schedule |
| description | Build the material contracts disclosure schedule from diligence findings, applying the purchase agreement's Material Contract definition and formatting per the agreement's schedule format. Use when user says "build the contracts schedule", "disclosure schedule", "schedule 3.X", "material contracts list", or when drafting disclosure schedules. |
| author | alexchlou |
| author_url | https://github.com/alexchlou/codex-for-legal/tree/main/plugins/corporate-legal/skills/material-contract-schedule |
| license | Apache-2.0 |
| version | 0.1.0 |
| execution_mode | open |
| jurisdiction | general |
| practice | corporate |
| language | en |
Codex v1 local-input note: This migrated skill supports local files and pasted text by default. References to Drive, CLM IDs, Slack, Westlaw, iManage, Ironclad, eDiscovery, dockets, or other remote systems require a separately configured Codex connector/MCP server. When a connector is unavailable, ask for a local export, local file path, or pasted excerpts. If config/local/codex-for-legal/<practice>/CLAUDE.md is missing, ask the user to run the relevant cold-start-interview or customize skill and copy from config/templates/codex-for-legal/<practice>/CLAUDE.md.
$corporate-legal:material-contract-schedule
- Load purchase agreement → Material Contract definition + schedule format.
- Use the workflow below.
- Apply definition to diligence findings. Flag edge cases.
- Format per agreement. Consent overlay feeds closing checklist.
Matter context
Matter context. Check ## Matter workspaces in the practice-level CLAUDE.md. If Enabled 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 $corporate-legal:matter-workspace switch <slug> or say practice-level." Load the active matter's matter.md for matter-specific context and overrides. Write outputs to the matter folder at config/local/codex-for-legal/corporate-legal/matters/<matter-slug>/. Never read another matter's files unless Cross-matter context is on.
Purpose
The purchase agreement has a rep: "Schedule 3.X lists all Material Contracts." This skill builds that schedule from the diligence findings — which contracts are material per the agreement's definition, in the format the agreement requires.
Load context
- Purchase agreement draft — for the definition of "Material Contract" and the schedule format
config/local/codex-for-legal/corporate-legal/CLAUDE.md → materiality thresholds (may differ from the agreement definition — use the agreement's)- Diligence findings from diligence-issue-extraction — contract-level data
Workflow
Step 1: Get the definition
Pull the definition of "Material Contract" from the purchase agreement — the PA definition controls. Deal-structure differences (stock vs. asset vs. merger) can change how a prong is interpreted, and regulated-industry overlays (healthcare, defense, financial services, telecom, government contracting) can add consent requirements that live outside the PA. If the deal involves any of those overlays, research the applicable anti-assignment or novation rules (for example, federal contracts, government contracting novation, sector-specific consent statutes) and cite the controlling rule.
