prosecutor
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.
- License 许可
- Apache-2.0
- 所属仓库
- monoes/monomind
- 最近更新
- 2026-11-14
- Stars
- ★ 23
- Forks
- 2
01 前言 Front Matter
- name
- prosecutor
- tags
- [ "legal", "strategy", "communication" ]
- tools
- []
- source
- https://github.com/monoes/monomind
- license
- Apache-2.0
- 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.
03 SKILL.md 正文
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.
04 同仓库更多 Skills
zk-steward
Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.
writing-plans
Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.
write-spec
Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.
write-query
Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.
workflow-automation
Org role guidance for workflow automation: build and maintain CI/CD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.
workflow-architect
Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.