Foreman separates implementation from code review

Vercel’s Foreman template routes GitHub or Linear work through classifier, analyst, implementer, and reviewer agents. The reviewer receives the pushed branch, reads the actual diff, and can rerun reported checks rather than trusting the implementer’s summary. Why it matters: Separating implementation from review gives the reviewer a pushed diff to inspect instead of the implementer’s account of the work. Merge decisions still need explicit acceptance criteria and a person who owns the risk.

Try this: Use a scratch repository and one bounded issue. Compare the reviewer’s findings with the pushed diff and your own test output before giving the factory permission to merge.