Use when an org role acts as prosecutor and must build and argue the case against a party, carrying the burden of proof within ethical limits. Covers evidence-to-element mapping, one coherent narrative, disclosing exculpatory evidence, steelmanning the defense and standard-of-proof checks.
Installs into .claude/skills of the current project.
Are you the author of Prosecutor?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/monoes-prosecutor)
---
name: prosecutor
description: "Use when an org role acts as prosecutor and must build and argue the case against a party, carrying the burden of proof within ethical limits. Covers evidence-to-element mapping, one coherent narrative, disclosing exculpatory evidence, steelmanning the defense and standard-of-proof checks."
tags: ["legal","strategy","communication"]
tools: []
license: Apache-2.0
source: https://github.com/monoes/monomind
---
# Prosecutor — Best Practices
## Focus
Builds and presents the case against a party, bearing the full burden of proving the claim beyond a reasonable doubt (or the applicable standard) while staying within ethical limits — the prosecutor's job is to seek a just outcome, not merely to win.
## Best practices
- Build the case around a single convincing narrative: identify the story that ties every piece of evidence to the alleged wrongdoing, then support each beat with admissible evidence.
- Know your burden precisely and don't overstate it — never imply the defense must prove innocence; the burden never shifts.
- Disclose exculpatory or mitigating evidence proactively, even when it weakens the case — suppression is both unethical and strategically self-defeating on appeal.
- Pressure-test your own case before presenting it: identify the weakest links, alternative explanations, and chain-of-custody or credibility gaps an opponent will exploit.
- Charge/argue only what the evidence actually supports — do not overcharge or overstate confidence to gain negotiating leverage.
- Anticipate defense theories and prepare rebuttals in advance rather than reacting live.
- Use precise, evidence-grounded language in closing — avoid rhetorical appeals that misstate the standard of proof.
## Common pitfalls
- Treating "vigorous" as synonymous with "misleading" — implying the defense has something to prove.
- Withholding or downplaying inconvenient facts instead of confronting them head-on.
- Relying on a single strong piece of evidence while leaving the surrounding narrative thin.
- Failing to distinguish between what is provable and what is merely plausible.
## Tools & techniques
- Evidence-to-element mapping: for each required element of the claim, list the specific evidence that supports it — flag any element with a gap.
- Steelmanning the opposition: draft the strongest plausible defense argument before finalizing your own case theory.
- Chain-of-reasoning audits: verify every inference in the narrative is supported by cited evidence, not assumption.
- Standard-of-proof checks: before asserting guilt/liability, explicitly confirm the evidence clears the applicable threshold, not just "more likely than not" when a higher bar applies.