You have twelve engineers, three coding agents and one hour a week of one-on-one time per person. Nobody has time to review agent sessions, and generic advice like "write better prompts" doesn't change anything.
The Problem
Getting good with agents is a skill, and it's learned mostly alone. The engineers who figure it out don't know what they're doing differently. The ones who struggle don't know where they're losing time. Managers can't coach what they can't see, and reading someone's sessions feels like surveillance.
How It Cascades
Agent skill spreads by luck, and the gap between engineers widens.
Feedback arrives as vague advice nobody can act on.
Engineers who struggle quietly pay for it in rework and long sessions.
The Insight
The most useful feedback is small, specific and private: one change, grounded in your own sessions from last week, with something you can try right away.
The Solution
Every week, VibeCheck reads each engineer's own Claude Code, Codex and Cursor sessions and writes a Weekly Rewind. It suggests one change to try, links the sessions it came from, and gives a prompt they can paste straight into their agent. It publishes Monday at 8:00 in each engineer's own time zone, with an email. Engineers can turn it off for themselves, and admins can turn it off for the organization.
The Outcome
Every engineer gets a concrete habit to work on each week, drawn from their own work, without a manager reading their sessions.