Agentic Engineering, Clearly Explained in 60 Min by an Ex-Meta L8 Engineer | Kun Chen

· Source: Behind the Craft · Field: Technology & Digital — Artificial Intelligence & Machine Learning, Software Development & Engineering, Emerging Technologies & Innovation · Depth: Intermediate, extended

Summary

Ex-Meta L8 principal engineer Kun Chen has developed a highly efficient agentic engineering workflow, enabling him to ship 20-40 pull requests daily with minimal manual code review. His system, detailed in a recent episode, centers on a "Plan, Code, Validate" paradigm, where AI agents handle most implementation and initial validation. Chen utilizes three open-source tools he built: Lavish, a visual HTML editor for detailed, interactive planning; Treehouse, for managing parallel agent sessions and worktrees efficiently; and No Mistakes, an AI-powered code review tool that scrutinizes agent-generated code in a fresh context window, auto-fixing minor issues and escalating complex problems. This approach shifts human effort to meticulous planning and high-level validation, allowing for significant parallelization of agent tasks and increased development velocity.

Key takeaway

For AI Engineers aiming to significantly scale your development output and maintain code quality, you must re-evaluate your workflow by prioritizing meticulous planning and robust, automated validation. Delegate coding entirely to agents, focusing your efforts on crafting detailed, interactive specifications and setting up comprehensive AI-driven review pipelines. This approach, supported by tools for parallel agent management and fresh-context code scrutiny, allows you to manage dozens of daily PRs, transforming your role into an orchestrator of high-velocity development.

Key insights

Agentic engineering prioritizes detailed planning and robust validation to scale development velocity with AI.

Principles

Method

The workflow follows Plan (visual HTML with Lavish), Code (AI agents), and Validate (AI agents with No Mistakes for review, testing, and documentation, escalating product-implication issues).

In practice

Topics

Code references

Best for: AI Architect, CTO, VP of Engineering/Data, AI Engineer, Machine Learning Engineer, Software Engineer

Related on AIssential

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by Behind the Craft.