本文へ移動
cccskills
無料GitHub で公開

capital-structure-and-covenants

Decides how the business is financed and what that financing then requires of it — debt versus equity, weighted average cost of capital as a hurdle rate, how much leverage cash flow can carry, and the financial, affirmative and negative covenants, definitions, test dates and cure rights that come attached. Use this to evaluate a financing option, set an investment hurdle, check whether a planned decision will trip a covenant, or work out what a lender can do when one breaks.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md4.2 KB
  • references/sources.md1.4 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Capital structure and covenants

Financing is not only where the money comes from. It is a set of ongoing constraints that will shape operating decisions for as long as the facility exists, and most of those constraints are discovered late.

Cost of capital sets the hurdle, so compute it rather than choosing a round number

Weighted average cost of capital blends the after-tax cost of debt and the cost of equity in the proportions actually used. It is the rate an investment has to clear before it creates value.

Debt is cheaper than equity — the rate is lower, the interest is deductible, and the claim is senior. That cheapness is exactly why leverage is tempting, and why the temptation needs a limit set in advance. Equity has a cost even though nobody writes a check for it; treating it as free is how capital gets consumed by projects that never earned their keep.

Size leverage to the bad case, not the plan

Leverage amplifies returns on equity and amplifies losses, and the losses arrive first because debt service does not wait for recovery.

Capacity is governed by the stability of cash flow, not by an industry average ratio. A predictable subscription business carries debt that a project business with lumpy collections cannot. The question is never "can we service this at plan" — it is "can we service this at the plan we would be embarrassed to show anyone."

Covenants are where financing becomes an operating constraint

  • Financial covenants — leverage ratio, interest coverage, fixed charge coverage, minimum liquidity, sometimes a minimum earnings floor. Tested quarterly in most agreements.
  • Affirmative covenants — what you must do: reporting by a deadline, audited statements, insurance, notice of material events.
  • Negative covenants — what you may not do without consent: additional debt, liens, asset sales, distributions, acquisitions, change of control.

The definitions matter more than the levels. Earnings in a credit agreement is a defined term with its own permitted add-backs and its own caps, and it will not equal the figure in your management accounts. Two facilities at the same headline ratio can allow very different behavior.

Model covenants forward at every material decision. A hiring plan, a capex commitment, or an acquisition can trip a ratio two quarters out while looking affordable this quarter. Headroom at each future test date belongs in the forecast, not in a separate spreadsheet nobody opens.

When a breach is coming, the timing of the conversation is the whole outcome

Approach the lender before the test date. A waiver requested in advance is a negotiation; a breach discovered afterward is a default, and the difference in leverage between those two positions is enormous.

Know what the agreement gives you before you need it: cure periods, grace periods, whether an equity cure is permitted and how often, and whether cross-default provisions pull other agreements in behind this one. Consequences escalate rather than arriving all at once — a fee, then a rate step-up, then tightened covenants, then a cash sweep, then acceleration.

Sources

references/sources.md in this skill lists the outside authorities that settle the questions here — what each one is authoritative for, and what you may do with it. Check them before answering on anything they cover, and cite what you used. Most are free to read and not free to reproduce; the use note on each is binding.

Never

  • Sign a facility without modeling its covenants against the downside case.
  • Read a covenant level without reading the definitions it depends on.
  • Arrive at a test date without already knowing the number.
  • Treat equity as costless because no payment leaves the account.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account. Use this to design or fix signup and onboarding, diagnose why signups do not convert to active use, reduce time-to-value, or decide what a new user must accomplish first.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

cbrock84 のスキルをすべて見る

このスキルの問題を報告する