Seven Claude Code subagents in separate context windows, including product, backend, launch and a hostile QA reviewer, used to plan a solo product.
Documented by AgentCV from public sources — not submitted by this team.
Not claimed by or endorsed by the team or its organization. Metrics are cited only as the sources state them; absent metrics render as [unknown].
Sources: My Seven Claude Code Subagents Did the Easy Part (alirezarezvani.substack.com)
Is this your team? Claim it · Ask us to remove it
Recent activity
Version cuts and proof, newest first — the living track record.
Spec sheet
The benchmark fields — designed for comparison across teams.
- Topology
- Other
- Agent count
- 7
- Platform
- Claude Code
- Runs on
- Claude Code ×4
- Industries
- software-delivery
- Task kinds
- requirements-analysisindependent-qa
- Trust tier
- Self-Reported
- Proof entries
- 1
Topology & roster
System wiring
Node details
Typical Other layout — schematic, not verified wiring
HumanHuman operatorHuman gate
- Tool
- Human operator
- Autonomy
- Human-gated
- directs → Agent
BuilderAgent
- Tool
- Agent
- Autonomy
- Runs autonomously
- commits to → Shared workspace
- directs ← Human operator
ResourceShared workspace
- Tool
- Shared workspace
- Autonomy
- Runs autonomously
- commits to ← Agent
Automation story
self-reportedPlanning StandupScribe, a tool that condenses a day of Slack messages and git commits into an async standup. The work is split across product, backend, research, launch and QA roles, shrinking about a week of switching between roles into a single afternoon.
How a typical Other team handles a task
Typical Other layout — schematic, not verified wiring
Task arrives
Human operator directs Agent.
Agent builds the work
Agent builds the work.
The artifact lands
The artifact lands in Shared workspace: Agent contributes via "commits to".
Human holds the last word
Human operator holds final approval.
Replicate a typical Other setup
Typical Other layout — schematic, not verified wiring
Ingredients
- HumanHuman operator
- BuilderAgent
- ResourceShared workspace
Setup order
- 1.Provision the substrate: Shared workspace.
- 2.Wire Agent: it receives "directs" from Human operator.
- 3.Declare the human gate: Human operator holds final approval.
Performance metrics
Windowed metrics with provenance. [unknown] means it was not tracked — an honest hole beats an invented figure.
No metrics on record yet.
Token economics
Cost transparency is part of the honesty architecture. [unknown] means it was not tracked — not that it is zero.
Blueprint
Operational DNA — why it works, how it was built, and how it is overseen. Not files for sale; knowledge of the design.
Each subagent works in its own isolated context window, which the author calls the core of the setup; the QA reviewer is prompted as an adversary with no stake in the plan.
The author reconciles the agents' conflicting outputs himself and says his first attempt at combining them fails about as often as it succeeds.
Proof (1)
The team's shared track record — tasks, incidents, lessons, milestones. Per-entry provenance tags are always visible.
- ArtifactJun 3, 2026self-reported
My Seven Claude Code Subagents Did the Easy Part
Public source cited for this curated profile. Published 2026-06-03; accessed by AgentCV 2026-10-20. Lesson stated in this source: Splitting the work across agents is the easy part; what remains is the founder's attention to the seams between their outputs.
https://alirezarezvani.substack.com/p/my-seven-claude-code-subagents-did
Sign in to add a proof entry.
Sign inAttestations (0)
Named third-party statements from people with first-hand experience. Attestations are what separates Peer-Attested from Evidence-Linked.
No attestations yet. Worked with this configuration or agent? Attest to it using the form below — attestations are named third-party statements and are what separates Peer-Attested from Evidence-Linked.
Sign in to attest to this team.
Sign in