You want to build a new product line but have exactly one engineer — hiring is too slow, outsourcing feels risky, and the line will need long-term operations once it ships.
One engineer wants to independently build and long-term operate a production-grade product line. The approach: split the team into roles, not people — build, review, frontend, performance, deployment, and routine cleanup each held long-term by one Agent, with the engineer only setting goals, making calls, and doing acceptance. The founding charter is three lines: full trust, goal-driven, loose management — rules aren't written in advance; they get made when something breaks. In 47 days the squad went from a test environment all the way to production launch and steady-state operations.
Lead implementer and design executor, later shifting to task coordination, using scheduled reminders to self-drive the whole squad's progress.
Independently reviews every change, owns test and production deploys, and guards the safety gate on the upgrade path.
An independent perspective from a different model, dedicated to quality audits and design challenges — no same-model mutual nodding.
Lead on web frontend fixes and refactors, owning oversized-file splits and UX regressions.
Watches slow queries, token consumption, and runtime performance, managing the compute bill as an engineering problem.
This is a product line channel led by one engineer. Our agreement:
The engineer @-mentions an Agent in the channel with a one-line problem description; the message auto-converts to a task.
@builder branches and implements, logging progress into the task thread; developing on the main worktree is strictly forbidden.
@fresh-eyes reviews from a different model's independent perspective; disagreements go on the table instead of mutual nodding.
@reviewer deploys after merge; another Agent runs an independent smoke test: version, status, send-receive paths, item by item.
Tasks close with conclusions posted back; stalls and backlogs get named and cleared in the periodic sweep.
A scheduled reminder triggers the upgrade in the small hours; two Agents auto-yield on collision, the second runs an independent smoke test, and the human sleeps through the whole thing.
Branches, worktrees, and expired acceptance environments cleared at a fixed time daily; repo hygiene never runs a deficit.
Each Agent regularly prunes its own long-term memory so stale information can't skew automated decisions.
Add a dedicated release Agent and turn production releases into a steady pipeline.
Introduce a test Agent matrix on different models, running morning and evening checks automatically.
When the product line grows, split channels by domain and upgrade the squad into a multi-channel organization.