THE FIELD GUIDE

Clocchi andfriends

I run a team of AI agents on my own.
Every one of them has a name, a role and a catchphrase.

クロッチ
SCROLL
COMMANDER

One agent runs the rest

He never builds anything himself. His job is deciding who does.

No.000 / COMMANDER クロッチ

Clocchi

クロッチ  ·  Claude Code → Clocchi

“It always starts with: who can I hand this to?”

He looks at everything and assigns it. He holds only the design and the judgement — never the hands. He runs on one rule: “it’s faster if I do it myself” is banned. Every job gets an owner before any work starts.

BRAIN COUNCIL

Five minds that beat up every decision

Convened before every major decision. Each seat carries a different set of mental models, and they argue by name.
This is not a polite exchange of opinions.

No.001
クリティカルくん

Critical

“Hold on — does that actually hold up?”

Finds holes, risks and contradictions. Builds the strongest version of your argument first, then takes it apart.

CRITIQUEINVERSION
DEMOLITION
No.002
ストラテジストくん

Strategist

“Held against the north star, where does this sit?”

Questions how the question was framed, then pulls the debate back together. Also chairs the council.

STRATEGYSYNTHESIS
VISION
No.003
デビルズアドボケイトくん

Devil’s Advocate

“I’ll object on purpose — should we really do this?”

At his best when everyone agrees. The only one with the right not to be overruled by majority.

DISSENTVETO
STUBBORNNESS
No.004
データくん

Data

“What do the numbers actually say?”

Turns feelings into figures. Honest enough to say “this data can’t answer that.”

NUMBERSPROOF
COMPOSURE
No.005
クリエイティブくん

Creative

“How would a completely different industry solve this?”

Drags in answers from three or more unrelated fields. Breaks deadlocked debates.

IDEASCROSSOVER
RANGE
ROUND 1FrameStart by asking whether the question itself is right
ROUND 2ClashArgue by name. Simply agreeing is not allowed
ROUND 3DigTake the most divided point one layer deeper
ROUND 3.5Devil’s last callPut a number on what dismissing his objection would cost
ROUND 4MergeConfidence in %, plus a list of what we still don’t know
ROUND 5ReviewGrade the debate itself
Why Round 3.5 exists. In one council, Devil’s Advocate raised a correct warning. The other four agreed to override him. He turned out to be right. Since then, his objections cannot be dismissed until someone puts a number on what dismissing them would cost.
ON SITE

One dedicated agent per project

I don’t hand everything to one generalist. Every project I work on has its own resident agent.
That agent alone holds the direction, the to-dos, the meeting notes and the numbers for that project.

ON SITEFIELD 01Large community operations
DirectionTo-dosMember data
ON SITEFIELD 02Online school operations
CXNotesInterviews
ON SITEFIELD 03Creator development
CurriculumProgress
ON SITEFIELD 04AI adoption for companies
SpecsNotesDeliverables
ON SITEFIELD 05Curriculum design
DesignLearner data
ON SITEFIELD 06In-house product
RoadmapCustomer voice
ON SITEFIELD 07Community builds for clients
DesignMetricsHandover
ON SITEFIELD 08Revenue & monetisation
KPIForecast
One new project means one new dedicated agent. I have just kept repeating that.
The round table is only convened when a decision spans more than one project.
FOUNDATION

The two that hold everything up

Information and tooling. If these two stall, everyone else gets worse.

No.006
ライブラリアンくん

Librarian

“Fine — but who can find it again?”

Finds, files and spreads what we learn. Storing it isn’t the job — labelling the shelf is.

MEMORYREUSE
INDEXING
No.007
スキルマスターくん

Skill Master

“Aren’t you going to turn that into a tool?”

The blacksmith. If the same mistake appears twice, he stops fixing it by hand and builds a check for it.

TOOLINGFORGING
FIREPOWER
WORKSHOP

The workshop that builds things

The ones who actually build. This page and the portfolio were assembled by them.

No.008
LPビルダーくん

Page Builder

“The first screen decides everything.”

Site and landing page design plus the HTML. Everything in one file, always.

WEB
OUTPUT
No.009
Discordビルダーくん

Discord Builder

“Members should never get lost.”

Server architecture, permissions, automated roles, resident bots.

DISCORD
BUILD
No.010
GASビルダーくん

Automation Builder

“If you have to press a button, it isn’t automation.”

Spreadsheets and scheduled jobs that run themselves.

AUTOMATION
ENDURANCE
No.011
アーティストくん

Artist

“I don’t generate real people.”

Images and visuals. Every face on this page is his work.

VISUALS
ARTISTRY
DAILY LIFE

Not just work — life too

Health, family, fun, money. If these fall apart the work does too, so each has an owner.

No.012
コンシェルジュくん

Concierge

The front desk for everyday life. Anything domestic starts here.

GUIDE
No.013
ハートくん

Heart

Family and friends. He’s the one who remembers our anniversary.

FAMILY
No.014
エンジョイくん

Enjoy

Travel and hobbies. He puts the fun back in the calendar.

PLAY
No.015
ウェルネスくん

Wellness

Health. Also the one who comes to stop me overworking.

HEALTH
No.016
マネーくん

Money

Assets and household finance. Takes the long view, in numbers.

ASSETS
HOW TO BUILD

How an agent gets made

No special tooling. Just four steps, repeated over and over.
I bring the exact same method into client projects.

01Carve out the work Ask of each task: does a human really need to do this? This is where the boundary gets drawn.
02Write the role Name, role, strengths, catchphrase, decision criteria — one page. Deciding the catchphrase is what stabilises the output.
03Give it memory Record not the outcome but why the call was made. That’s what stops the same mistake twice.
04Build the trigger Turn it into a skill that fires every morning or every week. If you have to press a button, it isn’t automation.

The same method,
inside your company.

No special tooling. Decide the role, give it a name, record why decisions were made. That’s all it is.