Skip to main content
This guide walks you through your first session. All you need is an installed plugin (Installation) and an idea — even a fuzzy one.

​
Your first session

1

Run /whats-next

In your idea’s workspace folder, run:
This is the plugin’s home base. On first run it notices there’s no project yet and starts the setup conversation.
2

Describe your idea

Tell the agent what you’re building — a sentence or a rambling voice-note-style paragraph, both work. It will ask follow-up questions one at a time to pin down the essentials: who it’s for, what problem it solves, how it solves it.
Use voice mode and think out loud. In the CLI, activate it once via /voice and then long-press space to speak. Don’t worry about structure — the more you dump, the better the agent can organise it.
Already made progress before installing the plugin — notes, interviews, a landing page? Say so: the setup flow has a materials-based onboarding path that ingests what you have instead of starting from zero.
3

Review what it writes

The agent proposes before it writes. When you confirm, it creates the startup/ folder in your project:
Both are plain markdown — open them, edit them, commit them to git.
4

Follow the plan

plan.md now holds your current focus and a checklist of next steps — typically starting with discovering competitors and drafting your first hypotheses. Each step maps to a skill, and the agent will route you to the right one.

​
After the first session

Come back to /whats-next whenever you want to know where you stand — it re-orients you, surfaces the sharpest next move, and updates the plan as evidence comes in. From there the typical journey runs:
  1. /competitors — map who else is solving this problem
  2. /market-research — check the market is real and see how buyers in it behave
  3. /hypotheses — write down what you’re assuming is true
  4. /interviews — test those assumptions in real conversations
  5. /surveys — test signals at larger scale
  6. /mvp — build the smallest thing that generates honest signal
Running alongside all of it: /first-users — where your audience actually spends its time, and who you can reach today. It’s easy to read that as a launch-day concern, but the first time you need it is usually step 4: research and hypotheses don’t help if you can’t find five people to talk to. It builds one shared list, so interviews, survey distribution, and your MVP launch all draw on the same names instead of each asking you again. Validation is rarely a straight line, and every skill also works standalone — see the Skills overview for what each one does and when to reach for it. To understand the files the plugin creates and how they link together, start with The startup/ workspace.