# AI adoption at enterprise scale

> I get agents into the hands of whole engineering organizations, and measure what changed.

Packaging and versioning agents like software, rollout across locked-down enterprise machines, catalogs and standards so teams reuse instead of copy, governance and trust tiers, and metrics that show leadership the effect of the AI programme.

- Core skills: Agent packaging and rollout, AI governance and standards, Developer experience tooling, Spec-driven development, Copilot custom agents and skills, Coverage and quality metrics
- Domains: Telecom, Quality engineering, Developer platforms and tooling
- URL: https://farhanbaluch.com/capabilities/ai-adoption

## Case studies

- [Custom Copilot agents for test-automation teams](https://farhanbaluch.com/work/copilot-agent-program.md) (Mar 2026 – Sep 2026, Enterprise test-automation teams): 27, agents and skills catalogued across seven SDLC phases. Teams had AI assistants, but generic prompts wrote generic tests that ignored each team's frameworks, page objects and naming, so adoption stayed shallow. Encoding those conventions into agents and skills is what made AI-generated tests mergeable, and the catalog is what turned individual agents into a toolkit the whole programme reuses.
- [Agent and skill distribution platform](https://farhanbaluch.com/work/agent-distribution.md) (May 2026 – present, National telecom carrier): 18 repos, on versioned agent packages, from 7 packages. Agents only change how an organization works if every team runs the same current, reviewed version. This is the supply chain for the AI programme: agents and skills versioned like dependencies, generated from one registry, and installable on locked-down laptops.
- [Coverage intelligence, a quality data layer for agents](https://farhanbaluch.com/work/coverage-insights.md) (Oct 2026 – present, National telecom carrier): 81.7%, regression automation coverage across 21 teams, now measured weekly. Agents can only answer "how automated are we, and where should we invest?" if the numbers come from a source they can trust. This pipeline is that source: test data read straight from code, normalized across 21 teams, and structured to be served through an MCP server, so engineers and leadership can ask an agent for coverage instead of opening a spreadsheet. It is also how the AI test-automation programme shows whether test-generation agents are moving the number.
- [Agent evaluation pipeline](https://farhanbaluch.com/work/agent-evaluation.md) (May 2026 – Jul 2026, Internal platform for an enterprise client): 10+, quality dimensions scored per agent, from traces as well as answers. An internal marketplace of agents, skills and MCP servers is only safe if something decides what gets published. This harness is that gate. It scores what an agent did, from its traces, as well as what it said.

## Evidence from the log

- 2026-10-19: **Extended coverage reporting to mobile test suites.** Mobile teams write tests in Java with TestNG, which the first parser couldn't read. Added a Java-aware parser so their coverage shows up in the same weekly report. AI angle: An agent asked "how covered is the app?" needs every platform in one model, or it answers for web only. This closes the gap so the coverage data an MCP server will serve to agents describes the whole product. [Knowledge, retrieval and context; AI adoption at enterprise scale] (https://farhanbaluch.com/work/coverage-insights.md)
- 2026-10-14: **Published a structure and naming standard for 20+ test repositories.** Every team laid out its repository differently, which made automated reporting brittle. Wrote one standard for folders, tags and naming, with a migration checklist per team. AI angle: A predictable layout is the context layer agents need. With one standard, every agent (test generation, review, coverage queries) finds tests, page objects and tags in the same place in every repository, instead of each agent being tuned per team. [Knowledge, retrieval and context; AI adoption at enterprise scale] (https://farhanbaluch.com/work/coverage-insights.md)
- 2026-10-06: **Shipped the first weekly automation-coverage report.** 21 teams, measured straight from code instead of spreadsheets. The first run put regression automation coverage at 81.7%. AI angle: Gives the AI test-automation programme a baseline measured from code, so the effect of test-generation agents shows up in the numbers, and gives future agents a trusted source to query. [AI adoption at enterprise scale; Knowledge, retrieval and context] (https://farhanbaluch.com/work/coverage-insights.md)
- 2026-09-29: **Started coverage measurement from source.** Leadership's automation numbers came from hand-kept spreadsheets nobody could trace. Prototyped a zero-dependency pipeline that clones every team repository and counts tests by tag. AI angle: The first step toward a quality data layer agents can read through MCP. An agent can't reason about coverage when the only source is a spreadsheet. [Knowledge, retrieval and context; AI adoption at enterprise scale] (https://farhanbaluch.com/work/coverage-insights.md)
- 2026-09-22: **Launched a searchable catalog of 27 agents.** Mapped every agent and skill to one of seven SDLC phases and published them in a docs portal, so engineers find an agent before they write a new one. AI angle: Turns a pile of agents into a toolkit. Reuse rises, duplicates fall, and the programme can see which SDLC phases still have no agent support. [AI adoption at enterprise scale; Agent architecture and orchestration] (https://farhanbaluch.com/work/copilot-agent-program.md)
- 2026-09-04: **Built a one-run installer for agent packages.** Engineers on Windows and macOS pull every approved agent package with one command, and a staleness report shows which repositories are behind. AI angle: Removes the setup friction that stops engineers from using agents at all, and tells the programme where teams are running stale agent versions. [AI adoption at enterprise scale] (https://farhanbaluch.com/work/agent-distribution.md)
- 2026-08-25: **Moved agent distribution to a single registry.** Copies of agent files had drifted across repositories. Now one registry generates every manifest, and packages are versioned and reviewed before release. AI angle: Agents are now shipped like software. A prompt or skill fix reaches every team, and nothing changes agent behavior without review. [AI adoption at enterprise scale; Agent architecture and orchestration] (https://farhanbaluch.com/work/agent-distribution.md)
- 2026-08-13: **Changed the rollout plan for code-review skills.** Found that code-review skills only load from a repository's default branch, so teams testing on feature branches saw nothing. Rewrote the rollout steps around that. AI angle: Knowing how the agent platform actually loads skills is the difference between a rollout that works and teams deciding AI review "doesn't do anything". [AI adoption at enterprise scale; Agent architecture and orchestration] (https://farhanbaluch.com/work/copilot-agent-program.md)
- 2026-05-29: **Prototyped an internal agent marketplace.** A place to publish agents, skills and MCP servers, with trust tiers (approved, community-vetted, beta) and trace-based vetting before anything is listed. AI angle: Governance for agent sprawl. Teams share agents and MCP servers through one marketplace, and evaluation decides what they can trust. [AI adoption at enterprise scale; AI evaluation and quality] (https://farhanbaluch.com/work/agent-evaluation.md)
- 2026-05-12: **Started versioned packaging for AI agents.** Test teams were copy-pasting agent files between repositories. Proposed packaging them like any other dependency, with a schema and a review gate. AI angle: The first move from "everyone has their own prompt files" to a managed agent supply chain the programme can govern. [AI adoption at enterprise scale] (https://farhanbaluch.com/work/agent-distribution.md)
- 2026-04-20: **Rolled out custom Copilot agents to test-automation teams.** Wrote agents and skills that generate Playwright tests in each team's own conventions, and ran hands-on sessions so teams actually used them. AI angle: Generic assistants write generic tests. Encoding each team's frameworks and conventions into agents is what made the output mergeable, and the sessions are what made people use it. [AI adoption at enterprise scale; Agent architecture and orchestration] (https://farhanbaluch.com/work/copilot-agent-program.md)
- 2025-11-10: **Moved Visual Basic modules to Java 21 with spec-driven agents.** Ad-hoc AI coding gave inconsistent results. Each module now gets a written spec first, then agents implement and test against it. AI angle: Spec-driven development makes agent output repeatable. The spec is the contract the agent is held to, and the CI loop lets it correct itself. [Agent architecture and orchestration; AI adoption at enterprise scale] (https://farhanbaluch.com/work/legacy-modernization.md)