skill business-interview
Stop explaining
your business
every session.
Claude Code reads a file at the top of every project. Almost nobody fills it in properly, because writing "here is my business" into a blank document is a chore, and what comes out reads like a brochure. So instead you re-explain the same five things at the start of every session, and the answers you get back are generic because the context was.
This turns that file into a conversation. Nine blocks of three or four questions, one block at a time, about twenty minutes. At the end it shows you what it learned and writes it down.
Get it on GitHub Read the limits firstWhy it exists
I wrote it for the first session of a workspace I hand to clients, and the thing that kept happening was the reason it exists. Ask someone to describe their business and you get the pitch. Ask them what a customer paid for last week, who they lost a deal to, and what number they actually check on a Monday, and you get the business.
The questions are the product here. A prompt that says "tell Claude about your company" gets you a paragraph. Nine blocks that wait for one answer at a time, push back once when an answer is vague, and refuse to write down a number you did not give, get you a file that makes every other thing Claude does for you specific.
The part I am proudest of is the fork. If the first block reveals there is no business yet, only an idea, it stops and changes the questions. Asking someone pre-launch about gross margin does not produce a blank, it produces a number they invented on the spot, and that invented number then sits in a file and poisons everything downstream. The pre-launch track asks about what already happened instead, and does the pricing arithmetic backwards from what they need to earn.
What it does
Asks one block at a time
Business, product, customer, how people find you, money, competition, goals, your stack, and how you want Claude to work. Three or four questions each, then it waits. It reads the room after the first block and drops the follow-ups that do not apply to your kind of business. If a later block is already answered, it skips it rather than asking twice.
Changes the questions when there is no business yet
Idea stage gets a different track: who you have already done this for, even free, and what their reaction was. What exactly someone would get if they paid you tomorrow. What it has to make per month to be worth doing. Then the arithmetic, in front of you: income target divided by how much you can deliver, minus tax and cost, compared against the price you had in mind. That calculation usually ends the conversation about price on the spot.
Writes unknown instead of guessing
If you do not know a figure, that is what goes in the file. It will push once on a vague answer, politely, then take what you give it. The money block is optional and it will not ask you twice.
Shows you the files before it writes them
It ends with a summary of your business in fifteen lines, the three places Claude can help you most, and a list of exactly what it is about to write and where. Nothing is saved until you say yes. Run it again in six months and it asks which parts have changed, then merges rather than overwriting.
What it cannot do
It records what you tell it. It is not a strategy document and it does not check your thinking. Thin answers make a thin file, and every skill that reads that file afterwards inherits the thinness. Twenty honest minutes or do not bother.
It does not research anything. No competitor lookups, no market data, no reading your analytics. Pure conversation, no tools connected, nothing leaves your machine.
It cannot tell when you are wrong about your own business. If you believe your customers buy on price and they actually buy on delivery time, it will write down price and be confidently unhelpful about it for months.
Skipping the money block is allowed and costs you more than it looks like. Without a revenue figure and a cost of delivery, Claude cannot say anything useful about pricing, which is the question most people actually want answered.
Installing it
One markdown file. No dependencies, nothing to configure, no account.
git clone https://github.com/aguevara92/business-interview.git mkdir -p your-project/.claude/skills/business-interview cp business-interview/SKILL.md your-project/.claude/skills/business-interview/
Then open Claude Code in that project and type:
/business-interview
It writes to context/business.md and its neighbours, creating them if your project has none. Anything else it might touch, an onboarding checklist, a journal, a clients folder, it touches only if that already exists. It will not build you a filing system you did not ask for.
This is the first hour of every project I take on
Before any automation is worth building, the thing building it has to know what the business actually is. That is why this one is free and why it comes first. What I do after it is the part where the answers turn into something that runs on its own.
or just take the file, it is yours
Talk to me