From founder-os
Collect what the ICP actually says about their problem, verbatim and sourced — run before a content plan, and whenever the founder is about to write about a topic instead of a question
How this skill is triggered — by the user, by Claude, or both
Slash command
/founder-os:audience-researchThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Research that produces topics is useless. "They care about scalability" is a
Research that produces topics is useless. "They care about scalability" is a topic; it cannot be written from, argued with, or headlined. "We rewrote it twice and I'm not doing that again" is a sentence a real person said, and it is the piece.
So this skill collects sentences, verbatim, with a source and a date. A paraphrase is the founder's words wearing the audience's clothes — and the founder's words are the problem, since they are the reason prospects say "I didn't really understand what you do".
Before content-plan, and whenever the plan starts filling with topics. Also
when the founder is about to open a keyword tool, which is a distant fourth
source and the only one that never argues back.
Read first, in order — house rule 1. The ranking is the method:
pipeline.md — what prospects actually asked on calls, and the objection
the founder answers every single time. This is the best data in the company
and it is already in the workspace, unread.clients/ — what buyers said before they bought, and what they complained
about afteroffer.md — the ICP. A quote from someone outside it is noise, and it is
attractive noise, because there is much more of it.ingestion-gate — every line this skill writes is a sentence a person said,
so the gate is not an extra step here, it is the ranking above restated as a
rule. Source 3 is where it bites: a public post is the ICP describing their own
situation, which is FACT, right up until it is a vendor describing a market,
which is paid speech and does not enter.pipeline.md and write down what
prospects asked, in their words. If the founder did not record the questions,
that is finding number one and it is worth more than this month's plan.Write to content.md, replacing ## Audience:
## Audience — updated YYYY-MM-DD
Sample: <n> quotes from <n> people (min 10 — below that, GUESS)
### What they say — verbatim
- "<exact quote, ugly phrasing intact>" (per <role, ICP-fitting company>,
<channel>, YYYY-MM-DD)
### Repeats — said 3+ times
- "<the question>" — heard <n>× (per <role> <date>; <role> <date>; <role> <date>)
→ planned as <piece> | handed to Positioning Advisor
### The sentence that works on calls
"<the founder's own spoken explanation>" — published: <yes | NO>
(per the founder, <channel>, YYYY-MM-DD)
### Translation table
| founder says | they say | first heard from | when |
|--------------|----------|------------------|------|
Every row in this file is a stamp with a sentence attached — that is not
ceremony, it is the skill. Repeats names all three speakers and all three
dates, not just the count. heard 3× is one integer standing in for three
tiers, and the whole argument of step 4 is that three is a pattern: three people
is a pattern, one person on three calls is a customer with a bugbear, and the
integer cannot tell them apart. If the three dates are all one week, that is not a
pattern either — it is a news cycle.
The translation table gains first heard from and when for the same reason: a
buyer vocabulary from 2023 is how a founder ends up carefully translating into
words nobody uses any more.
Never invent a quote and never invent a person. Not as an illustration, not as a placeholder, not "roughly what they'd say". A fabricated quote is indistinguishable from a real one in the file, and it will be published as evidence within a month.
Never paraphrase into the quote block. If you do not have the exact words, you have a note — file it as a note.
Never publish a quote from a private call without the founder confirming
permission. Public writing is public; a sales call is not, and that distinction
may also be a contract question. See guardrails.
If pipeline.md is thin, say the sample is too small rather than filling the
gap from what similar companies say. The gap is the finding: the founder has not
spoken to enough of their ICP, and no amount of desk research substitutes for
that.
npx claudepluginhub msolecki/founder-os --plugin founder-osGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.