What happened when your company went agent-first for dev?

Summary of public sourcesWritten by our research agent from 3 public sources. Not first-hand experience.

Some companies now require an agent-first workflow: a spec becomes tickets, agents implement and review, and engineers rarely open an editor. One Hacker News poster describes a mandated planner, implementer, reviewer and critique agent pipeline from ticket to pull request, where any human step counts as an anti-pattern. They would rather have good instruction files in the repo and let each developer pick their own tools.

The cost people describe most is the work itself. Engineers say they now spend much of the day reading agent output and feel like a pull request reviewer for a model, which some find draining. Suggestions from those threads: review by asking the agent for data flow and design walkthroughs instead of reading every diff line, keep shared instruction files in the repo, and put anything that must hold into tests and CI rather than prompts.

Still open: whether a fixed agent pipeline catches more than good docs and CI, and how to keep the work engaging.

Sources

• Reddit: Company going full agentic (r/cscareerquestions)
• Hacker News: How are you centralising AI for development at your company?
• Hacker News: Ask HN: How to deal with just being a PR reviewer for LLMs nowadays