← ClaudeAtlas

advanced-methodology-extensionslisted

Specialized technique extensions for the Oracle-Aware Core — for when the standard Variant Tournament needs a more powerful tool in one slot. Invoke when: (1) tournament variants are structurally similar and you need to force diversity; (2) the evaluation oracle produces binary pass/fail but you need gradient signal; (3) a second model is needed to catch shared Claude blind spots before promotion; (4) the variant must survive an adversary's attack, not just a quality review. Triggers: /advanced-methodology, "extend the tournament", "cross-model review", "PRM scoring", "fraud attack", "structural diversity". NOT a replacement for the Core — adds one specialized tool per slot, not a new pipeline.
sergeeey/Claude-cod-top-2026 · ★ 7 · AI & Automation · score 75
Install: claude install-skill sergeeey/Claude-cod-top-2026
# Advanced Methodology Extensions These techniques extend specific stages of `/evolve-solution` when the standard tool in that slot is insufficient. Each maps to exactly one stage. Use one extension at a time — stacking multiple extensions on a single run risks methodology theater. ## When to use this skill Do not invoke by default. Check first: | Signal | Extension indicated | |---|---| | Tournament variants all share the same core mechanism | Structural Diversity Enforcer (Stage 4) | | Oracle is binary; can't tell WHY a variant fails | PRM-lite intermediate scoring (Stage 4) | | Skeptic is Claude; Claude wrote the variant | Cross-Model Critic (Stage 5) | | Finalist touches security, fraud, or financial flow | Fraud Attack Simulator (Stage 5) | | Simulation produces results but you need an equation | Simulation-to-Equation extraction (Stage 6) | --- ## Extension 1 — Structural Diversity Enforcer (Stage 4 add-on) **Problem:** five variants that all use the same mechanism but with different parameters are not a tournament — they are a parameter sweep. Structural diversity means different causal paths to the goal, not different settings. **How it works:** Before scoring begins, build a Mechanism Map: ```yaml variant_id: V1 mechanism: "cache the embedding, reuse on re-query" # causal path assumption_set: [embeddings are stable, queries repeat] independent_of: [V2, V3] # yes/no: does this variant's mechanism differ from Vn? ``` If any two variants share the same me