What problem does it solve?
Removing a coding-agent operating layer like Citadel by hand risks deleting files you do not own, leaving orphaned hooks and registrations, or destroying state you later need. This Skill performs a safe, receipt-owned exit: it plans removal without writing anything, requires explicit approval, and proves exactly what was removed, retained, or left unknown.
Core Features & Use Cases
- No-write leave planning: Generates a reviewable plan listing exact files to remove or restore, modified entries to retain, and a portable archive path before any change occurs.
- Receipt-owned apply with confirmation token: Applies only the exact saved plan after explicit user approval, revalidating source, target, and pre-images, then runs a doctor check to verify the result.
- Legacy install handling: Detects non-adopted (legacy) installs, requires an import plan with its own approval first, and never claims exact removal without receipt evidence.
- Use Case: You installed Citadel in a repository and now want it gone. The Skill shows you the exact removal plan and archive location, waits for your approval token, removes only owned material, and reports retained conflicts and unknown external registrations.
Quick Start
Ask the agent to unharness Citadel from this project and show me the removal plan before deleting anything.