1---2name: extract-credit-agreement-covenants3task_id: corporate-ma/extract-credit-agreement-covenants4description: Guides extraction and analysis of the covenant package in a credit agreement for acquisition diligence, cross-referenced against current compliance data to identify constraints and risks.5activates_for: [planner, solver, checker]6metadata:7 source: https://skillmd.com/skills/finchipaiorg/extract-credit-agreement-covenants8---910# Skill: Credit Agreement Covenant Extraction for Acquisition Diligence1112## 1. Subject-matter triage1314- Determine the document set in scope before analysis: the credit agreement, amendments or joinders, the latest compliance certificate or officer certificate, and the Q3 compliance data referenced by the request.15- If multiple reporting periods, borrowers, guarantors, facilities, or tranches are present, enumerate them first and analyze each separately rather than collapsing them into a single pass.16- Treat the acquisition as the organizing fact pattern: identify whether it is a direct or indirect ownership change, whether control shifts at parent or sponsor level, and whether the transaction changes any covenant metric or consent condition.1718## 2. Failure modes the skill is correcting1920- The extraction lists covenant provisions without tying them to current financial data, leaving the buyer without a view of present covenant risk.21- Negative covenants are captured without their carve-outs, baskets, builder mechanics, or exceptions, producing an incomplete picture of permitted conduct.22- Financial maintenance covenants are identified but not tested against current compliance data, so headroom, breach risk, and cure mechanics remain unclear.23- Change-of-control and mandatory prepayment mechanics are extracted in isolation and not tested against the proposed acquisition, leaving the transactional consequence unanalyzed.24- The memo describes restrictions but does not translate them into deal-structuring implications, waiver needs, or diligence follow-up.2526## 3. Legal frameworks / domain conventions that apply2728- Credit agreements are typically organized into financial maintenance covenants, affirmative covenants, negative covenants, and change-of-control / event-of-default provisions.29- Financial maintenance covenants must be read with their test date, measurement period, applicable add-backs, cure rights, and any equity cure provisions; the operative rule is the agreement’s defined covenant text, not a shorthand label.30- Negative covenants must be analyzed together with exceptions, baskets, ratios, grower features, permitted acquisitions, permitted liens, permitted debt, and other defined carve-outs.31- Change-of-control provisions often trigger mandatory prepayment, lender consent, or an event of default; the operative consequence is controlled by the agreement’s express remedy language.32- The deal analysis should be anchored to the agreement’s defined terms and to any attached compliance materials; where a financial ratio is stated, the governing comparison is the agreement’s own methodology and the disclosed current compliance data.33- For legal propositions tied to interpretation, rely on the agreement’s definitions and operative provisions as the controlling authority; where a standard market concept is used, state it by its conventional name and tie it to the text that invokes it.3435## 4. Analytical scaffolds3637- Start with a covenant inventory:38 - identify each financial maintenance covenant;39 - identify each affirmative covenant that imposes ongoing reporting, delivery, insurance, tax, litigation, or maintenance obligations;40 - identify each negative covenant and every material exception;41 - identify any change-of-control, mandatory prepayment, or default provision implicated by ownership change.42- For each financial maintenance covenant, extract:43 - metric;44 - threshold;45 - testing frequency and measurement date;46 - whether the test is incurrence-based or maintenance-based;47 - cure right, if any, and its conditions;48 - whether the latest compliance data shows compliance, cushion, or stress.49- For each negative covenant, extract:50 - the base prohibition;51 - all material exceptions;52 - any basket, carve-out, or permitted transaction;53 - any grower or builder mechanic;54 - whether the acquisition falls within or outside the permitted scope.55- For each acquisition-sensitive provision, test the transaction against the definition and then the remedy:56 - does the transaction fit the definition;57 - if yes, what consequence follows;58 - if no, what factual assumption keeps it outside.59- Where several covenants interact, resolve the interaction explicitly rather than listing them separately; for example, note when a transaction could be permitted under a negative covenant but still fail a change-of-control test.60- Close each issue by stating the scale of the constraint using the source documents’ own figures or thresholds, the relevant cross-reference, and the downstream deal consequence.6162## 5. Vertical / structural / temporal relationships6364- Track hierarchy from defined term to covenant to exception to remedy; do not analyze an exception before identifying the prohibition it modifies.65- Track time from signing to closing to post-closing reporting dates; a covenant that is compliant at signing may still be stressed by the next test date or by closing mechanics.66- Track entity structure: parent, borrower, subsidiaries, guarantors, and restricted versus unrestricted entities may be treated differently, so state which entity is burdened or benefited.67- Track causation: covenant text controls conduct, compliance data tests current status, and the acquisition tests whether the transaction itself triggers a separate consequence.6869## 6. Output structure conventions7071- Produce a single memorandum in conventional diligence form, not a bare extraction table.72- Use a short executive summary up front, then a covenant-by-covenant analysis organized by category.73- For each issue or constraint, include an explicit severity label using a consistent ordinal scale stated once at the top of the memo.74- Each issue entry should state: the covenant, the operative text or defined concept in paraphrase, the current compliance status if applicable, the cross-reference that matters, the transaction consequence, and any diligence follow-up.75- End with a concise Recommended Actions section that assigns each action to a responsible role and ties it to the relevant transactional milestone or deadline.76- Keep the memo analytical and operative; do not merely restate document language, and do not omit the practical implication for acquisition diligence.