The problem
Small clients and side ventures need real websites with real infrastructure: custom domains, forms that store data, gated review portals, payments. Hand-building each one does not scale to one person, and most no-code tools stop exactly where the interesting requirements start.
An LLM coding agent can write all of it, but an agent that pushes to production is a liability. The platform had to give agents the autonomy to build while keeping every change reviewable, every infrastructure decision tracked, and the human in control of what merges.
What I did
-
Put GitHub in the middle. Agents work only from issues, in branches, and every change is a pull request with a structured description of what changed and why. Direct pushes to main are never allowed, and Cloudflare Pages deploys only what merges.
-
Wrote the orchestration layer as Claude Code agents. An epic manager reads an epic, builds a dependency graph from the task list, and dispatches waves of task workers, each in its own git worktree with file ownership, so three workers can build in parallel and merge serially without conflicts. Workers never ask the human mid-run; they return a structured result or a blocked reason.
-
Packaged the workflow as my own Claude Code plugin marketplace, so the same task worker, state dashboard hook, and repository admin commands are installed into every project from one source instead of being copied and drifting.
-
Wired MCP connectors into the agent workflows: Cloudflare for DNS, Pages, and KV; GitHub for issues and pull requests; Stripe for billing; Semrush for search data. Infrastructure the agents change through those connectors is also committed as configuration, so the repository is the audit trail.
-
Built the edge layer with Cloudflare primitives rather than servers: Pages Functions in TypeScript, D1 for form and comment storage, KV for billing and secrets, Access with one-time-PIN login and JWT verification for a private client review portal, Turnstile on public forms, and Stripe Checkout for payments.
- Epic issue The task list is the plan; GitHub is the source of truth.
- Epic manager Builds the dependency graph and dispatches waves.
- Task workers Each in its own worktree with file ownership; three build in parallel.
- Pull request A structured description of what changed and why. Never a push to main.
- Review gate Security review in CI and a human at the merge. gate
- Deploy Squash merge; Cloudflare Pages ships only what merged.
Outcome
Nine production sites run on the platform today, from a nonprofit and a direct-booking vacation rental to a client review portal and this resume, with 59 agent-authored pull requests merged through the review gate.
A full client engagement has run end to end on it: search and AI-visibility research through the Semrush connector, a strategy microsite, proposals, and a content pipeline where each article carries its own brief, draft, fact-check, schema, and publish log.
The platform is also the proof behind the claims on this page: the agents that built the site, the pull requests that shipped it, and the Pages Function that answers questions about it are all the same system.
59 merged through the review gate. Work lands in bursts: an epic is planned, then dispatched as waves of parallel workers, so quiet months are months spent on the client sites in their own repositories.
Table view
| Period | Pull requests |
|---|---|
| Apr | 23 |
| May | 4 |
| Jun | 0 |
| Jul | 24 |
| Aug | 0 |
| Sep | 0 |
| Oct | 1 |
| Nov | 7 |
In the stack
Where it sits
The highlighted nodes are the systems and people this project touched.
Skills used
- Cloudflare (Pages, Functions, D1, KV, Access)
- LLM coding agents (Claude Code) as a daily build tool
- Model Context Protocol (MCP) connectors wired into agent workflows
- Multi-agent orchestration (parallel workers, worktrees, PR gates)
- API integrations (Salesforce, DealHub, Cloudflare, Stripe, job-board APIs)
- Project management
- Change management