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.
A plan for a small product team that ships often: let the Coder merge and ship to staging when checks pass, and keep production deploys behind Approve.
A startup wins by shipping quickly without breaking the product. This playbook lets the Coder move fast on staging, while production stays behind your Approve.
House rules1. The Coder works on its own branch and opens a pull request for every change.2. If all checks pass and the change touches only [areas, such as docs, copy, or tests], the Coder may merge to [staging branch] and tells me afterwards.3. Changes to [payments, sign-in, database changes, or infrastructure] are opened as pull requests for a teammate to review. A person merges them after review.4. A deploy to production always waits for my Approve, with a summary of what is in it.5. If a check fails twice, the Coder stops and asks instead of trying a third time.6. Every bug fix includes a regression test.
Checkpoint
This is a starting point. In merge policy terms, low-risk areas use auto merge on green to staging, sensitive areas stay review only, and production ships only after CEO approval. The Coder can merge and ship when your house rules allow it, and your Auto-approve choices in Settings apply on top. Production actions ask unless you turn on auto-approve for them yourself, so leave that switch off.
Let the Coder fix a failing check and a flaky test.
3
Give it a small feature with a clear acceptance list.
4
Allow it to merge a low-risk change to staging, if your house rules say so, and watch what it does.
5
Review the week with the team and adjust the house rules.
PromptBuild from acceptance criteria
Coder, on [repository], build this ticket: [title]. Acceptance criteria: [list]. Add tests that prove each criterion and open a pull request.
PromptFix a failing pipeline
Coder, the pipeline on [branch or pull request] in [repository] is red. Find the cause, fix it in the smallest change, and explain what went wrong.
PromptHunt a flaky test
Coder, [test name] on [repository] fails now and then. Find out why, fix the cause, and do not just add a retry.
PromptPrepare a production release summary
Coder, list what is on [staging branch] but not yet in production on [repository]. Group it by risk and tell me what I should check before I approve a deploy.
PromptReview a teammate's pull request
Coder, review pull request #[number] on [repository]. Summarize it, flag risks and missing tests, and say what you would ask the author.
PromptImprove CI speed
Coder, make the checks on [repository] faster without making them weaker. Show me the before and after times in the pull request.
Note
Checkpoint. By Friday you have merged a few changes to staging, caught at least one failing check early, and written down which areas are safe for the Coder to merge on its own.
Product owner: keeps the backlog in shape so the top ticket is always buildable.
Marketing: turns each release into a changelog entry.
Accountant and Legal: keep the books and the policies tidy as you grow.
PromptTickets from the backlog
Product owner, read the open issues on [repository], rank the top five, and rewrite each as a ticket with acceptance criteria the Coder can build.
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.