Who it is forA founder or executive about to commit to a plan, hire, or product bet.
The problemDecisions often rest on one untested assumption that nobody has written down.
The outcomeThe key assumption, the strongest case against the decision, and what would have to be true for it to work.
What you need first
- Claude Code, or ChatGPT or Codex with the repository added as a plugin marketplace
- A project or document that the skills can read, such as a design doc, a page, or a figures summary
- Permission to add a plugin marketplace to your coding tool
Steps
- In Claude Code, run
/plugin marketplace add cbrock84/headcount. - Run
/plugin install executive@headcount. (inferred, check the README) - Describe the decision in a few sentences, including the plan, the cost, and the expected result.
- Write down the assumption the answer names and check it with real data.
Prompt for your agent
Using the cbrock84/headcount repo, load the executive:ceo-advisor skill and pressure-test the plan in <plan-file>. 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.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page