Skip to content

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.

US English enforcement, README org chart, Pages entry point (#11)

Chris Brock246477668511
diff --git a/.claude-plugin/marketplace.json b/.claude-plugin/marketplace.json
index 1f264c0..de2e3fb 100644
--- a/.claude-plugin/marketplace.json
+++ b/.claude-plugin/marketplace.json
@@ -160,7 +160,7 @@
{
"name": "pmo",
"source": "./plugins/pmo",
- "description": "Enterprise programme management office: portfolio governance, programme and project delivery, delivery risk, benefits realization, and adoption.",
+ "description": "Enterprise program management office: portfolio governance, program and project delivery, delivery risk, benefits realization, and adoption.",
"version": "1.0.0",
"author": {
"name": "Chris Brock"
diff --git a/.claude/agents/pmo.md b/.claude/agents/pmo.md
index ee626c1..a69d72c 100644
--- a/.claude/agents/pmo.md
+++ b/.claude/agents/pmo.md
@@ -1,9 +1,9 @@
---
name: pmo
-description: Enterprise PMO. Owns plugins/pmo/** and nothing else. Delegate portfolio governance, programme and project delivery, delivery risk, benefits and adoption work here.
+description: Enterprise PMO. Owns plugins/pmo/** and nothing else. Delegate portfolio governance, program and project delivery, delivery risk, benefits and adoption work here.
---
-# Programme Management Office (EPMO)
+# Program Management Office (EPMO)
## Why this agent exists
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index b5ac8ac..ebcc498 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,19 +1,19 @@
# Contributing
-Contributions are welcome. This document covers the licence, the bar for a skill, and the checks.
+Contributions are welcome. This document covers the license, the bar for a skill, and the checks.
-## Licence
+## License
-**By submitting a contribution you agree it is licensed under the [MIT Licence](LICENSE), the same
+**By submitting a contribution you agree it is licensed under the [MIT License](LICENSE), the same
terms as the rest of this repository.**
Contribute only work you have the right to license this way. In particular, do not paste in skills,
-prose, or reference material from another project unless you wrote it or its licence permits
+prose, or reference material from another project unless you wrote it or its license permits
relocation — and if it does, say so in the pull request. Every line in this repository is original
to it.
`scripts/check-provenance.py` is a backstop, not a proof. It scans every text file in the tree for
-licence headers, copyright notices, and SPDX identifiers, flags files named like licences
+license headers, copyright notices, and SPDX identifiers, flags files named like licenses
(`LICENSE`, `COPYING`, `NOTICE`, `PATENTS`, `AUTHORS`), and rejects bundled font assets. It cannot
detect prose lifted without a notice attached — which is the case that matters most. Review is what
catches that; the check only catches the obvious.
@@ -56,7 +56,7 @@ Four checks, the same ones CI runs:
|---|---|
| Surface map | Every tracked path has exactly one owner |
| Skill frontmatter | `name` equals the directory name, lowercase-hyphenated, unique, description substantial |
-| Provenance | No licence headers, copyright notices, licence-named files, or font assets |
+| Provenance | No license headers, copyright notices, license-named files, or font assets |
| Generated docs | README and org-chart tables match the tree |
**Stage your files first.** The surface guard reads `git ls-files`, so an unstaged file is invisible
@@ -71,6 +71,15 @@ present.
neither reliably wins — prefer extending an existing skill, or folding a family into one skill
with references, over adding a near-neighbour.
+## House style
+
+**US English.** The author writes in US English and the catalog does too — *license*, *program*,
+*catalog*, *behavior*, *prioritize*, *center*. `scripts/check-us-english.py` fails the build on
+British spellings and `--fix` rewrites them.
+
+The list is of exact word forms, not stems, because stems are a trap here: *analysis*, *analyst*,
+*specialist* and *realistic* are already correct US English and must never be rewritten.
+
## Adding a department
All five, in the same change, or the check fails:
diff --git a/README.md b/README.md
index 6847043..b38f45d 100644
--- a/README.md
+++ b/README.md
@@ -10,6 +10,19 @@
<a href="CONTRIBUTING.md"><img alt="PRs welcome" src="https://img.shields.io/badge/PRs-welcome-2EA043?style=flat-square"></a>
</p>
+<p align="center">
+ <a href="https://cbrock84.github.io/headcount/org-chart.html">
+ <picture>
+ <source media="(prefers-color-scheme: dark)" srcset="docs/assets/org-chart-dark.png">
+ <img alt="The headcount org chart — 16 departments, 135 skills, searchable" src="docs/assets/org-chart-light.png" width="840">
+ </picture>
+ </a>
+</p>
+
+<p align="center">
+ <a href="https://cbrock84.github.io/headcount/org-chart.html"><b>Open the interactive org chart</b></a> — search every skill, open a department, jump to the source.
+</p>
+
An agent organization for [Claude Code](https://claude.com/claude-code), structured as a company:
a chief executive over 16 departments, 135 skills in total.
@@ -70,7 +83,7 @@ to as a subagent with its own exclusive write surface.
| Skill | What it does |
|---|---|
| `ai-workflow-architect` | Designs AI systems, automations, and agent workflows for a business — identifying which manual work is worth automating, how to structure the system, which tools fi…. |
-| `api-design` | Designs interfaces that survive their consumers — resource modelling, errors, versioning, pagination, and compatibility. |
+| `api-design` | Designs interfaces that survive their consumers — resource modeling, errors, versioning, pagination, and compatibility. |
| `branch-and-worktree-workflow` | Isolates feature work in its own branch or worktree and integrates it cleanly when done. |
| `chief-technology-officer` | Owns architecture, engineering delivery, infrastructure, data platform, and internal systems. |
| `cloud-infrastructure` | Designs and runs cloud infrastructure — environments, infrastructure as code, networking and isolation, scaling, and cost. |
@@ -110,11 +123,11 @@ to as a subagent with its own exclusive write surface.
| Skill | What it does |
|---|---|
| `backup-and-recovery` | Protects and restores data — backup coverage and scope, retention, immutability against ransomware, and proving restores actually work. |
-| `endpoint-management` | Manages laptops, desktops and mobile devices — enrolment, configuration, patching, software distribution, and lost or compromised devices. |
+| `endpoint-management` | Manages laptops, desktops and mobile devices — enrollment, configuration, patching, software distribution, and lost or compromised devices. |
| `identity-lifecycle-administration` | Executes joiner, mover and leaver processes — provisioning, group membership, access changes on role change, and complete deprovisioning. |
| `it-asset-management` | Tracks hardware and software assets through their life — procurement, ownership, licensing, refresh, and disposal. |
| `network-administration` | Designs and operates the corporate network — segmentation, remote access, wireless, DNS and addressing, and diagnosing network problems. |
-| `service-desk` | Runs the IT service desk — intake, triage, prioritisation, escalation, knowledge, and the metrics that improve service rather than distort it. |
+| `service-desk` | Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. |
| `systems-administration` | Runs servers and corporate systems — patching, configuration baselines, change control, capacity, and the routine that prevents incidents. |
</details>
@@ -207,7 +220,7 @@ to as a subagent with its own exclusive write surface.
| `financial-modeling` | Builds and stress-tests financial models for forecasting, scenario planning, and decision support — revenue build, cost structure, driver logic, and the sensitiviti…. |
| `financial-reporting-and-close` | Runs the period-end close and produces reporting — close calendar, reconciliations, accruals, variance analysis, and reporting that gets read. |
| `internal-controls-and-audit` | Designs and tests controls over financial reporting — segregation of duties, approval limits, evidence, and preparing for audit. |
-| `revenue-recognition` | Determines when and how revenue is recognised — performance obligations, contract terms that change the answer, and the deal structures that create accounting probl…. |
+| `revenue-recognition` | Determines when and how revenue is recognized — performance obligations, contract terms that change the answer, and the deal structures that create accounting probl…. |
| `treasury-and-liquidity` | Manages cash and liquidity — cash forecasting, runway, working capital, banking structure, and currency and counterparty exposure. |
| `unit-economics` | Establishes whether the business makes money on each customer or unit — contribution margin, acquisition cost, payback period, lifetime value, and the cohort behavi…. |
@@ -224,20 +237,20 @@ to as a subagent with its own exclusive write surface.
| `process-design` | Designs, documents, and fixes operational processes — mapping the current state, finding where work actually stalls, redesigning the flow, and building controls tha…. |
| `quality-management` | Builds quality into operations — defining standards, catching defects at the right point, root cause analysis, and continuous improvement. |
| `service-level-management` | Defines and manages service levels — setting targets that reflect what customers need, measuring honestly, and handling breaches. |
-| `supply-chain-and-logistics` | Manages the flow of goods and inputs — sourcing, inventory, lead times, fulfilment, and supply risk. |
+| `supply-chain-and-logistics` | Manages the flow of goods and inputs — sourcing, inventory, lead times, fulfillment, and supply risk. |
| `vendor-management` | Selects, contracts, and manages suppliers and vendors — requirements, evaluation, negotiation support, onboarding, performance management, and exit. |
</details>
<details>
-<summary><b>Programme Management Office</b> (EPMO / COO) — 6 skills</summary>
+<summary><b>Program Management Office</b> (EPMO / COO) — 6 skills</summary>
| Skill | What it does |
|---|---|
| `benefits-realization` | Ensures projects deliver the value they were approved on — defining measurable benefits, baselining, tracking after delivery, and honest post-implementation review. |
| `change-and-adoption` | Gets people to actually use what was delivered — stakeholder analysis, communication, training, resistance, and measuring adoption. |
| `dependency-and-risk-management` | Manages delivery risk and cross-team dependencies — identifying, sizing, mitigating and escalating what could stop the work. |
-| `portfolio-governance` | Governs the portfolio of work — intake, prioritisation, stage gates, resource contention, and stopping things. |
+| `portfolio-governance` | Governs the portfolio of work — intake, prioritization, stage gates, resource contention, and stopping things. |
| `program-management` | Plans and drives cross-functional programs to delivery — scope, sequencing, dependencies, status, risk, and the escalations that keep work moving. |
| `project-delivery` | Plans and delivers a single project — scope, estimation, scheduling, critical path, tracking, and recovering when it slips. |
@@ -250,7 +263,7 @@ to as a subagent with its own exclusive write surface.
|---|---|
| `chief-customer-officer` | Owns the customer's experience after the sale — support, success, escalation, and the feedback loop back into product. |
| `escalation-management` | Handles customer situations that have exceeded normal support — severity assessment, incident communication, executive escalation, and recovering a relationship aft…. |
-| `self-service-and-knowledge` | Builds the help centre, in-product guidance, and knowledge base that let customers resolve problems without contacting anyone — content, findability, maintenance, a…. |
+| `self-service-and-knowledge` | Builds the help center, in-product guidance, and knowledge base that let customers resolve problems without contacting anyone — content, findability, maintenance, a…. |
| `support-operations` | Designs and runs the support function — channels, queues, routing, staffing, service levels, quality, and the metrics that show whether it is working. |
| `voice-of-customer` | Builds the loop from what customers say to what gets changed — collecting feedback, distinguishing signal from noise, routing it to owners, and closing the loop bac…. |
@@ -295,7 +308,7 @@ to as a subagent with its own exclusive write surface.
| `learning-and-development` | Builds capability — skills gaps, career frameworks, training that transfers to the job, and internal mobility. |
| `onboarding-and-offboarding` | Designs the joining and leaving experience — first-day readiness, ramp to productivity, knowledge capture, and clean exits. |
| `org-design` | Designs how an organization is structured — reporting lines, team boundaries, spans and layers, role definition, and workforce planning against the strategy. |
-| `performance-management` | Runs performance systems that change behaviour — expectations, feedback, review cycles, calibration, and handling underperformance. |
+| `performance-management` | Runs performance systems that change behavior — expectations, feedback, review cycles, calibration, and handling underperformance. |
| `workforce-planning` | Plans the shape and size of the workforce — demand for roles, build-versus-buy, attrition, and sequencing hiring against budget. |
</details>
@@ -328,6 +341,7 @@ docs/AGENT-SURFACES.md every path has exactly one owner, enforced in CI
docs/DECISION-LOG.md numbered decisions with options and recommendations
docs/USE-CASES.md situations worked end to end across departments
docs/org-chart.html interactive org chart, searchable across every skill
+docs/index.html GitHub Pages entry point, redirects to the chart
```
Agents split by **exclusive write surface**, not by topic — a topic split has no checkable
@@ -341,15 +355,16 @@ boundary, and two agents working on "SEO" and "UI" both end up in the same file.
```
Verifies the surface map is coherent, every skill's frontmatter is valid and unique, no
-third-party licence text has appeared, the generated README and social card are current, every
-`department:skill` reference in the docs resolves, and every manifest parses. CI runs the same
+third-party license text has appeared, the generated README and social card are current, every
+`department:skill` reference in the docs resolves, spelling is US English, and every manifest
+parses. CI runs the same
script, so local and CI cannot drift.
A new department needs its roster row in `docs/AGENT-SURFACES.md`, a surface block, a charter in
`.claude/agents/`, and an entry in `.claude-plugin/marketplace.json` — all in the same change, or
the check fails.
-## Licence
+## License
MIT — see [LICENSE](LICENSE). Every skill here was written for this repository.
diff --git a/docs/DECISION-LOG.md b/docs/DECISION-LOG.md
index 7148ddc..758c972 100644
--- a/docs/DECISION-LOG.md
+++ b/docs/DECISION-LOG.md
@@ -85,7 +85,7 @@ knowingly.
## D4. Rewrite-before-purge ordering — ✅ Resolved
-The first execution of D3 deleted the originals and then wrote replacements from a catalogue of
+The first execution of D3 deleted the originals and then wrote replacements from a catalog of
names and descriptions, so coverage was never verified against actual content.
**Resolution:** Corrected. All 100 superseded skills were restored from git history to a scratch
@@ -124,7 +124,7 @@ commits carrying the vendored tree are unreachable.
## D6. Provenance of the 12 Drive-sourced skills — ✅ Resolved
Twelve skills came from the shared Drive folder "12 ready-to-use Claude Skills that turn Claude into
-your own AI team," owned by an unfamiliar Gmail account. They carry **no licence and no stated terms**,
+your own AI team," owned by an unfamiliar Gmail account. They carry **no license and no stated terms**,
and they were never rewritten — they are the only skills in the repository that are not original work.
They are already merged to `main` via PR #1, and they sit in six departments: `ceo-advisor`,
@@ -132,7 +132,7 @@ They are already merged to `main` via PR #1, and they sit in six departments: `c
`prompt-optimizer`, `chief-content-officer`, `marketing-campaign-planner`, `newsletter-writer`,
`landing-page-cro-expert`, `youtube-producer`, `ux-product-auditor`.
-This matters because the whole point of D3 was to remove third-party licensed content. No licence is
+This matters because the whole point of D3 was to remove third-party licensed content. No license is
a *weaker* position than MIT, not a stronger one: MIT grants redistribution rights explicitly, while
absent terms grant nothing. If that folder is someone's paid product, the repository currently
redistributes it.
@@ -261,19 +261,19 @@ Public and likely to hold material: `a governance and compliance skill set`,
`evidence collection`, and `a workflow-automation script skill`.
- (a) Sweep them now and propose a `compliance` department.
-- **(b) Sweep and catalogue only** — report what is there, import nothing until D6 is settled. ←
+- **(b) Sweep and catalog only** — report what is there, import nothing until D6 is settled. ←
**recommended**
- (c) Defer entirely.
- (d) Also run the private/internal sweep via `docs/cross-org-sweep-prompt.md`.
-**Recommendation: (b).** The catalogue is cheap and informs D8 and D10. Importing anything before D6
+**Recommendation: (b).** The catalog is cheap and informs D8 and D10. Importing anything before D6
is resolved would repeat the exact mistake D3 and D4 were about — and these are forks of
third-party work, so the same licensing question applies to all of them.
-**Resolution: (d).** Catalogue the public repos from this session, and additionally start a separate
+**Resolution: (d).** Catalog the public repos from this session, and additionally start a separate
separate session to sweep private and internal repositories per `docs/cross-org-sweep-prompt.md`.
-**Constraint carried forward:** catalogue only. Nothing from either sweep is imported until its
+**Constraint carried forward:** catalog only. Nothing from either sweep is imported until its
licensing is established, since these are forks of third-party work and D3 and D6 both turned on
exactly that question.
@@ -389,7 +389,7 @@ of decisions.
| 5 | Mark PR #2 ready; squash-merge; delete the branch | D5, D15 | 6+ | ✅ done |
| 6 | Build `security` department + CISO charter, marked reviewer-class | D9, D10, D13 | — | ✅ done |
| 7 | Deepen `operations`, then `finance`, then `people` | D10 | — | |
-| 8 | Catalogue the other organizations' public repos — no import | D11 | — | |
+| 8 | Catalog the other organizations' public repos — no import | D11 | — | |
| 9 | Start a separate session for the private sweep | D11 | — | |
| 10 | Build the vertical generator: core, per-vertical config, one-way emit | D8 | — | |
| 11 | Revisit repo visibility | D16 | after 1 | ✅ done |
@@ -406,10 +406,10 @@ asked.
## D17. Which department is the next real gap — ✅ Resolved
-With `security` built, the catalogue covers eleven departments. Three functions a Fortune 500 has
+With `security` built, the catalog covers eleven departments. Three functions a Fortune 500 has
that this does not:
-- **(a) Customer Experience / Support.** Every business has support; the catalogue has none.
+- **(a) Customer Experience / Support.** Every business has support; the catalog has none.
`revenue:retention` is the only adjacent skill. Needed: support operations, escalation handling,
voice-of-customer, service-level design. ← **recommended**
- (b) **Data & Analytics (CDO).** `demand-generation:marketing-analytics` covers marketing
@@ -419,7 +419,7 @@ that this does not:
- (d) None — deepen the eleven that exist instead.
**Recommendation: (a), then (b).** Support is the most conspicuous absence to anyone reading the
-catalogue — it is the department every company has and this one does not. Data & Analytics is the
+catalog — it is the department every company has and this one does not. Data & Analytics is the
one most likely to be expected of a modern org chart. Corp Dev is real but only bites at a scale
this repo's likely users have not reached.
@@ -523,7 +523,7 @@ for inbound contributions.
- **(a) MIT.** ← **chosen**
- (b) Apache-2.0.
-- (c) A content licence such as CC-BY-4.0.
+- (c) A content license such as CC-BY-4.0.
- (d) Dual — CC-BY for the prose, MIT for the scripts.
**Resolution: (a).** The reasoning, recorded so it is not re-litigated:
@@ -536,15 +536,15 @@ for inbound contributions.
lets them, Apache asks them to annotate every file they touch.
- **MIT is the ecosystem norm.** Every collection this repository originally drew from was MIT, and
the Claude skills and plugins ecosystem is MIT by convention. Lower friction, fewer legal reviews.
-- **Short licences get complied with.** Two hundred lines of licence on a prose repository invites
+- **Short licenses get complied with.** Two hundred lines of license on a prose repository invites
the question of whether anyone read it.
- **(c) and (d) rejected:** Creative Commons explicitly advises against using CC for software, this
- repository contains executable scripts alongside the prose, and a split licence confuses tooling
+ repository contains executable scripts alongside the prose, and a split license confuses tooling
and adopters for no practical gain.
-**The one real gap MIT leaves** — what licence inbound contributions carry — is closed by
+**The one real gap MIT leaves** — what license inbound contributions carry — is closed by
`CONTRIBUTING.md` stating that contributions are accepted under MIT, rather than by changing the
-licence.
+license.
**Timing note, which is the part that matters later.** Relicensing is clean only while there is a
single copyright holder. Once outside contributions land under MIT, you cannot retroactively un-MIT
@@ -627,13 +627,13 @@ add after an incident rather than before one.
**Presentation — done in this change.**
-The README now opens with a centred title, the tagline, and a badge row: built-for Claude Code,
-department count, skill count, licence, and PRs-welcome. **The counts are generated from the same
+The README now opens with a centered title, the tagline, and a badge row: built-for Claude Code,
+department count, skill count, license, and PRs-welcome. **The counts are generated from the same
tree walk that builds the tables**, so they are covered by the existing staleness check — a badge
claiming the wrong number fails CI. A hand-typed badge would have become a lie on the next
department, which is precisely the D19 failure in a more visible place.
-**`.gitattributes` added.** GitHub labelled the repository *JavaScript* on the strength of a single
+**`.gitattributes` added.** GitHub labeled the repository *JavaScript* on the strength of a single
`.mjs` guard script, against 101 markdown skills that are the actual product. Linguist counts bytes
of code and does not know what a repository is for. The attributes file marks tooling as vendored
and generated documents as generated, so the language bar reflects the deliverable.
@@ -692,7 +692,7 @@ not zero.
A funding ask is a claim that ongoing maintenance has value to someone; that claim is currently
unevidenced, and a reader can tell.
- **It changes how the first impression reads.** A brand-new repository leading with a payment link
- invites the question of whether the catalogue was assembled to be monetised. That is a costly
+ invites the question of whether the catalog was assembled to be monetised. That is a costly
question to raise while the provenance story — 101 skills written from scratch after removing
every vendored collection — is the thing worth the reader's attention.
- **It is thirty seconds whenever you want it.** Enrol at `github.com/sponsors`, then a two-line
@@ -720,7 +720,7 @@ GitHub's About panel has a Website field. The available domains were `headcount.
- **`.biz` and `.info` are negative signals to this audience.** They are the TLDs of parked
pages and expired-domain farms. Someone deciding whether to install 101 skills into their
- agent is making a trust judgement, and that domain in the About field reads worse than a blank
+ agent is making a trust judgment, and that domain in the About field reads worse than a blank
field. A rare case where the cheap option is worse than nothing rather than merely weaker.
- **A domain does not serve this product yet.** Installation is `/plugin marketplace add
cbrock84/headcount`, typed inside Claude Code. Discovery runs through repository topics, the
@@ -769,7 +769,7 @@ discipline belongs in silos inside each department or as an enterprise function.
at this moment specifically: the repository published today with no external installs, so the
address is still free
to change. Once someone has the department installed and the address referenced, it is not — the same
-timing logic as the rename in D22 and the licence in D21. Verified no reference to the old address
+timing logic as the rename in D22 and the license in D21. Verified no reference to the old address
survives anywhere in the tree.
**Reporting line: the COO**, reflected in the org chart. The EPMO governs delivery across the
@@ -784,13 +784,13 @@ operational throughput; `pmo:dependency-and-risk-management` handles delivery ri
## D27. Splitting CIO-side IT operations out of `technology` — ✅ Resolved
-`technology` was labelled "CTO / CIO" and held twelve skills, all of them software development
+`technology` was labeled "CTO / CIO" and held twelve skills, all of them software development
workflow. The request to add help desk, network administration and system administration forced the
question of whether those belong in the same department.
- (a) **Add them to `technology`.** One department, around twenty-five skills.
- **(b) Split: `technology` for the CTO side, a new `it-operations` for the CIO side.** ← **chosen**
-- (c) Leave corporate IT out of the catalogue.
+- (c) Leave corporate IT out of the catalog.
**Resolution: (b).**
@@ -799,7 +799,7 @@ question of whether those belong in the same department.
team installing `technology` receives deskside support skills it will never open, and an IT
director receives worktree workflow they will never open. The split is what makes both installable
without noise.
-- **The combined "CTO / CIO" label was papering over a real division**, and the catalogue was
+- **The combined "CTO / CIO" label was papering over a real division**, and the catalog was
honest about only one half of it.
**What moved where.** `technology` gained `solution-architecture`, `api-design`,
@@ -823,3 +823,84 @@ earlier consolidation:
**Also fixed here.** Every agent charter carried a hardcoded skill count — `finance` claimed four
while holding nine. The count added nothing and rotted silently, so it was removed rather than
updated to a number that would rot again.
+
+---
+
+## D28. US English as house style — ✅ Resolved
+
+The catalog had drifted into British spelling across 178 occurrences in 49 files — the British
+forms of *license*, *program*, *catalog*, *behavior*, *prioritize* and *center*, among others. The
+author is in Georgia and writes in US English, so the repository was not speaking in his voice.
+
+- (a) **Fix the current occurrences.** A one-time rewrite.
+- **(b) Fix them and enforce it.** ← **chosen**
+- (c) Accept mixed spelling as unimportant.
+
+**Resolution: (b).** The one-time fix is the smaller half. Spelling drift is invisible to review and
+returns with the next contribution, and a repository of original work reading as though it came from
+somewhere else is precisely the wrong impression. `scripts/check-us-english.py` fails the build on
+British spellings and rewrites them under `--fix`; it is the ninth check.
+
+**Exact word forms, never stems.** This is the trap the check is built around: *analysis*,
+*analyst*, *specialist* and *realistic* are all correct US English already. A rewrite keyed on the
+stems those words share with their British-spelled cousins would have mangled all four across the
+catalog. The pairs list holds exact forms only, and those four words were confirmed unflagged before
+the rewrite was run.
+
+**`LICENSE` is never rewritten.** It carries the canonical MIT text, which is not ours to edit.
+
+**It exposed a latent bug rather than creating one.** Converting `CONTRIBUTING.md` to the US
+spelling of *license* immediately failed `check-provenance.py`, whose `\bMIT License\b` marker had
+never matched the British form. The provenance check had been passing that file **by accident** —
+anyone
+writing it the American way would have failed the build, for a reason that would have been
+baffling.
+
+Fixed with a deliberately narrow waiver: the `MIT License` marker alone is waived, in
+`CONTRIBUTING.md` and `README.md` alone, because naming our own license in our own documentation is
+expected. Every other marker still applies to those files, verified by planting a third-party
+copyright notice in one and Apache text in the other — both still caught.
+
+**The naming consequence.** The PMO department's display title becomes *Program Management Office*.
+The slug `pmo` and the skill addresses are unaffected, so nothing anyone could have installed
+changes.
+
+---
+
+## D29. Publishing the org chart so the README can link to it — 🔵 Open (needs your hands)
+
+The README now leads with a screenshot of the org chart. The screenshot is honest but static; the
+value is in the live page, and **GitHub does not render HTML from a repository** — a link to
+`docs/org-chart.html` shows a reader the source, not the chart.
+
+- **(a) GitHub Pages, serving `/docs` from `main`.** ← **recommended**
+- (b) A third-party HTML preview proxy.
+- (c) Screenshot only, no link.
+- (d) A hosted site on a purchased domain.
+
+**Recommendation: (a).** Free on public repositories, one setting, and it republishes on every push
+— so the live chart tracks the generator with no extra step. The URL becomes
+`https://cbrock84.github.io/headcount/org-chart.html`, which is what the README already points at.
+
+- **(b) rejected.** Depends on someone else's service staying up, and the URL is unpresentable.
+- **(c) rejected** as the default, though it is what you get until (a) is enabled: the screenshot is
+ the flair, the live page is the substance.
+- **(d) is D25 revisited and still premature** — Pages costs nothing and needs no domain.
+
+**Two consequences worth knowing before enabling it.**
+
+1. Pages serves everything in `/docs`, so the decision log and use cases become browsable as raw
+ files. The repository is already public, so nothing is newly exposed; it is only more visible.
+2. `docs/index.html` redirects the site root to the chart, so
+ `https://cbrock84.github.io/headcount` works rather than presenting a directory listing.
+
+**This also reopens the Website field from D25**, which was left empty for want of anything worth
+pointing at. A live, self-updating org chart is exactly that, at no cost and with none of the
+credibility risk of a degraded TLD. If Pages is enabled, the Website field should be set to the
+Pages URL. D25's reasoning about domains is unchanged: still not worth buying one.
+
+**Until enabled**, the README's two links to the Pages URL are dead. That is the one cost of
+shipping this before the setting is flipped, and it is a single line to revert if you would rather
+not publish a site.
+
+**To enable:** Settings → Pages → Source: *Deploy from a branch* → Branch: `main`, folder `/docs`.
diff --git a/docs/USE-CASES.md b/docs/USE-CASES.md
index 352ee48..4586b51 100644
--- a/docs/USE-CASES.md
+++ b/docs/USE-CASES.md
@@ -3,7 +3,7 @@
A collection of skills answers a question. An organization answers a *situation* — several
functions engaging in order, with someone able to say no.
-These are the situations this catalogue is shaped around. Every skill named here exists; a check
+These are the situations this catalog is shaped around. Every skill named here exists; a check
in CI fails if a reference stops resolving, so this page cannot rot as skills are renamed or
consolidated.
@@ -70,7 +70,7 @@ Everyone has an opinion and nobody has the number.
5. `security:threat-modeling` — before it is built, while changing the design is still cheap
6. `technology:implementation-planning` — what it actually takes
-**Where it stops.** Threat modelling after the build is archaeology. It sits at step five
+**Where it stops.** Threat modeling after the build is archaeology. It sits at step five
deliberately.
### Growth has stalled
diff --git a/docs/assets/org-chart-dark.png b/docs/assets/org-chart-dark.png
new file mode 100644
index 0000000..d5ac19d
Binary files /dev/null and b/docs/assets/org-chart-dark.png differ
diff --git a/docs/assets/org-chart-light.png b/docs/assets/org-chart-light.png
new file mode 100644
index 0000000..12a76b2
Binary files /dev/null and b/docs/assets/org-chart-light.png differ
diff --git a/docs/index.html b/docs/index.html
new file mode 100644
index 0000000..d69f87a
--- /dev/null
+++ b/docs/index.html
@@ -0,0 +1,10 @@
+<!-- GitHub Pages entry point. The org chart is the thing worth landing on, so the site root
+ goes there rather than presenting a directory of markdown files. -->
+<meta charset="utf-8">
+<title>headcount</title>
+<meta http-equiv="refresh" content="0; url=./org-chart.html">
+<link rel="canonical" href="./org-chart.html">
+<body style="margin:0;background:#0B0E14;color:#E6EDF3;
+ font-family:system-ui,sans-serif;padding:48px">
+ <p>Redirecting to <a href="./org-chart.html" style="color:#D97757">the org chart</a>.</p>
+</body>
diff --git a/docs/org-chart.html b/docs/org-chart.html
index b646ee8..06d04f0 100644
--- a/docs/org-chart.html
+++ b/docs/org-chart.html
@@ -248,7 +248,7 @@
</div>
<script>
-const DEPTS = [{"slug": "executive", "title": "Office of the CEO", "exec": "Chief Executive", "reviewer": false, "skills": [{"name": "agent-hierarchy", "summary": "Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independ…", "trigger": "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.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/executive/skills/agent-hierarchy/SKILL.md"}, {"name": "ai-research-analyst", "summary": "Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with th…", "trigger": "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.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/executive/skills/ai-research-analyst/SKILL.md"}, {"name": "business-growth-consultant", "summary": "Finds the single constraint currently limiting a business's growth and the highest-leverage moves against it, rather than producing a list of everyth…", "trigger": "Finds the single constraint currently limiting a business's growth and the highest-leverage moves against it, rather than producing a list of everything that could be improved. Use this when growth has stalled or slowed, when deciding where to spend limited time or budget, when revenue rises but profit does not, when prioritizing growth initiatives, or when a business feels busy without compounding.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/executive/skills/business-growth-consultant/SKILL.md"}, {"name": "ceo-advisor", "summary": "Pressure-tests a decision, plan, or idea before it is committed to — surfacing the assumption it rests on, the case against it, and what would have t…", "trigger": "Pressure-tests a decision, plan, or idea before it is committed to — surfacing the assumption it rests on, the case against it, and what would have to be true for it to work. Use this when weighing options, when a plan needs challenging before commitment, when you have already decided and want a genuine gut check, when processing meeting notes into decisions, or when competing initiatives need ranking. Distinct from `chief-executive`, which owns direction; this one interrogates a specific decision.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/executive/skills/ceo-advisor/SKILL.md"}, {"name": "chief-executive", "summary": "Sets direction, allocates capital and attention, and makes the calls no one else can make", "trigger": "Sets direction, allocates capital and attention, and makes the calls no one else can make. Use this when a decision spans more than one function, when priorities conflict and something must be cut, when a plan needs pressure-testing before commitment, or when the question is what the organization should do rather than how to do it. Also use to route a request to the right executive when it is unclear who owns it.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/executive/skills/chief-executive/SKILL.md"}, {"name": "saas-idea-validator", "summary": "Evaluates a software or startup idea against problem, market, competition, monetization, defensibility, and execution, and returns a verdict rather t…", "trigger": "Evaluates a software or startup idea against problem, market, competition, monetization, defensibility, and execution, and returns a verdict rather than encouragement. Use this when an idea needs pressure-testing before anyone builds, when deciding whether something is worth pursuing, when assessing competition or willingness to pay, or when a validated idea needs a first-customers and MVP plan. Default to scrutiny; the useful answer is usually the unwelcome one.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/executive/skills/saas-idea-validator/SKILL.md"}]}, {"slug": "technology", "title": "Technology", "exec": "CTO / CIO", "reviewer": false, "skills": [{"name": "ai-workflow-architect", "summary": "Designs AI systems, automations, and agent workflows for a business — identifying which manual work is worth automating, how to structure the system,…", "trigger": "Designs AI systems, automations, and agent workflows for a business — identifying which manual work is worth automating, how to structure the system, which tools fit, and what could go wrong. Use this to automate part of an operation, design an agent or MCP workflow, reduce repetitive manual work, connect tools into a system, decide which automation to build first, or audit an automation that is not delivering.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/ai-workflow-architect/SKILL.md"}, {"name": "api-design", "summary": "Designs interfaces that survive their consumers — resource modelling, errors, versioning, pagination, and compatibility", "trigger": "Designs interfaces that survive their consumers — resource modelling, errors, versioning, pagination, and compatibility. Use this to design a new API, review one before it ships, decide how to version or deprecate, fix an interface consumers keep misusing, or work out whether a change is breaking.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/api-design/SKILL.md"}, {"name": "branch-and-worktree-workflow", "summary": "Isolates feature work in its own branch or worktree and integrates it cleanly when done", "trigger": "Isolates feature work in its own branch or worktree and integrates it cleanly when done. Use this when starting work that should not disturb the current workspace, when several efforts must proceed in parallel on one repository, or when implementation is finished and the change needs merging, rebasing, or splitting for review.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/branch-and-worktree-workflow/SKILL.md"}, {"name": "chief-technology-officer", "summary": "Owns architecture, engineering delivery, infrastructure, data platform, and internal systems", "trigger": "Owns architecture, engineering delivery, infrastructure, data platform, and internal systems. Use this for build-versus-buy calls, technology selection, architectural direction, engineering capacity and delivery risk, technical debt tradeoffs, platform and tooling decisions, or when a technical choice has business consequences that need stating in business terms. Also use to judge whether a technical plan is sound before it is committed to.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/chief-technology-officer/SKILL.md"}, {"name": "cloud-infrastructure", "summary": "Designs and runs cloud infrastructure — environments, infrastructure as code, networking and isolation, scaling, and cost", "trigger": "Designs and runs cloud infrastructure — environments, infrastructure as code, networking and isolation, scaling, and cost. Use this to design a cloud environment, control infrastructure spend, set up environment separation, plan for scale or region failure, or review infrastructure someone configured by hand.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/cloud-infrastructure/SKILL.md"}, {"name": "code-review", "summary": "Conducts and responds to code review — reviewing a change for correctness, design, and risk, and evaluating review feedback received on your own work", "trigger": "Conducts and responds to code review — reviewing a change for correctness, design, and risk, and evaluating review feedback received on your own work. Use this before merging, when asked to review a diff or pull request, when review feedback has arrived and needs acting on, or when feedback seems wrong and needs a reasoned response rather than compliance.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/code-review/SKILL.md"}, {"name": "completion-verification", "summary": "Verifies that work is actually complete before it is claimed to be — running the checks, reading the output, and confirming the original request was…", "trigger": "Verifies that work is actually complete before it is claimed to be — running the checks, reading the output, and confirming the original request was satisfied rather than approximated. Use this before saying something is done, fixed, or passing; before committing or opening a pull request; and whenever a claim of success has not been backed by command output.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/completion-verification/SKILL.md"}, {"name": "implementation-planning", "summary": "Turns a spec or requirement into a written plan a separate session or agent can execute, then drives that plan through review checkpoints", "trigger": "Turns a spec or requirement into a written plan a separate session or agent can execute, then drives that plan through review checkpoints. Use this before touching code on any multi-step task, when work needs handing to someone else, when a task keeps sprawling mid-implementation, or when a plan exists and needs executing in order with verification between steps.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/implementation-planning/SKILL.md"}, {"name": "observability-and-reliability", "summary": "Makes systems debuggable and reliably operable — instrumentation, alerting that is worth waking for, service objectives, and learning from failure", "trigger": "Makes systems debuggable and reliably operable — instrumentation, alerting that is worth waking for, service objectives, and learning from failure. Use this to instrument a service, fix alerting that is ignored, set error budgets or reliability targets, prepare for on-call, or run a blameless post-incident review.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/observability-and-reliability/SKILL.md"}, {"name": "parallel-agent-delivery", "summary": "Splits work across multiple agents or sessions running at once, keeping their surfaces disjoint so results merge cleanly", "trigger": "Splits work across multiple agents or sessions running at once, keeping their surfaces disjoint so results merge cleanly. Use this when facing several independent tasks with no shared state, when a plan has parallelizable steps, when a broad search or audit would be faster fanned out, or when deciding whether work can safely be split at all.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/parallel-agent-delivery/SKILL.md"}, {"name": "prompt-optimizer", "summary": "Turns rough intent or a weak prompt into a reliable one — diagnosing why output is inconsistent, restructuring the instruction, and adapting it acros…", "trigger": "Turns rough intent or a weak prompt into a reliable one — diagnosing why output is inconsistent, restructuring the instruction, and adapting it across models. Use this when a prompt is not producing what was wanted, when output varies run to run, when writing a prompt for a repeated task, when moving a prompt between models, or when someone describes what they want an AI to do and needs it written properly.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/prompt-optimizer/SKILL.md"}, {"name": "release-and-deployment", "summary": "Ships changes safely and often — pipelines, deployment strategies, feature flags, rollback, and database changes", "trigger": "Ships changes safely and often — pipelines, deployment strategies, feature flags, rollback, and database changes. Use this to design a deployment pipeline, reduce release risk, roll out a risky change gradually, plan a schema migration, or work out why releases are infrequent and frightening.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/release-and-deployment/SKILL.md"}, {"name": "skill-authoring", "summary": "Writes and revises agent skills so they trigger at the right moments and give usable instruction when they do", "trigger": "Writes and revises agent skills so they trigger at the right moments and give usable instruction when they do. Use this when creating a new skill, editing an existing one, diagnosing a skill that fires too often or never fires, or reviewing a set of skills for overlap. Also use before adding to a skill library, to check the capability is not already covered.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/skill-authoring/SKILL.md"}, {"name": "solution-architecture", "summary": "Designs system structure and makes architectural decisions defensible — boundaries, coupling, trade-offs, and recording why", "trigger": "Designs system structure and makes architectural decisions defensible — boundaries, coupling, trade-offs, and recording why. Use this to design a new system or major component, choose between architectural options, review an existing design, decide where a boundary belongs, or document an architectural decision so it survives the people who made it.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/solution-architecture/SKILL.md"}, {"name": "solution-exploration", "summary": "Explores the problem and the range of possible approaches before any code is written — clarifying what is actually being asked, surfacing options wit…", "trigger": "Explores the problem and the range of possible approaches before any code is written — clarifying what is actually being asked, surfacing options with their tradeoffs, and converging on one. Use this at the start of any feature, component, or behavior change, when a request is ambiguous, when the first idea is the only idea on the table, or when a design decision needs pressure-testing before commitment.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/solution-exploration/SKILL.md"}, {"name": "systematic-debugging", "summary": "Finds the root cause of a bug, test failure, or unexpected behavior before proposing any fix", "trigger": "Finds the root cause of a bug, test failure, or unexpected behavior before proposing any fix. Use this whenever something is broken and the cause is not yet proven — a failing test, a production error, intermittent behavior, or a symptom that appeared after a change. Also use when a fix has been attempted and did not work, or when the same bug keeps coming back.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/systematic-debugging/SKILL.md"}, {"name": "technical-debt-management", "summary": "Makes technical debt visible and decidable — distinguishing real debt from mess, quantifying its cost, and arguing for remediation in business terms", "trigger": "Makes technical debt visible and decidable — distinguishing real debt from mess, quantifying its cost, and arguing for remediation in business terms. Use this to assess and prioritise debt, decide whether to fix or live with something, justify remediation work to non-engineers, or plan a migration off a system nobody wants to touch.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/technical-debt-management/SKILL.md"}, {"name": "test-driven-development", "summary": "Drives implementation by writing a failing test first, then the smallest code that passes it", "trigger": "Drives implementation by writing a failing test first, then the smallest code that passes it. Use this before writing implementation code for any feature or bugfix, when a bug needs a regression test, when existing code is hard to change safely, or when someone asks whether a change is covered. Also use to decide what is worth testing and what is not.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/test-driven-development/SKILL.md"}]}, {"slug": "security", "title": "Security", "exec": "CISO", "reviewer": true, "skills": [{"name": "access-and-identity", "summary": "Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process", "trigger": "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.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/security/skills/access-and-identity/SKILL.md"}, {"name": "chief-information-security-officer", "summary": "Owns the security posture of the organization — architecture, program strategy, risk acceptance, incident command, and the authority to stop work tha…", "trigger": "Owns the security posture of the organization — architecture, program strategy, risk acceptance, incident command, and the authority to stop work that creates unacceptable exposure. Use this for a security strategy or program decision, when a technical choice creates security risk that needs a verdict, when deciding whether to accept or block a risk, when standing up a security function, or when security and delivery priorities conflict and someone has to decide.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/security/skills/chief-information-security-officer/SKILL.md"}, {"name": "incident-response", "summary": "Runs a security incident from detection to closure — triage, containment, investigation, communication, and the review afterward", "trigger": "Runs a security incident from detection to closure — triage, containment, investigation, communication, and the review afterward. Use this when a compromise is suspected or confirmed, when preparing an incident response plan or running an exercise, when deciding whether something is an incident, or when a breach may trigger notification obligations.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/security/skills/incident-response/SKILL.md"}, {"name": "security-architecture-review", "summary": "Reviews a design or change for security before it ships — authentication and authorization, data handling, secrets, dependencies, and the secure-deve…", "trigger": "Reviews a design or change for security before it ships — authentication and authorization, data handling, secrets, dependencies, and the secure-development practices around it. Use this to review an architecture or pull request for security, set secure coding standards, choose or tune SAST and DAST tooling, assess a third-party integration, or decide whether a design is safe to build.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/security/skills/security-architecture-review/SKILL.md"}, {"name": "threat-modeling", "summary": "Identifies what could go wrong in a system before it is built or changed — the assets worth attacking, the entry points, the trust boundaries, and th…", "trigger": "Identifies what could go wrong in a system before it is built or changed — the assets worth attacking, the entry points, the trust boundaries, and the controls that actually address the realistic threats. Use this when designing a feature or system, when a change touches authentication, data handling, payments, or external input, before a security review, or when deciding which security work is worth doing at all.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/security/skills/threat-modeling/SKILL.md"}, {"name": "vulnerability-management", "summary": "Runs the loop from discovering a weakness to confirming it is fixed — scanning, triage, prioritization by real exploitability, remediation tracking,…", "trigger": "Runs the loop from discovering a weakness to confirming it is fixed — scanning, triage, prioritization by real exploitability, remediation tracking, and patch policy. Use this to stand up or fix a vulnerability program, triage scanner output, decide what to fix first, set patch SLAs, handle a disclosure from an outside researcher, or report posture to leadership.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/security/skills/vulnerability-management/SKILL.md"}]}, {"slug": "it-operations", "title": "IT Operations", "exec": "CIO", "reviewer": false, "skills": [{"name": "backup-and-recovery", "summary": "Protects and restores data — backup coverage and scope, retention, immutability against ransomware, and proving restores actually work", "trigger": "Protects and restores data — backup coverage and scope, retention, immutability against ransomware, and proving restores actually work. Use this to design a backup regime, verify restores, plan retention, protect backups from ransomware, or recover from data loss.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/it-operations/skills/backup-and-recovery/SKILL.md"}, {"name": "endpoint-management", "summary": "Manages laptops, desktops and mobile devices — enrolment, configuration, patching, software distribution, and lost or compromised devices", "trigger": "Manages laptops, desktops and mobile devices — enrolment, configuration, patching, software distribution, and lost or compromised devices. Use this to set up device management, standardise builds, roll out software or an OS upgrade, handle a lost device, or bring an unmanaged fleet under control.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/it-operations/skills/endpoint-management/SKILL.md"}, {"name": "identity-lifecycle-administration", "summary": "Executes joiner, mover and leaver processes — provisioning, group membership, access changes on role change, and complete deprovisioning", "trigger": "Executes joiner, mover and leaver processes — provisioning, group membership, access changes on role change, and complete deprovisioning. Use this to set up or fix joiner-mover-leaver, deprovision someone completely, clean up accumulated access, audit group membership, or find accounts that outlived their owners.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/it-operations/skills/identity-lifecycle-administration/SKILL.md"}, {"name": "it-asset-management", "summary": "Tracks hardware and software assets through their life — procurement, ownership, licensing, refresh, and disposal", "trigger": "Tracks hardware and software assets through their life — procurement, ownership, licensing, refresh, and disposal. Use this to build an asset register, prepare for a software audit, plan a refresh cycle, control licence spend, or dispose of equipment safely.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/it-operations/skills/it-asset-management/SKILL.md"}, {"name": "network-administration", "summary": "Designs and operates the corporate network — segmentation, remote access, wireless, DNS and addressing, and diagnosing network problems", "trigger": "Designs and operates the corporate network — segmentation, remote access, wireless, DNS and addressing, and diagnosing network problems. Use this to segment a network, set up or fix remote access, diagnose intermittent connectivity, plan addressing or DNS, or assess whether the network's trust assumptions still hold.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/it-operations/skills/network-administration/SKILL.md"}, {"name": "service-desk", "summary": "Runs the IT service desk — intake, triage, prioritisation, escalation, knowledge, and the metrics that improve service rather than distort it", "trigger": "Runs the IT service desk — intake, triage, prioritisation, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets still frustrates everyone.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/it-operations/skills/service-desk/SKILL.md"}, {"name": "systems-administration", "summary": "Runs servers and corporate systems — patching, configuration baselines, change control, capacity, and the routine that prevents incidents", "trigger": "Runs servers and corporate systems — patching, configuration baselines, change control, capacity, and the routine that prevents incidents. Use this to establish a patching cadence, standardise server configuration, plan a maintenance window, decide change control for infrastructure, or clean up systems that have drifted from any known state.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/it-operations/skills/systems-administration/SKILL.md"}]}, {"slug": "product", "title": "Product", "exec": "CPO", "reviewer": false, "skills": [{"name": "brand-identity", "summary": "Defines and applies visual brand — logo usage, palette, typography, imagery direction, and the guidelines that keep expression consistent across prod…", "trigger": "Defines and applies visual brand — logo usage, palette, typography, imagery direction, and the guidelines that keep expression consistent across product and marketing surfaces. Use this to establish a brand from scratch, audit whether an existing brand is being applied consistently, build brand guidelines, or decide how a brand should express itself in an unfamiliar format.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/product/skills/brand-identity/SKILL.md"}, {"name": "chief-product-officer", "summary": "Owns what gets built and why: product strategy, roadmap, discovery, user experience, and the definition of success for each release", "trigger": "Owns what gets built and why: product strategy, roadmap, discovery, user experience, and the definition of success for each release. Use this to decide what to build next, to cut scope, to turn a business goal into a product bet, to judge whether a feature is worth its cost, or when engineering and go-to-market disagree about what a release is for. Also use for roadmap sequencing and for killing work that is not earning its place.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/product/skills/chief-product-officer/SKILL.md"}, {"name": "design-styles", "summary": "Applies a deliberate visual direction to an interface — minimalist editorial, industrial utilitarian, or high-polish commercial — each with its own t…", "trigger": "Applies a deliberate visual direction to an interface — minimalist editorial, industrial utilitarian, or high-polish commercial — each with its own type scale, palette behavior, surface treatment, and motion. Use this when a product needs a point of view rather than defaults, when choosing between visual directions, when an interface reads as generic, or when restyling something without changing its structure.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/product/skills/design-styles/SKILL.md"}, {"name": "design-system", "summary": "Builds and maintains the design system a product is assembled from — tokens for color, type, spacing and elevation, component contracts, and the rule…", "trigger": "Builds and maintains the design system a product is assembled from — tokens for color, type, spacing and elevation, component contracts, and the rules that keep them coherent as the product grows. Use this when starting a new interface, when screens have drifted apart visually, when the same component exists three times in slightly different forms, or when a token or component needs adding without breaking what exists.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/product/skills/design-system/SKILL.md"}, {"name": "interface-craft", "summary": "Raises the visual and interaction quality of an interface — layout, hierarchy, type, spacing, density, and the details that separate a considered pro…", "trigger": "Raises the visual and interaction quality of an interface — layout, hierarchy, type, spacing, density, and the details that separate a considered product from a generic one. Use this when a screen works but looks unfinished or default, when a layout feels crowded or arbitrary, when a page has no clear focal point, or when an interface needs to feel trustworthy rather than merely functional.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/product/skills/interface-craft/SKILL.md"}, {"name": "interface-redesign", "summary": "Upgrades an existing interface to a higher standard without rebuilding it — auditing what is there, identifying what reads as generic or unfinished,…", "trigger": "Upgrades an existing interface to a higher standard without rebuilding it — auditing what is there, identifying what reads as generic or unfinished, and sequencing changes by impact. Use this when a product works but looks dated or default, when a redesign is being considered, when deciding whether to restyle or rebuild, or when a screen needs to look substantially better with limited effort.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/product/skills/interface-redesign/SKILL.md"}, {"name": "presentation-design", "summary": "Designs slide decks, one-pagers, and marketing graphics that carry an argument rather than decorate one", "trigger": "Designs slide decks, one-pagers, and marketing graphics that carry an argument rather than decorate one. Use this to build or fix a pitch deck, board deck, or conference talk; to design a banner, social graphic, or one-pager; or when a deck is dense, unfocused, or being read aloud from the slides.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/product/skills/presentation-design/SKILL.md"}, {"name": "ux-product-auditor", "summary": "Audits a website, app, onboarding flow, or design for usability, conversion, and product problems, tying every finding to a business outcome and a se…", "trigger": "Audits a website, app, onboarding flow, or design for usability, conversion, and product problems, tying every finding to a business outcome and a severity. Use this to review an interface, diagnose low conversion or activation, find where users drop off, get structured product feedback, or decide which UX fixes to ship first. For raising visual quality rather than finding problems, use `interface-craft`.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/product/skills/ux-product-auditor/SKILL.md"}, {"name": "visual-reference-generation", "summary": "Produces design reference imagery before implementation — screen concepts, layout directions, and flows for web or mobile that make a verbal brief co…", "trigger": "Produces design reference imagery before implementation — screen concepts, layout directions, and flows for web or mobile that make a verbal brief concrete enough to argue with. Use this when a brief needs visualizing before anyone builds, when comparing layout directions, when handing a developer a target, or when stakeholders are describing different things with the same words.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/product/skills/visual-reference-generation/SKILL.md"}]}, {"slug": "marketing", "title": "Marketing", "exec": "CMO", "reviewer": false, "skills": [{"name": "behavioral-marketing", "summary": "Applies decision science and cognitive bias research to marketing and product decisions — how people actually choose under uncertainty, and how frami…", "trigger": "Applies decision science and cognitive bias research to marketing and product decisions — how people actually choose under uncertainty, and how framing, defaults, sequencing, and social context change behavior. Use this to diagnose why a well-argued offer is not converting, to structure choices and pricing presentation, to design an experience around how attention and memory work, or to pressure-test whether a persuasion tactic is legitimate or manipulative.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/behavioral-marketing/SKILL.md"}, {"name": "brand-voice", "summary": "Captures how a person or brand actually writes and turns it into reusable voice instructions every other content skill draws from", "trigger": "Captures how a person or brand actually writes and turns it into reusable voice instructions every other content skill draws from. Use this before drafting any content for a new brand or client, when output keeps coming back sounding generic, when several writers need to sound like one, or when a voice needs defining without existing samples to learn from.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/brand-voice/SKILL.md"}, {"name": "chief-content-officer", "summary": "Runs content as an operation — the production pipeline, editorial calendar, repurposing engine, competitive content intelligence, and audits of what…", "trigger": "Runs content as an operation — the production pipeline, editorial calendar, repurposing engine, competitive content intelligence, and audits of what already exists. Use this to build or fix a content production system, plan a calendar, decide how one piece becomes many, rank content ideas by expected impact, or audit an existing library for what to update, consolidate, or retire. For deciding what territory to own and why, use `content-strategy` first.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/chief-content-officer/SKILL.md"}, {"name": "chief-marketing-officer", "summary": "Owns brand, demand generation, content, communications, and how the market understands what the business does", "trigger": "Owns brand, demand generation, content, communications, and how the market understands what the business does. Use this to set marketing strategy, allocate budget across channels, decide positioning and messaging, judge whether a campaign is worth running, diagnose why demand has stalled, or arbitrate between brand-building and short-term acquisition. Also use to decide which marketing work to stop.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/chief-marketing-officer/SKILL.md"}, {"name": "content-strategy", "summary": "Decides what content to make and why — topic territory, format mix, cadence, and how content connects to a business outcome rather than to traffic", "trigger": "Decides what content to make and why — topic territory, format mix, cadence, and how content connects to a business outcome rather than to traffic. Use this to plan a content program, choose topics, build an editorial calendar, decide which formats and platforms to commit to, or diagnose why content is producing audience but not results.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/content-strategy/SKILL.md"}, {"name": "customer-research", "summary": "Plans, runs, and synthesizes customer research — interviews, surveys, win-loss analysis, and message testing — into findings that change decisions", "trigger": "Plans, runs, and synthesizes customer research — interviews, surveys, win-loss analysis, and message testing — into findings that change decisions. Use this when the customer is being guessed at, before positioning or a major launch, when churn or conversion has an unexplained cause, or when a team is arguing from anecdotes. Also use to turn raw interview notes into usable findings.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/customer-research/SKILL.md"}, {"name": "marketing-campaign-planner", "summary": "Designs a coordinated multi-channel campaign or product launch around one story — objective, message, channel sequencing, timeline, assets, and the c…", "trigger": "Designs a coordinated multi-channel campaign or product launch around one story — objective, message, channel sequencing, timeline, assets, and the checklist that gets it out the door. Use this to plan a launch or campaign, sequence a go-to-market push, pressure-test a campaign before committing budget, or turn a product change into a coordinated set of activity. For ongoing channel programs rather than a bounded push, use `marketing-planning`.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/marketing-campaign-planner/SKILL.md"}, {"name": "marketing-copywriting", "summary": "Writes and edits marketing copy for any surface — homepage, product and pricing pages, ads, emails, and collateral — and sharpens existing copy that…", "trigger": "Writes and edits marketing copy for any surface — homepage, product and pricing pages, ads, emails, and collateral — and sharpens existing copy that is not working. Use this to write or rewrite page copy, tighten a draft, fix copy that is vague or feature-led, adapt one message across formats, or review copy before it ships.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/marketing-copywriting/SKILL.md"}, {"name": "marketing-planning", "summary": "Builds the marketing plan of record — objectives, channel mix, budget allocation, sequencing, and the measurement that says whether it worked", "trigger": "Builds the marketing plan of record — objectives, channel mix, budget allocation, sequencing, and the measurement that says whether it worked. Use this for annual or quarterly planning, when budget must be allocated or defended, when marketing activity feels busy but undirected, or when a plan needs pressure-testing before commitment.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/marketing-planning/SKILL.md"}, {"name": "newsletter-writer", "summary": "Writes and edits newsletters and marketing emails people actually open — subject lines, opening, structure, voice, and the conversion turn where ther…", "trigger": "Writes and edits newsletters and marketing emails people actually open — subject lines, opening, structure, voice, and the conversion turn where there is one. Use this to draft or rewrite a newsletter or email, sharpen weak email copy, plan a newsletter's structure and cadence, write a sequence, or repurpose an issue into other formats. For automated lifecycle and SMS programs, use `lifecycle-messaging`.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/newsletter-writer/SKILL.md"}, {"name": "partnership-marketing", "summary": "Builds reach through other people's audiences — co-marketing partnerships, creator and influencer programs, community building, and affiliate arrange…", "trigger": "Builds reach through other people's audiences — co-marketing partnerships, creator and influencer programs, community building, and affiliate arrangements. Use this to find and evaluate partners, structure a joint campaign or creator deal, plan a community strategy, or decide whether a partnership is worth the coordination cost.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/partnership-marketing/SKILL.md"}, {"name": "positioning-and-messaging", "summary": "Establishes what a product is understood to be, for whom, and instead of what — then turns that into the messaging every other surface inherits", "trigger": "Establishes what a product is understood to be, for whom, and instead of what — then turns that into the messaging every other surface inherits. Use this when messaging is inconsistent across channels, when prospects misunderstand what the product does, when entering a new segment, when competitors are being compared against you unfavorably, or before any campaign, launch, or site rewrite.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/positioning-and-messaging/SKILL.md"}, {"name": "public-relations", "summary": "Plans and executes earned media — press strategy, journalist outreach, announcements, commentary, and crisis response", "trigger": "Plans and executes earned media — press strategy, journalist outreach, announcements, commentary, and crisis response. Use this to plan a press push, write a pitch or release, find and approach the right journalists, prepare for an interview, decide whether something is newsworthy, or respond to a story going badly.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/public-relations/SKILL.md"}, {"name": "social-post-craft", "summary": "Writes, structures, and evaluates social posts end to end — hooks, body, formatting for how each platform renders, and a quality check before publish…", "trigger": "Writes, structures, and evaluates social posts end to end — hooks, body, formatting for how each platform renders, and a quality check before publishing. Use this to draft a post, rewrite one that underperformed, turn a longer piece into social content, sharpen an opening, or judge whether a draft is worth publishing.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/social-post-craft/SKILL.md"}, {"name": "video-content", "summary": "Plans and scripts short-form and long-form video, and designs the packaging — titles, thumbnails, and openings — that determines whether it gets watc…", "trigger": "Plans and scripts short-form and long-form video, and designs the packaging — titles, thumbnails, and openings — that determines whether it gets watched. Use this to script a video, plan a series, fix retention or click-through problems, design thumbnail and title concepts, or turn written content into video.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/video-content/SKILL.md"}, {"name": "visual-content", "summary": "Designs and directs the visual assets that carry content — carousels, infographics, quote graphics, diagrams, and social imagery — including the gene…", "trigger": "Designs and directs the visual assets that carry content — carousels, infographics, quote graphics, diagrams, and social imagery — including the generation prompts where they are AI-produced. Use this to turn a written piece into a visual format, design a carousel or infographic, create social graphics, or fix visuals that are not stopping the scroll.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/visual-content/SKILL.md"}, {"name": "youtube-producer", "summary": "Plans, packages, and scripts long-form video for retention and channel growth — idea selection, titles and thumbnails, script structure, and diagnosi…", "trigger": "Plans, packages, and scripts long-form video for retention and channel growth — idea selection, titles and thumbnails, script structure, and diagnosing why a video or channel underperforms. Use this for video ideas, packaging, scripting, a retention teardown, or channel strategy — including when someone describes a topic and wants it turned into something publishable. For short-form and cross-platform video, use `video-content`.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/youtube-producer/SKILL.md"}]}, {"slug": "demand-generation", "title": "Demand Generation", "exec": "CMO", "reviewer": false, "skills": [{"name": "ai-search-optimization", "summary": "Optimizes for AI assistants and AI-generated answers — being retrievable, being cited, and being represented accurately when a model answers on your…", "trigger": "Optimizes for AI assistants and AI-generated answers — being retrievable, being cited, and being represented accurately when a model answers on your behalf. Use this when traffic is shifting from links to AI answers, when a brand is misrepresented or absent in AI responses, when planning content for retrieval rather than ranking, or when deciding how AI search changes an existing SEO program.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/ai-search-optimization/SKILL.md"}, {"name": "app-store-optimization", "summary": "Improves visibility and conversion in the App Store and Google Play — metadata, keywords, screenshots, ratings, and the listing experience that turns…", "trigger": "Improves visibility and conversion in the App Store and Google Play — metadata, keywords, screenshots, ratings, and the listing experience that turns an impression into an install. Use this to audit or optimize an app listing, plan a launch listing, diagnose poor install conversion, or improve store search visibility.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/app-store-optimization/SKILL.md"}, {"name": "experimentation", "summary": "Designs, runs, and reads A/B tests and growth experiments — hypothesis, sample size, duration, and honest interpretation", "trigger": "Designs, runs, and reads A/B tests and growth experiments — hypothesis, sample size, duration, and honest interpretation. Use this to plan a test, judge whether a result is real, build an experimentation program, decide what to test next, or diagnose why tests keep producing inconclusive or non-replicating results.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/experimentation/SKILL.md"}, {"name": "landing-page-cro-expert", "summary": "Audits and rewrites landing pages, homepages, and sales pages to increase conversion — diagnosing why a page is not converting, rewriting headlines,…", "trigger": "Audits and rewrites landing pages, homepages, and sales pages to increase conversion — diagnosing why a page is not converting, rewriting headlines, hero copy and calls to action, and prioritizing which changes to test first. Use this when a page underperforms, when someone pastes a URL or screenshot asking what is wrong, when writing a new page, or when deciding which conversion changes are worth testing.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/landing-page-cro-expert/SKILL.md"}, {"name": "lead-capture", "summary": "Converts anonymous traffic into known contacts — lead magnets, gated content, free tools, popups, and the forms behind them", "trigger": "Converts anonymous traffic into known contacts — lead magnets, gated content, free tools, popups, and the forms behind them. Use this to design or improve a lead magnet, plan a free tool, add or fix popups and overlays, improve form conversion, or decide what is worth gating and what should stay open.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/lead-capture/SKILL.md"}, {"name": "lifecycle-messaging", "summary": "Designs automated email and SMS programs — welcome and onboarding sequences, nurture, re-engagement, transactional messaging, and the timing and segm…", "trigger": "Designs automated email and SMS programs — welcome and onboarding sequences, nurture, re-engagement, transactional messaging, and the timing and segmentation behind them. Use this to build or fix an email sequence, plan lifecycle automation, improve open or click performance, set up SMS flows, or decide what messages a customer should receive and when.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/lifecycle-messaging/SKILL.md"}, {"name": "listing-distribution", "summary": "Gets a product listed where buyers and crawlers look — directories, marketplaces, review sites, comparison pages, and aggregators", "trigger": "Gets a product listed where buyers and crawlers look — directories, marketplaces, review sites, comparison pages, and aggregators. Use this to plan a submission push, choose which directories are worth the effort, prepare listing assets, build comparison and alternative pages, or manage presence on review platforms.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/listing-distribution/SKILL.md"}, {"name": "marketing-analytics", "summary": "Sets up, audits, and reports on marketing measurement — tracking plans, event schemas, attribution models, and the dashboards built on them", "trigger": "Sets up, audits, and reports on marketing measurement — tracking plans, event schemas, attribution models, and the dashboards built on them. Use this to instrument a site or product, audit tracking nobody trusts, choose or interpret an attribution model, build reporting that answers a specific question, or reconcile numbers that disagree between tools.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/marketing-analytics/SKILL.md"}, {"name": "paid-advertising", "summary": "Plans, runs, and optimizes paid acquisition across search, social, and display — account structure, targeting, creative, bidding, budget, and the ana…", "trigger": "Plans, runs, and optimizes paid acquisition across search, social, and display — account structure, targeting, creative, bidding, budget, and the analysis that says whether to scale or stop. Use this to set up or restructure campaigns, write and iterate ad creative, diagnose rising costs or falling performance, decide budget allocation, or judge whether a channel is working.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/paid-advertising/SKILL.md"}, {"name": "programmatic-seo", "summary": "Builds large sets of search-targeted pages from a template and a dataset — the location, comparison, integration, and use-case pages that capture lon…", "trigger": "Builds large sets of search-targeted pages from a template and a dataset — the location, comparison, integration, and use-case pages that capture long-tail demand at scale. Use this when there is a repeating query pattern with real volume, when a dataset could answer many similar searches, or to judge whether a programmatic approach is viable before building it.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/programmatic-seo/SKILL.md"}, {"name": "seo-strategy", "summary": "Audits and improves organic search performance — technical health, site architecture, internal linking, structured data, and the content decisions th…", "trigger": "Audits and improves organic search performance — technical health, site architecture, internal linking, structured data, and the content decisions that determine what can rank. Use this to run an SEO audit, diagnose why pages are not ranking or were deindexed, plan a site's URL and navigation structure, add structured data, or prioritize which SEO fixes are worth doing.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/seo-strategy/SKILL.md"}]}, {"slug": "revenue", "title": "Revenue", "exec": "CRO", "reviewer": false, "skills": [{"name": "activation", "summary": "Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone bec…", "trigger": "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.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/revenue/skills/activation/SKILL.md"}, {"name": "chief-revenue-officer", "summary": "Owns the revenue engine end to end: sales, monetization, pricing, customer success, retention, and partnerships", "trigger": "Owns the revenue engine end to end: sales, monetization, pricing, customer success, retention, and partnerships. Use this for pricing and packaging decisions, sales strategy and coverage, forecast and pipeline health, churn and expansion, partner and channel strategy, or when marketing-sourced demand is not converting. Also use to decide which segments to pursue and which to decline.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/revenue/skills/chief-revenue-officer/SKILL.md"}, {"name": "outbound-prospecting", "summary": "Finds, qualifies, and reaches prospects through cold outreach — list building, qualification criteria, cold email and multi-channel sequences, and th…", "trigger": "Finds, qualifies, and reaches prospects through cold outreach — list building, qualification criteria, cold email and multi-channel sequences, and the follow-up that actually gets replies. Use this to build a prospect list, write cold outreach, fix a sequence that is not getting responses, define qualification criteria, or decide whether a segment is worth pursuing.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/revenue/skills/outbound-prospecting/SKILL.md"}, {"name": "pricing-and-packaging", "summary": "Sets price, structures packages and tiers, and designs the monetization surfaces that carry them — upgrade paths, paywalls, and offer construction", "trigger": "Sets price, structures packages and tiers, and designs the monetization surfaces that carry them — upgrade paths, paywalls, and offer construction. Use this to set or change pricing, design or restructure tiers, choose a pricing metric, build an offer, design upgrade prompts and paywalls, or evaluate whether a pricing change is safe to make.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/revenue/skills/pricing-and-packaging/SKILL.md"}, {"name": "referral-programs", "summary": "Designs and improves referral, affiliate, and word-of-mouth programs — incentive structure, mechanics, timing, and fraud control", "trigger": "Designs and improves referral, affiliate, and word-of-mouth programs — incentive structure, mechanics, timing, and fraud control. Use this to build a referral or affiliate program, diagnose one that is not producing, decide what incentive to offer, or judge whether referral is a realistic channel for a product.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/revenue/skills/referral-programs/SKILL.md"}, {"name": "retention", "summary": "Diagnoses and reduces churn — cancellation flows, save offers, failed-payment recovery, at-risk detection, and the product and service causes underne…", "trigger": "Diagnoses and reduces churn — cancellation flows, save offers, failed-payment recovery, at-risk detection, and the product and service causes underneath. Use this when churn is rising or unexplained, to design a cancellation or win-back flow, to recover involuntary churn, to identify at-risk accounts before they leave, or to decide whether a retention problem is a product problem.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/revenue/skills/retention/SKILL.md"}, {"name": "revenue-operations", "summary": "Runs the mechanics of the revenue engine — lead lifecycle definitions, routing, CRM hygiene, forecasting process, pipeline reporting, and the marketi…", "trigger": "Runs the mechanics of the revenue engine — lead lifecycle definitions, routing, CRM hygiene, forecasting process, pipeline reporting, and the marketing-to-sales handoff. Use this to fix a broken handoff, define lifecycle stages, improve forecast accuracy, clean up CRM data, design territory or routing rules, or diagnose why pipeline numbers are not trusted.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/revenue/skills/revenue-operations/SKILL.md"}, {"name": "sales-enablement", "summary": "Builds what a sales team needs to sell — pitch decks, one-pagers, objection handling, competitive battlecards, demo scripts, and case studies", "trigger": "Builds what a sales team needs to sell — pitch decks, one-pagers, objection handling, competitive battlecards, demo scripts, and case studies. Use this to create or fix sales collateral, prepare for a competitive deal, build a demo flow, document objection responses, or diagnose why a pitch is not converting.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/revenue/skills/sales-enablement/SKILL.md"}]}, {"slug": "finance", "title": "Finance", "exec": "CFO", "reviewer": false, "skills": [{"name": "budgeting-and-forecasting", "summary": "Runs the planning cycle — annual budget, rolling forecast, consolidation of business unit inputs, and the variance analysis that explains actuals aga…", "trigger": "Runs the planning cycle — annual budget, rolling forecast, consolidation of business unit inputs, and the variance analysis that explains actuals against plan. Use this to build or challenge a budget, run a forecast cycle, consolidate departmental submissions, explain why results diverged from plan, or improve forecast accuracy.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/budgeting-and-forecasting/SKILL.md"}, {"name": "capital-allocation", "summary": "Evaluates where to spend limited capital — investment appraisal, hurdle rates, payback, and comparing proposals that are not alike", "trigger": "Evaluates where to spend limited capital — investment appraisal, hurdle rates, payback, and comparing proposals that are not alike. Use this to evaluate an investment or major purchase, compare competing funding requests, set a hurdle rate, decide between building and buying, or review whether past investments delivered what was claimed.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/capital-allocation/SKILL.md"}, {"name": "chief-financial-officer", "summary": "Owns the financial position: planning, budgeting, forecasting, unit economics, cash, and the numbers the business is run and reported on", "trigger": "Owns the financial position: planning, budgeting, forecasting, unit economics, cash, and the numbers the business is run and reported on. Use this to build or challenge a budget, model a decision's financial consequence, assess unit economics or runway, evaluate an investment or spend request, set financial controls, or when a plan's numbers do not reconcile. Also use to decide whether the business can afford something.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/chief-financial-officer/SKILL.md"}, {"name": "financial-modeling", "summary": "Builds and stress-tests financial models for forecasting, scenario planning, and decision support — revenue build, cost structure, driver logic, and…", "trigger": "Builds and stress-tests financial models for forecasting, scenario planning, and decision support — revenue build, cost structure, driver logic, and the sensitivities that show where a plan breaks. Use this to model a decision's financial consequence, build a forecast or long-range plan, evaluate an investment or hire, or pressure-test someone else's model before relying on it.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/financial-modeling/SKILL.md"}, {"name": "financial-reporting-and-close", "summary": "Runs the period-end close and produces reporting — close calendar, reconciliations, accruals, variance analysis, and reporting that gets read", "trigger": "Runs the period-end close and produces reporting — close calendar, reconciliations, accruals, variance analysis, and reporting that gets read. Use this to shorten or stabilise a monthly close, design a close checklist, investigate a variance, structure management reporting, or work out why the numbers keep changing after close.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/financial-reporting-and-close/SKILL.md"}, {"name": "internal-controls-and-audit", "summary": "Designs and tests controls over financial reporting — segregation of duties, approval limits, evidence, and preparing for audit", "trigger": "Designs and tests controls over financial reporting — segregation of duties, approval limits, evidence, and preparing for audit. Use this to design controls for a process, prepare for an external audit, respond to an audit finding, set approval thresholds, or assess where a small team's segregation of duties is genuinely broken.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/internal-controls-and-audit/SKILL.md"}, {"name": "revenue-recognition", "summary": "Determines when and how revenue is recognised — performance obligations, contract terms that change the answer, and the deal structures that create a…", "trigger": "Determines when and how revenue is recognised — performance obligations, contract terms that change the answer, and the deal structures that create accounting problems. Use this to work out how a contract should be recognised, review a non-standard deal before it is signed, understand deferred revenue, or spot terms that would delay or reverse recognition.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/revenue-recognition/SKILL.md"}, {"name": "treasury-and-liquidity", "summary": "Manages cash and liquidity — cash forecasting, runway, working capital, banking structure, and currency and counterparty exposure", "trigger": "Manages cash and liquidity — cash forecasting, runway, working capital, banking structure, and currency and counterparty exposure. Use this to build a cash forecast, extend runway, improve working capital, decide where cash should sit, or assess exposure to a bank, currency, or customer concentration.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/treasury-and-liquidity/SKILL.md"}, {"name": "unit-economics", "summary": "Establishes whether the business makes money on each customer or unit — contribution margin, acquisition cost, payback period, lifetime value, and th…", "trigger": "Establishes whether the business makes money on each customer or unit — contribution margin, acquisition cost, payback period, lifetime value, and the cohort behavior underneath. Use this to assess whether growth is profitable, evaluate a channel or segment, support a pricing decision, judge how fast the business can afford to grow, or diagnose why revenue growth is not producing profit.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/unit-economics/SKILL.md"}]}, {"slug": "operations", "title": "Operations", "exec": "COO", "reviewer": false, "skills": [{"name": "business-continuity-and-resilience", "summary": "Plans for operating through disruption — impact analysis, recovery objectives, continuity plans, and the exercises that prove they work", "trigger": "Plans for operating through disruption — impact analysis, recovery objectives, continuity plans, and the exercises that prove they work. Use this to run a business impact analysis, set RTO and RPO, write or test a continuity plan, prepare for a supplier or site failure, or answer a customer's resilience questionnaire.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/operations/skills/business-continuity-and-resilience/SKILL.md"}, {"name": "capacity-and-demand-planning", "summary": "Matches operational capacity to expected demand — forecasting load, sizing teams and systems, managing queues, and deciding when to add capacity", "trigger": "Matches operational capacity to expected demand — forecasting load, sizing teams and systems, managing queues, and deciding when to add capacity. Use this to plan staffing for expected volume, diagnose a queue that keeps growing, size support or fulfilment capacity, or decide whether a bottleneck needs more capacity or better flow.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/operations/skills/capacity-and-demand-planning/SKILL.md"}, {"name": "chief-operating-officer", "summary": "Owns execution: how work actually gets done across the organization, including process, program management, capacity, vendors, supply chain, and serv…", "trigger": "Owns execution: how work actually gets done across the organization, including process, program management, capacity, vendors, supply chain, and service delivery. Use this when execution is the problem rather than strategy, to design or fix a process, to resolve cross-functional handoff failures, to plan capacity, to assess delivery risk, or when the same failure keeps recurring. Also use to decide whether to build, hire, or outsource a capability.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/operations/skills/chief-operating-officer/SKILL.md"}, {"name": "process-design", "summary": "Designs, documents, and fixes operational processes — mapping the current state, finding where work actually stalls, redesigning the flow, and buildi…", "trigger": "Designs, documents, and fixes operational processes — mapping the current state, finding where work actually stalls, redesigning the flow, and building controls that hold. Use this when the same failure keeps recurring, when a handoff between teams is unreliable, when onboarding a repeated task, when work takes far longer than the work itself, or when deciding whether to automate, standardize, or eliminate a process.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/operations/skills/process-design/SKILL.md"}, {"name": "quality-management", "summary": "Builds quality into operations — defining standards, catching defects at the right point, root cause analysis, and continuous improvement", "trigger": "Builds quality into operations — defining standards, catching defects at the right point, root cause analysis, and continuous improvement. Use this to reduce a defect or error rate, design quality controls into a process, run a root cause analysis, respond to a customer quality complaint, or set up quality metrics that drive behaviour.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/operations/skills/quality-management/SKILL.md"}, {"name": "service-level-management", "summary": "Defines and manages service levels — setting targets that reflect what customers need, measuring honestly, and handling breaches", "trigger": "Defines and manages service levels — setting targets that reflect what customers need, measuring honestly, and handling breaches. Use this to write or negotiate an SLA, decide what to measure and at what threshold, respond to a missed service level, or work out why a service that meets its targets still has unhappy customers.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/operations/skills/service-level-management/SKILL.md"}, {"name": "supply-chain-and-logistics", "summary": "Manages the flow of goods and inputs — sourcing, inventory, lead times, fulfilment, and supply risk", "trigger": "Manages the flow of goods and inputs — sourcing, inventory, lead times, fulfilment, and supply risk. Use this to reduce stockouts or excess inventory, plan for a supplier failure, decide reorder points and safety stock, improve fulfilment reliability, or assess concentration risk in a supply base.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/operations/skills/supply-chain-and-logistics/SKILL.md"}, {"name": "vendor-management", "summary": "Selects, contracts, and manages suppliers and vendors — requirements, evaluation, negotiation support, onboarding, performance management, and exit", "trigger": "Selects, contracts, and manages suppliers and vendors — requirements, evaluation, negotiation support, onboarding, performance management, and exit. Use this to choose a vendor, run a selection process, structure a service agreement's operational terms, manage an underperforming supplier, plan an exit or migration, or assess concentration and continuity risk.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/operations/skills/vendor-management/SKILL.md"}]}, {"slug": "pmo", "title": "Programme Management Office", "exec": "EPMO / COO", "reviewer": false, "skills": [{"name": "benefits-realization", "summary": "Ensures projects deliver the value they were approved on — defining measurable benefits, baselining, tracking after delivery, and honest post-impleme…", "trigger": "Ensures projects deliver the value they were approved on — defining measurable benefits, baselining, tracking after delivery, and honest post-implementation review. Use this to define benefits for a business case, set a baseline, track whether value actually landed, or run a post-implementation review that produces something useful.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/pmo/skills/benefits-realization/SKILL.md"}, {"name": "change-and-adoption", "summary": "Gets people to actually use what was delivered — stakeholder analysis, communication, training, resistance, and measuring adoption", "trigger": "Gets people to actually use what was delivered — stakeholder analysis, communication, training, resistance, and measuring adoption. Use this to plan a rollout, recover an implementation nobody is using, handle resistance to a change, sequence communications, or work out why a technically successful project changed nothing.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/pmo/skills/change-and-adoption/SKILL.md"}, {"name": "dependency-and-risk-management", "summary": "Manages delivery risk and cross-team dependencies — identifying, sizing, mitigating and escalating what could stop the work", "trigger": "Manages delivery risk and cross-team dependencies — identifying, sizing, mitigating and escalating what could stop the work. Use this to build a risk register that gets used, manage dependencies between teams, decide what to escalate and when, or work out why the same risks keep materialising unmanaged.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/pmo/skills/dependency-and-risk-management/SKILL.md"}, {"name": "portfolio-governance", "summary": "Governs the portfolio of work — intake, prioritisation, stage gates, resource contention, and stopping things", "trigger": "Governs the portfolio of work — intake, prioritisation, stage gates, resource contention, and stopping things. Use this to set up intake and prioritisation, run a stage gate, decide between competing initiatives, resolve resource contention across projects, or work out why everything is in flight and nothing is finishing.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/pmo/skills/portfolio-governance/SKILL.md"}, {"name": "program-management", "summary": "Plans and drives cross-functional programs to delivery — scope, sequencing, dependencies, status, risk, and the escalations that keep work moving", "trigger": "Plans and drives cross-functional programs to delivery — scope, sequencing, dependencies, status, risk, and the escalations that keep work moving. Use this to run a multi-team initiative, recover a program that is slipping, build a delivery plan with dependencies, structure status reporting, or diagnose why cross-team work keeps missing dates.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/pmo/skills/program-management/SKILL.md"}, {"name": "project-delivery", "summary": "Plans and delivers a single project — scope, estimation, scheduling, critical path, tracking, and recovering when it slips", "trigger": "Plans and delivers a single project — scope, estimation, scheduling, critical path, tracking, and recovering when it slips. Use this to plan a project, build or challenge a schedule, estimate credibly, track progress meaningfully, or recover a project that is late.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/pmo/skills/project-delivery/SKILL.md"}]}, {"slug": "customer-experience", "title": "Customer Experience", "exec": "CCO", "reviewer": false, "skills": [{"name": "chief-customer-officer", "summary": "Owns the customer's experience after the sale — support, success, escalation, and the feedback loop back into product", "trigger": "Owns the customer's experience after the sale — support, success, escalation, and the feedback loop back into product. Use this for a decision spanning support and product, when service quality and cost are in tension, when deciding what to staff or automate, when a customer relationship is at risk above the account-manager level, or when nobody owns a recurring customer problem.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/customer-experience/skills/chief-customer-officer/SKILL.md"}, {"name": "escalation-management", "summary": "Handles customer situations that have exceeded normal support — severity assessment, incident communication, executive escalation, and recovering a r…", "trigger": "Handles customer situations that have exceeded normal support — severity assessment, incident communication, executive escalation, and recovering a relationship after a failure. Use this when a customer issue is escalating or has gone to leadership, during a customer-affecting outage, when a major account is at risk, when a relationship needs repairing after a failure, or to design the escalation path itself.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/customer-experience/skills/escalation-management/SKILL.md"}, {"name": "self-service-and-knowledge", "summary": "Builds the help centre, in-product guidance, and knowledge base that let customers resolve problems without contacting anyone — content, findability,…", "trigger": "Builds the help centre, in-product guidance, and knowledge base that let customers resolve problems without contacting anyone — content, findability, maintenance, and deflection measurement. Use this to build or fix a help centre, reduce support volume, write documentation for customers, improve findability, or decide what deserves a help article versus a product fix.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/customer-experience/skills/self-service-and-knowledge/SKILL.md"}, {"name": "support-operations", "summary": "Designs and runs the support function — channels, queues, routing, staffing, service levels, quality, and the metrics that show whether it is working", "trigger": "Designs and runs the support function — channels, queues, routing, staffing, service levels, quality, and the metrics that show whether it is working. Use this to set up or fix support operations, choose channels, size a team, set or renegotiate service levels, reduce cost per contact, diagnose long queues or poor quality, or decide what to automate.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/customer-experience/skills/support-operations/SKILL.md"}, {"name": "voice-of-customer", "summary": "Builds the loop from what customers say to what gets changed — collecting feedback, distinguishing signal from noise, routing it to owners, and closi…", "trigger": "Builds the loop from what customers say to what gets changed — collecting feedback, distinguishing signal from noise, routing it to owners, and closing the loop back to the customer. Use this to set up a feedback programme, design or interpret CSAT/NPS, decide what customer feedback deserves action, get product to act on recurring issues, or diagnose why feedback is collected but nothing changes.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/customer-experience/skills/voice-of-customer/SKILL.md"}]}, {"slug": "data-analytics", "title": "Data & Analytics", "exec": "CDO", "reviewer": false, "skills": [{"name": "ai-ml-governance", "summary": "Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or ret…", "trigger": "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.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/data-analytics/skills/ai-ml-governance/SKILL.md"}, {"name": "business-intelligence", "summary": "Builds reporting and self-serve analytics that people actually use — metric trees, dashboard design, distribution, and the discipline that stops dash…", "trigger": "Builds reporting and self-serve analytics that people actually use — metric trees, dashboard design, distribution, and the discipline that stops dashboards proliferating. Use this to build a dashboard or report, design a metrics framework, set up self-serve analytics, decide what to measure, or diagnose why reporting exists but nobody uses it or trusts it.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/data-analytics/skills/business-intelligence/SKILL.md"}, {"name": "chief-data-officer", "summary": "Owns data as an asset — governance, quality, the warehouse and semantic layer, analytics capability, and the governance of models built on top", "trigger": "Owns data as an asset — governance, quality, the warehouse and semantic layer, analytics capability, and the governance of models built on top. Use this for a decision about how data is collected, stored, defined, or shared; when numbers disagree between teams; when deciding what to build in-house versus buy; when standing up a data function; or when an AI or model decision needs governance rather than engineering.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/data-analytics/skills/chief-data-officer/SKILL.md"}, {"name": "data-engineering", "summary": "Builds and operates data pipelines — ingestion, transformation, orchestration, quality testing, and reliability of data delivery", "trigger": "Builds and operates data pipelines — ingestion, transformation, orchestration, quality testing, and reliability of data delivery. Use this to design or debug a pipeline, decide batch versus streaming, add data quality checks, handle late or duplicate data, or work out why a dashboard's numbers changed without anyone changing the dashboard.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/data-analytics/skills/data-engineering/SKILL.md"}, {"name": "data-governance", "summary": "Establishes ownership, definitions, quality, access, and lineage for the organization's data", "trigger": "Establishes ownership, definitions, quality, access, and lineage for the organization's data. Use this when metrics disagree between teams, when nobody knows which dataset is authoritative, when setting up data ownership or access policy, when data quality is unreliable, or before opening a dataset to a wider audience.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/data-analytics/skills/data-governance/SKILL.md"}, {"name": "data-modeling", "summary": "Designs the warehouse and semantic layer — source-to-mart structure, dimensional modeling, grain, slowly changing dimensions, and the metric layer an…", "trigger": "Designs the warehouse and semantic layer — source-to-mart structure, dimensional modeling, grain, slowly changing dimensions, and the metric layer analytics reads through. Use this to design or restructure a warehouse, model a new source, decide on grain or table structure, build a semantic or metric layer, or diagnose why queries are slow, wrong, or impossible to write.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/data-analytics/skills/data-modeling/SKILL.md"}]}, {"slug": "corporate-strategy", "title": "Corporate Strategy", "exec": "CSO", "reviewer": false, "skills": [{"name": "chief-strategy-officer", "summary": "Owns where the business plays and how it wins over a multi-year horizon — portfolio choices, corporate development, strategic partnerships, and plann…", "trigger": "Owns where the business plays and how it wins over a multi-year horizon — portfolio choices, corporate development, strategic partnerships, and planning under uncertainty. Use this for a decision about which markets or businesses to be in, whether to build, buy, or partner, how to allocate capital across business lines, or when a long-horizon bet needs framing. Distinct from `chief-executive`, which arbitrates present-quarter conflicts.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/corporate-strategy/skills/chief-strategy-officer/SKILL.md"}, {"name": "mergers-and-acquisitions", "summary": "Runs corporate development — deal thesis, target screening, valuation framing, diligence, and integration planning", "trigger": "Runs corporate development — deal thesis, target screening, valuation framing, diligence, and integration planning. Use this when considering an acquisition or being approached about one, when evaluating build-versus-buy at company scale, when running or reviewing diligence, or when planning how an acquired business will actually be integrated.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/corporate-strategy/skills/mergers-and-acquisitions/SKILL.md"}, {"name": "portfolio-strategy", "summary": "Decides where capital and attention go across business lines, products, and markets — what to fund, hold, harvest, or exit, and on what evidence", "trigger": "Decides where capital and attention go across business lines, products, and markets — what to fund, hold, harvest, or exit, and on what evidence. Use this to allocate budget across businesses, evaluate whether a product line should continue, decide market entry or exit, structure a portfolio review, or when several initiatives compete for the same limited investment.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/corporate-strategy/skills/portfolio-strategy/SKILL.md"}, {"name": "scenario-planning", "summary": "Plans under genuine uncertainty — building scenarios, identifying which assumptions are load-bearing, setting early-warning indicators, and stress-te…", "trigger": "Plans under genuine uncertainty — building scenarios, identifying which assumptions are load-bearing, setting early-warning indicators, and stress-testing a plan against futures rather than forecasting one. Use this when a decision depends on something unknowable, when a plan assumes conditions that may not hold, before a large irreversible commitment, or when a market, regulatory, or technology shift could invalidate the strategy.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/corporate-strategy/skills/scenario-planning/SKILL.md"}, {"name": "strategic-alliances", "summary": "Structures partnerships that change what the business can do — technology integrations, channel and reseller arrangements, joint ventures, and OEM re…", "trigger": "Structures partnerships that change what the business can do — technology integrations, channel and reseller arrangements, joint ventures, and OEM relationships. Use this to evaluate or structure a strategic partnership, decide between partnering and building, negotiate commercial terms of an alliance, or diagnose a partnership that is signed but not producing. For audience-borrowing partnerships, use `marketing:partnership-marketing`.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/corporate-strategy/skills/strategic-alliances/SKILL.md"}]}, {"slug": "people", "title": "People", "exec": "CHRO", "reviewer": false, "skills": [{"name": "chief-human-resources-officer", "summary": "Owns the organization itself: org design, hiring, performance, compensation, development, culture, and employee relations", "trigger": "Owns the organization itself: org design, hiring, performance, compensation, development, culture, and employee relations. Use this to design or restructure a team, plan hiring, write a role or leveling definition, handle a performance or compensation question, diagnose why a team is underperforming for non-technical reasons, or assess the people risk in a plan. Also use for onboarding design and retention of key staff.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/chief-human-resources-officer/SKILL.md"}, {"name": "compensation-and-leveling", "summary": "Builds and maintains the leveling framework and pay structure — level definitions, salary bands, benchmarking, pay equity, and how raises and promoti…", "trigger": "Builds and maintains the leveling framework and pay structure — level definitions, salary bands, benchmarking, pay equity, and how raises and promotions are decided. Use this to design or revise leveling, set or adjust salary bands, benchmark against market, handle a compensation request or counteroffer, run a review cycle, or diagnose pay compression and equity issues.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/compensation-and-leveling/SKILL.md"}, {"name": "employee-relations", "summary": "Handles the difficult human situations — grievances, complaints, investigations, conflict, and separations conducted properly", "trigger": "Handles the difficult human situations — grievances, complaints, investigations, conflict, and separations conducted properly. Use this to respond to a complaint or grievance, structure an investigation, handle a conflict between colleagues, prepare for a difficult conversation, or work out what a manager can and cannot do in a given situation.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/employee-relations/SKILL.md"}, {"name": "hiring-and-interviewing", "summary": "Designs and runs hiring — role definition, sourcing, interview loop design, structured evaluation, and the decision itself", "trigger": "Designs and runs hiring — role definition, sourcing, interview loop design, structured evaluation, and the decision itself. Use this to open a role, write a job description or scorecard, design an interview process, prepare interview questions, calibrate a hiring decision, or diagnose why a hiring process produces poor outcomes.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/hiring-and-interviewing/SKILL.md"}, {"name": "learning-and-development", "summary": "Builds capability — skills gaps, career frameworks, training that transfers to the job, and internal mobility", "trigger": "Builds capability — skills gaps, career frameworks, training that transfers to the job, and internal mobility. Use this to design a career ladder, close a capability gap, decide whether to build or hire a skill, structure onboarding into a role, or work out why training keeps failing to change anything.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/learning-and-development/SKILL.md"}, {"name": "onboarding-and-offboarding", "summary": "Designs the joining and leaving experience — first-day readiness, ramp to productivity, knowledge capture, and clean exits", "trigger": "Designs the joining and leaving experience — first-day readiness, ramp to productivity, knowledge capture, and clean exits. Use this to design or fix onboarding, shorten time to productivity, structure a leaver process, capture knowledge before someone leaves, or coordinate the access and asset steps around a joiner or leaver.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/onboarding-and-offboarding/SKILL.md"}, {"name": "org-design", "summary": "Designs how an organization is structured — reporting lines, team boundaries, spans and layers, role definition, and workforce planning against the s…", "trigger": "Designs how an organization is structured — reporting lines, team boundaries, spans and layers, role definition, and workforce planning against the strategy. Use this to structure a new team, restructure an existing one, resolve unclear ownership between teams, plan headcount, or diagnose why a team underperforms for structural rather than individual reasons.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/org-design/SKILL.md"}, {"name": "performance-management", "summary": "Runs performance systems that change behaviour — expectations, feedback, review cycles, calibration, and handling underperformance", "trigger": "Runs performance systems that change behaviour — expectations, feedback, review cycles, calibration, and handling underperformance. Use this to design or fix a review process, run calibration, write or coach on feedback, address sustained underperformance, or work out why reviews consume weeks and change nothing.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/performance-management/SKILL.md"}, {"name": "workforce-planning", "summary": "Plans the shape and size of the workforce — demand for roles, build-versus-buy, attrition, and sequencing hiring against budget", "trigger": "Plans the shape and size of the workforce — demand for roles, build-versus-buy, attrition, and sequencing hiring against budget. Use this to build a hiring plan, decide which roles to open and in what order, model attrition and backfill, plan for a growth or contraction scenario, or connect headcount plans to the budget.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/workforce-planning/SKILL.md"}]}, {"slug": "legal-risk", "title": "Legal & Risk", "exec": "CLO / CCO", "reviewer": true, "skills": [{"name": "chief-legal-and-risk-officer", "summary": "Owns legal, contracts, intellectual property, regulatory compliance, privacy, security governance, enterprise risk, and audit readiness", "trigger": "Owns legal, contracts, intellectual property, regulatory compliance, privacy, security governance, enterprise risk, and audit readiness. Use this to review a contract or commitment, assess regulatory or privacy exposure, evaluate an IP or licensing question, judge the risk in a business decision, prepare for an audit or certification, or when a plan may create obligations the business cannot meet. Also use to decide whether a risk should be accepted, mitigated, or refused.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/legal-risk/skills/chief-legal-and-risk-officer/SKILL.md"}, {"name": "contract-review", "summary": "Reviews and negotiates commercial agreements — MSAs, SOWs, order forms, NDAs, vendor and data-processing agreements — identifying material risk, prop…", "trigger": "Reviews and negotiates commercial agreements — MSAs, SOWs, order forms, NDAs, vendor and data-processing agreements — identifying material risk, proposing positions, and recommending a path rather than listing issues. Use this to review a contract before signature, prepare a negotiation position, build fallback positions and approval thresholds, or assess exposure in terms already agreed.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/legal-risk/skills/contract-review/SKILL.md"}, {"name": "corporate-governance", "summary": "Maintains the corporate record and the governance machinery — entity records, board and committee support, resolutions and minutes, delegations of au…", "trigger": "Maintains the corporate record and the governance machinery — entity records, board and committee support, resolutions and minutes, delegations of authority, insurance, and business continuity. Use this to prepare board or committee materials, record a decision that needs to be minuted, set or check approval authority, review insurance and continuity coverage, establish a retention policy, or work out where a responsibility belongs when it falls between functions.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/legal-risk/skills/corporate-governance/SKILL.md"}, {"name": "enterprise-risk", "summary": "Identifies, assesses, and tracks organizational risk — building and maintaining a risk register, scoring exposure, assigning owners and treatments, a…", "trigger": "Identifies, assesses, and tracks organizational risk — building and maintaining a risk register, scoring exposure, assigning owners and treatments, and preparing for audit. Use this to stand up a risk program, assess the risk in a decision or initiative, prepare for a certification or audit, decide whether a risk should be accepted, mitigated, transferred, or avoided, or report risk posture to leadership.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/legal-risk/skills/enterprise-risk/SKILL.md"}, {"name": "privacy-and-data-protection", "summary": "Assesses and improves how personal data is collected, used, shared, and retained — data mapping, lawful basis, consent, processor agreements, subject…", "trigger": "Assesses and improves how personal data is collected, used, shared, and retained — data mapping, lawful basis, consent, processor agreements, subject rights, and breach obligations. Use this before launching anything that handles personal data, when adding a vendor that will process it, when a data subject request arrives, when assessing exposure under GDPR or US state privacy laws, or when preparing for a privacy review.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/legal-risk/skills/privacy-and-data-protection/SKILL.md"}]}];
+const DEPTS = [{"slug": "executive", "title": "Office of the CEO", "exec": "Chief Executive", "reviewer": false, "skills": [{"name": "agent-hierarchy", "summary": "Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independ…", "trigger": "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.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/executive/skills/agent-hierarchy/SKILL.md"}, {"name": "ai-research-analyst", "summary": "Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with th…", "trigger": "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.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/executive/skills/ai-research-analyst/SKILL.md"}, {"name": "business-growth-consultant", "summary": "Finds the single constraint currently limiting a business's growth and the highest-leverage moves against it, rather than producing a list of everyth…", "trigger": "Finds the single constraint currently limiting a business's growth and the highest-leverage moves against it, rather than producing a list of everything that could be improved. Use this when growth has stalled or slowed, when deciding where to spend limited time or budget, when revenue rises but profit does not, when prioritizing growth initiatives, or when a business feels busy without compounding.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/executive/skills/business-growth-consultant/SKILL.md"}, {"name": "ceo-advisor", "summary": "Pressure-tests a decision, plan, or idea before it is committed to — surfacing the assumption it rests on, the case against it, and what would have t…", "trigger": "Pressure-tests a decision, plan, or idea before it is committed to — surfacing the assumption it rests on, the case against it, and what would have to be true for it to work. Use this when weighing options, when a plan needs challenging before commitment, when you have already decided and want a genuine gut check, when processing meeting notes into decisions, or when competing initiatives need ranking. Distinct from `chief-executive`, which owns direction; this one interrogates a specific decision.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/executive/skills/ceo-advisor/SKILL.md"}, {"name": "chief-executive", "summary": "Sets direction, allocates capital and attention, and makes the calls no one else can make", "trigger": "Sets direction, allocates capital and attention, and makes the calls no one else can make. Use this when a decision spans more than one function, when priorities conflict and something must be cut, when a plan needs pressure-testing before commitment, or when the question is what the organization should do rather than how to do it. Also use to route a request to the right executive when it is unclear who owns it.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/executive/skills/chief-executive/SKILL.md"}, {"name": "saas-idea-validator", "summary": "Evaluates a software or startup idea against problem, market, competition, monetization, defensibility, and execution, and returns a verdict rather t…", "trigger": "Evaluates a software or startup idea against problem, market, competition, monetization, defensibility, and execution, and returns a verdict rather than encouragement. Use this when an idea needs pressure-testing before anyone builds, when deciding whether something is worth pursuing, when assessing competition or willingness to pay, or when a validated idea needs a first-customers and MVP plan. Default to scrutiny; the useful answer is usually the unwelcome one.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/executive/skills/saas-idea-validator/SKILL.md"}]}, {"slug": "technology", "title": "Technology", "exec": "CTO / CIO", "reviewer": false, "skills": [{"name": "ai-workflow-architect", "summary": "Designs AI systems, automations, and agent workflows for a business — identifying which manual work is worth automating, how to structure the system,…", "trigger": "Designs AI systems, automations, and agent workflows for a business — identifying which manual work is worth automating, how to structure the system, which tools fit, and what could go wrong. Use this to automate part of an operation, design an agent or MCP workflow, reduce repetitive manual work, connect tools into a system, decide which automation to build first, or audit an automation that is not delivering.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/ai-workflow-architect/SKILL.md"}, {"name": "api-design", "summary": "Designs interfaces that survive their consumers — resource modeling, errors, versioning, pagination, and compatibility", "trigger": "Designs interfaces that survive their consumers — resource modeling, errors, versioning, pagination, and compatibility. Use this to design a new API, review one before it ships, decide how to version or deprecate, fix an interface consumers keep misusing, or work out whether a change is breaking.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/api-design/SKILL.md"}, {"name": "branch-and-worktree-workflow", "summary": "Isolates feature work in its own branch or worktree and integrates it cleanly when done", "trigger": "Isolates feature work in its own branch or worktree and integrates it cleanly when done. Use this when starting work that should not disturb the current workspace, when several efforts must proceed in parallel on one repository, or when implementation is finished and the change needs merging, rebasing, or splitting for review.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/branch-and-worktree-workflow/SKILL.md"}, {"name": "chief-technology-officer", "summary": "Owns architecture, engineering delivery, infrastructure, data platform, and internal systems", "trigger": "Owns architecture, engineering delivery, infrastructure, data platform, and internal systems. Use this for build-versus-buy calls, technology selection, architectural direction, engineering capacity and delivery risk, technical debt tradeoffs, platform and tooling decisions, or when a technical choice has business consequences that need stating in business terms. Also use to judge whether a technical plan is sound before it is committed to.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/chief-technology-officer/SKILL.md"}, {"name": "cloud-infrastructure", "summary": "Designs and runs cloud infrastructure — environments, infrastructure as code, networking and isolation, scaling, and cost", "trigger": "Designs and runs cloud infrastructure — environments, infrastructure as code, networking and isolation, scaling, and cost. Use this to design a cloud environment, control infrastructure spend, set up environment separation, plan for scale or region failure, or review infrastructure someone configured by hand.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/cloud-infrastructure/SKILL.md"}, {"name": "code-review", "summary": "Conducts and responds to code review — reviewing a change for correctness, design, and risk, and evaluating review feedback received on your own work", "trigger": "Conducts and responds to code review — reviewing a change for correctness, design, and risk, and evaluating review feedback received on your own work. Use this before merging, when asked to review a diff or pull request, when review feedback has arrived and needs acting on, or when feedback seems wrong and needs a reasoned response rather than compliance.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/code-review/SKILL.md"}, {"name": "completion-verification", "summary": "Verifies that work is actually complete before it is claimed to be — running the checks, reading the output, and confirming the original request was…", "trigger": "Verifies that work is actually complete before it is claimed to be — running the checks, reading the output, and confirming the original request was satisfied rather than approximated. Use this before saying something is done, fixed, or passing; before committing or opening a pull request; and whenever a claim of success has not been backed by command output.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/completion-verification/SKILL.md"}, {"name": "implementation-planning", "summary": "Turns a spec or requirement into a written plan a separate session or agent can execute, then drives that plan through review checkpoints", "trigger": "Turns a spec or requirement into a written plan a separate session or agent can execute, then drives that plan through review checkpoints. Use this before touching code on any multi-step task, when work needs handing to someone else, when a task keeps sprawling mid-implementation, or when a plan exists and needs executing in order with verification between steps.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/implementation-planning/SKILL.md"}, {"name": "observability-and-reliability", "summary": "Makes systems debuggable and reliably operable — instrumentation, alerting that is worth waking for, service objectives, and learning from failure", "trigger": "Makes systems debuggable and reliably operable — instrumentation, alerting that is worth waking for, service objectives, and learning from failure. Use this to instrument a service, fix alerting that is ignored, set error budgets or reliability targets, prepare for on-call, or run a blameless post-incident review.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/observability-and-reliability/SKILL.md"}, {"name": "parallel-agent-delivery", "summary": "Splits work across multiple agents or sessions running at once, keeping their surfaces disjoint so results merge cleanly", "trigger": "Splits work across multiple agents or sessions running at once, keeping their surfaces disjoint so results merge cleanly. Use this when facing several independent tasks with no shared state, when a plan has parallelizable steps, when a broad search or audit would be faster fanned out, or when deciding whether work can safely be split at all.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/parallel-agent-delivery/SKILL.md"}, {"name": "prompt-optimizer", "summary": "Turns rough intent or a weak prompt into a reliable one — diagnosing why output is inconsistent, restructuring the instruction, and adapting it acros…", "trigger": "Turns rough intent or a weak prompt into a reliable one — diagnosing why output is inconsistent, restructuring the instruction, and adapting it across models. Use this when a prompt is not producing what was wanted, when output varies run to run, when writing a prompt for a repeated task, when moving a prompt between models, or when someone describes what they want an AI to do and needs it written properly.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/prompt-optimizer/SKILL.md"}, {"name": "release-and-deployment", "summary": "Ships changes safely and often — pipelines, deployment strategies, feature flags, rollback, and database changes", "trigger": "Ships changes safely and often — pipelines, deployment strategies, feature flags, rollback, and database changes. Use this to design a deployment pipeline, reduce release risk, roll out a risky change gradually, plan a schema migration, or work out why releases are infrequent and frightening.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/release-and-deployment/SKILL.md"}, {"name": "skill-authoring", "summary": "Writes and revises agent skills so they trigger at the right moments and give usable instruction when they do", "trigger": "Writes and revises agent skills so they trigger at the right moments and give usable instruction when they do. Use this when creating a new skill, editing an existing one, diagnosing a skill that fires too often or never fires, or reviewing a set of skills for overlap. Also use before adding to a skill library, to check the capability is not already covered.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/skill-authoring/SKILL.md"}, {"name": "solution-architecture", "summary": "Designs system structure and makes architectural decisions defensible — boundaries, coupling, trade-offs, and recording why", "trigger": "Designs system structure and makes architectural decisions defensible — boundaries, coupling, trade-offs, and recording why. Use this to design a new system or major component, choose between architectural options, review an existing design, decide where a boundary belongs, or document an architectural decision so it survives the people who made it.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/solution-architecture/SKILL.md"}, {"name": "solution-exploration", "summary": "Explores the problem and the range of possible approaches before any code is written — clarifying what is actually being asked, surfacing options wit…", "trigger": "Explores the problem and the range of possible approaches before any code is written — clarifying what is actually being asked, surfacing options with their tradeoffs, and converging on one. Use this at the start of any feature, component, or behavior change, when a request is ambiguous, when the first idea is the only idea on the table, or when a design decision needs pressure-testing before commitment.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/solution-exploration/SKILL.md"}, {"name": "systematic-debugging", "summary": "Finds the root cause of a bug, test failure, or unexpected behavior before proposing any fix", "trigger": "Finds the root cause of a bug, test failure, or unexpected behavior before proposing any fix. Use this whenever something is broken and the cause is not yet proven — a failing test, a production error, intermittent behavior, or a symptom that appeared after a change. Also use when a fix has been attempted and did not work, or when the same bug keeps coming back.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/systematic-debugging/SKILL.md"}, {"name": "technical-debt-management", "summary": "Makes technical debt visible and decidable — distinguishing real debt from mess, quantifying its cost, and arguing for remediation in business terms", "trigger": "Makes technical debt visible and decidable — distinguishing real debt from mess, quantifying its cost, and arguing for remediation in business terms. Use this to assess and prioritize debt, decide whether to fix or live with something, justify remediation work to non-engineers, or plan a migration off a system nobody wants to touch.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/technical-debt-management/SKILL.md"}, {"name": "test-driven-development", "summary": "Drives implementation by writing a failing test first, then the smallest code that passes it", "trigger": "Drives implementation by writing a failing test first, then the smallest code that passes it. Use this before writing implementation code for any feature or bugfix, when a bug needs a regression test, when existing code is hard to change safely, or when someone asks whether a change is covered. Also use to decide what is worth testing and what is not.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/technology/skills/test-driven-development/SKILL.md"}]}, {"slug": "security", "title": "Security", "exec": "CISO", "reviewer": true, "skills": [{"name": "access-and-identity", "summary": "Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process", "trigger": "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.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/security/skills/access-and-identity/SKILL.md"}, {"name": "chief-information-security-officer", "summary": "Owns the security posture of the organization — architecture, program strategy, risk acceptance, incident command, and the authority to stop work tha…", "trigger": "Owns the security posture of the organization — architecture, program strategy, risk acceptance, incident command, and the authority to stop work that creates unacceptable exposure. Use this for a security strategy or program decision, when a technical choice creates security risk that needs a verdict, when deciding whether to accept or block a risk, when standing up a security function, or when security and delivery priorities conflict and someone has to decide.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/security/skills/chief-information-security-officer/SKILL.md"}, {"name": "incident-response", "summary": "Runs a security incident from detection to closure — triage, containment, investigation, communication, and the review afterward", "trigger": "Runs a security incident from detection to closure — triage, containment, investigation, communication, and the review afterward. Use this when a compromise is suspected or confirmed, when preparing an incident response plan or running an exercise, when deciding whether something is an incident, or when a breach may trigger notification obligations.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/security/skills/incident-response/SKILL.md"}, {"name": "security-architecture-review", "summary": "Reviews a design or change for security before it ships — authentication and authorization, data handling, secrets, dependencies, and the secure-deve…", "trigger": "Reviews a design or change for security before it ships — authentication and authorization, data handling, secrets, dependencies, and the secure-development practices around it. Use this to review an architecture or pull request for security, set secure coding standards, choose or tune SAST and DAST tooling, assess a third-party integration, or decide whether a design is safe to build.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/security/skills/security-architecture-review/SKILL.md"}, {"name": "threat-modeling", "summary": "Identifies what could go wrong in a system before it is built or changed — the assets worth attacking, the entry points, the trust boundaries, and th…", "trigger": "Identifies what could go wrong in a system before it is built or changed — the assets worth attacking, the entry points, the trust boundaries, and the controls that actually address the realistic threats. Use this when designing a feature or system, when a change touches authentication, data handling, payments, or external input, before a security review, or when deciding which security work is worth doing at all.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/security/skills/threat-modeling/SKILL.md"}, {"name": "vulnerability-management", "summary": "Runs the loop from discovering a weakness to confirming it is fixed — scanning, triage, prioritization by real exploitability, remediation tracking,…", "trigger": "Runs the loop from discovering a weakness to confirming it is fixed — scanning, triage, prioritization by real exploitability, remediation tracking, and patch policy. Use this to stand up or fix a vulnerability program, triage scanner output, decide what to fix first, set patch SLAs, handle a disclosure from an outside researcher, or report posture to leadership.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/security/skills/vulnerability-management/SKILL.md"}]}, {"slug": "it-operations", "title": "IT Operations", "exec": "CIO", "reviewer": false, "skills": [{"name": "backup-and-recovery", "summary": "Protects and restores data — backup coverage and scope, retention, immutability against ransomware, and proving restores actually work", "trigger": "Protects and restores data — backup coverage and scope, retention, immutability against ransomware, and proving restores actually work. Use this to design a backup regime, verify restores, plan retention, protect backups from ransomware, or recover from data loss.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/it-operations/skills/backup-and-recovery/SKILL.md"}, {"name": "endpoint-management", "summary": "Manages laptops, desktops and mobile devices — enrollment, configuration, patching, software distribution, and lost or compromised devices", "trigger": "Manages laptops, desktops and mobile devices — enrollment, configuration, patching, software distribution, and lost or compromised devices. Use this to set up device management, standardize builds, roll out software or an OS upgrade, handle a lost device, or bring an unmanaged fleet under control.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/it-operations/skills/endpoint-management/SKILL.md"}, {"name": "identity-lifecycle-administration", "summary": "Executes joiner, mover and leaver processes — provisioning, group membership, access changes on role change, and complete deprovisioning", "trigger": "Executes joiner, mover and leaver processes — provisioning, group membership, access changes on role change, and complete deprovisioning. Use this to set up or fix joiner-mover-leaver, deprovision someone completely, clean up accumulated access, audit group membership, or find accounts that outlived their owners.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/it-operations/skills/identity-lifecycle-administration/SKILL.md"}, {"name": "it-asset-management", "summary": "Tracks hardware and software assets through their life — procurement, ownership, licensing, refresh, and disposal", "trigger": "Tracks hardware and software assets through their life — procurement, ownership, licensing, refresh, and disposal. Use this to build an asset register, prepare for a software audit, plan a refresh cycle, control license spend, or dispose of equipment safely.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/it-operations/skills/it-asset-management/SKILL.md"}, {"name": "network-administration", "summary": "Designs and operates the corporate network — segmentation, remote access, wireless, DNS and addressing, and diagnosing network problems", "trigger": "Designs and operates the corporate network — segmentation, remote access, wireless, DNS and addressing, and diagnosing network problems. Use this to segment a network, set up or fix remote access, diagnose intermittent connectivity, plan addressing or DNS, or assess whether the network's trust assumptions still hold.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/it-operations/skills/network-administration/SKILL.md"}, {"name": "service-desk", "summary": "Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it", "trigger": "Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets still frustrates everyone.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/it-operations/skills/service-desk/SKILL.md"}, {"name": "systems-administration", "summary": "Runs servers and corporate systems — patching, configuration baselines, change control, capacity, and the routine that prevents incidents", "trigger": "Runs servers and corporate systems — patching, configuration baselines, change control, capacity, and the routine that prevents incidents. Use this to establish a patching cadence, standardize server configuration, plan a maintenance window, decide change control for infrastructure, or clean up systems that have drifted from any known state.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/it-operations/skills/systems-administration/SKILL.md"}]}, {"slug": "product", "title": "Product", "exec": "CPO", "reviewer": false, "skills": [{"name": "brand-identity", "summary": "Defines and applies visual brand — logo usage, palette, typography, imagery direction, and the guidelines that keep expression consistent across prod…", "trigger": "Defines and applies visual brand — logo usage, palette, typography, imagery direction, and the guidelines that keep expression consistent across product and marketing surfaces. Use this to establish a brand from scratch, audit whether an existing brand is being applied consistently, build brand guidelines, or decide how a brand should express itself in an unfamiliar format.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/product/skills/brand-identity/SKILL.md"}, {"name": "chief-product-officer", "summary": "Owns what gets built and why: product strategy, roadmap, discovery, user experience, and the definition of success for each release", "trigger": "Owns what gets built and why: product strategy, roadmap, discovery, user experience, and the definition of success for each release. Use this to decide what to build next, to cut scope, to turn a business goal into a product bet, to judge whether a feature is worth its cost, or when engineering and go-to-market disagree about what a release is for. Also use for roadmap sequencing and for killing work that is not earning its place.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/product/skills/chief-product-officer/SKILL.md"}, {"name": "design-styles", "summary": "Applies a deliberate visual direction to an interface — minimalist editorial, industrial utilitarian, or high-polish commercial — each with its own t…", "trigger": "Applies a deliberate visual direction to an interface — minimalist editorial, industrial utilitarian, or high-polish commercial — each with its own type scale, palette behavior, surface treatment, and motion. Use this when a product needs a point of view rather than defaults, when choosing between visual directions, when an interface reads as generic, or when restyling something without changing its structure.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/product/skills/design-styles/SKILL.md"}, {"name": "design-system", "summary": "Builds and maintains the design system a product is assembled from — tokens for color, type, spacing and elevation, component contracts, and the rule…", "trigger": "Builds and maintains the design system a product is assembled from — tokens for color, type, spacing and elevation, component contracts, and the rules that keep them coherent as the product grows. Use this when starting a new interface, when screens have drifted apart visually, when the same component exists three times in slightly different forms, or when a token or component needs adding without breaking what exists.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/product/skills/design-system/SKILL.md"}, {"name": "interface-craft", "summary": "Raises the visual and interaction quality of an interface — layout, hierarchy, type, spacing, density, and the details that separate a considered pro…", "trigger": "Raises the visual and interaction quality of an interface — layout, hierarchy, type, spacing, density, and the details that separate a considered product from a generic one. Use this when a screen works but looks unfinished or default, when a layout feels crowded or arbitrary, when a page has no clear focal point, or when an interface needs to feel trustworthy rather than merely functional.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/product/skills/interface-craft/SKILL.md"}, {"name": "interface-redesign", "summary": "Upgrades an existing interface to a higher standard without rebuilding it — auditing what is there, identifying what reads as generic or unfinished,…", "trigger": "Upgrades an existing interface to a higher standard without rebuilding it — auditing what is there, identifying what reads as generic or unfinished, and sequencing changes by impact. Use this when a product works but looks dated or default, when a redesign is being considered, when deciding whether to restyle or rebuild, or when a screen needs to look substantially better with limited effort.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/product/skills/interface-redesign/SKILL.md"}, {"name": "presentation-design", "summary": "Designs slide decks, one-pagers, and marketing graphics that carry an argument rather than decorate one", "trigger": "Designs slide decks, one-pagers, and marketing graphics that carry an argument rather than decorate one. Use this to build or fix a pitch deck, board deck, or conference talk; to design a banner, social graphic, or one-pager; or when a deck is dense, unfocused, or being read aloud from the slides.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/product/skills/presentation-design/SKILL.md"}, {"name": "ux-product-auditor", "summary": "Audits a website, app, onboarding flow, or design for usability, conversion, and product problems, tying every finding to a business outcome and a se…", "trigger": "Audits a website, app, onboarding flow, or design for usability, conversion, and product problems, tying every finding to a business outcome and a severity. Use this to review an interface, diagnose low conversion or activation, find where users drop off, get structured product feedback, or decide which UX fixes to ship first. For raising visual quality rather than finding problems, use `interface-craft`.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/product/skills/ux-product-auditor/SKILL.md"}, {"name": "visual-reference-generation", "summary": "Produces design reference imagery before implementation — screen concepts, layout directions, and flows for web or mobile that make a verbal brief co…", "trigger": "Produces design reference imagery before implementation — screen concepts, layout directions, and flows for web or mobile that make a verbal brief concrete enough to argue with. Use this when a brief needs visualizing before anyone builds, when comparing layout directions, when handing a developer a target, or when stakeholders are describing different things with the same words.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/product/skills/visual-reference-generation/SKILL.md"}]}, {"slug": "marketing", "title": "Marketing", "exec": "CMO", "reviewer": false, "skills": [{"name": "behavioral-marketing", "summary": "Applies decision science and cognitive bias research to marketing and product decisions — how people actually choose under uncertainty, and how frami…", "trigger": "Applies decision science and cognitive bias research to marketing and product decisions — how people actually choose under uncertainty, and how framing, defaults, sequencing, and social context change behavior. Use this to diagnose why a well-argued offer is not converting, to structure choices and pricing presentation, to design an experience around how attention and memory work, or to pressure-test whether a persuasion tactic is legitimate or manipulative.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/behavioral-marketing/SKILL.md"}, {"name": "brand-voice", "summary": "Captures how a person or brand actually writes and turns it into reusable voice instructions every other content skill draws from", "trigger": "Captures how a person or brand actually writes and turns it into reusable voice instructions every other content skill draws from. Use this before drafting any content for a new brand or client, when output keeps coming back sounding generic, when several writers need to sound like one, or when a voice needs defining without existing samples to learn from.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/brand-voice/SKILL.md"}, {"name": "chief-content-officer", "summary": "Runs content as an operation — the production pipeline, editorial calendar, repurposing engine, competitive content intelligence, and audits of what…", "trigger": "Runs content as an operation — the production pipeline, editorial calendar, repurposing engine, competitive content intelligence, and audits of what already exists. Use this to build or fix a content production system, plan a calendar, decide how one piece becomes many, rank content ideas by expected impact, or audit an existing library for what to update, consolidate, or retire. For deciding what territory to own and why, use `content-strategy` first.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/chief-content-officer/SKILL.md"}, {"name": "chief-marketing-officer", "summary": "Owns brand, demand generation, content, communications, and how the market understands what the business does", "trigger": "Owns brand, demand generation, content, communications, and how the market understands what the business does. Use this to set marketing strategy, allocate budget across channels, decide positioning and messaging, judge whether a campaign is worth running, diagnose why demand has stalled, or arbitrate between brand-building and short-term acquisition. Also use to decide which marketing work to stop.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/chief-marketing-officer/SKILL.md"}, {"name": "content-strategy", "summary": "Decides what content to make and why — topic territory, format mix, cadence, and how content connects to a business outcome rather than to traffic", "trigger": "Decides what content to make and why — topic territory, format mix, cadence, and how content connects to a business outcome rather than to traffic. Use this to plan a content program, choose topics, build an editorial calendar, decide which formats and platforms to commit to, or diagnose why content is producing audience but not results.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/content-strategy/SKILL.md"}, {"name": "customer-research", "summary": "Plans, runs, and synthesizes customer research — interviews, surveys, win-loss analysis, and message testing — into findings that change decisions", "trigger": "Plans, runs, and synthesizes customer research — interviews, surveys, win-loss analysis, and message testing — into findings that change decisions. Use this when the customer is being guessed at, before positioning or a major launch, when churn or conversion has an unexplained cause, or when a team is arguing from anecdotes. Also use to turn raw interview notes into usable findings.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/customer-research/SKILL.md"}, {"name": "marketing-campaign-planner", "summary": "Designs a coordinated multi-channel campaign or product launch around one story — objective, message, channel sequencing, timeline, assets, and the c…", "trigger": "Designs a coordinated multi-channel campaign or product launch around one story — objective, message, channel sequencing, timeline, assets, and the checklist that gets it out the door. Use this to plan a launch or campaign, sequence a go-to-market push, pressure-test a campaign before committing budget, or turn a product change into a coordinated set of activity. For ongoing channel programs rather than a bounded push, use `marketing-planning`.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/marketing-campaign-planner/SKILL.md"}, {"name": "marketing-copywriting", "summary": "Writes and edits marketing copy for any surface — homepage, product and pricing pages, ads, emails, and collateral — and sharpens existing copy that…", "trigger": "Writes and edits marketing copy for any surface — homepage, product and pricing pages, ads, emails, and collateral — and sharpens existing copy that is not working. Use this to write or rewrite page copy, tighten a draft, fix copy that is vague or feature-led, adapt one message across formats, or review copy before it ships.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/marketing-copywriting/SKILL.md"}, {"name": "marketing-planning", "summary": "Builds the marketing plan of record — objectives, channel mix, budget allocation, sequencing, and the measurement that says whether it worked", "trigger": "Builds the marketing plan of record — objectives, channel mix, budget allocation, sequencing, and the measurement that says whether it worked. Use this for annual or quarterly planning, when budget must be allocated or defended, when marketing activity feels busy but undirected, or when a plan needs pressure-testing before commitment.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/marketing-planning/SKILL.md"}, {"name": "newsletter-writer", "summary": "Writes and edits newsletters and marketing emails people actually open — subject lines, opening, structure, voice, and the conversion turn where ther…", "trigger": "Writes and edits newsletters and marketing emails people actually open — subject lines, opening, structure, voice, and the conversion turn where there is one. Use this to draft or rewrite a newsletter or email, sharpen weak email copy, plan a newsletter's structure and cadence, write a sequence, or repurpose an issue into other formats. For automated lifecycle and SMS programs, use `lifecycle-messaging`.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/newsletter-writer/SKILL.md"}, {"name": "partnership-marketing", "summary": "Builds reach through other people's audiences — co-marketing partnerships, creator and influencer programs, community building, and affiliate arrange…", "trigger": "Builds reach through other people's audiences — co-marketing partnerships, creator and influencer programs, community building, and affiliate arrangements. Use this to find and evaluate partners, structure a joint campaign or creator deal, plan a community strategy, or decide whether a partnership is worth the coordination cost.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/partnership-marketing/SKILL.md"}, {"name": "positioning-and-messaging", "summary": "Establishes what a product is understood to be, for whom, and instead of what — then turns that into the messaging every other surface inherits", "trigger": "Establishes what a product is understood to be, for whom, and instead of what — then turns that into the messaging every other surface inherits. Use this when messaging is inconsistent across channels, when prospects misunderstand what the product does, when entering a new segment, when competitors are being compared against you unfavorably, or before any campaign, launch, or site rewrite.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/positioning-and-messaging/SKILL.md"}, {"name": "public-relations", "summary": "Plans and executes earned media — press strategy, journalist outreach, announcements, commentary, and crisis response", "trigger": "Plans and executes earned media — press strategy, journalist outreach, announcements, commentary, and crisis response. Use this to plan a press push, write a pitch or release, find and approach the right journalists, prepare for an interview, decide whether something is newsworthy, or respond to a story going badly.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/public-relations/SKILL.md"}, {"name": "social-post-craft", "summary": "Writes, structures, and evaluates social posts end to end — hooks, body, formatting for how each platform renders, and a quality check before publish…", "trigger": "Writes, structures, and evaluates social posts end to end — hooks, body, formatting for how each platform renders, and a quality check before publishing. Use this to draft a post, rewrite one that underperformed, turn a longer piece into social content, sharpen an opening, or judge whether a draft is worth publishing.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/social-post-craft/SKILL.md"}, {"name": "video-content", "summary": "Plans and scripts short-form and long-form video, and designs the packaging — titles, thumbnails, and openings — that determines whether it gets watc…", "trigger": "Plans and scripts short-form and long-form video, and designs the packaging — titles, thumbnails, and openings — that determines whether it gets watched. Use this to script a video, plan a series, fix retention or click-through problems, design thumbnail and title concepts, or turn written content into video.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/video-content/SKILL.md"}, {"name": "visual-content", "summary": "Designs and directs the visual assets that carry content — carousels, infographics, quote graphics, diagrams, and social imagery — including the gene…", "trigger": "Designs and directs the visual assets that carry content — carousels, infographics, quote graphics, diagrams, and social imagery — including the generation prompts where they are AI-produced. Use this to turn a written piece into a visual format, design a carousel or infographic, create social graphics, or fix visuals that are not stopping the scroll.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/visual-content/SKILL.md"}, {"name": "youtube-producer", "summary": "Plans, packages, and scripts long-form video for retention and channel growth — idea selection, titles and thumbnails, script structure, and diagnosi…", "trigger": "Plans, packages, and scripts long-form video for retention and channel growth — idea selection, titles and thumbnails, script structure, and diagnosing why a video or channel underperforms. Use this for video ideas, packaging, scripting, a retention teardown, or channel strategy — including when someone describes a topic and wants it turned into something publishable. For short-form and cross-platform video, use `video-content`.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/marketing/skills/youtube-producer/SKILL.md"}]}, {"slug": "demand-generation", "title": "Demand Generation", "exec": "CMO", "reviewer": false, "skills": [{"name": "ai-search-optimization", "summary": "Optimizes for AI assistants and AI-generated answers — being retrievable, being cited, and being represented accurately when a model answers on your…", "trigger": "Optimizes for AI assistants and AI-generated answers — being retrievable, being cited, and being represented accurately when a model answers on your behalf. Use this when traffic is shifting from links to AI answers, when a brand is misrepresented or absent in AI responses, when planning content for retrieval rather than ranking, or when deciding how AI search changes an existing SEO program.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/ai-search-optimization/SKILL.md"}, {"name": "app-store-optimization", "summary": "Improves visibility and conversion in the App Store and Google Play — metadata, keywords, screenshots, ratings, and the listing experience that turns…", "trigger": "Improves visibility and conversion in the App Store and Google Play — metadata, keywords, screenshots, ratings, and the listing experience that turns an impression into an install. Use this to audit or optimize an app listing, plan a launch listing, diagnose poor install conversion, or improve store search visibility.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/app-store-optimization/SKILL.md"}, {"name": "experimentation", "summary": "Designs, runs, and reads A/B tests and growth experiments — hypothesis, sample size, duration, and honest interpretation", "trigger": "Designs, runs, and reads A/B tests and growth experiments — hypothesis, sample size, duration, and honest interpretation. Use this to plan a test, judge whether a result is real, build an experimentation program, decide what to test next, or diagnose why tests keep producing inconclusive or non-replicating results.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/experimentation/SKILL.md"}, {"name": "landing-page-cro-expert", "summary": "Audits and rewrites landing pages, homepages, and sales pages to increase conversion — diagnosing why a page is not converting, rewriting headlines,…", "trigger": "Audits and rewrites landing pages, homepages, and sales pages to increase conversion — diagnosing why a page is not converting, rewriting headlines, hero copy and calls to action, and prioritizing which changes to test first. Use this when a page underperforms, when someone pastes a URL or screenshot asking what is wrong, when writing a new page, or when deciding which conversion changes are worth testing.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/landing-page-cro-expert/SKILL.md"}, {"name": "lead-capture", "summary": "Converts anonymous traffic into known contacts — lead magnets, gated content, free tools, popups, and the forms behind them", "trigger": "Converts anonymous traffic into known contacts — lead magnets, gated content, free tools, popups, and the forms behind them. Use this to design or improve a lead magnet, plan a free tool, add or fix popups and overlays, improve form conversion, or decide what is worth gating and what should stay open.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/lead-capture/SKILL.md"}, {"name": "lifecycle-messaging", "summary": "Designs automated email and SMS programs — welcome and onboarding sequences, nurture, re-engagement, transactional messaging, and the timing and segm…", "trigger": "Designs automated email and SMS programs — welcome and onboarding sequences, nurture, re-engagement, transactional messaging, and the timing and segmentation behind them. Use this to build or fix an email sequence, plan lifecycle automation, improve open or click performance, set up SMS flows, or decide what messages a customer should receive and when.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/lifecycle-messaging/SKILL.md"}, {"name": "listing-distribution", "summary": "Gets a product listed where buyers and crawlers look — directories, marketplaces, review sites, comparison pages, and aggregators", "trigger": "Gets a product listed where buyers and crawlers look — directories, marketplaces, review sites, comparison pages, and aggregators. Use this to plan a submission push, choose which directories are worth the effort, prepare listing assets, build comparison and alternative pages, or manage presence on review platforms.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/listing-distribution/SKILL.md"}, {"name": "marketing-analytics", "summary": "Sets up, audits, and reports on marketing measurement — tracking plans, event schemas, attribution models, and the dashboards built on them", "trigger": "Sets up, audits, and reports on marketing measurement — tracking plans, event schemas, attribution models, and the dashboards built on them. Use this to instrument a site or product, audit tracking nobody trusts, choose or interpret an attribution model, build reporting that answers a specific question, or reconcile numbers that disagree between tools.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/marketing-analytics/SKILL.md"}, {"name": "paid-advertising", "summary": "Plans, runs, and optimizes paid acquisition across search, social, and display — account structure, targeting, creative, bidding, budget, and the ana…", "trigger": "Plans, runs, and optimizes paid acquisition across search, social, and display — account structure, targeting, creative, bidding, budget, and the analysis that says whether to scale or stop. Use this to set up or restructure campaigns, write and iterate ad creative, diagnose rising costs or falling performance, decide budget allocation, or judge whether a channel is working.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/paid-advertising/SKILL.md"}, {"name": "programmatic-seo", "summary": "Builds large sets of search-targeted pages from a template and a dataset — the location, comparison, integration, and use-case pages that capture lon…", "trigger": "Builds large sets of search-targeted pages from a template and a dataset — the location, comparison, integration, and use-case pages that capture long-tail demand at scale. Use this when there is a repeating query pattern with real volume, when a dataset could answer many similar searches, or to judge whether a programmatic approach is viable before building it.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/programmatic-seo/SKILL.md"}, {"name": "seo-strategy", "summary": "Audits and improves organic search performance — technical health, site architecture, internal linking, structured data, and the content decisions th…", "trigger": "Audits and improves organic search performance — technical health, site architecture, internal linking, structured data, and the content decisions that determine what can rank. Use this to run an SEO audit, diagnose why pages are not ranking or were deindexed, plan a site's URL and navigation structure, add structured data, or prioritize which SEO fixes are worth doing.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/demand-generation/skills/seo-strategy/SKILL.md"}]}, {"slug": "revenue", "title": "Revenue", "exec": "CRO", "reviewer": false, "skills": [{"name": "activation", "summary": "Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone bec…", "trigger": "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.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/revenue/skills/activation/SKILL.md"}, {"name": "chief-revenue-officer", "summary": "Owns the revenue engine end to end: sales, monetization, pricing, customer success, retention, and partnerships", "trigger": "Owns the revenue engine end to end: sales, monetization, pricing, customer success, retention, and partnerships. Use this for pricing and packaging decisions, sales strategy and coverage, forecast and pipeline health, churn and expansion, partner and channel strategy, or when marketing-sourced demand is not converting. Also use to decide which segments to pursue and which to decline.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/revenue/skills/chief-revenue-officer/SKILL.md"}, {"name": "outbound-prospecting", "summary": "Finds, qualifies, and reaches prospects through cold outreach — list building, qualification criteria, cold email and multi-channel sequences, and th…", "trigger": "Finds, qualifies, and reaches prospects through cold outreach — list building, qualification criteria, cold email and multi-channel sequences, and the follow-up that actually gets replies. Use this to build a prospect list, write cold outreach, fix a sequence that is not getting responses, define qualification criteria, or decide whether a segment is worth pursuing.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/revenue/skills/outbound-prospecting/SKILL.md"}, {"name": "pricing-and-packaging", "summary": "Sets price, structures packages and tiers, and designs the monetization surfaces that carry them — upgrade paths, paywalls, and offer construction", "trigger": "Sets price, structures packages and tiers, and designs the monetization surfaces that carry them — upgrade paths, paywalls, and offer construction. Use this to set or change pricing, design or restructure tiers, choose a pricing metric, build an offer, design upgrade prompts and paywalls, or evaluate whether a pricing change is safe to make.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/revenue/skills/pricing-and-packaging/SKILL.md"}, {"name": "referral-programs", "summary": "Designs and improves referral, affiliate, and word-of-mouth programs — incentive structure, mechanics, timing, and fraud control", "trigger": "Designs and improves referral, affiliate, and word-of-mouth programs — incentive structure, mechanics, timing, and fraud control. Use this to build a referral or affiliate program, diagnose one that is not producing, decide what incentive to offer, or judge whether referral is a realistic channel for a product.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/revenue/skills/referral-programs/SKILL.md"}, {"name": "retention", "summary": "Diagnoses and reduces churn — cancellation flows, save offers, failed-payment recovery, at-risk detection, and the product and service causes underne…", "trigger": "Diagnoses and reduces churn — cancellation flows, save offers, failed-payment recovery, at-risk detection, and the product and service causes underneath. Use this when churn is rising or unexplained, to design a cancellation or win-back flow, to recover involuntary churn, to identify at-risk accounts before they leave, or to decide whether a retention problem is a product problem.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/revenue/skills/retention/SKILL.md"}, {"name": "revenue-operations", "summary": "Runs the mechanics of the revenue engine — lead lifecycle definitions, routing, CRM hygiene, forecasting process, pipeline reporting, and the marketi…", "trigger": "Runs the mechanics of the revenue engine — lead lifecycle definitions, routing, CRM hygiene, forecasting process, pipeline reporting, and the marketing-to-sales handoff. Use this to fix a broken handoff, define lifecycle stages, improve forecast accuracy, clean up CRM data, design territory or routing rules, or diagnose why pipeline numbers are not trusted.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/revenue/skills/revenue-operations/SKILL.md"}, {"name": "sales-enablement", "summary": "Builds what a sales team needs to sell — pitch decks, one-pagers, objection handling, competitive battlecards, demo scripts, and case studies", "trigger": "Builds what a sales team needs to sell — pitch decks, one-pagers, objection handling, competitive battlecards, demo scripts, and case studies. Use this to create or fix sales collateral, prepare for a competitive deal, build a demo flow, document objection responses, or diagnose why a pitch is not converting.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/revenue/skills/sales-enablement/SKILL.md"}]}, {"slug": "finance", "title": "Finance", "exec": "CFO", "reviewer": false, "skills": [{"name": "budgeting-and-forecasting", "summary": "Runs the planning cycle — annual budget, rolling forecast, consolidation of business unit inputs, and the variance analysis that explains actuals aga…", "trigger": "Runs the planning cycle — annual budget, rolling forecast, consolidation of business unit inputs, and the variance analysis that explains actuals against plan. Use this to build or challenge a budget, run a forecast cycle, consolidate departmental submissions, explain why results diverged from plan, or improve forecast accuracy.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/budgeting-and-forecasting/SKILL.md"}, {"name": "capital-allocation", "summary": "Evaluates where to spend limited capital — investment appraisal, hurdle rates, payback, and comparing proposals that are not alike", "trigger": "Evaluates where to spend limited capital — investment appraisal, hurdle rates, payback, and comparing proposals that are not alike. Use this to evaluate an investment or major purchase, compare competing funding requests, set a hurdle rate, decide between building and buying, or review whether past investments delivered what was claimed.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/capital-allocation/SKILL.md"}, {"name": "chief-financial-officer", "summary": "Owns the financial position: planning, budgeting, forecasting, unit economics, cash, and the numbers the business is run and reported on", "trigger": "Owns the financial position: planning, budgeting, forecasting, unit economics, cash, and the numbers the business is run and reported on. Use this to build or challenge a budget, model a decision's financial consequence, assess unit economics or runway, evaluate an investment or spend request, set financial controls, or when a plan's numbers do not reconcile. Also use to decide whether the business can afford something.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/chief-financial-officer/SKILL.md"}, {"name": "financial-modeling", "summary": "Builds and stress-tests financial models for forecasting, scenario planning, and decision support — revenue build, cost structure, driver logic, and…", "trigger": "Builds and stress-tests financial models for forecasting, scenario planning, and decision support — revenue build, cost structure, driver logic, and the sensitivities that show where a plan breaks. Use this to model a decision's financial consequence, build a forecast or long-range plan, evaluate an investment or hire, or pressure-test someone else's model before relying on it.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/financial-modeling/SKILL.md"}, {"name": "financial-reporting-and-close", "summary": "Runs the period-end close and produces reporting — close calendar, reconciliations, accruals, variance analysis, and reporting that gets read", "trigger": "Runs the period-end close and produces reporting — close calendar, reconciliations, accruals, variance analysis, and reporting that gets read. Use this to shorten or stabilise a monthly close, design a close checklist, investigate a variance, structure management reporting, or work out why the numbers keep changing after close.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/financial-reporting-and-close/SKILL.md"}, {"name": "internal-controls-and-audit", "summary": "Designs and tests controls over financial reporting — segregation of duties, approval limits, evidence, and preparing for audit", "trigger": "Designs and tests controls over financial reporting — segregation of duties, approval limits, evidence, and preparing for audit. Use this to design controls for a process, prepare for an external audit, respond to an audit finding, set approval thresholds, or assess where a small team's segregation of duties is genuinely broken.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/internal-controls-and-audit/SKILL.md"}, {"name": "revenue-recognition", "summary": "Determines when and how revenue is recognized — performance obligations, contract terms that change the answer, and the deal structures that create a…", "trigger": "Determines when and how revenue is recognized — performance obligations, contract terms that change the answer, and the deal structures that create accounting problems. Use this to work out how a contract should be recognized, review a non-standard deal before it is signed, understand deferred revenue, or spot terms that would delay or reverse recognition.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/revenue-recognition/SKILL.md"}, {"name": "treasury-and-liquidity", "summary": "Manages cash and liquidity — cash forecasting, runway, working capital, banking structure, and currency and counterparty exposure", "trigger": "Manages cash and liquidity — cash forecasting, runway, working capital, banking structure, and currency and counterparty exposure. Use this to build a cash forecast, extend runway, improve working capital, decide where cash should sit, or assess exposure to a bank, currency, or customer concentration.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/treasury-and-liquidity/SKILL.md"}, {"name": "unit-economics", "summary": "Establishes whether the business makes money on each customer or unit — contribution margin, acquisition cost, payback period, lifetime value, and th…", "trigger": "Establishes whether the business makes money on each customer or unit — contribution margin, acquisition cost, payback period, lifetime value, and the cohort behavior underneath. Use this to assess whether growth is profitable, evaluate a channel or segment, support a pricing decision, judge how fast the business can afford to grow, or diagnose why revenue growth is not producing profit.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/finance/skills/unit-economics/SKILL.md"}]}, {"slug": "operations", "title": "Operations", "exec": "COO", "reviewer": false, "skills": [{"name": "business-continuity-and-resilience", "summary": "Plans for operating through disruption — impact analysis, recovery objectives, continuity plans, and the exercises that prove they work", "trigger": "Plans for operating through disruption — impact analysis, recovery objectives, continuity plans, and the exercises that prove they work. Use this to run a business impact analysis, set RTO and RPO, write or test a continuity plan, prepare for a supplier or site failure, or answer a customer's resilience questionnaire.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/operations/skills/business-continuity-and-resilience/SKILL.md"}, {"name": "capacity-and-demand-planning", "summary": "Matches operational capacity to expected demand — forecasting load, sizing teams and systems, managing queues, and deciding when to add capacity", "trigger": "Matches operational capacity to expected demand — forecasting load, sizing teams and systems, managing queues, and deciding when to add capacity. Use this to plan staffing for expected volume, diagnose a queue that keeps growing, size support or fulfillment capacity, or decide whether a bottleneck needs more capacity or better flow.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/operations/skills/capacity-and-demand-planning/SKILL.md"}, {"name": "chief-operating-officer", "summary": "Owns execution: how work actually gets done across the organization, including process, program management, capacity, vendors, supply chain, and serv…", "trigger": "Owns execution: how work actually gets done across the organization, including process, program management, capacity, vendors, supply chain, and service delivery. Use this when execution is the problem rather than strategy, to design or fix a process, to resolve cross-functional handoff failures, to plan capacity, to assess delivery risk, or when the same failure keeps recurring. Also use to decide whether to build, hire, or outsource a capability.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/operations/skills/chief-operating-officer/SKILL.md"}, {"name": "process-design", "summary": "Designs, documents, and fixes operational processes — mapping the current state, finding where work actually stalls, redesigning the flow, and buildi…", "trigger": "Designs, documents, and fixes operational processes — mapping the current state, finding where work actually stalls, redesigning the flow, and building controls that hold. Use this when the same failure keeps recurring, when a handoff between teams is unreliable, when onboarding a repeated task, when work takes far longer than the work itself, or when deciding whether to automate, standardize, or eliminate a process.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/operations/skills/process-design/SKILL.md"}, {"name": "quality-management", "summary": "Builds quality into operations — defining standards, catching defects at the right point, root cause analysis, and continuous improvement", "trigger": "Builds quality into operations — defining standards, catching defects at the right point, root cause analysis, and continuous improvement. Use this to reduce a defect or error rate, design quality controls into a process, run a root cause analysis, respond to a customer quality complaint, or set up quality metrics that drive behavior.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/operations/skills/quality-management/SKILL.md"}, {"name": "service-level-management", "summary": "Defines and manages service levels — setting targets that reflect what customers need, measuring honestly, and handling breaches", "trigger": "Defines and manages service levels — setting targets that reflect what customers need, measuring honestly, and handling breaches. Use this to write or negotiate an SLA, decide what to measure and at what threshold, respond to a missed service level, or work out why a service that meets its targets still has unhappy customers.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/operations/skills/service-level-management/SKILL.md"}, {"name": "supply-chain-and-logistics", "summary": "Manages the flow of goods and inputs — sourcing, inventory, lead times, fulfillment, and supply risk", "trigger": "Manages the flow of goods and inputs — sourcing, inventory, lead times, fulfillment, and supply risk. Use this to reduce stockouts or excess inventory, plan for a supplier failure, decide reorder points and safety stock, improve fulfillment reliability, or assess concentration risk in a supply base.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/operations/skills/supply-chain-and-logistics/SKILL.md"}, {"name": "vendor-management", "summary": "Selects, contracts, and manages suppliers and vendors — requirements, evaluation, negotiation support, onboarding, performance management, and exit", "trigger": "Selects, contracts, and manages suppliers and vendors — requirements, evaluation, negotiation support, onboarding, performance management, and exit. Use this to choose a vendor, run a selection process, structure a service agreement's operational terms, manage an underperforming supplier, plan an exit or migration, or assess concentration and continuity risk.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/operations/skills/vendor-management/SKILL.md"}]}, {"slug": "pmo", "title": "Program Management Office", "exec": "EPMO / COO", "reviewer": false, "skills": [{"name": "benefits-realization", "summary": "Ensures projects deliver the value they were approved on — defining measurable benefits, baselining, tracking after delivery, and honest post-impleme…", "trigger": "Ensures projects deliver the value they were approved on — defining measurable benefits, baselining, tracking after delivery, and honest post-implementation review. Use this to define benefits for a business case, set a baseline, track whether value actually landed, or run a post-implementation review that produces something useful.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/pmo/skills/benefits-realization/SKILL.md"}, {"name": "change-and-adoption", "summary": "Gets people to actually use what was delivered — stakeholder analysis, communication, training, resistance, and measuring adoption", "trigger": "Gets people to actually use what was delivered — stakeholder analysis, communication, training, resistance, and measuring adoption. Use this to plan a rollout, recover an implementation nobody is using, handle resistance to a change, sequence communications, or work out why a technically successful project changed nothing.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/pmo/skills/change-and-adoption/SKILL.md"}, {"name": "dependency-and-risk-management", "summary": "Manages delivery risk and cross-team dependencies — identifying, sizing, mitigating and escalating what could stop the work", "trigger": "Manages delivery risk and cross-team dependencies — identifying, sizing, mitigating and escalating what could stop the work. Use this to build a risk register that gets used, manage dependencies between teams, decide what to escalate and when, or work out why the same risks keep materialising unmanaged.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/pmo/skills/dependency-and-risk-management/SKILL.md"}, {"name": "portfolio-governance", "summary": "Governs the portfolio of work — intake, prioritization, stage gates, resource contention, and stopping things", "trigger": "Governs the portfolio of work — intake, prioritization, stage gates, resource contention, and stopping things. Use this to set up intake and prioritization, run a stage gate, decide between competing initiatives, resolve resource contention across projects, or work out why everything is in flight and nothing is finishing.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/pmo/skills/portfolio-governance/SKILL.md"}, {"name": "program-management", "summary": "Plans and drives cross-functional programs to delivery — scope, sequencing, dependencies, status, risk, and the escalations that keep work moving", "trigger": "Plans and drives cross-functional programs to delivery — scope, sequencing, dependencies, status, risk, and the escalations that keep work moving. Use this to run a multi-team initiative, recover a program that is slipping, build a delivery plan with dependencies, structure status reporting, or diagnose why cross-team work keeps missing dates.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/pmo/skills/program-management/SKILL.md"}, {"name": "project-delivery", "summary": "Plans and delivers a single project — scope, estimation, scheduling, critical path, tracking, and recovering when it slips", "trigger": "Plans and delivers a single project — scope, estimation, scheduling, critical path, tracking, and recovering when it slips. Use this to plan a project, build or challenge a schedule, estimate credibly, track progress meaningfully, or recover a project that is late.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/pmo/skills/project-delivery/SKILL.md"}]}, {"slug": "customer-experience", "title": "Customer Experience", "exec": "CCO", "reviewer": false, "skills": [{"name": "chief-customer-officer", "summary": "Owns the customer's experience after the sale — support, success, escalation, and the feedback loop back into product", "trigger": "Owns the customer's experience after the sale — support, success, escalation, and the feedback loop back into product. Use this for a decision spanning support and product, when service quality and cost are in tension, when deciding what to staff or automate, when a customer relationship is at risk above the account-manager level, or when nobody owns a recurring customer problem.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/customer-experience/skills/chief-customer-officer/SKILL.md"}, {"name": "escalation-management", "summary": "Handles customer situations that have exceeded normal support — severity assessment, incident communication, executive escalation, and recovering a r…", "trigger": "Handles customer situations that have exceeded normal support — severity assessment, incident communication, executive escalation, and recovering a relationship after a failure. Use this when a customer issue is escalating or has gone to leadership, during a customer-affecting outage, when a major account is at risk, when a relationship needs repairing after a failure, or to design the escalation path itself.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/customer-experience/skills/escalation-management/SKILL.md"}, {"name": "self-service-and-knowledge", "summary": "Builds the help center, in-product guidance, and knowledge base that let customers resolve problems without contacting anyone — content, findability,…", "trigger": "Builds the help center, in-product guidance, and knowledge base that let customers resolve problems without contacting anyone — content, findability, maintenance, and deflection measurement. Use this to build or fix a help center, reduce support volume, write documentation for customers, improve findability, or decide what deserves a help article versus a product fix.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/customer-experience/skills/self-service-and-knowledge/SKILL.md"}, {"name": "support-operations", "summary": "Designs and runs the support function — channels, queues, routing, staffing, service levels, quality, and the metrics that show whether it is working", "trigger": "Designs and runs the support function — channels, queues, routing, staffing, service levels, quality, and the metrics that show whether it is working. Use this to set up or fix support operations, choose channels, size a team, set or renegotiate service levels, reduce cost per contact, diagnose long queues or poor quality, or decide what to automate.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/customer-experience/skills/support-operations/SKILL.md"}, {"name": "voice-of-customer", "summary": "Builds the loop from what customers say to what gets changed — collecting feedback, distinguishing signal from noise, routing it to owners, and closi…", "trigger": "Builds the loop from what customers say to what gets changed — collecting feedback, distinguishing signal from noise, routing it to owners, and closing the loop back to the customer. Use this to set up a feedback program, design or interpret CSAT/NPS, decide what customer feedback deserves action, get product to act on recurring issues, or diagnose why feedback is collected but nothing changes.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/customer-experience/skills/voice-of-customer/SKILL.md"}]}, {"slug": "data-analytics", "title": "Data & Analytics", "exec": "CDO", "reviewer": false, "skills": [{"name": "ai-ml-governance", "summary": "Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or ret…", "trigger": "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.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/data-analytics/skills/ai-ml-governance/SKILL.md"}, {"name": "business-intelligence", "summary": "Builds reporting and self-serve analytics that people actually use — metric trees, dashboard design, distribution, and the discipline that stops dash…", "trigger": "Builds reporting and self-serve analytics that people actually use — metric trees, dashboard design, distribution, and the discipline that stops dashboards proliferating. Use this to build a dashboard or report, design a metrics framework, set up self-serve analytics, decide what to measure, or diagnose why reporting exists but nobody uses it or trusts it.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/data-analytics/skills/business-intelligence/SKILL.md"}, {"name": "chief-data-officer", "summary": "Owns data as an asset — governance, quality, the warehouse and semantic layer, analytics capability, and the governance of models built on top", "trigger": "Owns data as an asset — governance, quality, the warehouse and semantic layer, analytics capability, and the governance of models built on top. Use this for a decision about how data is collected, stored, defined, or shared; when numbers disagree between teams; when deciding what to build in-house versus buy; when standing up a data function; or when an AI or model decision needs governance rather than engineering.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/data-analytics/skills/chief-data-officer/SKILL.md"}, {"name": "data-engineering", "summary": "Builds and operates data pipelines — ingestion, transformation, orchestration, quality testing, and reliability of data delivery", "trigger": "Builds and operates data pipelines — ingestion, transformation, orchestration, quality testing, and reliability of data delivery. Use this to design or debug a pipeline, decide batch versus streaming, add data quality checks, handle late or duplicate data, or work out why a dashboard's numbers changed without anyone changing the dashboard.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/data-analytics/skills/data-engineering/SKILL.md"}, {"name": "data-governance", "summary": "Establishes ownership, definitions, quality, access, and lineage for the organization's data", "trigger": "Establishes ownership, definitions, quality, access, and lineage for the organization's data. Use this when metrics disagree between teams, when nobody knows which dataset is authoritative, when setting up data ownership or access policy, when data quality is unreliable, or before opening a dataset to a wider audience.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/data-analytics/skills/data-governance/SKILL.md"}, {"name": "data-modeling", "summary": "Designs the warehouse and semantic layer — source-to-mart structure, dimensional modeling, grain, slowly changing dimensions, and the metric layer an…", "trigger": "Designs the warehouse and semantic layer — source-to-mart structure, dimensional modeling, grain, slowly changing dimensions, and the metric layer analytics reads through. Use this to design or restructure a warehouse, model a new source, decide on grain or table structure, build a semantic or metric layer, or diagnose why queries are slow, wrong, or impossible to write.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/data-analytics/skills/data-modeling/SKILL.md"}]}, {"slug": "corporate-strategy", "title": "Corporate Strategy", "exec": "CSO", "reviewer": false, "skills": [{"name": "chief-strategy-officer", "summary": "Owns where the business plays and how it wins over a multi-year horizon — portfolio choices, corporate development, strategic partnerships, and plann…", "trigger": "Owns where the business plays and how it wins over a multi-year horizon — portfolio choices, corporate development, strategic partnerships, and planning under uncertainty. Use this for a decision about which markets or businesses to be in, whether to build, buy, or partner, how to allocate capital across business lines, or when a long-horizon bet needs framing. Distinct from `chief-executive`, which arbitrates present-quarter conflicts.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/corporate-strategy/skills/chief-strategy-officer/SKILL.md"}, {"name": "mergers-and-acquisitions", "summary": "Runs corporate development — deal thesis, target screening, valuation framing, diligence, and integration planning", "trigger": "Runs corporate development — deal thesis, target screening, valuation framing, diligence, and integration planning. Use this when considering an acquisition or being approached about one, when evaluating build-versus-buy at company scale, when running or reviewing diligence, or when planning how an acquired business will actually be integrated.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/corporate-strategy/skills/mergers-and-acquisitions/SKILL.md"}, {"name": "portfolio-strategy", "summary": "Decides where capital and attention go across business lines, products, and markets — what to fund, hold, harvest, or exit, and on what evidence", "trigger": "Decides where capital and attention go across business lines, products, and markets — what to fund, hold, harvest, or exit, and on what evidence. Use this to allocate budget across businesses, evaluate whether a product line should continue, decide market entry or exit, structure a portfolio review, or when several initiatives compete for the same limited investment.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/corporate-strategy/skills/portfolio-strategy/SKILL.md"}, {"name": "scenario-planning", "summary": "Plans under genuine uncertainty — building scenarios, identifying which assumptions are load-bearing, setting early-warning indicators, and stress-te…", "trigger": "Plans under genuine uncertainty — building scenarios, identifying which assumptions are load-bearing, setting early-warning indicators, and stress-testing a plan against futures rather than forecasting one. Use this when a decision depends on something unknowable, when a plan assumes conditions that may not hold, before a large irreversible commitment, or when a market, regulatory, or technology shift could invalidate the strategy.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/corporate-strategy/skills/scenario-planning/SKILL.md"}, {"name": "strategic-alliances", "summary": "Structures partnerships that change what the business can do — technology integrations, channel and reseller arrangements, joint ventures, and OEM re…", "trigger": "Structures partnerships that change what the business can do — technology integrations, channel and reseller arrangements, joint ventures, and OEM relationships. Use this to evaluate or structure a strategic partnership, decide between partnering and building, negotiate commercial terms of an alliance, or diagnose a partnership that is signed but not producing. For audience-borrowing partnerships, use `marketing:partnership-marketing`.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/corporate-strategy/skills/strategic-alliances/SKILL.md"}]}, {"slug": "people", "title": "People", "exec": "CHRO", "reviewer": false, "skills": [{"name": "chief-human-resources-officer", "summary": "Owns the organization itself: org design, hiring, performance, compensation, development, culture, and employee relations", "trigger": "Owns the organization itself: org design, hiring, performance, compensation, development, culture, and employee relations. Use this to design or restructure a team, plan hiring, write a role or leveling definition, handle a performance or compensation question, diagnose why a team is underperforming for non-technical reasons, or assess the people risk in a plan. Also use for onboarding design and retention of key staff.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/chief-human-resources-officer/SKILL.md"}, {"name": "compensation-and-leveling", "summary": "Builds and maintains the leveling framework and pay structure — level definitions, salary bands, benchmarking, pay equity, and how raises and promoti…", "trigger": "Builds and maintains the leveling framework and pay structure — level definitions, salary bands, benchmarking, pay equity, and how raises and promotions are decided. Use this to design or revise leveling, set or adjust salary bands, benchmark against market, handle a compensation request or counteroffer, run a review cycle, or diagnose pay compression and equity issues.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/compensation-and-leveling/SKILL.md"}, {"name": "employee-relations", "summary": "Handles the difficult human situations — grievances, complaints, investigations, conflict, and separations conducted properly", "trigger": "Handles the difficult human situations — grievances, complaints, investigations, conflict, and separations conducted properly. Use this to respond to a complaint or grievance, structure an investigation, handle a conflict between colleagues, prepare for a difficult conversation, or work out what a manager can and cannot do in a given situation.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/employee-relations/SKILL.md"}, {"name": "hiring-and-interviewing", "summary": "Designs and runs hiring — role definition, sourcing, interview loop design, structured evaluation, and the decision itself", "trigger": "Designs and runs hiring — role definition, sourcing, interview loop design, structured evaluation, and the decision itself. Use this to open a role, write a job description or scorecard, design an interview process, prepare interview questions, calibrate a hiring decision, or diagnose why a hiring process produces poor outcomes.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/hiring-and-interviewing/SKILL.md"}, {"name": "learning-and-development", "summary": "Builds capability — skills gaps, career frameworks, training that transfers to the job, and internal mobility", "trigger": "Builds capability — skills gaps, career frameworks, training that transfers to the job, and internal mobility. Use this to design a career ladder, close a capability gap, decide whether to build or hire a skill, structure onboarding into a role, or work out why training keeps failing to change anything.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/learning-and-development/SKILL.md"}, {"name": "onboarding-and-offboarding", "summary": "Designs the joining and leaving experience — first-day readiness, ramp to productivity, knowledge capture, and clean exits", "trigger": "Designs the joining and leaving experience — first-day readiness, ramp to productivity, knowledge capture, and clean exits. Use this to design or fix onboarding, shorten time to productivity, structure a leaver process, capture knowledge before someone leaves, or coordinate the access and asset steps around a joiner or leaver.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/onboarding-and-offboarding/SKILL.md"}, {"name": "org-design", "summary": "Designs how an organization is structured — reporting lines, team boundaries, spans and layers, role definition, and workforce planning against the s…", "trigger": "Designs how an organization is structured — reporting lines, team boundaries, spans and layers, role definition, and workforce planning against the strategy. Use this to structure a new team, restructure an existing one, resolve unclear ownership between teams, plan headcount, or diagnose why a team underperforms for structural rather than individual reasons.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/org-design/SKILL.md"}, {"name": "performance-management", "summary": "Runs performance systems that change behavior — expectations, feedback, review cycles, calibration, and handling underperformance", "trigger": "Runs performance systems that change behavior — expectations, feedback, review cycles, calibration, and handling underperformance. Use this to design or fix a review process, run calibration, write or coach on feedback, address sustained underperformance, or work out why reviews consume weeks and change nothing.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/performance-management/SKILL.md"}, {"name": "workforce-planning", "summary": "Plans the shape and size of the workforce — demand for roles, build-versus-buy, attrition, and sequencing hiring against budget", "trigger": "Plans the shape and size of the workforce — demand for roles, build-versus-buy, attrition, and sequencing hiring against budget. Use this to build a hiring plan, decide which roles to open and in what order, model attrition and backfill, plan for a growth or contraction scenario, or connect headcount plans to the budget.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/people/skills/workforce-planning/SKILL.md"}]}, {"slug": "legal-risk", "title": "Legal & Risk", "exec": "CLO / CCO", "reviewer": true, "skills": [{"name": "chief-legal-and-risk-officer", "summary": "Owns legal, contracts, intellectual property, regulatory compliance, privacy, security governance, enterprise risk, and audit readiness", "trigger": "Owns legal, contracts, intellectual property, regulatory compliance, privacy, security governance, enterprise risk, and audit readiness. Use this to review a contract or commitment, assess regulatory or privacy exposure, evaluate an IP or licensing question, judge the risk in a business decision, prepare for an audit or certification, or when a plan may create obligations the business cannot meet. Also use to decide whether a risk should be accepted, mitigated, or refused.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/legal-risk/skills/chief-legal-and-risk-officer/SKILL.md"}, {"name": "contract-review", "summary": "Reviews and negotiates commercial agreements — MSAs, SOWs, order forms, NDAs, vendor and data-processing agreements — identifying material risk, prop…", "trigger": "Reviews and negotiates commercial agreements — MSAs, SOWs, order forms, NDAs, vendor and data-processing agreements — identifying material risk, proposing positions, and recommending a path rather than listing issues. Use this to review a contract before signature, prepare a negotiation position, build fallback positions and approval thresholds, or assess exposure in terms already agreed.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/legal-risk/skills/contract-review/SKILL.md"}, {"name": "corporate-governance", "summary": "Maintains the corporate record and the governance machinery — entity records, board and committee support, resolutions and minutes, delegations of au…", "trigger": "Maintains the corporate record and the governance machinery — entity records, board and committee support, resolutions and minutes, delegations of authority, insurance, and business continuity. Use this to prepare board or committee materials, record a decision that needs to be minuted, set or check approval authority, review insurance and continuity coverage, establish a retention policy, or work out where a responsibility belongs when it falls between functions.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/legal-risk/skills/corporate-governance/SKILL.md"}, {"name": "enterprise-risk", "summary": "Identifies, assesses, and tracks organizational risk — building and maintaining a risk register, scoring exposure, assigning owners and treatments, a…", "trigger": "Identifies, assesses, and tracks organizational risk — building and maintaining a risk register, scoring exposure, assigning owners and treatments, and preparing for audit. Use this to stand up a risk program, assess the risk in a decision or initiative, prepare for a certification or audit, decide whether a risk should be accepted, mitigated, transferred, or avoided, or report risk posture to leadership.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/legal-risk/skills/enterprise-risk/SKILL.md"}, {"name": "privacy-and-data-protection", "summary": "Assesses and improves how personal data is collected, used, shared, and retained — data mapping, lawful basis, consent, processor agreements, subject…", "trigger": "Assesses and improves how personal data is collected, used, shared, and retained — data mapping, lawful basis, consent, processor agreements, subject rights, and breach obligations. Use this before launching anything that handles personal data, when adding a vendor that will process it, when a data subject request arrives, when assessing exposure under GDPR or US state privacy laws, or when preparing for a privacy review.", "url": "https://github.com/cbrock84/headcount/blob/main/plugins/legal-risk/skills/privacy-and-data-protection/SKILL.md"}]}];
const grid = document.getElementById('grid');
const q = document.getElementById('q');
diff --git a/docs/org-chart.md b/docs/org-chart.md
index 9991f7d..e5657ab 100644
--- a/docs/org-chart.md
+++ b/docs/org-chart.md
@@ -8,7 +8,7 @@
Technology Product Marketing + Revenue Finance Operations Data & Corporate
│ Demand Gen │ Analytics Strategy
CIO EPMO
-IT Operations Programme Management Office
+IT Operations Program Management Office
CHRO CCO
People Customer Experience
@@ -42,7 +42,7 @@ than into the function they oversee.
| `revenue` | Revenue | CRO | 8 |
| `finance` | Finance | CFO | 9 |
| `operations` | Operations | COO | 8 |
-| `pmo` | Programme Management Office | EPMO / COO | 6 |
+| `pmo` | Program Management Office | EPMO / COO | 6 |
| `customer-experience` | Customer Experience | CCO | 5 |
| `data-analytics` | Data & Analytics | CDO | 6 |
| `corporate-strategy` | Corporate Strategy | CSO | 5 |
diff --git a/plugins/corporate-strategy/skills/chief-strategy-officer/SKILL.md b/plugins/corporate-strategy/skills/chief-strategy-officer/SKILL.md
index 13f29fb..9644533 100644
--- a/plugins/corporate-strategy/skills/chief-strategy-officer/SKILL.md
+++ b/plugins/corporate-strategy/skills/chief-strategy-officer/SKILL.md
@@ -49,7 +49,7 @@ finance must agree before an approach is made, not after.
## The failure mode
-Strategy functions drift into producing analysis nobody acts on. The defence is that every piece of
+Strategy functions drift into producing analysis nobody acts on. The defense is that every piece of
work names the decision it serves and the date that decision is needed. Analysis with no decision
attached is a hobby.
diff --git a/plugins/corporate-strategy/skills/scenario-planning/SKILL.md b/plugins/corporate-strategy/skills/scenario-planning/SKILL.md
index 1b53a1d..ba22712 100644
--- a/plugins/corporate-strategy/skills/scenario-planning/SKILL.md
+++ b/plugins/corporate-strategy/skills/scenario-planning/SKILL.md
@@ -27,7 +27,7 @@ with the numbers scaled, and it teaches nothing.
Take the two most consequential uncertainties and build the quadrants. Each scenario should be
internally coherent: if demand is high *and* supply is constrained, what else follows — pricing,
-competitor behaviour, regulatory attention?
+competitor behavior, regulatory attention?
Give each a name that captures its logic. Names make scenarios usable in conversation, which is where
they earn their keep.
diff --git a/plugins/customer-experience/skills/chief-customer-officer/SKILL.md b/plugins/customer-experience/skills/chief-customer-officer/SKILL.md
index 60baaee..cc8a2af 100644
--- a/plugins/customer-experience/skills/chief-customer-officer/SKILL.md
+++ b/plugins/customer-experience/skills/chief-customer-officer/SKILL.md
@@ -17,7 +17,7 @@ customer actually experiences, and the loop that turns what they report into wha
- Escalation: the path from a frustrated customer to someone who can act.
- Customer success: adoption, expansion readiness, renewal risk.
- Voice of customer: the loop from complaint to fix, and whether it closes.
-- Self-service: the help centre, documentation, and what people can resolve without contacting you.
+- Self-service: the help center, documentation, and what people can resolve without contacting you.
## What this role owns
diff --git a/plugins/customer-experience/skills/escalation-management/SKILL.md b/plugins/customer-experience/skills/escalation-management/SKILL.md
index 5fc35b3..0a45b64 100644
--- a/plugins/customer-experience/skills/escalation-management/SKILL.md
+++ b/plugins/customer-experience/skills/escalation-management/SKILL.md
@@ -25,7 +25,7 @@ get worse when ownership is ambiguous — the customer starts re-explaining, whi
update at three" preserves trust; silence destroys it faster than bad news does. Customers escalate
again because they heard nothing, far more often than because of the underlying issue.
-**Separate acknowledgement from explanation.** Acknowledge the impact immediately, in their terms.
+**Separate acknowledgment from explanation.** Acknowledge the impact immediately, in their terms.
Explanation comes when you actually know. Leading with a cause you have not confirmed means
retracting it later, and the retraction is what they remember.
diff --git a/plugins/customer-experience/skills/self-service-and-knowledge/SKILL.md b/plugins/customer-experience/skills/self-service-and-knowledge/SKILL.md
index 635ff19..f4f0cdd 100644
--- a/plugins/customer-experience/skills/self-service-and-knowledge/SKILL.md
+++ b/plugins/customer-experience/skills/self-service-and-knowledge/SKILL.md
@@ -1,6 +1,6 @@
---
name: self-service-and-knowledge
-description: Builds the help centre, in-product guidance, and knowledge base that let customers resolve problems without contacting anyone — content, findability, maintenance, and deflection measurement. Use this to build or fix a help centre, reduce support volume, write documentation for customers, improve findability, or decide what deserves a help article versus a product fix.
+description: Builds the help center, in-product guidance, and knowledge base that let customers resolve problems without contacting anyone — content, findability, maintenance, and deflection measurement. Use this to build or fix a help center, reduce support volume, write documentation for customers, improve findability, or decide what deserves a help article versus a product fix.
---
# Self-service and knowledge
@@ -38,12 +38,12 @@ An article nobody finds does not exist. Findability comes from titles matching r
in-product links at the moment of confusion, and search that tolerates the words customers actually
use rather than your internal vocabulary.
-Read your help-centre search logs, especially the queries returning nothing. That list is your
+Read your help-center search logs, especially the queries returning nothing. That list is your
content backlog, ranked by demand, already written for you.
-## In-product beats the help centre
+## In-product beats the help center
-Guidance at the point of confusion deflects far more than a help centre does, because it requires no
+Guidance at the point of confusion deflects far more than a help center does, because it requires no
decision to go looking. A well-written empty state, field hint, or error message removes contacts
that documentation never would.
diff --git a/plugins/customer-experience/skills/support-operations/SKILL.md b/plugins/customer-experience/skills/support-operations/SKILL.md
index d6428bb..947aafc 100644
--- a/plugins/customer-experience/skills/support-operations/SKILL.md
+++ b/plugins/customer-experience/skills/support-operations/SKILL.md
@@ -19,14 +19,14 @@ to demand you could have eliminated.
In order of cost, cheapest first. Push volume up this list rather than getting faster at the bottom:
1. **Eliminate** — fix the product defect or confusing flow generating the contact.
-2. **Deflect** — answer it in the interface at the moment of confusion, not in a help centre nobody
+2. **Deflect** — answer it in the interface at the moment of confusion, not in a help center nobody
visits.
3. **Self-serve** — findable documentation for people who go looking.
4. **Automate** — genuine resolution of routine requests, not a bot that stalls people before a
human.
5. **Assist** — a person.
-Most support improvement programmes work on level 5 exclusively, because it is the visible one.
+Most support improvement programs work on level 5 exclusively, because it is the visible one.
## Channels
@@ -67,4 +67,4 @@ by a wide margin and then blames the team.
## Quality
Review a sample of resolved contacts against a rubric agreed with the team, and coach against it.
-Reviewing only escalations trains for defence rather than quality.
+Reviewing only escalations trains for defense rather than quality.
diff --git a/plugins/customer-experience/skills/voice-of-customer/SKILL.md b/plugins/customer-experience/skills/voice-of-customer/SKILL.md
index 3e91b50..550c011 100644
--- a/plugins/customer-experience/skills/voice-of-customer/SKILL.md
+++ b/plugins/customer-experience/skills/voice-of-customer/SKILL.md
@@ -1,11 +1,11 @@
---
name: voice-of-customer
-description: Builds the loop from what customers say to what gets changed — collecting feedback, distinguishing signal from noise, routing it to owners, and closing the loop back to the customer. Use this to set up a feedback programme, design or interpret CSAT/NPS, decide what customer feedback deserves action, get product to act on recurring issues, or diagnose why feedback is collected but nothing changes.
+description: Builds the loop from what customers say to what gets changed — collecting feedback, distinguishing signal from noise, routing it to owners, and closing the loop back to the customer. Use this to set up a feedback program, design or interpret CSAT/NPS, decide what customer feedback deserves action, get product to act on recurring issues, or diagnose why feedback is collected but nothing changes.
---
# Voice of customer
-Most feedback programmes collect diligently and change nothing. The collection is the easy half; the
+Most feedback programs collect diligently and change nothing. The collection is the easy half; the
loop is the whole value.
## Sources, weighted honestly
@@ -14,7 +14,7 @@ loop is the whole value.
People contacting you have a real problem nobody asked them about. But the sample is strongly
self-selected: it excludes everyone who silently churned, worked around the problem, or would
never contact you. Treat it as operational evidence to be normalized per active account and
- triangulated against churn and behavioural data — never as representative of the customer base.
+ triangulated against churn and behavioral data — never as representative of the customer base.
- **Churn and loss reasons** — the most valuable and most under-sampled. People leaving have no
reason to be polite.
- **Interviews** — depth, small n, best for understanding *why* something in the data is happening.
@@ -27,13 +27,13 @@ Anything a customer built a workaround for outranks anything they merely said in
## On CSAT and NPS
Both are useful as trends and misleading as targets. The moment a team is measured on a score, the
-score improves faster than the experience does — asking at the favourable moment, coaching for the
+score improves faster than the experience does — asking at the favorable moment, coaching for the
rating, excluding difficult segments.
Treat the score as a prompt for the free-text answer, which is where the information is. Segment
before concluding: an overall score is an average of experiences that have nothing in common.
-Never target a number without also watching the behaviour it is supposed to predict.
+Never target a number without also watching the behavior it is supposed to predict.
## Turning feedback into change
@@ -61,5 +61,5 @@ stop escalating.
- Report themes without volume.
- Let one loud enterprise account set the roadmap without checking how widely the problem is shared.
-- Run a programme with no mechanism for anything to change as a result. That is a survey habit, not
+- Run a program with no mechanism for anything to change as a result. That is a survey habit, not
a feedback loop.
diff --git a/plugins/data-analytics/skills/data-engineering/SKILL.md b/plugins/data-analytics/skills/data-engineering/SKILL.md
index cd653c6..9b1afae 100644
--- a/plugins/data-analytics/skills/data-engineering/SKILL.md
+++ b/plugins/data-analytics/skills/data-engineering/SKILL.md
@@ -18,7 +18,7 @@ point, and raw data is what lets you reprocess rather than re-request from a sou
longer have it.
Business logic belongs downstream where it is visible and testable, not buried in ingestion. The
-exception is transformation required for privacy — minimisation, pseudonymisation, dropping fields
+exception is transformation required for privacy — minimization, pseudonymization, dropping fields
you have no basis to hold — which belongs at ingest precisely because raw storage is what the
obligation attaches to. See `legal-risk:privacy-and-data-protection`.
diff --git a/plugins/executive/skills/agent-hierarchy/references/starter-rosters.md b/plugins/executive/skills/agent-hierarchy/references/starter-rosters.md
index e7ae864..61af5a7 100644
--- a/plugins/executive/skills/agent-hierarchy/references/starter-rosters.md
+++ b/plugins/executive/skills/agent-hierarchy/references/starter-rosters.md
@@ -23,7 +23,7 @@ security-deps reviewer planned
analytics event schema, the version/compat policy. Sole agent permitted to change a
contract, and it does so as a **coordinated pair** with a consumer PR.
- **`core-qa`** — tests the compat matrix: does version N read version N-1's save files.
-- **`security-deps`** — sole reviewer for manifests, lockfiles, and third-party licences.
+- **`security-deps`** — sole reviewer for manifests, lockfiles, and third-party licenses.
**The single most valuable rule here:** never remove a core export because it looks
unused. You cannot see the consumers from inside the core. Deprecate, announce, remove.
diff --git a/plugins/finance/skills/capital-allocation/SKILL.md b/plugins/finance/skills/capital-allocation/SKILL.md
index 5ee3db5..2d46ea3 100644
--- a/plugins/finance/skills/capital-allocation/SKILL.md
+++ b/plugins/finance/skills/capital-allocation/SKILL.md
@@ -48,7 +48,7 @@ first is usually cheaper than being right by luck.
## Look back, or the numbers stay fictional
-Compare realised outcomes against the approved case, and make it routine rather than punitive. Where
+Compare realized outcomes against the approved case, and make it routine rather than punitive. Where
nobody looks back, forecasts drift optimistic because optimism is rewarded at approval and never
tested afterwards.
diff --git a/plugins/finance/skills/internal-controls-and-audit/SKILL.md b/plugins/finance/skills/internal-controls-and-audit/SKILL.md
index 76394cb..7182283 100644
--- a/plugins/finance/skills/internal-controls-and-audit/SKILL.md
+++ b/plugins/finance/skills/internal-controls-and-audit/SKILL.md
@@ -30,7 +30,7 @@ position; an unacknowledged one is a finding waiting to be written.
## Design controls that leave evidence
A control that happened but left no trace did not happen, as far as an auditor can determine. Each
-control needs a stated owner, frequency, what is examined, and an artefact produced as a by-product
+control needs a stated owner, frequency, what is examined, and an artifact produced as a by-product
of doing the work — not assembled afterwards for the audit.
Prefer **preventive** controls, which stop the transaction, over **detective** ones, which find it
@@ -46,8 +46,8 @@ threshold creates, and it is straightforward to monitor for.
## Audit findings
-Treat a finding as information. Fix the cause rather than the instance, and be sceptical of
-remediation that consists of more careful behaviour: the same conditions will reproduce the finding
+Treat a finding as information. Fix the cause rather than the instance, and be skeptical of
+remediation that consists of more careful behavior: the same conditions will reproduce the finding
with different people.
Related but distinct: `legal-risk:corporate-governance` owns board and entity governance,
diff --git a/plugins/finance/skills/revenue-recognition/SKILL.md b/plugins/finance/skills/revenue-recognition/SKILL.md
index c190908..2565130 100644
--- a/plugins/finance/skills/revenue-recognition/SKILL.md
+++ b/plugins/finance/skills/revenue-recognition/SKILL.md
@@ -1,6 +1,6 @@
---
name: revenue-recognition
-description: Determines when and how revenue is recognised — performance obligations, contract terms that change the answer, and the deal structures that create accounting problems. Use this to work out how a contract should be recognised, review a non-standard deal before it is signed, understand deferred revenue, or spot terms that would delay or reverse recognition.
+description: Determines when and how revenue is recognized — performance obligations, contract terms that change the answer, and the deal structures that create accounting problems. Use this to work out how a contract should be recognized, review a non-standard deal before it is signed, understand deferred revenue, or spot terms that would delay or reverse recognition.
---
# Revenue recognition
@@ -16,7 +16,7 @@ contract need your auditors or a qualified accountant, not a checklist.**
Recognition follows the transfer of control to the customer, worked through in five steps: identify
the contract, identify the distinct performance obligations, determine the transaction price,
-allocate it across the obligations, then recognise as each is satisfied.
+allocate it across the obligations, then recognize as each is satisfied.
Most disputes happen at step two and step four. What sales sold as one thing is frequently several
obligations for accounting purposes — software plus implementation plus support — and the price has
@@ -45,7 +45,7 @@ nothing commercially can move revenue across a period boundary, and by the time
signed paper the trade has already been made.
Give `revenue:chief-revenue-officer` and `revenue:pricing-and-packaging` a small set of standard
-structures that recognise cleanly, and route anything outside them through review before signature —
+structures that recognize cleanly, and route anything outside them through review before signature —
alongside `legal-risk:contract-review`, which owns the legal exposure the same clauses create.
## Deferred revenue is an obligation
@@ -56,7 +56,7 @@ surprises you.
## Never
-- Recognise on invoice date or cash receipt as a shortcut.
+- Recognize on invoice date or cash receipt as a shortcut.
- Allocate price across obligations the way the quote happened to be laid out.
- Let a side letter exist.
- Conclude a material or novel contract's treatment without your auditors.
diff --git a/plugins/it-operations/skills/endpoint-management/SKILL.md b/plugins/it-operations/skills/endpoint-management/SKILL.md
index c96ae03..29580d6 100644
--- a/plugins/it-operations/skills/endpoint-management/SKILL.md
+++ b/plugins/it-operations/skills/endpoint-management/SKILL.md
@@ -1,6 +1,6 @@
---
name: endpoint-management
-description: Manages laptops, desktops and mobile devices — enrolment, configuration, patching, software distribution, and lost or compromised devices. Use this to set up device management, standardise builds, roll out software or an OS upgrade, handle a lost device, or bring an unmanaged fleet under control.
+description: Manages laptops, desktops and mobile devices — enrollment, configuration, patching, software distribution, and lost or compromised devices. Use this to set up device management, standardize builds, roll out software or an OS upgrade, handle a lost device, or bring an unmanaged fleet under control.
---
# Endpoint management
@@ -8,12 +8,12 @@ description: Manages laptops, desktops and mobile devices — enrolment, configu
Endpoints are the most exposed and least controlled part of the estate: they leave the building, run
arbitrary software, and are operated by people whose job is not IT.
-## Enrolment is the control point
+## Enrollment is the control point
A device that never enrolled is a device with no patching, no encryption guarantee, and no remote
-wipe. Enrolment must be a precondition of access to company data, not a request made afterwards.
+wipe. Enrollment must be a precondition of access to company data, not a request made afterwards.
-Automate it from procurement so a device is enrolled before the user opens it. Manual enrolment as a
+Automate it from procurement so a device is enrolled before the user opens it. Manual enrollment as a
post-delivery step is skipped exactly when the desk is busy.
Handle personal devices as a deliberate policy decision, not an accident. If personal devices reach
@@ -37,7 +37,7 @@ deferral with a hard deadline and force after it, and communicate the deadline i
unexpected forced reboot during a customer call is what teaches people to avoid management.
Report coverage as a percentage of the fleet, and specifically chase the long tail. The devices that
-never appear in patch reports are usually the interesting ones: travelling users, spares, and the
+never appear in patch reports are usually the interesting ones: traveling users, spares, and the
machine in a cupboard still holding a domain account.
## Lost, stolen, or leaving
diff --git a/plugins/it-operations/skills/it-asset-management/SKILL.md b/plugins/it-operations/skills/it-asset-management/SKILL.md
index bad0240..84d73a4 100644
--- a/plugins/it-operations/skills/it-asset-management/SKILL.md
+++ b/plugins/it-operations/skills/it-asset-management/SKILL.md
@@ -1,13 +1,13 @@
---
name: it-asset-management
-description: Tracks hardware and software assets through their life — procurement, ownership, licensing, refresh, and disposal. Use this to build an asset register, prepare for a software audit, plan a refresh cycle, control licence spend, or dispose of equipment safely.
+description: Tracks hardware and software assets through their life — procurement, ownership, licensing, refresh, and disposal. Use this to build an asset register, prepare for a software audit, plan a refresh cycle, control license spend, or dispose of equipment safely.
---
# IT asset management
The register exists to answer operational questions: what do we have, who has it, is it supported, is
it licensed, and when does it need replacing. An inventory that answers none of those is an
-accounting artefact.
+accounting artifact.
## One register, reconciled against reality
@@ -32,12 +32,12 @@ is wrong between batches, which is most of the time.
Under-licensing is a financial and legal exposure that surfaces at audit; over-licensing is money
spent on nothing, and it is usually the larger number.
-Reconcile entitlements against actual installs and actual use. Reclaiming licences from people who
+Reconcile entitlements against actual installs and actual use. Reclaiming licenses from people who
stopped using a tool typically funds a meaningful fraction of the next renewal, and the data for it
already exists.
-Watch licence models that change cost with infrastructure — per-core, per-socket, per-user in a
-system that provisions freely. A routine infrastructure change can multiply a licence bill with no
+Watch license models that change cost with infrastructure — per-core, per-socket, per-user in a
+system that provisions freely. A routine infrastructure change can multiply a license bill with no
procurement decision anywhere in the path.
## Refresh and disposal
@@ -54,5 +54,5 @@ breach with no date attached.
- Maintain a register by hand and trust it.
- Record a team as an asset owner.
-- Renew licences without reconciling against actual use.
+- Renew licenses without reconciling against actual use.
- Dispose of storage without evidence of destruction or wipe.
diff --git a/plugins/it-operations/skills/service-desk/SKILL.md b/plugins/it-operations/skills/service-desk/SKILL.md
index 659fda7..c7aecc7 100644
--- a/plugins/it-operations/skills/service-desk/SKILL.md
+++ b/plugins/it-operations/skills/service-desk/SKILL.md
@@ -1,6 +1,6 @@
---
name: service-desk
-description: Runs the IT service desk — intake, triage, prioritisation, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets still frustrates everyone.
+description: Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets still frustrates everyone.
---
# Service desk
@@ -26,12 +26,12 @@ Keep **incidents** (something broken) separate from **requests** (something want
different clocks, different queues, and different success conditions, and merging them lets routine
requests bury outages.
-Escalation should be time-based and automatic. Relying on someone to notice a ticket ageing means the
+Escalation should be time-based and automatic. Relying on someone to notice a ticket aging means the
tickets that age are the ones nobody is watching.
## Measure service, not activity
-Tickets closed measures activity, and optimising it produces premature closure and reopened tickets.
+Tickets closed measures activity, and optimizing it produces premature closure and reopened tickets.
Better:
- **First-contact resolution** — resolved without a handoff.
diff --git a/plugins/it-operations/skills/systems-administration/SKILL.md b/plugins/it-operations/skills/systems-administration/SKILL.md
index 94f938a..f1894e0 100644
--- a/plugins/it-operations/skills/systems-administration/SKILL.md
+++ b/plugins/it-operations/skills/systems-administration/SKILL.md
@@ -1,6 +1,6 @@
---
name: systems-administration
-description: Runs servers and corporate systems — patching, configuration baselines, change control, capacity, and the routine that prevents incidents. Use this to establish a patching cadence, standardise server configuration, plan a maintenance window, decide change control for infrastructure, or clean up systems that have drifted from any known state.
+description: Runs servers and corporate systems — patching, configuration baselines, change control, capacity, and the routine that prevents incidents. Use this to establish a patching cadence, standardize server configuration, plan a maintenance window, decide change control for infrastructure, or clean up systems that have drifted from any known state.
---
# Systems administration
@@ -17,7 +17,7 @@ Every system class needs a defined baseline: build, hardening, agents, logging,
built by hand from memory diverge immediately and cannot be reasoned about as a group.
Drift is the real enemy. Detect it continuously and correct rather than document — a system that no
-longer matches its baseline is a system whose behaviour under patching or failover is unknown.
+longer matches its baseline is a system whose behavior under patching or failover is unknown.
The strongest form is disposability: rebuild rather than repair. A system you can rebuild in an hour
never accumulates the sediment of a decade of manual fixes.
diff --git a/plugins/legal-risk/skills/corporate-governance/SKILL.md b/plugins/legal-risk/skills/corporate-governance/SKILL.md
index 685b08c..64f4f7a 100644
--- a/plugins/legal-risk/skills/corporate-governance/SKILL.md
+++ b/plugins/legal-risk/skills/corporate-governance/SKILL.md
@@ -12,7 +12,7 @@ something goes wrong. Unglamorous until it is the only thing that matters.
One authoritative place holding: formation and entity documents, ownership and cap table, board and
shareholder resolutions, minutes, signed agreements above the review threshold, insurance policies,
-and material licences and registrations.
+and material licenses and registrations.
The failure mode is not losing a document; it is not knowing which version is current. Every record
carries its effective date, and superseded versions are marked superseded rather than deleted —
diff --git a/plugins/operations/skills/business-continuity-and-resilience/SKILL.md b/plugins/operations/skills/business-continuity-and-resilience/SKILL.md
index de90230..2488a97 100644
--- a/plugins/operations/skills/business-continuity-and-resilience/SKILL.md
+++ b/plugins/operations/skills/business-continuity-and-resilience/SKILL.md
@@ -18,7 +18,7 @@ systems tells you what you own, never what matters.
For each critical process establish:
- **Maximum tolerable outage** — the point past which the damage is not recoverable by working harder
- afterwards. This is a business judgement, made by the process owner, not by IT.
+ afterwards. This is a business judgment, made by the process owner, not by IT.
- **RTO** — how quickly it must be back. Always shorter than someone wants to pay for.
- **RPO** — how much data you can afford to lose, measured in time. An RPO of zero is a claim about
spending, not about intent.
@@ -27,7 +27,7 @@ RTO and RPO that were not signed by the person accountable for the process are a
## Plans people can follow badly
-A continuity plan is read by a stressed person at 03:00 who did not write it. Optimise for that
+A continuity plan is read by a stressed person at 03:00 who did not write it. Optimize for that
reader: named roles rather than names, decision authority stated explicitly, and the first three
actions on the first page.
diff --git a/plugins/operations/skills/capacity-and-demand-planning/SKILL.md b/plugins/operations/skills/capacity-and-demand-planning/SKILL.md
index da698f6..64c9219 100644
--- a/plugins/operations/skills/capacity-and-demand-planning/SKILL.md
+++ b/plugins/operations/skills/capacity-and-demand-planning/SKILL.md
@@ -1,6 +1,6 @@
---
name: capacity-and-demand-planning
-description: Matches operational capacity to expected demand — forecasting load, sizing teams and systems, managing queues, and deciding when to add capacity. Use this to plan staffing for expected volume, diagnose a queue that keeps growing, size support or fulfilment capacity, or decide whether a bottleneck needs more capacity or better flow.
+description: Matches operational capacity to expected demand — forecasting load, sizing teams and systems, managing queues, and deciding when to add capacity. Use this to plan staffing for expected volume, diagnose a queue that keeps growing, size support or fulfillment capacity, or decide whether a bottleneck needs more capacity or better flow.
---
# Capacity and demand planning
diff --git a/plugins/operations/skills/quality-management/SKILL.md b/plugins/operations/skills/quality-management/SKILL.md
index 203ac36..97a4d91 100644
--- a/plugins/operations/skills/quality-management/SKILL.md
+++ b/plugins/operations/skills/quality-management/SKILL.md
@@ -1,6 +1,6 @@
---
name: quality-management
-description: Builds quality into operations — defining standards, catching defects at the right point, root cause analysis, and continuous improvement. Use this to reduce a defect or error rate, design quality controls into a process, run a root cause analysis, respond to a customer quality complaint, or set up quality metrics that drive behaviour.
+description: Builds quality into operations — defining standards, catching defects at the right point, root cause analysis, and continuous improvement. Use this to reduce a defect or error rate, design quality controls into a process, run a root cause analysis, respond to a customer quality complaint, or set up quality metrics that drive behavior.
---
# Quality management
diff --git a/plugins/operations/skills/service-level-management/SKILL.md b/plugins/operations/skills/service-level-management/SKILL.md
index e32b55d..e52a333 100644
--- a/plugins/operations/skills/service-level-management/SKILL.md
+++ b/plugins/operations/skills/service-level-management/SKILL.md
@@ -14,7 +14,7 @@ The characteristic failure is a service meeting every target while customers are
when the measure is chosen for availability of data rather than relevance:
- **Uptime that excludes degraded operation.** Technically up and unusably slow is down.
-- **Response time instead of resolution time.** An instant acknowledgement that resolves nothing
+- **Response time instead of resolution time.** An instant acknowledgment that resolves nothing
measures the autoresponder.
- **Averages instead of percentiles.** A mean hides the tail, and the tail is who complains. Commit
at p95 or p99, not the mean.
diff --git a/plugins/operations/skills/supply-chain-and-logistics/SKILL.md b/plugins/operations/skills/supply-chain-and-logistics/SKILL.md
index 312f4c5..e3873c8 100644
--- a/plugins/operations/skills/supply-chain-and-logistics/SKILL.md
+++ b/plugins/operations/skills/supply-chain-and-logistics/SKILL.md
@@ -1,6 +1,6 @@
---
name: supply-chain-and-logistics
-description: Manages the flow of goods and inputs — sourcing, inventory, lead times, fulfilment, and supply risk. Use this to reduce stockouts or excess inventory, plan for a supplier failure, decide reorder points and safety stock, improve fulfilment reliability, or assess concentration risk in a supply base.
+description: Manages the flow of goods and inputs — sourcing, inventory, lead times, fulfillment, and supply risk. Use this to reduce stockouts or excess inventory, plan for a supplier failure, decide reorder points and safety stock, improve fulfillment reliability, or assess concentration risk in a supply base.
---
# Supply chain and logistics
@@ -38,13 +38,13 @@ qualifying an alternate under pressure is where quality problems enter.
Supplier commercial terms and exit rights belong with `operations:vendor-management`; continuity of
the wider business process belongs with `operations:business-continuity-and-resilience`.
-## Fulfilment reliability
+## Fulfillment reliability
Measure on-time-in-full, not on-time and in-full separately — partial shipments that arrive on
schedule are a way of appearing to hit a target while failing the customer.
Diagnose misses by cause: supply, capacity, information, or process. The remedies do not overlap,
-and a fulfilment problem attributed to the wrong one gets more expensive rather than better.
+and a fulfillment problem attributed to the wrong one gets more expensive rather than better.
## Never
diff --git a/plugins/people/skills/employee-relations/SKILL.md b/plugins/people/skills/employee-relations/SKILL.md
index 681e1e0..5579e1c 100644
--- a/plugins/people/skills/employee-relations/SKILL.md
+++ b/plugins/people/skills/employee-relations/SKILL.md
@@ -42,7 +42,7 @@ complaint.
## Conflict that is not misconduct
-Most friction is not a policy matter. Address it directly and early: separate the behaviour from the
+Most friction is not a policy matter. Address it directly and early: separate the behavior from the
person, establish what each actually needs, and be explicit that the working relationship has to
function even where warmth is not available.
diff --git a/plugins/people/skills/learning-and-development/SKILL.md b/plugins/people/skills/learning-and-development/SKILL.md
index f04aebd..f6a6ad7 100644
--- a/plugins/people/skills/learning-and-development/SKILL.md
+++ b/plugins/people/skills/learning-and-development/SKILL.md
@@ -54,6 +54,6 @@ quietly resisted, and quiet resistance always wins.
## Never
- Deliver training for a problem that is not a capability problem.
-- Measure a programme by satisfaction scores.
+- Measure a program by satisfaction scores.
- Write levels in adjectives rather than observable scope and impact.
- Make management the only route to progression.
diff --git a/plugins/people/skills/onboarding-and-offboarding/SKILL.md b/plugins/people/skills/onboarding-and-offboarding/SKILL.md
index dae3374..5891289 100644
--- a/plugins/people/skills/onboarding-and-offboarding/SKILL.md
+++ b/plugins/people/skills/onboarding-and-offboarding/SKILL.md
@@ -42,7 +42,7 @@ not.
Knowledge capture has to precede the access cutoff, which means starting on the day notice is given,
not the day before departure.
-Prioritise what is genuinely undocumented and only in one head: the systems they alone maintain, the
+Prioritize what is genuinely undocumented and only in one head: the systems they alone maintain, the
relationships they hold, the decisions whose reasoning exists nowhere. Ask directly — "what will
break, and who will not know why?" — because they know and will usually say.
diff --git a/plugins/people/skills/performance-management/SKILL.md b/plugins/people/skills/performance-management/SKILL.md
index b9e3ef3..de053ae 100644
--- a/plugins/people/skills/performance-management/SKILL.md
+++ b/plugins/people/skills/performance-management/SKILL.md
@@ -1,6 +1,6 @@
---
name: performance-management
-description: Runs performance systems that change behaviour — expectations, feedback, review cycles, calibration, and handling underperformance. Use this to design or fix a review process, run calibration, write or coach on feedback, address sustained underperformance, or work out why reviews consume weeks and change nothing.
+description: Runs performance systems that change behavior — expectations, feedback, review cycles, calibration, and handling underperformance. Use this to design or fix a review process, run calibration, write or coach on feedback, address sustained underperformance, or work out why reviews consume weeks and change nothing.
---
# Performance management
@@ -21,7 +21,7 @@ as justification.
Separate two axes deliberately, because conflating them is the most common structural flaw:
- **Outcomes** — what was delivered, which is partly situational.
-- **Behaviours** — how it was done, which is more within the person's control.
+- **Behaviors** — how it was done, which is more within the person's control.
Someone who delivered through a collapsing market and someone who delivered by scorching the earth
around them are different cases. A single blended rating hides both.
@@ -56,7 +56,7 @@ capability, a role mismatch, or something outside work. Treating a role mismatch
problem produces a performance plan that fails for reasons nobody named.
Where a formal plan is warranted it needs specific outcomes, a real timeframe, defined support, and a
-stated consequence. A plan that is only a paper trail for a decision already taken is recognised as
+stated consequence. A plan that is only a paper trail for a decision already taken is recognized as
such and does damage well beyond the individual.
## Never
diff --git a/plugins/people/skills/workforce-planning/SKILL.md b/plugins/people/skills/workforce-planning/SKILL.md
index 8228c18..751aaec 100644
--- a/plugins/people/skills/workforce-planning/SKILL.md
+++ b/plugins/people/skills/workforce-planning/SKILL.md
@@ -53,5 +53,5 @@ which parts of the plan can still be unwound and by when.
- Build a plan on salary rather than fully loaded cost.
- Hire faster than the organization can absorb and expect output to rise.
-- Treat attrition as a residual instead of a modelled input.
+- Treat attrition as a residual instead of a modeled input.
- Report aggregate attrition without looking at it by team and by manager.
diff --git a/plugins/pmo/.claude-plugin/plugin.json b/plugins/pmo/.claude-plugin/plugin.json
index be1d4ba..fa4ca4f 100644
--- a/plugins/pmo/.claude-plugin/plugin.json
+++ b/plugins/pmo/.claude-plugin/plugin.json
@@ -1,6 +1,6 @@
{
"name": "pmo",
- "description": "Enterprise programme management office: portfolio governance, programme and project delivery, dependencies and delivery risk, benefits realization, and adoption.",
+ "description": "Enterprise program management office: portfolio governance, program and project delivery, dependencies and delivery risk, benefits realization, and adoption.",
"version": "1.0.0",
"author": {
"name": "Chris Brock"
@@ -10,7 +10,7 @@
"pmo",
"portfolio",
"project-management",
- "programme-management",
+ "program-management",
"delivery"
]
}
diff --git a/plugins/pmo/skills/change-and-adoption/SKILL.md b/plugins/pmo/skills/change-and-adoption/SKILL.md
index 3e119ae..08c4d16 100644
--- a/plugins/pmo/skills/change-and-adoption/SKILL.md
+++ b/plugins/pmo/skills/change-and-adoption/SKILL.md
@@ -36,7 +36,7 @@ People adopt what respected colleagues adopt. A message from an executive establ
is sanctioned; it does not establish that it is sensible.
Find the people others actually ask, involve them early enough to influence the outcome, and let them
-carry it. Involvement after the decisions are made is recognised as decoration and costs more
+carry it. Involvement after the decisions are made is recognized as decoration and costs more
credibility than it buys.
## Train at the moment of use
@@ -50,15 +50,15 @@ change.
## Measure adoption, not deployment
-Licences deployed, accounts created and sessions logged measure nothing about whether the work
-changed. Measure the behaviour: is the new process being followed, is the old path still being used,
+Licenses deployed, accounts created and sessions logged measure nothing about whether the work
+changed. Measure the behavior: is the new process being followed, is the old path still being used,
have the outcomes moved?
Watch for the workaround. Where people have quietly kept the old spreadsheet, adoption is nominal —
and the workaround is data about what the new system fails to do, not merely non-compliance.
Adoption is the mechanism by which `pmo:benefits-realization` becomes possible; without it there is
-nothing to realise.
+nothing to realize.
## Never
diff --git a/plugins/pmo/skills/dependency-and-risk-management/SKILL.md b/plugins/pmo/skills/dependency-and-risk-management/SKILL.md
index 28f9183..9085cb3 100644
--- a/plugins/pmo/skills/dependency-and-risk-management/SKILL.md
+++ b/plugins/pmo/skills/dependency-and-risk-management/SKILL.md
@@ -15,7 +15,7 @@ A dependency in your plan that the owning team has not agreed to, with a date th
to, is a wish. Most plans contain several.
For each: what exactly is needed, from whom by name, by when, and what happens if it is late. Then
-confirm it with the owning team in a way they would recognise as a commitment — an item on their
+confirm it with the owning team in a way they would recognize as a commitment — an item on their
plan, not a mention in a meeting.
Track dependencies both ways. Teams reliably track what they are owed and forget what they owe, which
diff --git a/plugins/pmo/skills/portfolio-governance/SKILL.md b/plugins/pmo/skills/portfolio-governance/SKILL.md
index c220441..97580bf 100644
--- a/plugins/pmo/skills/portfolio-governance/SKILL.md
+++ b/plugins/pmo/skills/portfolio-governance/SKILL.md
@@ -1,6 +1,6 @@
---
name: portfolio-governance
-description: Governs the portfolio of work — intake, prioritisation, stage gates, resource contention, and stopping things. Use this to set up intake and prioritisation, run a stage gate, decide between competing initiatives, resolve resource contention across projects, or work out why everything is in flight and nothing is finishing.
+description: Governs the portfolio of work — intake, prioritization, stage gates, resource contention, and stopping things. Use this to set up intake and prioritization, run a stage gate, decide between competing initiatives, resolve resource contention across projects, or work out why everything is in flight and nothing is finishing.
---
# Portfolio governance
@@ -19,10 +19,10 @@ evidence it matters, a rough size, the accountable owner, and what will not happ
That last one is the honest part — capacity is fixed, so approving anything is declining something
else, whether or not the decline is ever stated.
-## Prioritise against capacity, not against merit
+## Prioritize against capacity, not against merit
Ranking by value produces a list where everything above the line is approved and the line is
-imaginary. Prioritisation only means something when the cut is made at real, measured delivery
+imaginary. Prioritization only means something when the cut is made at real, measured delivery
capacity — see `operations:capacity-and-demand-planning` for the throughput side.
**Limit work in progress.** An organization running twenty concurrent initiatives with capacity for
diff --git a/plugins/product/skills/interface-craft/SKILL.md b/plugins/product/skills/interface-craft/SKILL.md
index 483090a..34e17a1 100644
--- a/plugins/product/skills/interface-craft/SKILL.md
+++ b/plugins/product/skills/interface-craft/SKILL.md
@@ -48,7 +48,7 @@ must all be handled, not hoped about.
Inverting a light theme produces the characteristic bad dark mode: pure black backgrounds, pure
white text, and shadows that do nothing.
-- Use a very dark grey rather than pure black, and a slightly dimmed white rather than pure white.
+- Use a very dark gray rather than pure black, and a slightly dimmed white rather than pure white.
Maximum contrast between the two causes halation and is genuinely tiring to read.
- Elevation reverses: in light themes raised surfaces cast shadows, in dark themes they get
*lighter*. Shadow alone conveys nothing on a dark ground.
diff --git a/plugins/revenue/skills/retention/SKILL.md b/plugins/revenue/skills/retention/SKILL.md
index e889801..81dfbae 100644
--- a/plugins/revenue/skills/retention/SKILL.md
+++ b/plugins/revenue/skills/retention/SKILL.md
@@ -34,7 +34,7 @@ the cause:
## Cancellation flow
-Make cancelling straightforward. Obstruction generates chargebacks, public complaints, and in a
+Make canceling straightforward. Obstruction generates chargebacks, public complaints, and in a
growing number of jurisdictions, regulatory exposure.
Do ask why, with specific options plus free text — this is the highest-quality product feedback you
diff --git a/plugins/technology/skills/api-design/SKILL.md b/plugins/technology/skills/api-design/SKILL.md
index 2d41644..5957fff 100644
--- a/plugins/technology/skills/api-design/SKILL.md
+++ b/plugins/technology/skills/api-design/SKILL.md
@@ -1,6 +1,6 @@
---
name: api-design
-description: Designs interfaces that survive their consumers — resource modelling, errors, versioning, pagination, and compatibility. Use this to design a new API, review one before it ships, decide how to version or deprecate, fix an interface consumers keep misusing, or work out whether a change is breaking.
+description: Designs interfaces that survive their consumers — resource modeling, errors, versioning, pagination, and compatibility. Use this to design a new API, review one before it ships, decide how to version or deprecate, fix an interface consumers keep misusing, or work out whether a change is breaking.
---
# API design
diff --git a/plugins/technology/skills/cloud-infrastructure/SKILL.md b/plugins/technology/skills/cloud-infrastructure/SKILL.md
index 2f23d2c..26bcbae 100644
--- a/plugins/technology/skills/cloud-infrastructure/SKILL.md
+++ b/plugins/technology/skills/cloud-infrastructure/SKILL.md
@@ -27,7 +27,7 @@ boundary; separate namespaces in one account give a soft one that a misconfigure
crosses.
Production data does not belong in lower environments. Where realistic data is needed, mask or
-synthesise it — a copied production database is a breach waiting for a misconfigured bucket, and it
+synthesize it — a copied production database is a breach waiting for a misconfigured bucket, and it
is one of the most common ways personal data escapes.
## Networking and isolation
diff --git a/plugins/technology/skills/release-and-deployment/SKILL.md b/plugins/technology/skills/release-and-deployment/SKILL.md
index eb840c9..99c7654 100644
--- a/plugins/technology/skills/release-and-deployment/SKILL.md
+++ b/plugins/technology/skills/release-and-deployment/SKILL.md
@@ -11,7 +11,7 @@ release larger. The loop is the problem.
## Separate deploy from release
-Deploying code and exposing behaviour to users are different acts, and coupling them forces every
+Deploying code and exposing behavior to users are different acts, and coupling them forces every
deployment to be a business decision.
Decouple with flags: deploy continuously, expose deliberately. This makes rollback a configuration
@@ -30,7 +30,7 @@ Order gates fast-to-slow so failure is cheap: lint and unit tests, then integrat
requiring a deployed environment. A pipeline slow enough to be circumvented is worse than a fast one
with fewer checks, because it will be circumvented.
-Build once and promote the same artefact through environments. Rebuilding per environment means the
+Build once and promote the same artifact through environments. Rebuilding per environment means the
thing you tested is not the thing you shipped.
## Roll out gradually
@@ -48,11 +48,11 @@ structure, write to both, migrate, switch reads, then remove the old — with th
of both shapes throughout.
Test the migration against production-scale data. A migration that is instant on a development
-dataset can lock a large table for a length of time nobody modelled.
+dataset can lock a large table for a length of time nobody modeled.
## Never
-- Couple deploying code to exposing behaviour.
-- Promote a different artefact than the one that was tested.
+- Couple deploying code to exposing behavior.
+- Promote a different artifact than the one that was tested.
- Begin a rollout without a defined abort condition.
- Ship a schema change that requires the application and database to deploy simultaneously.
diff --git a/plugins/technology/skills/technical-debt-management/SKILL.md b/plugins/technology/skills/technical-debt-management/SKILL.md
index 0625096..9468899 100644
--- a/plugins/technology/skills/technical-debt-management/SKILL.md
+++ b/plugins/technology/skills/technical-debt-management/SKILL.md
@@ -1,6 +1,6 @@
---
name: technical-debt-management
-description: Makes technical debt visible and decidable — distinguishing real debt from mess, quantifying its cost, and arguing for remediation in business terms. Use this to assess and prioritise debt, decide whether to fix or live with something, justify remediation work to non-engineers, or plan a migration off a system nobody wants to touch.
+description: Makes technical debt visible and decidable — distinguishing real debt from mess, quantifying its cost, and arguing for remediation in business terms. Use this to assess and prioritize debt, decide whether to fix or live with something, justify remediation work to non-engineers, or plan a migration off a system nobody wants to touch.
---
# Technical debt management
@@ -9,7 +9,7 @@ Debt is a deliberate trade: taking on future cost to move faster now. Most of wh
is not that — it is mess, which was never a decision, or drift, where the world moved and the code
did not. The distinction matters because the arguments and remedies differ.
-## Classify before prioritising
+## Classify before prioritizing
- **Deliberate debt** — a known shortcut with a reason. Has a principal and interest. Legitimate.
- **Mess** — nobody chose it; it accumulated. No trade was made, so there is nothing to defend.
@@ -39,7 +39,7 @@ Frame remediation as capacity recovery with a payback period — the same terms
## Remediate incrementally
Large rewrites fail at a well-documented rate: they take longer than estimated, deliver no value
-until the end, and are cancelled halfway leaving two systems. Prefer strangling the old system
+until the end, and are canceled halfway leaving two systems. Prefer strangling the old system
gradually behind a stable interface, so value lands continuously and the work can stop at any point
without leaving a mess.
@@ -49,6 +49,6 @@ cheapest code to improve, and it is by definition the code that is being touched
## Never
- Present debt as a quality argument to someone accountable for delivery dates.
-- Prioritise by how bad code looks rather than how often it is paid for.
+- Prioritize by how bad code looks rather than how often it is paid for.
- Start a rewrite with no value delivered until completion.
- Classify taste as debt.
diff --git a/scripts/build-org-chart.py b/scripts/build-org-chart.py
index d8a5eca..16d9463 100755
--- a/scripts/build-org-chart.py
+++ b/scripts/build-org-chart.py
@@ -5,16 +5,27 @@ Every department, skill, count and description comes from the tree, so the chart
organization the repository does not have. `--check` compares the committed file against freshly
generated output, the same contract as the README and the social card.
- python3 scripts/build-org-chart.py regenerate
+ python3 scripts/build-org-chart.py regenerate, then render the README screenshots
python3 scripts/build-org-chart.py --check fail if stale (CI)
+ python3 scripts/build-org-chart.py --html regenerate HTML only, skip rendering
+
+The screenshots are a light and a dark crop of this same page, embedded in the README inside a
+<picture> element so GitHub serves whichever matches the reader's theme. They are rendered from
+the generated HTML in the same run, so they cannot describe a different organization than it does.
+Rendering needs Chromium; without it the HTML is still written.
"""
import glob
import json
import os
import re
+import shutil
+import subprocess
import sys
OUT = "docs/org-chart.html"
+SHOT_LIGHT = "docs/assets/org-chart-light.png"
+SHOT_DARK = "docs/assets/org-chart-dark.png"
+SHOT_W, SHOT_H = 1280, 1010 # hero crop: masthead through the first full row of departments
REPO = "cbrock84/headcount"
BLOB = f"https://github.com/{REPO}/blob/main"
@@ -454,6 +465,28 @@ def render():
return html.replace("Search 135 skills", f"Search {total} skills"), len(depts), total
+def find_chromium():
+ """Playwright's bundled Chromium first, then anything on PATH."""
+ pw = os.environ.get("PLAYWRIGHT_BROWSERS_PATH", "/opt/pw-browsers")
+ candidates = [
+ os.path.join(pw, "chromium"),
+ *(shutil.which(n) for n in
+ ("chromium", "chromium-browser", "google-chrome", "google-chrome-stable")),
+ ]
+ return next((c for c in candidates if c and os.path.exists(c)), None)
+
+
+def shoot(chrome, out, dark):
+ subprocess.run(
+ [chrome, "--headless", "--no-sandbox", "--disable-gpu", "--hide-scrollbars",
+ "--force-device-scale-factor=2", f"--window-size={SHOT_W},{SHOT_H}",
+ "--virtual-time-budget=5000"]
+ + (["--force-dark-mode"] if dark else [])
+ + [f"--screenshot={out}", OUT],
+ check=True, capture_output=True)
+ return os.path.getsize(out) // 1024
+
+
def main():
html, ndept, nskill = render()
if "--check" in sys.argv:
@@ -466,6 +499,18 @@ def main():
os.makedirs(os.path.dirname(OUT), exist_ok=True)
open(OUT, "w", encoding="utf-8").write(html)
print(f"{OUT} regenerated — {ndept} departments, {nskill} skills")
+
+ if "--html" in sys.argv:
+ return 0
+ chrome = find_chromium()
+ if not chrome:
+ print(" no Chromium found — HTML written, README screenshots not re-rendered.")
+ return 0
+ os.makedirs(os.path.dirname(SHOT_LIGHT), exist_ok=True)
+ light = shoot(chrome, SHOT_LIGHT, dark=False)
+ dark = shoot(chrome, SHOT_DARK, dark=True)
+ print(f"{SHOT_LIGHT} {light} KB, {SHOT_DARK} {dark} KB "
+ f"— {SHOT_W*2}x{SHOT_H*2}, embedded in the README as a <picture>")
return 0
diff --git a/scripts/build-readme.py b/scripts/build-readme.py
index 278d202..797080c 100755
--- a/scripts/build-readme.py
+++ b/scripts/build-readme.py
@@ -17,7 +17,7 @@ META = {
"revenue": (70, "Revenue", "CRO"),
"finance": (80, "Finance", "CFO"),
"operations": (90, "Operations", "COO"),
- "pmo": (95, "Programme Management Office", "EPMO / COO"),
+ "pmo": (95, "Program Management Office", "EPMO / COO"),
"customer-experience": (100, "Customer Experience", "CCO"),
"data-analytics": (110, "Data & Analytics", "CDO"),
"corporate-strategy": (120, "Corporate Strategy", "CSO"),
@@ -82,6 +82,23 @@ out = [
f' <a href="CONTRIBUTING.md"><img alt="PRs welcome" src="{B}/PRs-welcome-2EA043?style=flat-square"></a>',
"</p>",
"",
+ # The chart is the clearest single statement of what this is, so it leads. GitHub does not
+ # render HTML from a repository, so the image links to the Pages copy, which does.
+ '<p align="center">',
+ ' <a href="https://cbrock84.github.io/headcount/org-chart.html">',
+ " <picture>",
+ ' <source media="(prefers-color-scheme: dark)" srcset="docs/assets/org-chart-dark.png">',
+ f' <img alt="The headcount org chart — {len(ORDER)} departments, {total} skills, searchable"'
+ ' src="docs/assets/org-chart-light.png" width="840">',
+ " </picture>",
+ " </a>",
+ "</p>",
+ "",
+ '<p align="center">',
+ ' <a href="https://cbrock84.github.io/headcount/org-chart.html"><b>Open the interactive org'
+ " chart</b></a> — search every skill, open a department, jump to the source.",
+ "</p>",
+ "",
"An agent organization for [Claude Code](https://claude.com/claude-code), structured as a company:",
f"a chief executive over {len(ORDER)} departments, {total} skills in total.",
"",
@@ -148,6 +165,7 @@ out += [
"docs/DECISION-LOG.md numbered decisions with options and recommendations",
"docs/USE-CASES.md situations worked end to end across departments",
"docs/org-chart.html interactive org chart, searchable across every skill",
+ "docs/index.html GitHub Pages entry point, redirects to the chart",
"```",
"",
"Agents split by **exclusive write surface**, not by topic — a topic split has no checkable",
@@ -161,15 +179,16 @@ out += [
"```",
"",
"Verifies the surface map is coherent, every skill's frontmatter is valid and unique, no",
- "third-party licence text has appeared, the generated README and social card are current, every",
- "`department:skill` reference in the docs resolves, and every manifest parses. CI runs the same",
+ "third-party license text has appeared, the generated README and social card are current, every",
+ "`department:skill` reference in the docs resolves, spelling is US English, and every manifest",
+ "parses. CI runs the same",
"script, so local and CI cannot drift.",
"",
"A new department needs its roster row in `docs/AGENT-SURFACES.md`, a surface block, a charter in",
"`.claude/agents/`, and an entry in `.claude-plugin/marketplace.json` — all in the same change, or",
"the check fails.",
"",
- "## Licence",
+ "## License",
"",
"MIT — see [LICENSE](LICENSE). Every skill here was written for this repository.",
"",
diff --git a/scripts/build-social-card.py b/scripts/build-social-card.py
index 52541c9..7d205d8 100755
--- a/scripts/build-social-card.py
+++ b/scripts/build-social-card.py
@@ -10,7 +10,7 @@ without needing a browser.
python3 scripts/build-social-card.py --check fail if the HTML is stale (CI)
python3 scripts/build-social-card.py --html regenerate HTML only, skip rendering
-Rendering needs Chromium. The PNG is a build artefact committed for convenience: GitHub wants a
+Rendering needs Chromium. The PNG is a build artifact committed for convenience: GitHub wants a
file upload, not a URL, so a copy in the repository is what you re-download when re-uploading it.
"""
import glob
diff --git a/scripts/check-all.sh b/scripts/check-all.sh
index ab5684b..76b6a0d 100755
--- a/scripts/check-all.sh
+++ b/scripts/check-all.sh
@@ -21,7 +21,7 @@ run "Surface map is coherent" \
node plugins/executive/skills/agent-hierarchy/scripts/agent-guard.mjs check
run "Skill frontmatter is valid" \
python3 scripts/validate-skills.py
-run "No third-party licence text" \
+run "No third-party license text" \
python3 scripts/check-provenance.py
run "README is current" \
python3 scripts/build-readme.py --check
@@ -31,6 +31,8 @@ run "Org chart is current" \
python3 scripts/build-org-chart.py --check
run "Skill references resolve" \
python3 scripts/check-skill-refs.py
+run "US English spelling" \
+ python3 scripts/check-us-english.py
run "Manifests parse" \
python3 -c "
import json,glob,sys
diff --git a/scripts/check-provenance.py b/scripts/check-provenance.py
index c443f4b..3f76f57 100755
--- a/scripts/check-provenance.py
+++ b/scripts/check-provenance.py
@@ -1,10 +1,10 @@
#!/usr/bin/env python3
"""All content here is original. This is a heuristic backstop, not proof: it catches the common
-shapes of third-party licence text and vendored assets. It cannot detect prose copied without a
+shapes of third-party license text and vendored assets. It cannot detect prose copied without a
notice, so it supplements review rather than replacing it."""
import glob, os, re, sys
-# Markers for the licences most likely to arrive with vendored material.
+# Markers for the licenses most likely to arrive with vendored material.
PATTERNS = [
r"\bMIT License\b",
r"\bApache License\b",
@@ -21,13 +21,26 @@ PATTERNS = [
]
# Filenames that carry someone else's terms, whatever their extension.
-LICENCE_NAMES = re.compile(
+LICENSE_NAMES = re.compile(
r"^(licen[cs]e|copying|notice|patents|authors|ofl)(\..*)?$|licen[cs]e", re.I
)
# Binary assets that are always third-party when present.
ASSET_EXTS = (".ttf", ".otf", ".woff", ".woff2", ".eot")
-OWN_LICENCE = "LICENSE" # ours, and the only one expected
+OWN_LICENSE = "LICENSE" # ours, and the only one expected
+
+# Naming our own license in our own documentation is expected and is not evidence of vendored
+# material: the decision log records why MIT was chosen, and the other two tell contributors what
+# they are agreeing to. Only the "MIT License" marker is waived, and only in these files — every
+# other pattern still applies, so an actually pasted license is still caught by its body text
+# ("Permission is hereby granted", "Copyright (c)"), which no real license lacks.
+#
+# This exemption exists because the check was previously passing these files by accident: they
+# spelled the word the British way, which this American-spelled pattern never matched. Converting
+# the prose to US English exposed the gap rather than creating it.
+OWN_LICENSE_MENTION = {"CONTRIBUTING.md", "README.md", "docs/DECISION-LOG.md"}
+OWN_LICENSE_PATTERN = r"\bMIT License\b"
+
SKIP_DIRS = (".git/",)
@@ -52,22 +65,25 @@ for path in glob.glob("**/*", recursive=True):
continue
if os.path.abspath(path) == os.path.abspath(__file__):
continue # this file necessarily contains the patterns it searches for
- if path == OWN_LICENCE:
+ if path == OWN_LICENSE:
continue
name = os.path.basename(path)
if name.lower().endswith(ASSET_EXTS):
problems.append(f"{path}: third-party font asset")
continue
- if LICENCE_NAMES.match(name):
- problems.append(f"{path}: third-party licence or notice file")
+ if LICENSE_NAMES.match(name):
+ problems.append(f"{path}: third-party license or notice file")
continue
# Every text file, whatever its extension — an extension allowlist is how a .txt slips past.
if not is_probably_text(path):
continue
text = open(path, encoding="utf-8", errors="replace").read()
+ waived = OWN_LICENSE_PATTERN if path in OWN_LICENSE_MENTION else None
for pattern in PATTERNS:
+ if pattern == waived:
+ continue
if re.search(pattern, text):
problems.append(f"{path}: matches {pattern!r}")
break
diff --git a/scripts/check-us-english.py b/scripts/check-us-english.py
new file mode 100755
index 0000000..7d08c4d
--- /dev/null
+++ b/scripts/check-us-english.py
@@ -0,0 +1,141 @@
+#!/usr/bin/env python3
+"""Enforce US English spelling across the repository.
+
+The author writes in US English, so the catalogue does too. This is a house style rule rather than
+a correctness one, but it is the kind that decays without enforcement: a single skill written in
+British spelling reads as though it came from somewhere else, which is exactly the impression a
+repository of original work should not give.
+
+ python3 scripts/check-us-english.py report British spellings (CI)
+ python3 scripts/check-us-english.py --fix rewrite them in place
+
+Only exact word forms are listed. Stems are a trap here: "analysis", "analyst", "specialist" and
+"realistic" are correct US English and must never be rewritten, so `analyse` is listed and `analys`
+is not.
+"""
+import os
+import re
+import sys
+
+# British -> American. Exact forms only, matched on word boundaries.
+PAIRS = {
+ "programme": "program", "programmes": "programs",
+ "licence": "license", "licences": "licenses", "licenced": "licensed",
+ "behaviour": "behavior", "behaviours": "behaviors", "behavioural": "behavioral",
+ "favour": "favor", "favours": "favors", "favoured": "favored",
+ "favourable": "favorable", "favourite": "favorite",
+ "colour": "color", "colours": "colors", "coloured": "colored",
+ "honour": "honor", "honours": "honors", "labour": "labor",
+ "analyse": "analyze", "analysed": "analyzed", "analyses": "analyzes",
+ "analysing": "analyzing",
+ "organise": "organize", "organised": "organized", "organising": "organizing",
+ "organisation": "organization", "organisations": "organizations",
+ "organisational": "organizational",
+ "prioritise": "prioritize", "prioritised": "prioritized",
+ "prioritising": "prioritizing", "prioritisation": "prioritization",
+ "optimise": "optimize", "optimised": "optimized", "optimising": "optimizing",
+ "optimisation": "optimization",
+ "recognise": "recognize", "recognised": "recognized", "recognising": "recognizing",
+ "recognisable": "recognizable",
+ "realise": "realize", "realised": "realized", "realising": "realizing",
+ "realisation": "realization",
+ "minimise": "minimize", "minimised": "minimized", "minimising": "minimizing",
+ "minimisation": "minimization",
+ "maximise": "maximize", "maximised": "maximized", "maximising": "maximizing",
+ "standardise": "standardize", "standardised": "standardized",
+ "standardising": "standardizing",
+ "specialise": "specialize", "specialised": "specialized", "specialising": "specializing",
+ "summarise": "summarize", "summarised": "summarized", "summarising": "summarizing",
+ "authorise": "authorize", "authorised": "authorized", "authorising": "authorizing",
+ "authorisation": "authorization",
+ "customise": "customize", "customised": "customized",
+ "utilise": "utilize", "utilised": "utilized", "utilising": "utilizing",
+ "capitalise": "capitalize", "capitalised": "capitalized",
+ "amortise": "amortize", "amortised": "amortized", "amortisation": "amortization",
+ "pseudonymise": "pseudonymize", "pseudonymised": "pseudonymized",
+ "pseudonymisation": "pseudonymization",
+ "synthesise": "synthesize", "synthesised": "synthesized",
+ "catalogue": "catalog", "catalogues": "catalogs", "catalogued": "cataloged",
+ "artefact": "artifact", "artefacts": "artifacts",
+ "judgement": "judgment", "judgements": "judgments",
+ "acknowledgement": "acknowledgment", "acknowledgements": "acknowledgments",
+ "ageing": "aging", "grey": "gray",
+ "sceptic": "skeptic", "sceptical": "skeptical", "scepticism": "skepticism",
+ "defence": "defense", "defences": "defenses",
+ "offence": "offense", "offences": "offenses",
+ "practise": "practice", "practised": "practiced", "practising": "practicing",
+ "fulfilment": "fulfillment", "enrolment": "enrollment",
+ "instalment": "installment", "instalments": "installments",
+ "modelling": "modeling", "modelled": "modeled",
+ "labelling": "labeling", "labelled": "labeled",
+ "signalling": "signaling", "signalled": "signaled",
+ "cancelling": "canceling", "cancelled": "canceled",
+ "travelling": "traveling", "travelled": "traveled",
+ "centre": "center", "centres": "centers", "centred": "centered",
+ "whilst": "while", "amongst": "among",
+ "learnt": "learned", "spelt": "spelled", "burnt": "burned",
+ "manoeuvre": "maneuver", "cheque": "check",
+}
+WORD = re.compile(r"\b(" + "|".join(sorted(PAIRS, key=len, reverse=True)) + r")\b", re.I)
+
+SKIP_DIRS = {".git", "node_modules", "__pycache__"}
+# LICENSE is the canonical MIT text and is never rewritten. This file lists British spellings by
+# definition, so it excludes itself the way check-provenance.py does.
+SKIP_FILES = {"LICENSE", os.path.basename(__file__)}
+TEXT_EXT = {".md", ".py", ".sh", ".json", ".yml", ".yaml", ".html", ".txt", ".mjs", ".js"}
+
+
+def match_case(british, american):
+ if british.isupper():
+ return american.upper()
+ if british[0].isupper():
+ return american[0].upper() + american[1:]
+ return american
+
+
+def files():
+ for root, dirs, names in os.walk("."):
+ dirs[:] = [d for d in dirs if d not in SKIP_DIRS]
+ for n in names:
+ if n in SKIP_FILES or os.path.splitext(n)[1] not in TEXT_EXT:
+ continue
+ yield os.path.join(root, n)
+
+
+def main():
+ fix = "--fix" in sys.argv
+ problems, changed = [], 0
+
+ for path in sorted(files()):
+ try:
+ text = open(path, encoding="utf-8").read()
+ except (UnicodeDecodeError, OSError):
+ continue
+ if not WORD.search(text):
+ continue
+
+ if fix:
+ new = WORD.sub(lambda m: match_case(m.group(1), PAIRS[m.group(1).lower()]), text)
+ if new != text:
+ open(path, "w", encoding="utf-8").write(new)
+ changed += 1
+ else:
+ for n, line in enumerate(text.splitlines(), 1):
+ for m in WORD.finditer(line):
+ b = m.group(1)
+ problems.append(f"{path}:{n}: '{b}' -> '{match_case(b, PAIRS[b.lower()])}'")
+
+ if fix:
+ print(f"US English: rewrote {changed} file(s)")
+ return 0
+ for p in problems[:40]:
+ print(f" {p}")
+ if len(problems) > 40:
+ print(f" … and {len(problems) - 40} more")
+ print(f"US English: {len(problems)} British spelling(s)"
+ + ("" if not problems else " — run: python3 scripts/check-us-english.py --fix"))
+ return 1 if problems else 0
+
+
+if __name__ == "__main__":
+ sys.exit(main())