Ajay Prakash is a senior staff software engineer at LinkedIn. He builds infrastructure that gives AI coding agents access to organizational context, tools and reusable workflows, and develops Stratos for authoring agent workflows in TypeScript.[1][2][3]
Start with Contextual agent playbooks and tools →
Career
Prakash works on platforms and infrastructure for enterprise AI agents at LinkedIn. His QCon biography describes earlier leadership of AI platform and product work for Sales Navigator and his current focus on the agent platform. His personal writing and presentations explain how existing coding agents can work with a company’s internal systems and practices.[1][5]
Contributions
Serve instructions alongside tools
Prakash coauthored LinkedIn’s account of Contextual Agent Playbooks & Tools with Nikhilesh Payyavuala. CAPT exposes both operational tools and reusable instructions through MCP. A playbook supplies the organization-specific steps for a task, then directs the agent to the relevant tools. The design augments existing coding assistants rather than requiring a separate model trained on every internal workflow.[2]
Put workflow coordination in code
Stratos makes agents, MCP tools and decision models available as TypeScript workflow components. Code handles branches, loops, parallel execution and passing data between steps, while agents handle the reasoning tasks assigned to them. Saved workflows can be reused and revised using traces from earlier runs. Its repository labels the project early-stage software and specifies its license.[3]
Ideas
In his conference talk, Prakash explains why a growing inventory of tools and instructions can overwhelm an agent’s context. LinkedIn’s approach uses search, schema retrieval and execution as a smaller interface to the underlying inventory. Smaller playbooks can reference one another so the agent discovers context progressively. He also describes agents proposing repository changes when they encounter outdated instructions, preserving a path for review.[4]
Tools, writing & talks
Writing, research & talks
Start here
Contextual agent playbooks and toolslinkedin.comLinkedIn’s engineering account of connecting coding agents with internal systems and procedures.
Start with the description of tools plus playbooks and follow one workflow through the system. Familiarity with coding agents helps; the architecture is explained without requiring access to LinkedIn’s internal services.
Coauthor with Nikhilesh Payyavuala[2]LinkedIn engineer Ajay Prakash explains how the company collapsed 1,300 internal tools and 600 playbooks behind three primitives (search, get schema, execute) after finding MCP degrades past 30-40 tools.
Catalog workOriginal source- 500 Skills, Zero Fine-Tuningai.engineer
Explains playbooks, progressive context retrieval and the interface to a large internal tool inventory.
Speaker[4]