# Analyze Counterparty Markup Of Executive Employment Agreement > Guides the analyst to compare a counterparty redline against the company draft and negotiation playbook, applying sponsor-side framing across compensation, equity, termination, restrictive covenants, and miscellaneous provisions. - Skill: `finchipaiorg/analyze-counterparty-markup-of-executive-employment-agreemen` (Agent Skill) - Install (CLI): `npx skillmds@latest add finchipaiorg/analyze-counterparty-markup-of-executive-employment-agreemen` - Raw SKILL.md: https://api.skillmd.com/api/skills/finchipaiorg/analyze-counterparty-markup-of-executive-employment-agreemen/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: FinchipAIOrg (https://skillmd.com/u/finchipaiorg) - Updated: 2026-09-22 - Page: https://skillmd.com/skills/finchipaiorg/analyze-counterparty-markup-of-executive-employment-agreemen --- # Skill: Analyze Counterparty Markup of Executive Employment Agreement ## 1. Subject-matter triage - Treat the assignment as a sponsor-side redline analysis of an executive employment agreement against the company draft and any referenced guidance materials. - Confirm the source set before analysis: company draft, counterparty markup, playbook/guidance, equity plan or award terms if referenced, and any ancillary documents that interact with the agreement. - If the redline touches more than one executive, equity vehicle, or termination scenario, enumerate the distinct items first and analyze each separately; do not collapse them into a single generic pass. - If the task asks for a memo rather than a fresh draft, preserve the redline record and advisory analysis together; do not replace the requested review with a high-level summary. ## 2. Failure modes the skill is correcting - Analyst evaluates compensation, equity, and severance terms in isolation rather than tracing the cumulative economic and control consequences across the full agreement. - Analyst treats equity acceleration generically rather than distinguishing trigger mechanics, performance conditions, and plan-level interaction. - Analyst accepts a counterparty position without anchoring it to the company’s negotiation guidance or market baseline. - Analyst omits ambiguity risk, cross-document conflict risk, or drafting gaps that would create interpretive leverage for the executive. - Analyst describes issues without ranking them, stating why they matter, or proposing a concrete sponsor-side response. - Analyst relies on visual redline styling alone and produces markup that cannot be reconstructed from plain text. - Analyst states legal conclusions without identifying the governing rule, doctrine, or authority that supports the point. ## 3. Legal frameworks / domain conventions that apply - Executive employment agreements typically organize around base salary, incentive compensation, equity, termination, restrictive covenants, indemnification/insurance, taxes, dispute resolution, and boilerplate. - Sponsor-side analysis should treat double-trigger acceleration as the default reference point and single-trigger acceleration as a broader executive concession. - Change-in-control mechanics should be checked against the agreement and any linked equity or plan documents to avoid accidental triggers, duplicative benefits, or inconsistent definitions. - Severance analysis should map each termination path to its payment, vesting, and benefits consequence, including disability, death, without cause, for good reason, and control-change termination. - Restrictive covenant review should assess duration, geography, and activity scope under the governing law selected in the agreement and any applicable statutory or common-law limits. - Change-of-control tax provisions should be reviewed for whether the agreement includes a gross-up, best-net cutback, or no special tax protection, and for how it coordinates with contingent compensation rules. - When a provision’s economic formula depends on cost basis, grant value, or a threshold metric, the actual metric in the source documents controls the analysis; do not assume the formula works as drafted. - Cite the legal rule or authority supporting each substantive proposition, using the authority named in the source documents where available and otherwise the generally recognized authority for the issue. ## 4. Analytical scaffolds - Start with a short executive summary that ranks the most material negotiation points and identifies sponsor-side priorities. - For each redlined provision, state: what changed, why it matters, how it compares to the playbook or benchmark, and what the recommended sponsor response is. - Track the original company language, the counterparty change, and the practical effect of the revision; if the change is ambiguous, say so and recommend clarifying language. - For compensation terms, state the rate, target, threshold, or maximum in the form used by the documents; explain the economic impact over the relevant service period where duration matters. - For equity terms, identify each instrument separately, then state vesting schedule, acceleration trigger, and any performance condition or plan-level constraint. - For termination terms, map each triggering event to the severance package, continued benefits, equity treatment, and any release or condition precedent. - For restrictive covenants, assess duration, scope, and prohibited conduct, then state whether the counterparty has narrowed or expanded the covenant relative to market or playbook. - For miscellaneous terms, focus on indemnification, D&O coverage, tax, arbitration, governing law, venue, assignment, and integration, especially where they interact with the main economics. - Each issue entry should include an ordinal severity label defined once at the top of the memo and applied consistently. - Close each issue with three moves: quantify or scale the point from the source documents, cross-reference any interacting clause or document, and state the client consequence. - Where the same concept appears in multiple documents, reconcile the provisions instead of analyzing them in isolation. - If the legal significance depends on a rule or doctrine, name the authority and explain the point in one sentence; do not leave the conclusion unsupported. - Include a recommended response for every issue, framed as accept, reject, revise, or defer, with a brief rationale. ## 5. Vertical / structural / temporal relationships - Read the employment agreement alongside any referenced equity plan, award agreement, or policy so that acceleration, forfeiture, and definition mechanics are internally consistent. - Read defined terms vertically: if the counterparty revises a definition in one section, check all downstream provisions that use that term. - Read payment and vesting mechanics temporally: identify when amounts accrue, when they become payable, when conditions are tested, and when rights terminate. - Read severance, restrictive covenant, and tax provisions as a sequence, not as isolated clauses, because one can condition or override another. - If multiple agreements or schedules interact, resolve the conflict by identifying the controlling document or the express order-of-precedence language. - Any deviation from the company’s negotiation guidance must be flagged as such, with a concise explanation of why the departure matters. ## 6. Output structure conventions - Write the deliverable as a formal advisory memorandum addressed to the deal team or general counsel. - Use conventional memorandum headings rather than the rubric’s internal section labels; organize by contract topic and address each redlined provision individually. - Begin with a brief executive summary and a severity legend using an ordinal scale such as Critical / High / Medium / Low. - For each issue, include: the affected provision, the counterparty change, severity, significance, controlling authority or governing rule, cross-document interaction, and recommended sponsor response. - Preserve the redline logic in plain text by marking substantive changes with explicit textual conventions that survive export, such as [DELETED: …], [INSERTED: …], or [REPLACED: old → new], and attach a short rationale note to each change. - If the source materials call for a comparison across multiple provisions, list the affected provisions first and then analyze them one by one. - End with a Recommended Actions section that gives imperative next steps, identifies the responsible role, and ties each step to a practical timing anchor from the transaction or review process. - Keep the tone concise, operational, and sponsor-side; do not pad with generic legal background.