Review an LP's marked-up LPA and comment letter against the applicable negotiation policy and prior precedent materials to produce an internal GP response memorandum that catalogs all LP comments, assesses overlap between sources, and develops a procedural response position and MFN impact analysis for each item.
Scanned 9/11/2026
Install to Claude Code
npx -y skills add sunyifeisb-art/legalwork --skill analyze-lp-comment-memo --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Analyze Lp Comment Memo?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/sunyifeisb-art-analyze-lp-comment-memo)More formats (shields.io, HTML) on the badges page.
---
name: analyze-lp-comment-memo
task_id: funds-asset-management/analyze-lp-comment-memo
description: Review an LP's marked-up LPA and comment letter against the applicable negotiation policy and prior precedent materials to produce an internal GP response memorandum that catalogs all LP comments, assesses overlap between sources, and develops a procedural response position and MFN impact analysis for each item.
activates_for: [planner, solver, checker]
---
# Skill: LP Comment Response Memo
## 1. Subject-matter triage
- Confirm the task is an internal response memo, not a negotiated draft or final side letter.
- Identify the source set before analysis: marked-up LPA, separate comment letter, negotiation policy, and precedent side letters.
- If the LP materials contain multiple comments, treat each distinct request as a separate issue unless the same point is repeated across documents and can be consolidated.
- If only one issue appears, say so explicitly and explain why no further issue splitting is needed.
- Preserve the GP’s negotiation posture: the memo should assess response options, not overcommit to concessions.
## 2. Failure modes the skill is correcting
- Not cataloging all LP redline comments systematically by number, or failing to cross-reference overlapping items that appear in both the marked-up LPA and the separate comment letter.
- Not identifying when a fee-reduction request should be tested against the applicable policy limit for the LP’s commitment tier, or failing to state the requested reduction in relative terms.
- Not analyzing MFN eligibility — whether this LP’s commitment tier qualifies it to receive or trigger MFN elections for other LPs.
- Not providing a clear response posture or compromise formulation for each comment.
- Not tying each issue back to the controlling document, the practical consequence, and the appropriate vehicle for any concession.
- Not distinguishing non-negotiable points from items that can be reframed or softened.
## 3. Legal frameworks / domain conventions that apply
- Treat the negotiation policy as the controlling authority for categorizing and testing LP asks.
- Use prior fund-vintage side letters and precedent materials as the principal source of compromise positions and marketable fallback language.
- For any legal or policy conclusion, name the governing authority or document basis that supports it; do not leave the rationale implicit.
- Management fee requests must be evaluated against the LP’s commitment tier, the policy ceiling for that tier, and the requested delta relative to the standard fee.
- If a requested fee concession is outside policy, flag the downstream MFN risk for other LPs that may elect the same treatment.
- For clawback, assess whether individual liability tracks economics actually received, and distinguish principals who received carry from those who did not.
- For key-person requests, test materiality, key-person-event sensitivity, and consistency with GP policy; consider whether the person belongs on the core list, a secondary list, or should be declined.
- For no-fault removal, preserve the standard threshold where it protects GP stability and avoids unilateral removal by a large LP.
- For ESG asks, distinguish a binding LPA screen from a softer best-efforts or notice-based commitment.
- For reporting, distinguish monthly obligations from standard quarterly reporting and consider whether enhanced quarterly or ad hoc reporting is an acceptable compromise.
- For LPAC seats, distinguish an intent-to-offer formulation from a contractual guarantee.
- For co-investment, distinguish a binding allocation promise from a fair-allocation or commercially reasonable efforts standard.
- For affiliate transfers, test whether the right is too broad and whether it should be narrowed to successor or internal reorganizational transferees with consent.
- For FOIA or public-records concerns, preserve confidentiality to the extent legally workable while allowing legally compelled disclosure, notice, and cooperation with protective-order efforts.
- For MFN, determine both what this LP can elect and what concessions to this LP might cascade to others.
## 4. Analytical scaffolds
1. Enumerate every distinct LP comment from the markup and comment letter before drafting responses.
2. Cross-reference the markup and letter; consolidate duplicates and identify where one item is split across multiple sources.
3. For each issue, record:
- the affected LPA section or concept;
- the LP’s request in plain English;
- the governing policy or precedent anchor;
- the GP’s recommended posture;
- the vehicle for any accommodation, if any.
4. For each issue, close the analysis by stating:
- the scale or threshold implicated by the source documents;
- the interaction with any other clause, schedule, or source document;
- the downstream consequence for the GP or fund.
5. For fee requests, compare the requested concession to the applicable policy limit and state whether it is within, at, or beyond the policy envelope.
6. For MFN analysis, complete the concession assessment first, then evaluate cascade effects.
7. For any item that is likely non-negotiable, say so directly and explain the market or policy reason.
8. Draft the memo so that a reader can see both the issue set and the recommended negotiation posture without consulting the source documents line by line.
## 5. Vertical / structural / temporal relationships
- The comment letter and marked-up LPA must be read together; a repeated point should be handled once, with cross-references to both sources.
- The negotiation policy controls baseline classification, while precedent side letters supply fallback language or compromise structures.
- MFN analysis comes after the concession set is identified, because every concession may create a cascade for other investors.
- If a requested accommodation is better handled outside the LPA, the memo should recommend the side-letter route rather than embedding it in the main agreement.
- Where the LP’s request affects future governance, reporting, or allocation mechanics, note the ongoing operational burden, not just the signing-date effect.
## 6. Output structure conventions
- Produce a single internal response memorandum in document form.
- Open with a concise executive summary covering the LP’s commitment context, the overall negotiation posture, and the highest-risk issues.
- Include a summary matrix that lists each consolidated comment and, for each row, the issue number, source, affected provision, request, severity, recommended response, MFN note, and preferred vehicle.
- Use an ordinal severity scale defined once at the top and apply it uniformly to every issue.
- Follow with a detailed analysis section that discusses each issue in order and explains the rationale, policy basis, precedent support, and downstream impact.
- Include an appendix cross-referencing each comment to the relevant LPA section or concept.
- End with a Recommended Actions block that assigns the next step to the relevant internal role and ties it to the closing timing of the review cycle or negotiation milestone.
- Keep the memo advisory in tone: identify the position, the reason, and the practical next move for each item.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!