▶ Watch ↗AI Engineer World's Fair 202620:30
Conference affiliation: QuantumBlack · 2026
Imad Touil is an engineering leader at QuantumBlack, AI by McKinsey, focused on how enterprises reorganize software delivery around AI agents. His distinctive contribution is an approach to agent skills as organizational knowledge: reusable instructions and executable procedures that preserve a company’s engineering practices, domain expertise, and operating rules across teams.
His earlier work included web and mobile development at WebFullCircle in 2012, encompassing customer-management software, middleware, and business-process integration. At MyOpla, he developed a mass-mailing platform, taking responsibility for specifications, application architecture, and Scrum-based development.
He subsequently moved into engineering leadership at BN Corporation, associated with Cue Connect. His responsibilities expanded to distributed teams, technology roadmaps, product priorities, and the relationship between technical strategy and business goals. He worked on microservice architecture and continuous delivery on AWS, while coordinating development, operations, and quality assurance. Alongside that work, a 2017 consulting engagement at INWI involved agile coaching, workflow improvement, and operational reporting. These earlier engineering roles involved both building software and changing how organizations delivered it.
At QuantumBlack, Touil applies that combination to agentic software engineering. He introduced himself as a distinguished engineer in 2026, with a focus on making AI-assisted work usable across an organization rather than confined to individual developers. His argument about software delivery extends beyond implementation: product strategy, customer discovery, data preparation, infrastructure provisioning, launch, and incident response all shape whether software produces business value.
Touil’s approach to scaling agent skills borrows from established software architecture. A skill should do a specific job, remain reusable across workflows, and be discoverable by engineers who did not create it. He favors specialized, composable skills over large instruction bundles whose responsibilities overlap or conflict. Progressive disclosure supplies relevant instructions when needed, helping keep unnecessary material out of the agent’s context.
A regulatory-review workflow makes the idea concrete. Data-retention rules, disclosure standards, privacy requirements, and filing templates can become separate skills that a workflow combines. The intended result is consistent application of organizational rules across web, mobile, and other products, with review findings and audit artifacts that teams can inspect and act on. This is a proposed architecture for dependable execution, rather than a claim that instructions alone guarantee compliance.
Several concerns define his approach:
Touil’s writing on adopting agentic engineering gives this platform-oriented thinking a practical sequence. Start with a small group using one platform on noncritical work, observe the failures, and encode architecture conventions, security rules, domain language, and testing standards. Build custom infrastructure when actual constraints justify it. He argues that faster code generation shifts attention toward intent, system design, and quality governance—and warns that vague instructions and unmonitored agents can accelerate the accumulation of poor software. For Touil, the lasting investment is the organization’s ability to make its knowledge usable, maintainable, and shared.
▶ Watch ↗AI Engineer World's Fair 202620:30
Loading more talks and highlights…