Creates behavioral personas, ideal customer profiles, and applies Jobs-to-be-Done framework via user interviews. Generates MY-ICP.md for other skills.
npx claudepluginhub whawkinsiv/solo-founder-superpowers --plugin solo-founder-superpowersThis skill uses the workspace's default tool permissions.
Personas based on demographics are useless. Personas based on behaviors, goals, and constraints drive decisions. This skill helps you run interviews, apply Jobs-to-be-Done, and build personas that actually inform your product.
Provides Ktor server patterns for routing DSL, plugins (auth, CORS, serialization), Koin DI, WebSockets, services, and testApplication testing.
Conducts multi-source web research with firecrawl and exa MCPs: searches, scrapes pages, synthesizes cited reports. For deep dives, competitive analysis, tech evaluations, or due diligence.
Provides demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation for multi-location retailers managing 300-800 SKUs.
Personas based on demographics are useless. Personas based on behaviors, goals, and constraints drive decisions. This skill helps you run interviews, apply Jobs-to-be-Done, and build personas that actually inform your product.
A "job" is the progress a user is trying to make in a specific circumstance.
Job statement format: "When I [situation], I want to [motivation], so I can [desired outcome]."
Examples:
Discover jobs by asking:
## [Persona Name] — [One-line role description]
### Behavioral Segment
What behavior defines this group? (e.g., "Uses the product daily for team
coordination" or "Evaluates tools quarterly for the team")
### Primary Job
[Job statement in JTBD format]
### Context
- Role and responsibilities (relevant to product usage)
- Team size and structure
- Tools they use alongside yours
- Technical sophistication level
- Decision-making authority (buyer, influencer, user)
### Current Workflow (without your product)
Step-by-step: How do they accomplish this job today?
Where are the friction points?
### Key Pain Points
1. [Specific, observed pain — not assumed]
2. [Another specific pain]
3. [Another specific pain]
### Success Criteria
How do they measure whether the job is done well?
What would make them say "this is working"?
### Objections / Barriers to Adoption
What would prevent them from trying or buying?
### Trigger Events
What circumstances push them to seek a new solution?
(Team growth, tool sunset, new mandate, frustration peak)
Before the interview:
Opening (2 min): "Thanks for joining. I'm trying to understand how people [do X]. There are no right answers — I'm learning from your experience. Can I ask you some questions about how you currently handle [topic]?"
Core questions (25 min):
Closing (3 min): "Is there anything about [topic] I should have asked but didn't?" "Would you be open to trying an early version and giving feedback?"
If you're building for your own profession, you have a unique advantage and a unique blind spot.
The advantage: You understand the pain deeply. You don't need to "discover" the problem — you've lived it.
The blind spot: You assume everyone does the job the way you do. They don't. After 20 years, your workflow is optimized. A 3-year practitioner's workflow is different. A solo practitioner's is different from someone at a large firm.
How to correct for this:
After interviews, synthesize:
Research is only valuable if it changes decisions:
Research is useful in the moment. MY-ICP.md makes it useful forever. This file captures who your customer is so every other skill — landing pages, ads, email, pricing copy — can use their language instead of your marketing language.
If you ARE your customer (or were recently), you can skip interviews and write this directly. But be honest about your blind spots — the "When You ARE the Persona" section above still applies.
Describe your ideal customer. Be specific about who they are, what frustrates them, what they're trying to accomplish, how they make buying decisions, and what words they actually use when talking about this problem. If you have multiple customer types, describe each one — start with your primary.
Pull from your Interview Analysis above:
# My Ideal Customer Profile
## Primary ICP: [Name or label — e.g., "Solo Consultants" or "Marketing Managers at Series A startups"]
### Who They Are
[Role, company size, experience level, relevant demographics.
Not a persona — specific enough that you could find them on LinkedIn.]
### Their Pain
[Primary problems, current workarounds, what frustrates them.
Use THEIR words, not your marketing language.
Example: "I spend 3 hours every Monday pulling reports from 4 different tools"
not "inefficient multi-platform reporting workflows."]
### Their Goals
[What success looks like to them. What they're trying to achieve.
The outcome they'd pay for, in their framing.]
### How They Buy
[Decision process — do they decide alone or need approval?
Common objections. Price sensitivity. What triggers a purchase.
What makes them say no.]
### Their Language
[Actual words and phrases they use to describe the problem.
Pull directly from interviews, Reddit posts, reviews, support tickets.
This section is gold for landing pages, ads, and email subject lines.]
### Where They Are
[Communities, publications, events, Slack groups, subreddits, LinkedIn groups.
Where you can reach them. Where they go for advice.]
---
## Secondary ICP: [Name or label] (if applicable)
[Same sections as above. Only add a secondary if the audiences are
genuinely distinct — different roles, different pains, different language.
If they're similar, one profile is fine.]
ABOUT-ME.md, the companion file. MY-ICP.md is who your customer is. ABOUT-ME.md is who you are. Together they let skills personalize both message and voice.