# Respond To Lp Comment Letter > Review an LP comment package and accompanying LPA markup, then produce a GP counsel response memo that includes a summary matrix, comment-by-comment responses with accept/modify/reject decisions, precedent-based analysis where relevant, and an appendix cross-referencing comments to the applicable LPA sections. - Skill: `finchipaiorg/respond-to-lp-comment-letter` (Agent Skill) - Install (CLI): `npx skillmds@latest add finchipaiorg/respond-to-lp-comment-letter` - Raw SKILL.md: https://api.skillmd.com/api/skills/finchipaiorg/respond-to-lp-comment-letter/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/respond-to-lp-comment-letter --- # Skill: GP Counsel Response Memo for LP Comment Packages ## 1. Subject-matter triage - Treat the comment letter and the marked-up LPA as a single integrated package; reconcile them before drafting any response. - Identify whether the LP is seeking economics, governance, transfer, reporting, fiduciary, or process changes, because the response posture depends on the category. - Flag items that appear to be repeated across both documents and consolidate them into one issue entry with both sources noted. - If the package includes multiple LPs or multiple side-letter contexts, separate the analysis by investor and by governing precedent set. ## 2. Failure modes the skill is correcting - Reviewer reads only the letter and misses edits embedded in the markup, or vice versa. - Related comments are answered piecemeal, leading to inconsistent positions across the memo. - The memo lacks a complete tracking matrix, making the negotiation state hard to manage. - Responses state outcomes without tying them to the governing policy, the relevant provision, or the controlling precedent. - Precedent is discussed abstractly instead of linked to the specific requested provision and the actual prior treatment. - Accepted changes are described without enough specificity for drafting follow-through. - The appendix does not map each comment to the relevant LPA section, slowing implementation. - The memo gives a conclusion without a clear recommendation to counsel on next steps. ## 3. Legal frameworks / domain conventions that apply - Use the GP’s negotiation policy as the first filter for each request, then test against relevant side-letter precedent. - Treat the comment package as a comparison exercise across: requested language, current fund form, prior fund treatment, and policy constraints. - For fee or economics requests, anchor the response to the applicable commitment tier, side-letter policy band, or comparable economics framework in the source set. - For transfer, excusal, ESG, MFN, clawback, removal, and subscription-facility issues, assess both contractual consequence and operational or fiduciary effect. - Where a request could narrow the GP’s discretion or create inconsistency with the fund mandate, state that tension expressly and frame any alternative in objective terms. - Where a prior investor received similar or more favorable treatment, analyze scope, timing, and election mechanics before deciding whether the current LP can rely on it. - Use controlling legal or market authorities when stated propositions depend on them; name the rule, statute, regulation, or recognized market convention that supports the position. - Keep the response internal and negotiation-oriented: it should guide counsel, not read like a signed external letter. ## 4. Analytical scaffolds - First, read both source documents end-to-end and enumerate every distinct comment or requested change. - Assign each item a stable identifier and note whether it appears in the letter, the markup, or both. - Then build a master matrix that records the issue, source location, policy posture, precedent match, recommended position, and implementation note. - For each issue, decide whether to accept, partially accept, reject, or reserve for discussion, and explain why in one concise paragraph. - Where a request is outside policy, say so directly and identify the nearest permitted alternative, if any. - Where a request is inside policy but inconsistent with prior treatment, explain the distinction or align the response if precedent supports it. - Where multiple comments affect the same clause, resolve them as a single substantive issue and note the cross-dependencies. - Draft proposed language only for items the GP is prepared to modify; otherwise provide a concise reason for refusal and any fallback framing. - Close each issue with the practical consequence of the request for the fund, the GP, or the LP cohort. - After drafting, verify that the matrix, the responses, and the appendix use the same identifiers and do not conflict. ## 5. Vertical / structural / temporal relationships - Compare the requested treatment against prior side letters only to the extent those provisions are within the current LP’s scope and timing window. - If a prior investor accepted a more permissive or more restrictive formulation, explain whether that precedent is binding, persuasive, or outside scope. - For interim testing, reporting, or election rights, consider whether timing within the fund lifecycle changes the feasibility or precedent value of the request. - For transfer and excusal provisions, distinguish among direct transfer, transfer by operation of law, affiliate transfer, and consent-based exceptions. - For MFN items, assess both substantive similarity and whether the prior treatment was granted in a form the current LP can elect. - For fee and economics requests, confirm the relevant commitment tier or investment stage before comparing against policy or prior deals. - For ESG and mandate-related requests, distinguish between aspirational language, reporting commitments, and binding investment constraints. ## 6. Output structure conventions - Prepare a single internal response memo with three integrated parts: a summary matrix, detailed comment responses, and an appendix mapping comments to LPA sections. - Start the matrix with a uniform severity or priority label for each issue so counsel can triage quickly. - Each matrix row should capture the comment ID, short issue description, source document(s), policy status, precedent status, recommended GP position, and implementation note. - In the detailed responses, organize by comment ID or clause order and keep each entry self-contained. - Each response should state the decision, the rationale, the precedent or policy hook, and any proposed revised wording if the item is accepted or modified. - Use plain textual markup for any proposed changes so the operative language is unmistakable in the memo itself. - Ensure the appendix cross-references every comment to the applicable LPA section or sections, including overlapping issues. - End with a concise recommended actions block directed to the responsible internal role, with an action verb and timing tied to the drafting or negotiation timeline.