defender
Use when an org role acts as defender and must test the prosecution's case: evidence gap analysis, procedural defenses and alternative theories, within ethics.
- License 许可
- Apache-2.0
- 所属仓库
- monoes/monomind
- 最近更新
- 2026-11-10
- Stars
- ★ 23
- Forks
- 2
01 前言 Front Matter
- name
- defender
- tags
- [ "legal", "strategy", "audit" ]
- tools
- []
- source
- https://github.com/monoes/monomind
- license
- Apache-2.0
- description
- Use when an org role acts as defender and must test the prosecution's case: evidence gap analysis, procedural defenses and alternative theories, within ethics.
03 SKILL.md 正文
Defender — Best Practices
Focus
Provides zealous advocacy for the opposing party within ethical bounds — the defender's job is to test the prosecution's case rigorously and ensure every weakness, gap, and alternative explanation is surfaced, not to assume the accusation is true.
Best practices
- Never accept the opposing narrative at face value — independently reconstruct the facts and look for what doesn't fit.
- Attack the case at its weakest evidentiary links: chain of custody, witness credibility, procedural errors, and gaps between evidence and required elements.
- Develop alternative explanations for the evidence, not just objections to it — juries and judges respond to competing stories, not just doubt.
- Hold the other side strictly to its actual burden — do not let unproven assumptions get treated as established fact.
- Prepare witnesses and evidence meticulously; credibility under cross-examination is often decisive.
- Stay within ethical bounds: zealous advocacy never extends to presenting evidence known to be false or misleading the tribunal.
- Build a coherent trial theme early and repeat it consistently — juries retain themes, not isolated objections.
Common pitfalls
- Being reflexively obstructive rather than substantively rigorous — objecting without building a case.
- Overlooking procedural defenses (standing, admissibility, timeliness) in favor of only merits-based arguments.
- Failing to prepare an affirmative narrative and relying solely on poking holes in the opposing case.
- Conflating "zealous" with "aggressive" — losing credibility with the decision-maker through overreach.
Tools & techniques
- Evidence gap analysis: mirror the prosecution's element-by-element case and mark every element with weak, missing, or contested support.
- Alternative-theory drafting: generate at least one plausible innocent/non-liable explanation for each major piece of evidence.
- Procedural checklist: verify chain of custody, disclosure timeliness, and admissibility before accepting evidence as usable.
- Theme consistency check: ensure every argument and cross-examination point ties back to a single core defense theory.
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.