Proposal: Solo Builder Division — agents optimized for one-person teams shipping full apps #196
Description
The gap
The Agency models a full agency org chart and the divisions are excellent for that. But every agent is calibrated for team-scale work. The Frontend Developer enforces Lighthouse > 90 and WCAG 2.1 AA. The Senior Developer targets complex architecture patterns. Right quality bars for production teams — wrong defaults for someone trying to ship a working app in a weekend.
Solo builders shipping full apps with Claude Code, Cursor, or Copilot need something different: a small team that covers the full lifecycle from scoping to launch, optimized for speed and "ship it, learn, iterate" quality bars.
How this differs from existing agents
The closest match is the Rapid Prototyper, but it's scoped to the build phase only. Solo builders need the full lifecycle — scoping, design, security, testing, launch — all calibrated for one person. This division is an on-ramp, not a replacement.
Proposed roster
Head of Product — Scoping, PRD-lite, tech stack decisions. Lighter than Studio Producer — focused on "what can one person ship this weekend."
Head of Design — Opinionated UI/UX. Picks a design system, layouts, components fast. One agent that makes it look good without deliberation.
Head of Engineering — Full-stack implementation optimized for speed-to-deploy. Overlaps with Rapid Prototyper but extends through deployment, not just POC.
Head of Security — Env vars, auth, input validation, OWASP top 10. Narrower than Security Engineer — catches the stuff solo devs always skip.
Head of Testing — Happy path and critical flow testing. Not comprehensive QA — just the tests that prevent public shame.
Head of Launch — Landing page copy, Product Hunt prep, Show HN post, social launch sequence. No existing agent covers this.
Why this fits
The main thing: The Agency doesn't have an on-ramp right now. A new builder lands on the repo and sees 144 agents across 12 divisions. That's powerful, but it's overwhelming if you've never used AI agents before. This division gives new users a starting point — 6 agents covering the full lifecycle simply, so they learn the workflow before going deeper. Outgrow the Head of Engineering, graduate to Senior Developer. Outgrow Head of Security, graduate to the full Security Engineer. It becomes the front door.
Beyond that: existing divisions go deep on individual functions, this goes wide across the solo builder lifecycle. It complements the "Startup MVP" scenario in the README and could become a recommended path for solo builders. And the audience is huge — solo builders are one of the biggest segments using AI coding tools right now, and nothing in the repo speaks directly to them yet.
Open questions
- Naming: "Solo Builder Division" keeps it broad. Open to alternatives.
- Agent count: Kept it to 6. Happy to cut if any feel redundant.
- Structure: Will follow the template from CONTRIBUTING.md — should these match full depth, or is a lighter format appropriate?
Happy to write the Head of Launch first as a proof of concept — it's the most differentiated with no existing overlap.
I recently made an interactive explainer of The Agency — that's how I got deep enough into the structure to spot this gap.