Run a tiny business with scheduled Claude Code agents
Five roles (CEO, builder, growth, verifier, board) wake on GitHub Actions; files are the memory; a script guards the money.
Prompt for your agent
Goal: Have agents run a small online business on a schedule. Setup: agents used in source: Claude; tools/MCPs stated: GitHub Actions, claude-code-action, Gumroad API. Steps: 1. Make the repo the brain: CLAUDE.md as constitution, STATE.md generated by script, STRATEGY.md, BACKLOG.md as the handoff table, JOURNAL.md per run, role files in .claude/agents. 2. Wake each role with a scheduled workflow running claude-code-action (e.g. CEO daily, builder twice daily). 3. Agents don’t touch git: after they edit, shell steps revert protected files, then commit. 4. Money rules live in a non-AI treasury script (sales sync, reserve). 5. Before marking done, hand acceptance criteria to a fresh-context verifier subagent. Rules: ask me before anything irreversible (sending, posting, paying, deleting); don’t invent data, results or tools I haven’t given you; tell me what you couldn’t verify. Based on: Nick T — https://dev.to/nick_t_eac6be7ee8e88de2f3/i-handed-a-tiny-business-to-claude-code-agents-on-a-cron-schedule-heres-the-architecture-2615
Steps are from the source. Includes a “Based on” credit line.
I tried this
Tell the next builder. One anonymous answer each; click again to undo.
Agents, models and tools only what the source states
- Agents
- Claude
- Tools
- GitHub Actions
- claude-code-action
- Gumroad API
Sources & credit
- Nick T @nick_t_eac6be7ee8e88de2f3 primaryDEV post · 26 Sep 2026https://dev.to/nick_t_eac6be7ee8e88de2f3/i-handed-a-tiny-business-to-claude-code-agents-on-a-cron-schedule-heres-the-architecture-2615