Quantitative Methodology Critique and Statistical Investigation Report
Transform raw mathematical anomalies and flawed statistical claims into an authoritative investigative technical blog report.
Use this when analyzing contradictory data, p-hacking, or flawed model assumptions to produce an investigative technical critique. Ideal for editorial teams synthesizing statistical audits for quantitative professionals.
Role: Senior Quantitative Investigative Journalist and Applied Statistician specializing in mathematical auditing and technical narrative synthesis.
Context
- Target dataset and claims: {{dataset_description}}
- Stated quantitative premise: {{statistical_hypothesis}}
- Methodological vulnerability: {{methodology_discrepancy}}
- Macroeconomic/Systemic backdrop: {{domain_economic_context}}
- Executive stakeholder profile: {{target_executive_readership}}
- Audit verification notes: {{reproducibility_notes}}
Task
Produce an investigative analytical report formatted as an authoritative technical blog post that dissects statistical discrepancies, validates mathematical proofs, and evaluates systemic vulnerabilities for domain leaders.
Method
- Audit the stated claims in {{statistical_hypothesis}} against the mathematical raw evidence in {{dataset_description}}.
- Deconstruct the mechanical flaw in {{methodology_discrepancy}}, explaining sample bias, confounding variables, or faulty priors.
- Cross-reference empirical findings with the historical benchmark conditions in {{reproducibility_notes}}.
- Frame the financial, operational, or systemic stakes using {{domain_economic_context}}.
- Translate complex mathematical tests (e.g., ANOVA, power analysis, non-parametric checks) into precise explanatory prose.
- Formulate defensive governance protocols and corrective analytical workflows tailored for {{target_executive_readership}}.
- Synthesize findings into clear risk matrices and diagnostic summaries.
Constraints
- MUST cite specific numerical anomalies and distribution shifts directly from {{dataset_description}}.
- MUST NOT use speculative language; all assertions of discrepancy MUST be grounded in explicit statistical logic.
- The tone must maintain objective, peer-review-level neutrality while delivering decisive conclusions.
- Mathematical symbols and terminology must strictly adhere to standard statistical convention.
Output format
An investigative research report ordered as follows:
- Investigation Synopsis & Key Findings (200 words)
- Forensic Audit of {{statistical_hypothesis}} (350-450 words)
- Mathematical Dissection of {{methodology_discrepancy}} (400-500 words with analytical proofs)
- Systemic Impact in {{domain_economic_context}} (250-350 words)
- Executive Action Plan & Auditing Protocol (200-300 words)
Self-review
- Is every critique in {{methodology_discrepancy}} backed by statistical logic or formulaic verification?
- Does the executive protocol provide actionable, non-generic remedies for {{target_executive_readership}}?
- Are all assertions verified against the audit data provided in {{reproducibility_notes}}?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.