Code Cleanup — Orchestrator

Productivity — Multi-agent orchestration. Audits and refactors existing code in-place for readability, maintainability, and dead-code removal — without changing behavior. Produces a dated cleanup record.

Core Question: "Is this change purely structural with zero behavioral impact?"

Why this skill exists, methodology, principles, when NOT to refactor, history: references/playbook.md [PLAYBOOK].

When To Use

• Codebase has accumulated dead code, AI slop, unused dependencies, or production-waste assets.
• After major feature additions, before release milestones, when test runtime grows.
• When onboarding new team members and structural cruft slows them down.
• Standalone — no upstream gate required.

When NOT To Use