sunsetlisted
Install: claude install-skill thdelmas/sunset
# Sunset — retire a project with dignity
A grief function for a portfolio. When an effort is over, the failure mode isn't ending it — it's *not* ending it: leaving it half-alive in the backlog, quietly taxing attention, accumulating guilt, its reusable parts buried with it. This is the ritual that closes it well — extract the value, archive with a marked grave, and release the rent it was charging.
Ending a project cleanly is a skill, not a confession. **Dignity, not guilt:** a project's death is information, not a verdict on you.
## Death vs. freeze — don't euthanize the living
First, be honest about what's actually happening:
- **Frozen** → paused with a real, written revival condition (a date, a dependency, a decision point). Don't sunset it — instead archive its *state* cleanly and record the trigger that would wake it. A freeze is a sleeping body, not a corpse.
- **Merged** → not dying, migrating. Its value is moving into another effort. Sunset the husk, but the harvest (below) is really a transplant — track where each part goes.
- **Dead** → genuinely over. Full sunset. But a death has a second axis you must name — whether the substrate survives it:
- **Dormant death** → over, but the substrate persists (archived code, a doc, a brand you still own). The grave is **exhumable** — revival is possible if the world changes. This is hibernation with a tombstone.
- **Terminal death** → over, and the substrate itself is gone or unrepeatable — a team that dissolved, a m