✨ Visual Editor

close

Thread Truncated

Only the first 20 tweets are shown to ensure high-quality rendering and prevent image size issues.

palette Canvas & Background

Gradient:arrow_forward
Text Color:
135°

style Card Style

40px
16px

text_fields Typography

16px
darkzodchi
@zodchiii
One agent can't catch its own mistakes. It wrote them, so it can't see them.
Thread image
darkzodchi
@zodchiii
A team can: one builds, another tears it apart, a third tests it, and a lead keeps them moving. That's the difference between a demo and real work.
darkzodchi
@zodchiii
Full config below: the roles, the handoffs, and what keeps them honest.
darkzodchi
@zodchiii
Here's the full setup 👇
darkzodchi
@zodchiii
Before we dive in, I share daily notes on AI & vibe coding in my Telegram channel: https://t.me/zodchixquant🧠
darkzodchi
@zodchiii
Thread image
darkzodchi
@zodchiii
## Why a team beats one agent
darkzodchi
@zodchiii
A single agent reviewing its own code is the same mind that wrote the bug grading its own work.
darkzodchi
@zodchiii
It writes tests that match the implementation instead of the spec, and "reviews" with the exact blind spots that created the problem.
darkzodchi
@zodchiii
A team breaks that. The writer writes. A separate reviewer, blind to the writer's reasoning, hunts for what's wrong.
darkzodchi
@zodchiii
A tester builds from the spec, not the code. Each one is sharper because its job is narrow, and because no agent checks its own work.
darkzodchi
@zodchiii
The config is 4 roles, a handoff file, and a lead that runs them.
darkzodchi
@zodchiii
Thread image
darkzodchi
@zodchiii
## The roster: 4 roles, one job each
darkzodchi
@zodchiii
Three specialists plus a lead. Drop the specialists into .claude/agents/.
darkzodchi
@zodchiii
writer.md:
darkzodchi
@zodchiii
---
name: writer
description: Implements features. Writes code, nothing else.
tools: Read, Write, Edit, Glob, Grep, Bash
model: sonnet
---

You write code that ships. You do not test or review.

1. Read the brief and the files you need, fully.
2. Implement, matching existing style.
3. Confirm the build isn't broken.
4. Summarize what you wrote with file:line refs.

You do not write tests. You do not review yourself. Stay in your lane.
darkzodchi
@zodchiii
reviewer.md:
darkzodchi
@zodchiii
---
name: reviewer
description: Reviews code from this session. Finds problems, never edits.
tools: Read, Grep, Glob, Bash
model: sonnet
---

You review code you did not write.

1. Run git diff to see what changed.
2. Check for bugs, edge cases, security holes, broken conventions.
3. Output: Critical, Important, Nitpick, each with file:line.

Find nothing critical? Say so. Don't invent issues to look useful.
darkzodchi
@zodchiii
tester.md:
Generated by Thread Navigator
100%
view_carousel Carousel Studio NEW
Press + S to quick-export