resurrection-advocacy
$
npx mdskill add yogsoth-ai/de-anthropocentric-research-engine/resurrection-advocacyAdvocates for rejected candidates to ensure fair elimination
- Solves the problem of unjustified candidate rejection due to bias or oversight
- Uses adversarial-debate-protocol and multi-perspective-attack tactics
- Analyzes resurrection candidates based on unique strengths and narrow rejection margins
- Delivers final dispositions like REAFFIRM_REJECTION, REVIVE, or MERGE_STRENGTHS
SKILL.md
.github/skills/resurrection-advocacyView on GitHub ↗
---
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>
```
More from yogsoth-ai/de-anthropocentric-research-engine
- abductive-hypothesis-generationStrategy: 面对异常的最佳解释推理
- ablation-brainstormRemove components one by one, observe system changes to reveal hidden dependencies and generate ideas from structural gaps.
- ablation-component-mappingMap system architecture to ablatable units for ablation studies
- ablation-designDesign ablation studies to isolate component contributions in ML systems
- ablation-executionRemove components one by one from a system, record the response/impact of each removal.
- abp-vulnerability-classificationClassify assumptions on 2 axes — load-bearing (how much conclusion depends on it) × vulnerable (how likely to be false). Focuses attention on High-Load × High-Vulnerable quadrant.
- abstraction-extractionExtract abstract principles from concrete domain cases. Strips domain-specific details to reveal transferable mechanisms.
- abstraction-ladderPerform bisociation at multiple abstraction levels
- abstraction-ladderingMove between concrete and abstract framings — 3 levels up (Why?) and 3 levels down (How?) to find the most productive research level.
- abstraction-to-designAbstract biological principle to design principle. Bridge from biology to engineering.