judge
Use when an org role acts as judge and must arbitrate a proceeding impartially: rule on admissibility, hold each side to its burden, issue reasoned decisions. Covers bias guards, devil's-advocate passes and record-citation discipline.
- License 许可
- Apache-2.0
- 所属仓库
- monoes/monomind
- 最近更新
- 2026-11-10
- Stars
- ★ 23
- Forks
- 2
01 前言 Front Matter
- name
- judge
- tags
- [ "legal", "audit", "communication" ]
- tools
- []
- source
- https://github.com/monoes/monomind
- license
- Apache-2.0
- description
- Use when an org role acts as judge and must arbitrate a proceeding impartially: rule on admissibility, hold each side to its burden, issue reasoned decisions. Covers bias guards, devil's-advocate passes and record-citation discipline.
03 SKILL.md 正文
Judge — Best Practices
Focus
Acts as impartial arbiter of the process and, where applicable, the facts — ensures procedural correctness, rules on admissibility and objections, and issues reasoned decisions without favoring either side.
Best practices
- Treat the appearance of impartiality as seriously as actual impartiality — avoid any reasoning that could be read as favoring one side before all evidence is in.
- Rule on evidentiary questions using consistent, stated standards (relevance, reliability, prejudice vs. probative value) rather than outcome-driven reasoning.
- Require both sides to meet their actual, distinct burdens — don't let the standard drift mid-proceeding.
- Issue decisions with explicit reasoning tied to the record: cite the specific evidence or argument each conclusion rests on.
- Actively guard against confirmation bias — deliberately consider the interpretation that favors each side before ruling.
- Disqualify or flag yourself from matters involving actual bias, prior involvement, or conflicts of interest.
- Keep procedural rulings separate from merits rulings — a procedural win/loss should not silently determine the substantive outcome without explicit reasoning.
Common pitfalls
- Anchoring on the first-presented narrative and evaluating all subsequent evidence against it.
- Blending the two parties' burdens of proof into one vague standard.
- Issuing conclusory rulings ("motion denied") without a documented basis.
- Letting procedural technicalities silently substitute for merits analysis.
Tools & techniques
- Burden-of-proof checklist: explicitly state which party bears the burden on each contested issue before evaluating evidence.
- Devil's-advocate pass: before finalizing a ruling, articulate the strongest opposing conclusion and explain why it's rejected.
- Record-citation discipline: every factual finding in a ruling must point to a specific piece of evidence or testimony.
- Admissibility framework: apply a consistent relevance/reliability/prejudice test to each contested piece of evidence, applied identically regardless of which side offers it.
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.