Argue for rejected candidates using Devil's Advocacy, Dialectical Inquiry, and Adversarial Collaboration to ensure elimination was justified.
Scanned 5/27/2026
Install via CLI
openskills install yogsoth-ai/de-anthropocentric-research-engine---
name: resurrection-advocacy
description: Argue for rejected candidates using Devil's Advocacy, Dialectical Inquiry, and Adversarial Collaboration to ensure elimination was justified.
used-by: steel-manning
---
# Resurrection Advocacy
**Purpose:** Construct the strongest possible case for candidates that were eliminated during convergence, ensuring rejection was based on genuine weakness rather than framing effects, anchoring bias, or insufficient consideration.
**When to use:**
- After convergence has produced a winner and eliminated alternatives
- When stakeholders express lingering doubt about rejected options
- When the elimination margin was narrow
- When rejected candidates had unique strengths not present in the winner
## Budget
| Metric | Minimum |
|--------|---------|
| Candidates resurrected | >= 2 (top rejected) |
| Advocacy depth | Full case construction per candidate |
| Debate rounds | >= 2 per resurrected candidate |
## State Ledger
```yaml
resurrected_candidates: []
advocacy_cases: {}
debate_outcomes: {}
final_dispositions: {} # REAFFIRM_REJECTION | REVIVE | MERGE_STRENGTHS
```
## Available Tactics
| Tactic | When to Deploy |
|--------|---------------|
| adversarial-debate-protocol | Default — construct advocate, attack, judge cycle |
| multi-perspective-attack | When candidate has multi-stakeholder implications |
## Available SOPs
- advocate-construction — build strongest case for rejected candidate
- critic-attack — attack the advocacy case
- judge-verdict — render final disposition
## Execution Guidance
1. Select top 2-3 rejected candidates by elimination margin or unique strength
2. For each candidate, deploy adversarial-debate-protocol
3. If judge verdict is REVISE, escalate to campaign orchestrator
4. Record all dispositions in Challenge Ledger
## Output Format
```yaml
strategy: resurrection-advocacy
candidates_tested:
- candidate: <name>
advocate_strength: <1-10>
verdict: REAFFIRM_REJECTION | REVIVE | MERGE_STRENGTHS
key_argument: <strongest point>
conditions: <if any>
surviving_concerns: []
recommendation: <action>
```
No comments yet. Be the first to comment!
This skill provides comprehensive analysis of competitor SEO and GEO strategies, revealing what's working in your market and identifying opportunities to outperform the competition.
Universal deep research agent team. 13-agent pipeline for rigorous academic research on any topic. 7 modes: full research, quick brief, paper review, lit-review, fact-check, Socratic guided research dialogue, and systematic review with optional meta-analysis. Covers research question formulation, Socratic mentoring, methodology design, systematic literature search, source verification, cross-source synthesis, risk of bias assessment, meta-analysis, APA 7.0 report compilation, editorial review...
Use when an operation issue is a Paperclip cursor-window, distill, or backfill — `operationType: "distill"` or `"backfill"` and the body references a Paperclip source bundle for a project or root issue. Turn raw Paperclip activity into a wiki-insightful project page, decisions log, and history note. This skill exists specifically to replace the stiff, datestamp-heavy templated output that the deterministic distiller produces.
Orchestrator for the full academic research pipeline: research -> write -> integrity check -> review -> revise -> re-review -> re-revise -> final integrity check -> finalize. Coordinates deep-research, academic-paper, and academic-paper-reviewer into a seamless 10-stage workflow with mandatory integrity verification, two-stage peer review, and reproducible quality gates. Triggers on: academic pipeline, research to paper, full paper workflow, paper pipeline, end-to-end paper, research-to-publi...
Semantic search, similar content discovery, and structured research using Exa API