The GTM Co-Founder
For the founder building it alone.
If you're a technical founder pouring your own money, your nights, and your weekends into something you believe in, with no funding, no team, no commercial co-founder, and some days it is just plain hard, then this is for you. Especially you.
Building alone is isolating. The engineering, you can do in your sleep. It's the other half that keeps you up at 2am, with no one in the room to think it through: who is this even for? why would anyone pay? why did nobody come when I shipped?
That's what this is: the GTM co-founder you don't have (yet), a full set of go-to-market skills sitting in your corner, inside the agent you already code in. Not a course. Frameworks with real numbers and concrete next steps, not theory, built from years of selling and advising developer tools, sharpened by the sharpest thinking in the field (Adam Frankl and Jakub Czakon), and pressure-tested by founders who used it in the trenches, so the commercial side can feel as rigorous, and as doable, as the code.
You don't have to figure this part out alone anymore.
Answer a set of questions once (about 15 minutes), and your agent builds you a prioritized GTM roadmap, then works it with you one move at a time: positioning, first users, launch, pricing, in the order that matters for your stage.
Not marketing tactics or SEO skills. This is the strategy half of go-to-market: who it's for, why they'd pay, and how to land your first users. For the founder who can build anything but freezes on that.
Works with Claude Code, Cursor, Codex, Windsurf, Antigravity and any agent that supports the Agent Skills spec.
See it in action
A real example: five questions, then a diagnosis the founder couldn't see themselves.
https://github.com/user-attachments/assets/54bbb54a-006d-4189-ba63-5f754fdf5268
How to use it
Never used "skills" before? You don't need to. These are just markdown playbooks. The "skill" part only means an agent knows when to reach for each one. Pick the path that fits.
Path 1: zero setup (30 seconds)
Open any skill, copy the text, paste it into ChatGPT, Claude, or Cursor, and say:
Apply this to my product: [one line on what you're building].
Start with 00-start-here, then 01-strategy-and-roadmap. That is the spine of the whole thing.
Path 2: download and drop in (no terminal)
No CLI, no git. Grab a zip from the latest release.
- Claude apps (claude.ai, desktop): download any single skill's zip, then go to Customize → Skills → Create skill and upload it. Claude reads it and switches it on. Start with
00-start-here, then add the others you want. - Claude Code, without the CLI: download
gtm-cofounder-skills.zip, unzip it, and move the folders into~/.claude/skills/.
Path 3: hand your agent the folder (2 minutes)
In Cursor or Claude Code, open this repo (or your own project with it cloned) and paste this once:
You are my GTM co-founder. Read AGENTS.md and the skills in this repo. Start with 00-start-here to interview me one question at a time and write a docs/gtm-cofounder/founder-brief.md. Then run 01-strategy-and-roadmap to turn that into a prioritized docs/gtm-cofounder/gtm-roadmap.md. From then on, work the roadmap with me one move at a time. Offer, never impose: don't start a task I haven't picked, and if I say no to something, park it and move on. Be direct and specific, no fluff, and always end by telling me the single next move.
Path 4: install as real skills (they auto-trigger)
Claude Code (direct)
git clone https://github.com/AIDevGTM/gtm-cofounder.git
cp -r gtm-cofounder/skills/* ~/.claude/skills/
Claude Code (plugin marketplace) (run these in the Claude Code CLI)
/plugin marketplace add AIDevGTM/gtm-cofounder
/plugin install gtm-cofounder@gtm-cofounder
skills.sh CLI (any agent) (requires Node.js)
npx skills add AIDevGTM/gtm-cofounder
Cursor / Codex / other agents
Copy the skills/ folder into your agent's skills directory. Each skill is self-contained: one folder, one SKILL.md, zero dependencies.
The skills
0 · Start here: brief, then plan (do this first)
Two one-time steps set up everything else. First, the founder brief: answer just five core questions and the agent writes a docs/gtm-cofounder/founder-brief.md it reads before every other skill, so "sharpen your ICP" means your ICP and "find your villain" means your villain, not a textbook's. If you run it inside your project, it reads your repo first (README, recent commits, PR titles, open issues) to pre-fill the brief with what you've actually shipped, so the advice is specific from the first minute instead of generic. The rest of the intake is optional and answered as you go: each skill asks for the deeper questions it needs, when it needs them, and tells you what answering unlocks, so you get value in minutes instead of after a long form. It separates what you've validated with real users from what you're still assuming, and routes the assumptions to talk-to-users so the brief gets truer over time instead of ossifying a guess.
Then the roadmap: the agent turns that brief into an honest diagnosis and a prioritized, stage-aware plan in docs/gtm-cofounder/gtm-roadmap.md, the one Now move, what's Next, and what to park for Later. This is the hub you come back to every session, so you never stare at a dead chat wondering what to do next. It sequences the skills for you instead of leaving you to guess which one to trigger.
| Skill | Reach for it when… |
|---|---|
| start-here | Setup, or the agent keeps giving generic advice because it doesn't know your business |
| strategy-and-roadmap | You don't know what to work on next, or you're being handed one-off tasks that don't add up to a plan |
Runs throughout (a gate, not a step)
| Skill | Reach for it when… |
|---|---|
| review-the-work | Before you ship anything. The agent stops being the author and stress-tests the piece as a skeptic, so weak or unprovable claims never reach you |
1 · Figure out who it's for
| Skill | Reach for it when… |
|---|---|
| who-is-this-for | You built it "for developers", but "developers" is not an ICP, and you can't say who says no |
| talk-to-users | You've never interviewed a user who isn't already your friend, so your roadmap is a guess |
2 · Say it so it lands
| Skill | Reach for it when… |
|---|---|
| positioning-and-story | Your homepage describes your solution, not their problem, and you sound like every competitor |
| beyond-the-wrapper | (AI products only, skip if not) People call your AI product "just a wrapper," everyone claims AI, and you can't say why you win when the model is a commodity |
| value-prop-that-converts | Your value prop says "powerful," "better," and "seamless", words a developer has learned to ignore |
| the-homepage | Your landing page is written for the buyer, who never visits it, instead of the developer, who does |
3 · Get your first users
| Skill | Reach for it when… |
|---|---|
| time-to-first-value | People sign up or star it, then never get it working, or come once and never come back |
| first-50-users | You shipped, tweeted once, and nobody came, and you don't know which channel to even try |
| launch-it | You're sitting on a Show HN / Reddit / Product Hunt launch because you're scared of getting flamed |
| market-to-devs-sell-to-buyers | Developers love it, star it, use the free tier, and nobody will pay |
| pricing | You're guessing at a number, gave it away too cheap, or "developers won't pay" so you never charge |
| founder-led-sales | Developers love it and use the free tier, but you've never sold anything and "let me think about it" kills every deal |
4 · Keep it going
| Skill | Reach for it when… |
|---|---|
| founder-led-content | "Marketing" feels gross, so you do none, while your competitor owns the conversation |
| know-if-its-working | You have dashboards full of vanity metrics and no idea whether GTM is actually working |
| market-scan | A rival just rebranded or a new tool appeared, and your positioning is answering last year's market |
What's inside each skill
Every SKILL.md gives you frameworks with actual thresholds (not principles), decision trees for the calls that stall technical founders, the mistakes that look reasonable but quietly kill you, real examples, and a checklist you can run in the next 30 minutes. Written in a founder's language, direct, specific, allergic to fluff.
Where this comes from
The spine of this pack is my own experience selling and advising developer tools: years as an enterprise and founding account executive, and advising early-stage dev-tool founders through exactly the fights these skills cover. That lived experience is what most of this is.
It's sharpened by the two people who have shaped developer go-to-market thinking the most, and their work is worth reading in full:
- Adam Frankl, The Developer-Facing Startup. Strategy and philosophy: TAB customer discovery, the Hero/Villain/Wise-Advisor story, the DREAM funnel, differentiation levels, net developer retention.
- Jakub Czakon, markepear.dev. Tactical execution: homepage anatomy, developer psychol