A day of VibeFlock, minute by minute
By Soumen Sarkar · October 2026
Scenario. One developer, four agents, one working day: briefs, assumptions, corrections, landed work and handoffs, minute by minute, with nobody waiting.
What does a working day look like when nobody waits?
It looks like a day where context arrives before anyone goes looking for it. Agents start knowing what changed, name what they don't know and carry on, and people answer from wherever they are. Here is one developer's day, minute by minute.
A made-up team, a real way of working.
Rosa builds a booking app for small clinics with two teammates: Aiko, who owns the clinic calendar, and Dev, who owns patient messages. Rosa runs four Claude Code sessions most days. Today she is building a waitlist: when a patient cancels, the slot is offered to someone waiting.
08:52
Rosa opens her first session. Before she types anything, the session brief is there, and at the top is "Pick up where it was left":
Pick up where it was left
- Yours: Waitlist signup form, half done (handoff from yesterday 17:40)
Dev's session stopped yesterday with the SMS reminders half built, and Rosa is taking them over. She opens a second session and pastes Dev's handoff into her first prompt, so it starts with what's done, what's left, the next step, and one trap ("the SMS provider rejects messages over 160 characters without saying why").
She tells the session to finish the reminders. Its first request becomes the one-line goal of its work in progress, visible to the team.
09:04
Her second session starts on the waitlist itself. The first time it reads the calendar code, it gets the area brief for Calendar · lib/calendar:
Being changed right now
Aiko: Clinics can block out holidays and closed days
Plan: a blockedDays list per clinic; booking skips blocked days
Expected: today, 14:00
Decisions here
Slots are 15 minutes; longer appointments take several slots
Tried and dropped
Holding a cancelled slot for the same patient for a day: confused patients
The agent calls wait_on with Aiko's work and builds the offer logic to skip blocked days, by her plan.
09:20
The waitlist session meets an unknown: how long does a patient have to accept an offered slot? It doesn't stop.
state_assumption
question: How long does a waitlisted patient have to accept a slot?
assumption: Two hours, then it goes to the next person
likely answers: 30 minutes · 2 hours · until the day before
It keeps building, with the time limit in one setting.
09:41
Aiko made the closest decision, so the assumption reaches her on Activity. Clinics told her same-day slots fill fast. She follows its "Answer it" link and clicks the likely answer "30 minutes". At its next turn, Rosa's agent hears the correction and changes one number.
10:15
Rosa opens Activity with Since set to "your last visit". An agent of Dev's has assumed that deleting a clinic removes its future appointments, marked High stakes. Dev is on a train. Rosa knows this one: she follows its "Answer it" link, clicks "Correct it…" and writes, "Never delete appointments. Mark them cancelled and tell each patient." Dev's agent hears it at its next turn, and Dev reads the whole exchange later.
10:50
Her third session is fixing a time zone bug in the confirmation email. It searches the team's record first, finds the rule "Show times in the clinic's time zone, not the patient's", and builds to it. There's nothing to ask.
11:30
The reminders session commits. The change's reasons are written for the reviewer: what it's for, that Dev's trap was handled by splitting long messages, and the assumption it made about quiet hours. Rosa opens a pull request and pastes the reasons link into the description.
12:10
Before lunch Rosa glances at the feed: nothing new is waiting on her. She goes to lunch. Her agents don't need her for the next hour.
13:45
Aiko's holiday work lands, a little ahead of time and a little different from the plan. Rosa's waitlist session hears at its next turn:
Landed: Clinics can block out holidays (Aiko)
You built on this. What changed from the plan:
- Blocked days are called closures, and each has a reason
The agent renames one call and shows the reason on the offer: "Tuesday is closed for a staff day, so here's Wednesday." Seven minutes.
14:30
Dev gets off his train and opens Activity with Since set to "your last visit". In the feed he finds the assumption Rosa corrected for his agent, with her sentence beneath it. He doesn't message her to ask what happened. It's already there, and his agent has been building to the correction for four hours.
15:05
The waitlist session makes a call that's Rosa's to make and records it with its reason:
log_decision
title: Waitlist offers go by SMS first, email only if there's no phone
why: Patients answer texts within minutes; offers last 30 minutes
It's checked against the decisions that stand, and nothing clashes.
16:40
Rosa wraps up. Two sessions are finished and call finish_work with their outcome. The waitlist session isn't done, so when it stops, a handoff is written from the session:
Done: offer logic, 30-minute expiry, closures skipped, SMS offers
Left: email fallback for patients without a phone
Next step: reuse the confirmation email layout for the offer
Watch out: the offer link must expire with the offer
17:30
At her end of day, Rosa's daily update is written in plain words from her work logs: reminders shipped for review, waitlist nearly there, one wrong assumption caught before it reached a patient. She didn't write it. Tomorrow at 08:52, "Pick up where it was left" will be waiting.
What made it work
- [Keep moving](/vibeflock/keep-moving). Every session started with the context it needed, so nothing stopped for a person all day.
- [Turn unknowns into calls](/vibeflock/turn-unknowns-into-calls). The 30-minute question cost one changed number, not a morning of waiting.
- [Build on what's coming](/vibeflock/build-on-whats-coming). The waitlist was built on Aiko's work hours before it landed.
- [Let the work speak](/vibeflock/let-the-work-speak). Dev's handoff and Rosa's own meant both pieces of work were picked up without a single question.
To set this up for your own team, start with VibeFlock in two minutes.
The principle behind this: Keep moving: The work never waits, and neither do we.
Move as one at agent speed. Nobody waits. Add Campfyrr to Claude: it briefs every agent before it touches the code, keeps assumptions and handoffs where the team can see them, and never takes your code (what it keeps).