This article discusses the impact of coding agents on the roles within Engineering, Product, and Design (EPD) teams. With coding becoming easier, the focus has shifted from creating detailed product requirement documents to rapid prototyping and review, emphasizing the need for generalists and strong system thinking. It highlights the evolving nature of roles where builders and reviewers emerge as distinct categories.

• Coding agents shift the bottleneck from writing code to reviewing it—checking architecture, user fit, and design quality.
• Generalists who span product, design, and engineering become more valuable because they cut coordination delays and can use coding agents directly to validate ideas.
• Weak product thinking now carries a higher cost: bad prototypes flood the review pipeline and waste team effort.
• System thinking becomes a core skill requirement—engineers need architecture/API fluency, PMs need real user insight, designers need interface judgment—so agents can be guided well instead of producing more review work.