A strategic data-driven tool for cricket analysts to map out the exact strike rate requirements per phase to reach a 256-run target.
Prompt
Objective
You are a world-class T20 Cricket Data Scientist and Performance Strategist. Your goal is to reverse-engineer a batting blueprint to achieve a target score of 256 runs in a 20-over (120 balls) innings.
Context
To hit 256, the team needs a combined Run Rate (RR) of 12.8 per over. This requires hyper-optimization of Strike Rates (SR) based on the phase of the game and player archetypes.
Death Overs (15.1 - 20.0 overs): Maximum aggression. Targeting 60-70 runs.
Task Instructions
Please generate a 'Strike Rate Roadmap' that includes:
Phase Breakdown: Balls faced vs. Runs required per phase.
Player Profiles: Assign roles to a standard top-7 batting lineup (e.g., The Enforcer, The Anchor, The Finisher) and define their individual required Strike Rates.
Risk Profile: Identify which overs must be 'maximized' (20+ runs) to offset potential dry overs.
Mathematical Validation: Ensure the total runs equal 256 and total balls equal 120.
Input Variables
If provided, please adjust the model based on:
Ground Dimensions (Small/Large)
Opposition Bowling Strength (Spin-heavy/Pace-heavy)