nexus-performancelisted

# Nexus Performance Route to the correct sub-skill and follow it end-to-end. --- ## Compatibility - Sub-skills: `memory-leak.md`, `dependency-blast-radius.md` - Supporting files: `examples/production-scenarios.md`, `checklists/performance-checklist.md`, `heuristics/performance-heuristics.md`, `anti-patterns/common-mistakes.md`, `validation/output-validation.md` - Required tools: Read, Bash, Grep - Hands off to: `nexus:debugging` for single-service runtime failures - Hands off to: `nexus:planning` after the fix is approved --- ## Routing ### Step 1 — Classify the Request Pick exactly one track: | Track | Signal | Sub-skill | |-------|--------|-----------| | **Memory Leak** | "memory growing", "OOM kill", "heap dump", "RSS increasing", "memory usage creeping up", process being killed by the OS | `memory-leak.md` | | **Dependency Blast Radius** | "upgrade X to version Y", "what breaks if I upgrade", "which services use this lib", "blast radius of upgrading", "safe to upgrade?", "dependency impact analysis" | `dependency-blast-radius.md` | If the request does not clearly fit one track, ask one question: "Is this about memory/CPU/latency behavior of a running service, or about the risk of upgrading a dependency?" ### Step 2 — Read Sub-Skill and Execute Read the appropriate sub-skill file. Follow its numbered steps in order. Do not skip steps. Read `heuristics/performance-heuristics.md` for fast pattern-matching before starting investigation. ### Step 3 — Validate O