← Back to library

Nightly product loop for a side project, with a go gate

u/intensityflow made Claude Code acting CEO of Stackboard, their free Chrome extension that turns the new tab into a bookmark board. Every night at nine, a scheduled task loads a playbook skill the agent itself maintains, reads the store dashboard and post comments, scans subreddits, improves the product and logs a Notion report. Public posts still need their go.

  • OutcomeLet a coding agent run your small product's support, research and next version on a nightly schedule, filing a report and posting nothing public until you reply go.
  • SetupAn afternoon+
  • LevelAdvanced
  • Creditu/intensityflow on r/ClaudeAI
View original
Works with
Claude Code

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 23, 2026

When should you use it?

  • You run a small free or side product alone
  • Support, listings and promotion keep slipping
  • You can review a short report each morning

Not for: Products with paying customers and contracts; Accounts that forbid automated posting

What do you need, and what do you get?

You need

  • Product repo and store dashboard access
  • Signed-in browser profile for the agent
  • Report page and a go rule

You get

  • Nightly report with what happened and what it needs
  • Draft posts waiting for go
  • Code changes with tests

How does it work, step by step?

  1. Write the goalGive the agent one goal, such as more installs and active users, and its duties.
  2. Schedule itRun it each night at a fixed time from a scheduled task.
  3. Keep a playbookLet the agent keep a skill file with its routine and update it as it learns.
  4. Report dailyHave it write a dated page with results, blockers and questions for you.
  5. Gate public postsHold every public post until you answer go.

The prompt

Our own prompt, inspired by u/intensityflow on r/ClaudeAI and written to work in Claude Code. Values in lime are placeholders.

Fill in the blanks (optional; the copied prompt uses your values)

Prompt2 variables
You run {product} overnight. Goal: {goal}. Each night: read the store dashboard and comments, find forum threads where people want a tool like this, plan posts, and work on the product with tests.
Write a dated report with what you did, what you found and what you need from me. Do not post anything public until I reply 'go'. Never type passwords.

Inspired by u/intensityflow on r/ClaudeAI: I gave Claude Code the CEO job for my free Chrome extension. Week 1: it made me rename it, built the next version, and still needs my "go" for every post. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • Store dashboards may ask for your password; the agent should not type it, so releases can stall.
  • Promotion posts can look spammy; read each one.
  • Say no to asks like messaging your friends for users, as the poster did.

Our take

Ignore the CEO label and look at the loop, because that is what u/intensityflow got right. The agent starts every night from real signals, the store dashboard, comments and forum questions, rather than from its own ideas about what users want. It keeps a playbook it rewrites as it learns, so the process improves instead of resetting each session, and it ends with a dated report a person can skim over coffee. The single go word on public posts is the essential gate: shipping code to a free extension is reversible, but a clumsy post under your name is not. The poster's honest first week, a rename to avoid confusion with a similar product, a corrected listing claim and a tested new version, shows the scale to expect. Those are housekeeping wins a busy owner skips, not growth miracles. If you copy this, keep the agent away from store submission credentials until you have read several reports, and cap how many changes it may make per night so each one stays reviewable.

Where the time goes back: Night work turns into a morning report and a few posts to approve.

FAQ

What did it achieve?
After a week the poster reported four weekly users, fourteen installs over 30 days and zero spend.
Why the go rule?
So the agent can draft freely while every public post still has a human yes.

Source and credit

Inspired by u/intensityflow on r/ClaudeAI. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
I gave Claude Code the CEO job for my free Chrome extension. Week 1: it made me rename it, built the next version, and still needs my "go" for every post
Creator
u/intensityflow on r/ClaudeAI
Published on
Reddit
Original date
Oct 2, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
Claude Code
AI dry run
Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends, bookings or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Marketing

All 97 Marketing playbooks →

Related playbooks

MarketingPrompt✓ AI dry run

Build a terminal command that edits your tech drafts

Run one command on any Markdown draft and get a structured edit covering typos, clarity, structure, code accuracy and publishing readiness.

Credit: Connie Leung

Under an hour
MarketingWorkflow✓ AI dry run

Build a weekly LinkedIn Ads pacing report with Claude

Have Claude turn each week's LinkedIn Ads results into one written report: progress against pipeline targets, the main platform metrics, the audiences, campaigns and ads that are falling behind, ads whose click-through to the landing page is slipping, and a short list of last week's finished work and what is planned next.

Credit: Patrick Cumming

An afternoon+
MarketingWorkflow✓ AI dry run

Clear a docs backlog with an agent opening PRs

Hand recurring docs chores, old issues and term renames to an agent that opens pull requests your writers review.

Credit: Daniel Price

Under an hour