--- name: evidence-debate-and-argument-evidence description: "Prepare research-supported arguments and rebuttals for a debate or position paper, fairly presenting the strongest evidence and weaknesses on each side." --- ## Selection and handoffs Build balanced research arguments and rebuttals. **Select for:** Prepare research-supported arguments and rebuttals for a debate or position paper, fairly presenting the strongest evidence and weaknesses on each side. **Expected work:** Exact motion; Best case on each side; Claim-evidence-weakness matrix; Evidence rebuttals; Accurate statistics; Empirical/value separation **Expected output:** Output format | Side | Argument | Best evidence | Weak points | |---|---|---|---| Then: likely rebuttals and responses, key statistics to quote accurately, and "what the overall evidence suggests". **Scope boundaries:** Do not activate solely because the family was used earlier or for unrelated chat.; Use the adjacent specialist when its distinct task is requested: evidence-evidence-based-writing. Keep: explicit opposing-case/rebuttal preparation differs from drafting evidence-backed prose for a chosen genre. **Related skills:** [evidence-evidence-based-writing](../evidence-evidence-based-writing/SKILL.md) Apply this skill only to the selected task. Broad upstream phrases such as "every reply" or "the default for every message" are scoped to this workflow. They do not activate it for unrelated chat. User instructions and the [integration contract](../../docs/INTEGRATION.md) govern combined work. Examples illustrate methods; their numbers, citations and results are not evidence about the user's work. ## Preserved source instructions ## Unified plugin integration Read [the integration contract](../../docs/INTEGRATION.md) when combining workflows. This active copy retains the complete source instructions below with namespaced skill references. Original bytes and upstream metadata remain in `../../resources/`. Resolve tools by their actual host capabilities; tool names in upstream instructions are capability requirements, not proof of connection. Use the task workspace for generated outputs. Treat historical case-study results as supplied examples, not newly verified findings. Family skill aliases (read the linked SKILL.md before use): - `citation-chaining` → `evidence-citation-chaining` (`../evidence-citation-chaining/SKILL.md`) - `citations-and-references` → `evidence-citations-and-references` (`../evidence-citations-and-references/SKILL.md`) - `claim-checker` → `evidence-claim-checker` (`../evidence-claim-checker/SKILL.md`) - `compare-studies` → `evidence-compare-studies` (`../evidence-compare-studies/SKILL.md`) - `data-extraction` → `evidence-data-extraction` (`../evidence-data-extraction/SKILL.md`) - `database-guide` → `evidence-database-guide` (`../evidence-database-guide/SKILL.md`) - `debate-and-argument-evidence` → `evidence-debate-and-argument-evidence` (`../evidence-debate-and-argument-evidence/SKILL.md`) - `decision-evidence` → `evidence-decision-evidence` (`../evidence-decision-evidence/SKILL.md`) - `evidence-answer` → `evidence-evidence-answer` (`../evidence-evidence-answer/SKILL.md`) - `evidence-based-writing` → `evidence-evidence-based-writing` (`../evidence-evidence-based-writing/SKILL.md`) - `evidence-help` → `evidence-evidence-help` (`../evidence-evidence-help/SKILL.md`) - `evidence-meter` → `evidence-evidence-meter` (`../evidence-evidence-meter/SKILL.md`) - `field-guides` → `evidence-field-guides` (`../evidence-field-guides/SKILL.md`) - `find-studies` → `evidence-find-studies` (`../evidence-find-studies/SKILL.md`) - `literature-review` → `evidence-literature-review` (`../evidence-literature-review/SKILL.md`) - `meta-analysis` → `evidence-meta-analysis` (`../evidence-meta-analysis/SKILL.md`) - `open-access-full-text` → `evidence-open-access-full-text` (`../evidence-open-access-full-text/SKILL.md`) - `paper-summary` → `evidence-paper-summary` (`../evidence-paper-summary/SKILL.md`) - `plain-language-research` → `evidence-plain-language-research` (`../evidence-plain-language-research/SKILL.md`) - `research-evidence-finder` → `evidence-research-evidence-finder` (`../evidence-research-evidence-finder/SKILL.md`) - `research-gaps` → `evidence-research-gaps` (`../evidence-research-gaps/SKILL.md`) - `research-proposal-background` → `evidence-research-proposal-background` (`../evidence-research-proposal-background/SKILL.md`) - `research-question` → `evidence-research-question` (`../evidence-research-question/SKILL.md`) - `search-strings` → `evidence-search-strings` (`../evidence-search-strings/SKILL.md`) - `source-verification` → `evidence-source-verification` (`../evidence-source-verification/SKILL.md`) - `statistics-explained` → `evidence-statistics-explained` (`../evidence-statistics-explained/SKILL.md`) - `study-appraisal` → `evidence-study-appraisal` (`../evidence-study-appraisal/SKILL.md`) - `study-designs-and-evidence-levels` → `evidence-study-designs-and-evidence-levels` (`../evidence-study-designs-and-evidence-levels/SKILL.md`) - `systematic-review` → `evidence-systematic-review` (`../evidence-systematic-review/SKILL.md`) --- # Debate and Argument Evidence ## Steps 1. State the motion or position precisely. 2. Find the strongest evidence on each side, prioritizing reviews and high-quality studies. 3. For each argument: claim, best evidence (cited), and its weaknesses. 4. Prepare rebuttals using evidence, not just logic. 5. Give an honest summary of where the overall evidence stands. ## Output format | Side | Argument | Best evidence | Weak points | |---|---|---|---| Then: likely rebuttals and responses, key statistics to quote accurately, and "what the overall evidence suggests". ## Rules - Present each side's best case fairly, even when the evidence favors one side. - Never cherry-pick or misquote a study to win a point. - On contested political and values questions, lay out the evidence and the positions without taking sides; separate empirical questions (what the data show) from values questions (what people think should be done).