# AI use cases for Headcount (cbrock84/headcount) Repo: [cbrock84/headcount](https://github.com/cbrock84/headcount) | Use cases: 4 | Page: https://dedupedai.com/use-cases/cbrock84-headcount/ Headcount is a set of AI agent skills organized as a company, with departments such as security, finance, and product that you install separately into Claude Code, ChatGPT, or Codex. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Review a design for threats before building it: https://dedupedai.com/use-cases/cbrock84-headcount/review-design-before-build/ - Check whether a planned hire is affordable: https://dedupedai.com/use-cases/cbrock84-headcount/check-hire-affordability/ - Diagnose why a landing page is not converting: https://dedupedai.com/use-cases/cbrock84-headcount/diagnose-landing-page-conversion/ - Pressure-test a business decision before committing: https://dedupedai.com/use-cases/cbrock84-headcount/pressure-test-a-decision/ ## How to review a design for threats before building it with Headcount Repo: [cbrock84/headcount](https://github.com/cbrock84/headcount) | Difficulty: Beginner | Time: 15 minutes | Basis: From the README Load the security threat-modeling skill to find assets, entry points, and trust boundaries in a planned design. **Who it is for:** An engineer or tech lead with a design doc for a new feature who wants security issues found before code is written. **The problem:** Security gaps in a design are cheaper to fix before build, but reviewing them needs a specialist lens that is easy to skip. **The outcome:** A threat model for the design that names the assets worth attacking, the entry points, the trust boundaries, and the controls that address them. ### Steps 1. In Claude Code, run `/plugin marketplace add cbrock84/headcount`. 2. Run `/plugin install security@headcount`. 3. Ask in plain words, for example "review this design before we build it", and attach or paste the design doc. 4. To call the skill directly, run `/security:threat-modeling`. (inferred, check the README) ### Prompt to paste into your agent ```text Using the cbrock84/headcount repo, load the security:threat-modeling skill and run it against the design in . Expected output: a list of assets, entry points, trust boundaries, and controls for that design. Verify that every trust boundary named in the output appears in the design doc. ``` ### Caveat The README describes the security department as reviewer-class, so expect it to flag stop conditions rather than only offer opinions. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/cbrock84-headcount/review-design-before-build/ ## How to check whether a planned hire is affordable with Headcount Repo: [cbrock84/headcount](https://github.com/cbrock84/headcount) | Difficulty: Beginner | Time: 15 minutes | Basis: From the README Use the finance unit-economics skill to test a hire against your revenue and cost figures. **Who it is for:** A founder or operator deciding whether the company can carry a new salary. **The problem:** A hire can look reasonable on a salary line alone while the wider unit economics do not support it. **The outcome:** An assessment of whether the hire fits the business numbers you provide, based on the unit-economics skill. ### Steps 1. In Claude Code, run `/plugin marketplace add cbrock84/headcount`. 2. Run `/plugin install finance@headcount`. (inferred, check the README) 3. Ask "can we afford this hire?" and give the salary, the fully loaded cost, and the revenue or margin figures you have. 4. Check the answer against your own numbers before acting on it. ### Prompt to paste into your agent ```text Using the cbrock84/headcount repo, load the finance:unit-economics skill and assess the hire described in . Expected output: an affordability view based only on the figures in that file. Verify that every number cited in the answer appears in the input file. ``` ### Caveat The skill can only reason from the figures you supply, so missing revenue or cost data will limit the answer. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/cbrock84-headcount/check-hire-affordability/ ## How to diagnose why a landing page is not converting with Headcount Repo: [cbrock84/headcount](https://github.com/cbrock84/headcount) | Difficulty: Beginner | Time: 15 minutes | Basis: From the README Load the demand-generation landing-page CRO skill to find the likely causes of low conversion. **Who it is for:** A marketer or founder whose landing page gets visits but few sign-ups. **The problem:** Low conversion has many possible causes, and it is hard to tell which one applies to a specific page. **The outcome:** A diagnosis of the conversion problem on the page you share, with the specific changes the skill suggests. ### Steps 1. In Claude Code, run `/plugin marketplace add cbrock84/headcount`. 2. Run `/plugin install demand-generation@headcount`. (inferred, check the README) 3. Ask "why isn't this landing page converting?" and paste the page copy or share its URL with the traffic and goal you have. 4. Test one suggested change at a time and measure the result. ### Prompt to paste into your agent ```text Using the cbrock84/headcount repo, load the demand-generation:landing-page-cro-expert skill and review the page content in . Expected output: likely causes of low conversion and the changes it recommends. Verify that each recommendation refers to an element that exists in the page copy. ``` ### Caveat The README gives no conversion benchmarks, so the skill's recommendations should be tested against your own traffic before you rely on them. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/cbrock84-headcount/diagnose-landing-page-conversion/ ## How to pressure-test a business decision before committing with Headcount Repo: [cbrock84/headcount](https://github.com/cbrock84/headcount) | Difficulty: Beginner | Time: 15 minutes | Basis: From the README Use the CEO advisor skill to surface the assumption a plan rests on and the case against it. **Who it is for:** A founder or executive about to commit to a plan, hire, or product bet. **The problem:** Decisions often rest on one untested assumption that nobody has written down. **The outcome:** The key assumption, the strongest case against the decision, and what would have to be true for it to work. ### Steps 1. In Claude Code, run `/plugin marketplace add cbrock84/headcount`. 2. Run `/plugin install executive@headcount`. (inferred, check the README) 3. Describe the decision in a few sentences, including the plan, the cost, and the expected result. 4. Write down the assumption the answer names and check it with real data. ### Prompt to paste into your agent ```text Using the cbrock84/headcount repo, load the executive:ceo-advisor skill and pressure-test the plan in . Expected output: the main assumption, the case against the plan, and what would have to be true. Verify that the named assumption is actually stated or implied in the plan file. ``` ### Caveat The skill gives a challenge to the decision, not a verdict, so the final call stays with you. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/cbrock84-headcount/pressure-test-a-decision/