# Fusion playbook

Use this playbook when two skills overlap enough that maintaining them separately creates routing confusion or duplicated workflows.

## Merge candidate signals

- Descriptions target the same user intent.
- Trigger evals repeatedly select the wrong neighbor skill.
- Output contracts are materially similar.
- One skill is rarely used but appears as a top overlap neighbor.
- Users frequently ask which one to use.

## Fusion plan sections

- Keep: workflow, evals, scripts, references, or examples worth preserving.
- Rename: final skill name and alias strategy.
- Merge: shared output contract, trigger set, references, scripts, and release gates.
- Drop: outdated triggers, duplicated examples, stale references, and wrapper forks.
- Migration: deprecate source skills, route old triggers to the replacement, and keep tombstone content until safe removal.

## Evidence

Run `scripts/detect_merge_candidates.py`, then create a concrete plan with `scripts/plan_skill_fusion.py`.