1---2name: draft-credit-agreement-markup3task_id: banking-finance/draft-credit-agreement-markup4description: Produces a borrower-side markup memo identifying deviations between a draft credit agreement and the operative financing summary materials, with proposed redlines and priority classification.5activates_for: [planner, solver, checker]6metadata:7 source: https://skillmd.com/skills/finchipaiorg/draft-credit-agreement-markup8---910# Skill: Borrower's Counsel Credit Agreement Markup Memo (LBO Financing)1112## 1. Subject-matter triage (only if applicable)1314- Treat the draft credit agreement as the primary work product and the memo as a secondary advisory attachment.15- First confirm the operative source set: executed term sheet, commitment letter, partner instructions, and the draft agreement.16- If the source materials address multiple tranches, baskets, currencies, maturity paths, or borrower entities, enumerate them before analysis and review each separately.17- If only one facility or one borrower group is in scope, state that explicitly and proceed on that basis.1819## 2. Failure modes the skill is correcting2021- Failing to cross-check each financial covenant level against the operative financing summary materials; even small numeric differences can create a more restrictive covenant than intended.22- Missing the absence of a replacement lender or comparable transfer mechanism, which is a common borrower protection against holdout lenders blocking amendments or waivers.23- Stating restricted payment basket components imprecisely, without separating any fixed-capacity and ratio-based components that both need to be checked.24- Specifying the equity cure rolling cap without stating both the per-period dimension and the lifetime dimension.25- Collapsing distinct deviations into a generic “market” comment instead of isolating each operative difference, its source, and its consequence.26- Marking issues narratively without a durable plain-text redline convention that survives export.2728## 3. Legal frameworks / domain conventions that apply2930- Compare the draft credit agreement against the operative financing summary materials provision by provision; the deal documents control commercial intent, and the markup should reflect that hierarchy.31- Financial covenant levels must be checked line by line against the agreed summary; any divergence should be treated as a borrower-side point requiring explicit confirmation or correction.32- Borrower-transfer protection should be verified for a workable replacement lender or transfer-out mechanism where a lender refuses a routine amendment, waiver, or consent.33- Restricted payment capacity should be parsed by component, including any fixed basket, ratio basket, builder basket, carve-outs, and carryforward logic.34- Equity cure mechanics should be checked for both frequency and lifetime constraints, including any rolling-window formulation.35- Defined terms, basket mechanics, lien permissions, debt incurrence, investments, junior debt, prepayment rights, mandatory prepayments, and amendment mechanics should be checked for internal cross-references and consistency.36- For any proposition presented as controlling, cite the governing source in the work product by name or section where available; do not state a conclusion without tying it to the operative document language or a recognized drafting convention.3738## 4. Analytical scaffolds39401. Build an issue inventory by provision family, not by document order.412. For each provision family, compare:42 - the operative financing summary language,43 - the draft agreement language,44 - the borrower-side proposed correction.453. For each issue, capture:46 - the precise deviation,47 - the source of the intended position,48 - the practical effect on borrower economics, flexibility, or risk.494. Assign every issue a severity level from a stated ordinal scale:50 - Critical: must be corrected before execution or borrower economics/control are materially impaired.51 - High: likely inconsistent with the agreed deal or materially borrower-unfriendly.52 - Medium: drafting mismatch, missing clarification, or scope ambiguity with limited immediate impact.53 - Low: cleanup, consistency, or style point.545. Close each issue with three elements:55 - the scale of the deviation as reflected in the source materials,56 - the related provision or document that interacts with it,57 - the downstream consequence for the borrower.586. Where a term appears in multiple places, trace the cross-reference chain and confirm the defined term is used consistently everywhere it matters.597. Where the draft is silent on a borrower-protective concept, propose affirmative replacement language rather than only noting the absence.608. For redlines, use text that remains readable outside formatting:61 - [DELETED: …]62 - [INSERTED: …]63 - [REPLACED: old → new]64 - add a short [Rationale: …] note for each substantive change.6566## 5. Vertical / structural / temporal relationships (only if applicable)6768- Check whether a covenant, basket, or cure right applies at signing, at closing, upon a leverage test date, or only after a specified delivery trigger.69- Verify whether temporal windows roll forward, reset, or accumulate; do not assume a one-time cap where the draft uses a rolling concept.70- If a mechanic references a historical period, confirm the period length, measurement date, and any lifetime ceiling are all stated.71- If a provision depends on another document, schedule, or definition, trace that dependency and ensure the dependency is not broken by a draft change.72- If multiple borrower or guarantor tiers exist, confirm the obligation applies at the correct vertical level and does not inadvertently capture a narrower or broader set than intended.7374## 6. Output structure conventions7576- Produce a borrower-side markup memo organized by issue family with a short executive summary up front.77- State the severity scale once, then apply it uniformly to every issue.78- For each issue, include:79 - issue title,80 - severity,81 - operative source position,82 - draft agreement position,83 - proposed redline,84 - concise rationale,85 - borrower consequence.86- Use explicit plain-text redline markup for every substantive change so the result is intelligible without track changes.87- Where an issue turns on a comparison to a specific source clause, cite that source in the memo.88- End with a Recommended Actions block that assigns the next step to counsel or the appropriate business contact and ties it to the signing or execution timeline.89- Before finishing, confirm the memo is complete, internally consistent, and ready to be exported as `credit-agreement-markup-memo.docx`.