Skip to main content
ClaudeWave
Skill389 estrellas del repoactualizado 19d ago

ablation-brainstorm

Ablation-Brainstorm systematically removes individual components from a target system and observes resulting changes to map hidden dependencies and structural weaknesses. Use this skill when you need to understand system fragility, discover non-obvious relationships between parts, or generate innovative redesign concepts grounded in what actually breaks when components disappear.

Instalar en Claude Code
Copiar
git clone --depth 1 https://github.com/yogsoth-ai/de-anthropocentric-research-engine /tmp/ablation-brainstorm && cp -r /tmp/ablation-brainstorm/skills/ablation-brainstorm ~/.claude/skills/ablation-brainstorm
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

SKILL.md

# Ablation Brainstorm

Systematically remove components from a system one by one, observe what changes, and use the resulting insights to generate novel ideas.

## State Ledger

| Resource | Target | Current | % |
|----------|--------|---------|---|
| web-search | 20 | 0 | 0% |
| web-research | 5 | 0 | 0% |
| paper-overview | 20 | 0 | 0% |
| paper-search | 12 | 0 | 0% |
| paper-research | 5 | 0 | 0% |

## HARD-GATE

Cannot exit strategy until ≥80% of each budget line is consumed OR yield targets are met with justification for remaining budget.

## Available Tactics

| Tactic | Role |
|--------|------|
| coverage-analysis | Ensure all components are ablated |
| evaluation-filtering | Score and filter ablation-derived ideas |

## Available SOPs

| SOP | Role |
|-----|------|
| ablation-execution | Remove components one by one, record responses |
| dependency-identification | Extract dependency graph from ablation results |
| enumeration-synthesis | Synthesize ablation insights into idea report |

## Execution Guidance

1. **Decompose**: List all components of the target system
2. **Ablate**: Run ablation-execution — remove each component, record effects
3. **Analyze**: Run dependency-identification to find critical dependencies
4. **Ideate**: For each critical dependency, ask "what if this were replaced/eliminated/redesigned?"
5. **Filter**: Apply evaluation-filtering to rank generated ideas
6. **Synthesize**: Produce structured report via enumeration-synthesis

<!-- BEGIN available-tables (generated) -->

## Available Tactics

Optional, no fixed order; the final leaf is always a sop.

| Tactic | When to use |
| --- | --- |
| coverage-analysis | Systematic coverage evaluation pipeline — benchmark inventory, method-problem crossing, and intersection evaluation to map explored vs unexplored solution space. |

## Available SOPs

Optional, no fixed order; the final leaf is always a sop.

| SOP | When to use |
| --- | --- |
| ablation-execution | Remove components one by one from a system, record the response/impact of each removal. |
| dependency-identification | Identify critical dependencies from ablation results, producing a dependency graph and highlighting critical components. |
| enumeration-synthesis | Synthesize all systematic enumeration outputs into a structured idea report with prioritized recommendations. |

<!-- END available-tables (generated) -->