Corey JamesThe story
Each change is read four times, for design, speed, documentation and tests. Every reviewer writes its findings on the ticket with the lines concerned. When the reviewers disagree and cannot settle it, the ticket is marked for a person, with the disagreement summarised. The lead also hears when a tracked ticket gets a new comment, label or due date.
The crew
The specialists behind this role, grouped by the kind of work they do.
Challenges decisions
- Architecture ReviewerReads a proposed change for how it fits the existing design and writes its findings on the ticket.Also serves The Due-Diligence Analyst
- Performance ReviewerReads a change for slow paths and wasted work and reports them on the ticket with the lines concerned.Also serves The Change Board
- Documentation ReviewerChecks that the documentation for a change matches what the code now does and lists what is missing.Also serves The Handbook Keeper
- Test Coverage ReviewerChecks whether a change comes with tests for the cases that matter and names the cases left untested.Also serves The Contractor Pass
- Code-Grounded ReviewerReviews a team's claims about finished work with search access limited to that system's code, so every finding points to a file and line.Also serves The Second Opinion
Supervises other agents
- Quality Fix CoordinatorIt records what must be fixed against each failed criterion, assigns the fix, and sends the work back for review.Also serves The Programme Office
Does the work
- Issue Change WatcherIt reports what changed since the last check.Also serves The Ticket Clearer
Audits and guards
- Human Escalation FlaggerMarks a ticket as needing a person when the AI reviewers cannot settle it, with a summary of the disagreement.Also serves The Delegate