IPL 2026 - Umpiring/DRS Controversy Analyzer

Example Input

Goal: create a rules & law analysis for cricket analysts
Audience: [describe who will read or use it]
Tone: [clear, practical, persuasive, friendly, formal]
Constraints: [word count, format, platform, examples, must-include points]

Example Output

Sample output:
- Match context: venue, team form, pitch behavior, toss impact, and likely playing XI changes
- Key factors: top-order stability, death bowling, spin matchups, and impact-player options
- Prediction: cautious forecast with confidence level, risk notes, and what could change the result

Useful Variations

• Make the output shorter and more actionable for cricket analysts.
• Rewrite the answer for a beginner audience and include concrete examples.
• Turn the result into a checklist, table, or step-by-step workflow.

Customization Tips

• Add real names, examples, target platform, and desired length before running the prompt.
• Tell the model what a bad answer looks like so it avoids generic output.
• Ask for one revision focused only on accuracy, clarity, or conversion depending on your goal.

Best Model to Use

Use ChatGPT, Claude, Gemini, or Grok, then refine the first answer with follow-up instructions.

Expected Output

• A structured rules & law analysis tailored to cricket analysts.
• Clear sections, bullets, or steps that are easy to edit.
• A final answer that can be shortened, expanded, reformatted, or adapted for a specific platform.

Common Mistakes

• Running the prompt without replacing placeholders with real context.
• Asking for a final answer before defining audience, goal, tone, and constraints.
• Publishing the output without checking facts, examples, links, claims, or brand voice.