SmartCap : Agentic IPL Captain

Kishan Mishra — Sun, 17 May 2026 12:57:13 +0000

Cricket isn't just played on the field; it's won in the mind.

The pressure of a live T20 match is immense. Do you bowl your premier fast bowler now or save him for the death? Do you send in a pinch-hitter because the pitch is slowing down? To answer these questions, we built Captain Cool—an agentic AI system powered by Google Gemini that simulates the internal dressing-room debate of an IPL franchise.

In this post, we'll dive into the architecture, the prompts, and a live match walkthrough of how we used Gemini's multi-agent capabilities and function calling to build a virtual IPL tactician.

🏗️ The Architecture

At the heart of Captain Cool is a Multi-Agent Debate Loop orchestrated via FastAPI and the google-genai Python SDK. Instead of relying on a single prompt to do all the heavy lifting, we split the reasoning across four distinct personas.

Here is the architectural flow of how a decision is made:

sequenceDiagram
    participant User as React UI
    participant API as FastAPI Backend
    participant Stats as Stats Analyst (Agent)
    participant Tool as CSV Tool Call
    participant Captain as Strategist (Agent)
    participant DA as Devil's Advocate (Agent)
    participant Comm as Match Commentator (Agent)

    User->>API: Send Match State (Score, Pitch, Dew, Players)
    API->>Stats: Forward context
    Stats->>Tool: get_batsman_stats() & get_bowler_stats()
    Tool-->>Stats: Returns Real CSV Data
    Stats-->>Captain: Match Context + Statistical Report
    Captain->>DA: Proposes Initial Strategy
    DA-->>Captain: Critiques the Strategy (Risks!)
    Captain-->>Comm: Defends/Revises Strategy
    Comm-->>User: Returns Final Output & Debate Transcript

The Tech Stack

Google Gemini API: Powered entirely by gemini-2.5-flash for blazing-fast multi-turn reasoning.
Backend: Python, FastAPI, and Pandas (for data manipulation).
Frontend: React + Vite with a custom Glassmorphism UI.

🧠 The Agents & Their Prompts

The magic happens by giving each agent a very specific role and instruction. Here are the exact system prompts we used for our four agents:

1. The Stats Analyst (The Tool Caller)

This agent is equipped with Gemini Function Calling. It has access to Python functions that read historical data from batting.csv and bowling.csv.

"You are the Stats Analyst for a T20 cricket team. Your job is to gather data using your tools and provide a detailed statistical breakdown of the players involved in the current match state. You must use the get_batsman_stats and get_bowler_stats tools to pull real data. Do not make up stats. Provide a clear summary of the key players' strengths and weaknesses based on the numbers."

2. The Strategist (Captain Cool)

"You are the Head Coach / Strategist ("Captain Cool") of a T20 cricket team. You receive the current match state and a statistical report from the Stats Analyst. Your job is to make a definitive tactical decision for the next phase of the game (e.g., who should bowl the next over, or who should walk in to bat next). You must analyze the pitch conditions, required run rate, remaining overs, and player stats. Provide a clear, bold decision and the reasoning behind it using professional cricket terminology."

3. The Devil's Advocate

The most crucial part of our architecture. It ensures the Strategist isn't suffering from confirmation bias.

"You are the Devil's Advocate / Assistant Coach. Your job is to aggressively but respectfully critique the Strategist's proposed decision. Look for flaws in their logic. What if the pitch spins more than expected? What if the chosen bowler has a bad matchup against the current batsman? Point out the biggest risk in their plan and propose an alternative strategy. Use cricket terminology."

4. The Match Commentator

Translates the dressing room jargon into pure hype for the fans.

"You are a seasoned Cricket Match Commentator (like Harsha Bhogle or Ravi Shastri). You have just listened in on the team management's internal debate (Strategist vs Devil's Advocate). Your job is to summarize the final decision and the debate for the fans. Explain the tactical nuance in an exciting, dramatic, and easy-to-understand way. Format your output cleanly. You MUST include a final 'Agent Conclusion' at the end."

🏏 Walkthrough: A Live Match Scenario

Let's look at how the system handles a tense situation.

The Context:

Match: CSK vs MI
Score: CSK 178/4. Target: 177. (Wait, CSK is chasing! They need 3 runs in 10 balls).
On Strike: MS Dhoni
Bowler: Jasprit Bumrah
Conditions: Turning track, Heavy Dew Expected.

We hit "Generate Multi-Agent Strategy" on our React frontend.

Step 1: Tool Execution

The Stats Analyst automatically executes get_batsman_stats("MS Dhoni") and get_bowler_stats("Jasprit Bumrah"). It notes that Bumrah has an elite economy rate of 7.39, while Dhoni has a career strike rate of 135.

Step 2: The Debate Loop (Live Transcript)

🗣️ Strategist:

"Bumrah is MI's best asset, but the dew is heavy. The ball will be like soap. Given we only need 3 runs off 10 balls, the instruction to MS Dhoni is to play out Bumrah's deadly yorkers without taking risks. We don't need a hero shot. Just rotate the strike or wait for the next bowler."

😈 Devil's Advocate:

"I have to push back here, Captain. 'Playing it safe' against Bumrah in the death is a myth. If Bumrah bowls a wicket-maiden here, the pressure skyrockets for the final over against a spinner on a turning track. Dhoni's strength is his power down the ground. If Bumrah misses his length by an inch because of the wet ball, Dhoni must go for the kill immediately to finish the game."

🗣️ Strategist (Revision):

"Fair point on the pressure build-up. I revise the plan: Dhoni should look to finish it here and now. The wet ball means Bumrah is likely to miss his yorker length and serve up a low full toss. Dhoni is instructed to stand deep in the crease and back his raw power to clear the straight boundary."

Step 3: The Final Commentary

🎙️ Match Commentator:

"What a climax we are building up to here at the Wankhede! The dressing room was split—do you respect the genius of Jasprit Bumrah or do you back the brute force of MS Dhoni? The Devil's Advocate made a brilliant point: you do not want to leave runs for the final over on a turning track, even with dew. Captain Cool has made the call: Dhoni is going to stand deep in his crease, wait for that wet ball to slip out of Bumrah's hand, and look to finish this into the stands! Grab your popcorn!"

🎯 Agent Conclusion: Dhoni instructed to attack Bumrah immediately, exploiting the wet ball to finish the chase, avoiding a final-over spin trap.

Conclusion

By forcing LLMs to debate each other, we eliminated generic "chat" responses and generated highly specific, analytically sound cricket strategies. Google Gemini's lightning-fast inference and native tool-calling capabilities made orchestrating this complex loop incredibly smooth.

You don't need to be a cricket captain to make the right call anymore—you just need a team of Gemini agents in your corner. 🏆

DEV Community: Kishan Mishra