StackMap
Subscribe
Explore / three-man-team
russelleNVy

three-man-team

A disciplined 3-agent dev process as context files — Architect plans, Builder builds the brief, Reviewer gates — running in one Claude Code session via subagents. Token-frugal by design.

877 112 Shell MITupdated 1 months ago
Curator's take

It's a process, not software: three markdown personas with strict handoffs (plan → brief → build → review → deploy) that target the classic solo-agent failure modes — scope drift, unrequested features, token burn. The five CLAUDE.md token rules ('is this speculative? kill the tool call') are genuinely good hygiene even outside the team. Everything runs in one Claude Code session via the Agent tool; works with anything that reads context files. NOT a framework, and not for exploratory hacking — the ceremony pays off on production work and taxes quick experiments. Know the two strings attached: a commercial 'Pro' waitlist, and Arch phones a version registry at session start to offer updates (auditable, consent-gated, but it's there).

Mapped by ShipWithAI editors · links verified
README.md

Three Man Team

russellenvy.github.io/three-man-team

By RUSSΞLL AARØN


What's New — v1.3.0

  • New: manifest.md — Arch generates this at first-time setup. Single source of truth for your install: team names, role filenames, handoff directory, repo, branch.
  • Improved: version check now reads a version registry (releases/latest.json) instead of hitting the GitHub API. Critical updates are mandatory checkpoints; non-critical ones are your choice.
  • Improved: Arch reads your actual files before walking through any change — no more guessing at your setup.
  • Removed: VERSION file retired. Version lives in manifest.md.

See all releases →


Three Man Team Pro

Pre-built teams for developers, marketers, content creators, and more — install in minutes, start working immediately.

Join the waitlist →


The Problem With AI Coding Tools

AI coding tools are powerful but undisciplined. They read entire codebases when they need one function. They add features nobody asked for. They drift mid-task. They burn tokens on every session doing work that didn't need to happen.

The solution isn't a better prompt. It's a process.

Three Man Team gives you three agents with distinct jobs, clear handoffs, and rules that prevent the most expensive failure modes. The Architect plans and deploys. The Builder builds exactly what the brief says. The Reviewer doesn't pass work that isn't right.


Why Three Agents

Three is not arbitrary. Solo agents drift — there's no one to catch a wrong turn. Large teams generate coordination overhead that eats the productivity gain. Three is the minimum for meaningful review and the maximum before the team starts managing itself instead of the work.

The roles map to how real software ships:

  • Someone who understands the whole system and owns the deploy
  • Someone who builds fast and clean
  • Someone who catches what the builder missed

Quick Start

How the team runs: Three Man Team uses one Claude Code session. Arch is your main agent. When work is ready to build, Arch spins up Bob as a subagent via Claude Code's Agent tool. When Bob is done, Arch spins up Richard the same way. You don't open three windows — everything runs inside your single session.

Choose your install type:


Per-project install (recommended)

One project, one install. Clone directly into your project folder.

Step 1 — Navigate to your project folder and clone

git clone https://github.com/russelleNVy/three-man-team.git .claude/skills/three-man-team

Step 2 — Run setup and follow the instructions

cd .claude/skills/three-man-team && ./setup

Setup takes over from here. It will give you the exact commands to run and the prompt to paste into Claude to get started. Follow what it prints.


Global install (all projects)

Install once, use in any project.

Step 1 — Clone to your global Claude skills folder

git clone https://github.com/russelleNVy/three-man-team.git ~/.claude/skills/three-man-team
cd ~/.claude/skills/three-man-team && ./setup

That's the one-time install. Setup will confirm everything is in place.


For each project you want to use Three Man Team on:

Step 2 — Copy agent files into your project, then spin up Claude

cp -r ~/.claude/skills/three-man-team/templates/project-folder/. /path/to/your/project/
cd /path/to/your/project

Open Claude Code and paste:

You are the Architect on this project. Please read new-setup.md.

Arch will handle the rest — project context file, team names, and your first session prompt.


The Workflow

Continue your stack

What teams reach for next — and why each earns a place beside three-man-team. Ranked by curator confidence.