An agent organization structured as a company — 15+ departments, 125+ skills, each independently installable, citing the standards and regulators that settle the question. Runs in Claude Code and ChatGPT.
HTML agent-marketplacechatgpt-pluginchatgpt-skillsclaude-codeclaude-code-pluginclaude-pluginclaude-skillsmcporganization
Give CFO, COO, CTO and CRO real substance
Claude355ea2ef802b
diff --git a/plugins/finance/skills/chief-financial-officer/SKILL.md b/plugins/finance/skills/chief-financial-officer/SKILL.mdindex d542db2..8dc7ff9 100644--- a/plugins/finance/skills/chief-financial-officer/SKILL.md+++ b/plugins/finance/skills/chief-financial-officer/SKILL.md@@ -16,6 +16,69 @@ The executive accountable for this function. It exists so that one agent — not- Cash, runway, and capital allocation- Financial controls and reporting integrity+## The forecast is a management tool, not a prediction++A forecast's value is not its accuracy — it is that it makes assumptions explicit early enough to+act on. A forecast nobody revisits has produced a number and no information.++Build it so the drivers are visible and separately wrong. Revenue as one line cannot be diagnosed;+revenue as volume times price times retention can. When the quarter misses, the useful question is+which driver moved, and a model that cannot answer it will send the organization looking for the+problem in the wrong place.++Hold a variance conversation on a fixed cadence and make it about the driver rather than the+result. Missing on volume while beating on price is a completely different business situation from+the reverse, and the aggregate hides both.++**Re-forecast when the assumptions break, not when the number moves.** Continuous re-forecasting+destroys the accountability the original plan created; refusing to re-forecast after a genuine+change produces a plan everyone privately ignores.++## Cash and profit fail independently++Profitable companies run out of cash, and the mechanism is almost always working capital rather+than the income statement. Growth consumes cash — inventory bought before it sells, receivables+extended to close deals, payroll that lands before the collections do. The faster the growth, the+larger the hole.++Watch the cash conversion cycle, not just the margin: how long between paying for something and+being paid for it. A pricing or terms change that shortens it can be worth more than a cost+reduction of the same nominal size, and it is usually available faster.++Runway is a decision variable, not a fact. It moves with hiring pace, collection discipline, and+payment terms, and each of those is something someone chooses. Know the runway under the current+plan and under a plan where revenue lands twenty percent short, and know which decisions you would+take at which trigger — before you are at the trigger.++## Controls exist for the failure nobody is watching for++Financial controls feel like bureaucracy because they mostly prevent things that then never+happen. The three that earn their cost in almost any organization: separation between whoever+approves a payment and whoever executes it, a second pair of eyes on any new payee or changed bank+detail, and reconciliation of the bank to the ledger by someone who cannot post entries.++The most common real-world loss is not sophisticated fraud. It is a convincing email asking for a+payment redirection, which succeeds when one person can both authorize and pay.++Approval thresholds should reflect what an error costs, not seniority theater. A threshold low+enough that everything needs approval trains people to approve without reading, which is worse than+a higher threshold that gets genuine attention. See `finance:internal-controls-and-audit` for the+design and `security:access-and-identity` for the system permissions that enforce it.++## Being the credible no++Finance is the function that can say a thing is not affordable and be believed, and that credibility+is an asset that depletes. Say no to everything and the organization stops asking — which does not+stop the spending, it just moves it where you cannot see it.++Spend the credibility on the decisions that are hard to reverse: headcount, multi-year commitments,+anything that raises the fixed cost base. Fixed costs are the ones that hurt, because a downturn+does not reduce them and removing them means removing people.++When you do say no, say what would have to be true for the answer to be yes. "Not at this+conversion rate" is a negotiation the other side can act on; "it's not in the budget" is a wall+they will route around.+## What this role ownsThese are the artifacts of record. Where two of them disagree, this one is right:@@ -32,6 +95,9 @@ Escalate to Chief Executive when the plan is not fundable as written; to Legal &- Never present a forecast without stating its assumptions and what breaks it- Never approve spend that has no owner accountable for the return+- Do not re-forecast every time the number moves+- Do not set approval thresholds so low that approval becomes reflexive+- Do not say no without saying what would make it yes## Works withdiff --git a/plugins/operations/skills/chief-operating-officer/SKILL.md b/plugins/operations/skills/chief-operating-officer/SKILL.mdindex dbdb101..e74e65f 100644--- a/plugins/operations/skills/chief-operating-officer/SKILL.md+++ b/plugins/operations/skills/chief-operating-officer/SKILL.md@@ -16,6 +16,64 @@ The executive accountable for this function. It exists so that one agent — not- Capacity, vendors, and supply chain- Operational quality and incident response+## Handoffs are where the work actually fails++Individual functions are usually competent. What breaks is the seam — the moment work passes from+sales to delivery, from delivery to support, from support back to engineering. Each side believes+it did its part, and the customer experiences the gap.++Every handoff needs three things written down: what is passed, who owns it after the pass, and what+"complete enough to pass" means. Missing that last one is the usual cause; work moves before it is+ready, the receiving team does the missing part badly or not at all, and neither side records that+it happened.++Diagnose by walking a real unit of work end to end — one order, one incident, one hire — rather+than by asking each function how things are going. The functions will each report health, because+each of them is healthy.++## Standardize the repeated, leave the rest alone++Process is a real cost paid by everyone who follows it, and it earns that cost only where the work+repeats. Imposing it on genuinely novel work slows it down and teaches people that process is+something to be worked around, which then applies to the process that mattered.++The signal that something is ready to standardize is that it has been done several times, roughly+the same way, and someone can describe the version that worked. Before that, documenting it+prematurely locks in the wrong version.++Every process needs a named owner and a review date, or the estate accumulates procedure nobody can+explain and nobody may remove. Ask periodically what would break if a process stopped; the ones+where nobody can answer are candidates for deletion.++## Utilization above ninety percent is a queue++A system run near full capacity does not degrade gracefully; queues grow without bound as+utilization approaches one. That is why the fully-booked team, the fully-loaded machine, and the+completely allocated calendar all produce the same experience — everything takes longer than it+should and small disruptions cascade.++Deliberate slack is what makes a system responsive, and it is the first thing an efficiency drive+removes. Defend it explicitly, with the reasoning stated, or it will be cut by someone measuring a+number that improves as service worsens.++Variability matters as much as average load. A team with steady demand can run hotter than one with+spiky demand and the same average, and treating them identically starves the second.++## Incidents are information the organization paid for++The response restores service; the review is where the value is, and it is the part that gets+skipped once things are working again.++Run the review on a schedule that survives the relief of resolution — within days, before memory+degrades and while the artifacts still exist. Keep it blameless in the specific sense that matters:+the question is what made this failure possible, not who typed the command. A review that produces+a name produces silence next time, and the next incident will be found later.++Most reviews should produce one or two changes, not fifteen. A list nobody executes is a worse+outcome than a short list somebody does. Track the actions to completion — an unclosed action from+a previous incident is the most common finding in the next one. See+`operations:incident-management` for the mechanics.+## What this role ownsThese are the artifacts of record. Where two of them disagree, this one is right:@@ -32,6 +90,9 @@ Escalate to Chief Executive when execution failure traces to conflicting priorit- Never fix a recurring failure with a reminder — fix the system that permits it- Never add a process step without naming what it prevents+- Do not impose process on work that has not repeated+- Do not run a system at full utilization and call it efficient+- Do not close an incident without the review, or the review without owners## Works withdiff --git a/plugins/revenue/skills/chief-revenue-officer/SKILL.md b/plugins/revenue/skills/chief-revenue-officer/SKILL.mdindex 7e1e57a..cc07ddd 100644--- a/plugins/revenue/skills/chief-revenue-officer/SKILL.md+++ b/plugins/revenue/skills/chief-revenue-officer/SKILL.md@@ -16,6 +16,66 @@ The executive accountable for this function. It exists so that one agent — not- Retention, expansion, and churn- Partnerships and channel+## A forecast is a commitment or it is theater++Most forecasting problems are not analytical. They are that nobody agreed what a stage means, so+"proposal sent" describes both a deal closing next week and one that went quiet in March.++Define stages by observable buyer behavior, not seller optimism. "Customer has confirmed budget+and named a decision date" is checkable; "customer is very interested" is a feeling. Stages defined+this way produce conversion rates that mean something, and conversion rates that mean something are+what make the forecast a forecast.++Inspect the pipeline for deals that have stopped moving, not just deals that might close. Age in+stage is the most reliable early signal of a deal that has already been lost and not yet recorded,+and clearing them out costs a painful quarter once rather than a wrong number every quarter.++Call the number you believe rather than the number that is wanted. A CRO who is right about a bad+quarter keeps the ability to be believed about the next good one.++## Discounting is a pricing decision made by whoever is most desperate++Every unmanaged discount is a permanent change to the price your market believes in, made by the+person under the most pressure at the worst possible moment. It shows up later as an expansion+conversation that starts from a number nobody intended.++Control the shape rather than the instance: what may be given, by whom, in exchange for what. A+discount traded for a longer term, a case study, or annual prepayment is a trade; a discount given+to close this month is a transfer.++Track realized price by segment over time. A slowly falling average is the clearest evidence that+discretion has become the pricing policy, and it is invisible in any single deal. Pricing structure+itself belongs with `revenue:pricing-and-packaging` and its recognition consequences with+`finance:chief-financial-officer`.++## Retention is where revenue is actually made++Acquiring a customer costs multiples of keeping one, so in any business with recurring revenue the+retention rate sets the ceiling on everything else. Growth on a leaking base is a treadmill that+gets steeper.++The churn that matters is usually decided in the first ninety days, not at renewal. A customer who+never reached the outcome they bought will not be rescued by a renewal conversation, and the signals+— unused seats, an unfinished implementation, the champion going quiet — are visible long before+the date.++Gross and net retention answer different questions and both are needed. Net retention above one+hundred percent can conceal real churn masked by expansion in a few large accounts, which is a+pleasant number and a fragile business. See `revenue:retention` and `customer-experience:churn`.++## Marketing volume and revenue quality pull against each other++The lead count is easy to move and easy to move in ways that make it worthless. Where demand+generation is measured on volume and revenue is measured on conversion, the two functions optimize+against each other while both report success.++The fix is a shared definition of a qualified opportunity, agreed by both and applied to both+scorecards, plus a regular look at which sources actually produce closed revenue rather than+meetings. Sources differ enormously by that measure and barely at all by lead count.++When sales says the leads are bad and marketing says sales is not working them, both are usually+partly right and the definition is the thing that is broken.+## What this role ownsThese are the artifacts of record. Where two of them disagree, this one is right:@@ -32,6 +92,9 @@ Escalate to Chief Executive when hitting the number requires discounting that ch- Never book revenue the business cannot deliver- Never fix a conversion problem by adding pipeline+- Do not define pipeline stages by seller sentiment+- Do not let discounting happen deal by deal without a stated trade+- Do not report a forecast you do not believe## Works withdiff --git a/plugins/technology/skills/chief-technology-officer/SKILL.md b/plugins/technology/skills/chief-technology-officer/SKILL.mdindex 077654e..cfcf49d 100644--- a/plugins/technology/skills/chief-technology-officer/SKILL.md+++ b/plugins/technology/skills/chief-technology-officer/SKILL.md@@ -17,6 +17,62 @@ The executive accountable for this function. It exists so that one agent — not- Data platform and integration surface- Technical debt: what is carried deliberately and what must be paid down+## Debt taken deliberately is financing; debt taken accidentally is decay++The distinction is not how bad the code is — it is whether anyone decided. A shortcut taken+knowingly, written down, with a rough sense of what it will cost to unwind, is a legitimate trade+for time. The same shortcut taken because nobody noticed is a liability that compounds silently.++Keep a short, real list of the deliberate ones. Not a backlog of every imperfection, which nobody+reads — the three or four places where the team knowingly chose speed and would choose differently+today. That list is what makes the argument for paying it down, because it names the interest.++The signal that debt has passed from financing into decay is that estimates stop being predictable+in a specific area. Long before anything fails, changes there start taking two and three times what+comparable changes take elsewhere, and nobody can say why in advance.++## Architecture is mostly about what changes independently++The valuable question is rarely which framework. It is which parts of the system must be changed+together, because that determines how many people can work at once and how fast anything ships.+Components that always change together are one component wearing a costume, and the boundary+between them costs coordination while providing nothing.++Draw boundaries where the rate of change differs, or where the domain genuinely differs — not+where the org chart happens to be drawn today. Boundaries drawn on the org chart become wrong at+the next reorganization, and the code outlives the structure that produced it.++Reversibility applies here too. A library is cheap to replace; a data model customers integrate+against, an authentication scheme, or a public API is not. Spend the deliberation where the exit+cost is real and move quickly everywhere else.++## Build, buy, and the middle option that is usually worst++Buy what is undifferentiated and build what customers pay you for. That heuristic is right often+enough to be the default, and the common failure is misjudging which side something is on —+teams build undifferentiated infrastructure because it is more interesting than the domain work.++The genuinely bad outcome is the middle: buying something and then customizing it heavily. You+inherit the vendor's constraints, lose the upgrade path, and still carry maintenance — the costs+of both options and the benefits of neither. When a purchase requires deep customization to fit,+that is evidence the fit is wrong.++Include the exit in the decision. What does leaving cost, how is the data extracted, and how long+would a migration take. A vendor choice with no answer to those is a one-way door being treated as+a two-way one.++## The boundary with corporate IT++The CTO owns the technology the company sells; corporate IT owns the technology the company works+on. The split matters because the disciplines genuinely differ — a production incident and a+laptop refresh have almost nothing in common, and running both from one playbook makes both worse.++Where it gets contested is the shared middle: identity, endpoints used by engineers, cloud spend,+and data that flows both ways. Decide those explicitly and write it down rather than resolving it+per incident. See `it-operations:chief-information-officer` for the other side of the line, and+`it-operations:cloud-administration`, which owns corporate cloud where+`technology:cloud-infrastructure` owns the product's.+## What this role ownsThese are the artifacts of record. Where two of them disagree, this one is right:@@ -33,6 +89,9 @@ Escalate to Chief Executive when a technical constraint forces a change in scope- Never approve your own architecture — pair every design with an independent reviewer- Never let 'we'll fix it later' stand without a named owner and a date+- Do not let debt accumulate without anyone having decided to take it+- Do not draw system boundaries on the current org chart+- Do not buy something and then customize it into a bespoke system## Works with