Moneybees · The Swarm cycle

How I build with Claude

At Moneybees, we call this the Swarm: different Claude agents plan, build, and review while I decide what merges.

→ Different roles. One checked cycle.

01 Scope agent

Check the task

Claude checks the current code to confirm the issue and its cause before making changes.

Check the code before trusting the ticket.
Tools
JiraConfluenceGitClaude Code
Inputs
TicketWhat was reportedread
Current codeWhat actually runscheck
Related codeWhat else may changecheck
Continue, stop, or ask.
02 Builder agent

Build safely

Claude builds and tests in a separate Git worktree. The main branch stays untouched.

Keep each task separate.
Tools
Claude CodeGitTest suitepush-lock
Git worktree
Claude works in a separate Git worktree The main branch remains unchanged while the Builder agent builds, tests, and saves changes in a separate Claude worktree. MAIN BRANCH UNCHANGED git worktree B CLAUDE WORKTREE Changes stay here until review Build Test Save
03 Builder agent

Open a draft PR

Claude opens a draft pull request with the code, tests, and screenshots.

A draft PR is ready for review, not merge.
Tools
BitbucketGitPlaywrightJira
Ready for review
Draft pull requestDRAFT
testsscreenshotsrelated coderisks
04 Guard agent

Check the change

A separate Claude reviews the change, runs tests, and checks past failures.

The builder does not review its own work.
Tools
Claude CodeGitswarm-gatesREGRESSION-GUARDS.md
Separate reviewer
Builder

Creates the change.

DRAFT PR
≠
Guard

Checks the change.

testspast issuessecurity
APPROVE OR REJECT
05 Human approval

A person merges

Checks must pass, but Jeff decides whether to merge.

Claude prepares the change. A person approves it.
Tools
premerge-gateBitbucketmerge-pr-as-jeffAWS CodePipeline
Final authority
CHECKS PASSED

Jeff approves and merges.

Built by · ClaudeMerged by · Jeff Kent
06 Release tools

Confirm it deployed

The new version is deployed, tested in staging, and checked for errors.

A merged PR does not prove the new version is live.
Tools
AWS CodePipelinedeploy-verifyPlaywrightSentryJira
Live checks
1Buildpassed
2Deployfinished
3Testlive app
4Closetask
merged≠live
07 Swarm memory

Save the lesson

Rejected work returns to Build. After the fix, the lesson becomes a check for future work.

Fix the change, then remember the failure.
Tools
Claude CodeGitBitbucketREGRESSION-GUARDS.md
Fix and remember
REJECT → FIX → REVIEW
Buildcorrect the change
Guardreview again
save the lesson
Saved lessoncheck future work
08 Connected tools

Connected tools

Claude uses a small set of named tools. Credentials stay outside the project.

Tools limit what Claude can do.
Tools
tmuxClaude Code hooksShell scriptsPython scripts
Tool names
TG
Telegram
BB
Bitbucket
JI
Jira
CO
Confluence
AWS
AWS
SE
Sentry
PW
Playwright
TM
tmux
SessionStartPreToolUseusage-gateworktree-cleanuppush-lockpremerge-gatedeploy-verifystaging-smoke
THE OPERATING PRINCIPLE

“Done” needs a second check.

Claude helps with the work. Separate review, human approval, and live checks make it safer.

✓