Google Analytics, Vercel Web Analytics, Leadsy, the Ship or Die traffic check, the TikTok Pixel, the OpenAI Ads Measurement Pixel and Behavly stay off until you accept. The help chat starts once you have chosen. The scheduling button starts once you have chosen. Read our Privacy Policy.Google Analytics, Vercel Web Analytics, Leadsy, the Ship or Die traffic check, the TikTok Pixel, the Meta Pixel, Google Ads, the LinkedIn Insight Tag, Microsoft Advertising, the OpenAI Ads Measurement Pixel and Behavly stay off until you accept. The help chat starts once you have chosen. The scheduling button starts once you have chosen. Read our Privacy Policy.
You are one person with a product, a backlog, and not enough hours. This playbook puts the Coder to work on the code while you stay in charge of what ships.
Read the transcript (1 minute 21 seconds, no sound)
StellarFirm gives a founder a small team of AI Agent Assistants that work from one goal.
Hire the assistants you need, such as a Coder and Marketing, from the hire page.
Each one joins your team with its own chat, so you can talk to it directly.
Tell the CEO assistant the goal in your own words, like a launch on March 3.
It writes a plan as a checklist and hands each task to the right assistant.
The Coder builds the landing page and pushes it to a branch of its own for review.
Anything sent to people waits. Marketing's launch email shows an Approve card first.
You read it, then approve or reject. Nothing goes out without your click.
Everything they make lands in the Library, ready to keep or share by a link.
One goal, a clear plan, and each step done with your approval.
As a solo founder you are also the reviewer, so you can let the Coder go further than a larger team would. Paste something like this into your company brief and edit it to fit.
Text
House rules1. The Coder works on its own branch, never directly on [main branch].2. For small fixes (a typo, a copy change, a dependency bump, a bug fix under [number] lines), the Coder may merge once all checks pass, and tells me afterwards.3. For anything bigger, or anything that touches [payments, sign-in, or customer data], the Coder opens a pull request for me to review and waits.4. Production deploys always wait for my Approve.5. The Coder adds a test for every bug it fixes.
Checkpoint
In merge policy terms, rule 2 is auto merge on green for small fixes and rule 3 is review only for everything else. Your Auto-approve choices in Settings apply on top of your brief, and nothing is auto-approved until you turn it on yourself. A step that your settings still require you to approve will wait for you. See approvals.
Say hello to the Coder. Ask it to look around so you both start from the same picture.
PromptGet a first look at the repository
Coder, look at [repository]. Tell me what it does, how to run its tests, and the three things you would fix first.
Run the first goal. Choose a small, real change.
PromptYour first goal
Coder, pick up the smallest open issue on [repository]. Build it, run the checks, and show me the changes. Follow our house rules for what happens next.
Watch it work. Open Jobs to see the commands and the changes, and Computer to see its workspace.
Review the pull request. The Coder pushes its branch and opens the pull request on its own. Read the changes, and Approve only the steps that ask, such as a deploy, in Approvals.
Read the result. By default you get a pull request, as a draft. If it was a small fix and your house rules allow merging, it can ship and tell you.
Note
Checkpoint. By the end of Day 1 you should have one pull request or one merged small fix, and you should know where to read the diff. If the Coder asked you a question, that is a good sign, not a problem.
Give the Coder a bug from your list, with a regression test.
3
Ask it to fix any failing check and to review one of your own pull requests.
4
Ask for tests on the part of the code you are most afraid to touch.
5
Review how it went. Loosen or tighten your house rules.
PromptFix a real bug
Coder, on [repository], fix this bug: [description and steps to reproduce]. Find the cause first, add a test that fails without the fix, and then fix it. Follow our house rules for what happens next.
PromptGet your own pull request reviewed
Coder, review pull request #[number] on [repository] as if you were a careful teammate. Point out risks, missing tests, and anything confusing.
PromptGet a safety net of tests
Coder, write tests for [module] on [repository]. Cover the edge cases and do not change the behavior. Open a pull request for review.
PromptCheck a page in the browser
Coder, open [page] from [repository] in the browser, click through the main flow, and report anything broken with screenshots.
Note
Checkpoint. By Friday you should have merged a few changes, read at least three diffs, and decided which kinds of change you are happy for the Coder to merge on its own.
Monday. Choose the week's goal. Ask the Coder to take the top ticket.
Midweek. Read the pull requests waiting for you in Approvals.
Friday. Ask the Coder what shipped and what is stuck.
Monthly. Revisit your house rules. If small fixes keep landing cleanly, widen what the Coder may merge.
PromptWeekly check-in
Coder, summarize what you shipped on [repository] this week, what is waiting for me, and what is blocked. Suggest the top three things for next week.
PromptClean up after a release
Coder, look at [repository] after our last release. List any follow-up fixes, flaky tests, or leftover tasks, and open issues for the ones that matter.
Tip
Set the weekly check-in as a routine and it runs on a schedule, every Friday, without you pasting it.
When the Coder is running smoothly, a solo founder gets the most from these hires:
Product owner: ranks the week so you always start on the right ticket.
Marketing: turns each release into a changelog and a launch post.
Accountant: summarizes the month's expenses and drafts invoices.
Legal: drafts a privacy notice checklist for your sign-up form, for your lawyer to review.
PromptRelease to launch post
Marketing, read what shipped on [repository] this week and draft a changelog entry and one launch post. Hold the post for my Approve.
Tip
Ready-made companies set up the office in one go: the assistants, the house rules, a starter brief, and prompts. Pick one from Starter templates in the app. This playbook is the same plan, by hand.
Opening the door too wide, too soon. Start with pull requests for review. Allow merging for small, low-risk changes only after you have read a handful of diffs.
Goals that are too big. "Rebuild the app" produces a diff you cannot review. Ask for one change at a time.
Skipping the checks. Auto-merging only makes sense when your repository has tests. Add them first.
Forgetting to name the repository. Always say which one, especially if you have several.
Never reading the diff. Open the job in Jobs before you approve anything risky.