Founder Consumer
The consumer panel.
Install
npx skills add Jakeschincariol/founder-skill --skill founder-consumer -g -a claude-code -y- Repository
- Jakeschincariol/founder-skill2.3k
- Category
- Testing
- Updated
- 29d ago
- License
- MIT
- Context cost
- Lightabout 1,257 tokens
- Runs scripts
- Yes, review before use
What it does
The consumer panel. Spins up a swarm of buyer sub-agents (default 100, --quick for 20) trained on the user's target customer, each with a different income, age, buying behaviour and objection, shows every one the same pitch, and runs the business through 100 buyer scenarios to see who buys, who doesn't, and why. Tallies the answers into buy rates by segment, the reasons people pass in their own words, what would flip a no, and price answers for founder-pricing. Use when the user says "would people buy this", "test it on customers", "run the consumer panel", "simulate buyers", "who is my customer", or "validate demand".
founder-consumer
The craziest part of the pack. Instead of guessing whether people will buy, you ask a hundred of them, each one a sub-agent playing a specific buyer drawn from your target customer. You are the moderator. You never answer for a buyer.
What the user typed after /founder-consumer: $ARGUMENTS
The tool
All bookkeeping goes through panel.py in this skill's folder:
python3 "${CLAUDE_SKILL_DIR}/panel.py" <command>
Below, PANEL means exactly that. If the path is not expanded, use the base
directory Claude Code printed for this skill. State lives in founder/panel/.
Step 1: the target customer
Write founder/customer.json (shape: customer.example.json in this folder):
business, andtarget: who the customer is, in one specific line.segments: 2 to 4 groups with ashareand anincomerange [low, high].behaviours: 4 to 8 buying behaviours with ashareand ahowline (daily regular, deal hunter, reads every review, loyal to a competitor...).objections: the 4 to 8 doubts this kind of buyer really has.habits(optional): everyday context lines that make a buyer concrete.
Ground it in something real. Use what the user knows about their customers, and
if /founder-competitors ran, the complaints in founder/competitors.md. If the
user has real customer data (interviews, reviews, survey answers), prefer it to
your guesses and say which parts are guesses. Show the user the profile in a few
lines and let them correct it before you deal: a wrong customer makes the whole
panel wrong.
Step 2: the pitch
Write founder/pitch.md: what a buyer would actually see. The product, the price,
where and how to get it, any opening offer. Three to six plain lines, no
superlatives, nothing the business cannot deliver. Every buyer sees exactly this.
Step 3: deal and run
PANEL init --customer founder/customer.json --pitch founder/pitch.md --n 100
PANEL prompts
