From citadel
Exports Citadel state (campaigns, postmortems, research, backlog, discoveries) to docs/citadel/ markdown, removes harness files/hooks/directories. Enables restore on reinstall via /do setup.
npx claudepluginhub sethgammon/citadel --plugin citadelThis skill uses the workspace's default tool permissions.
**Use when:** removing Citadel from a project entirely -- exports state and cleans up hooks before uninstall.
Configures Citadel harness on first run: installs hooks, detects stack, generates harness.json, restores project archives if present, runs live demo on real code, prints reference card. Modes: Recommended (~3min), Full Tour (~8min), Express (~30s).
Removes optimus-generated files from .claude/ directories in single, monorepo, or multi-repo projects. Classifies unmodified/generated/modified, skips tests, confirms before delete.
Uninstalls Pith from Claude Code by removing hooks, slash commands, and cleaning settings.json entries. Use via /pith uninstall or removal requests. Preserves token history unless full wipe requested.
Share bugs, ideas, or general feedback.
Use when: removing Citadel from a project entirely -- exports state and cleans up hooks before uninstall. Don't use when: pausing campaign work (just stop or use /session-handoff); removing a single skill (delete its directory manually).
/unharness # Export archive, then remove harness
/unharness --export-only # Export to docs/citadel/ without removing anything
Read .citadel/plugin-root.txt to locate the Citadel install.
If missing, use the directory containing this SKILL.md as the fallback.
cat .citadel/plugin-root.txt 2>/dev/null || echo "fallback"
Store as {citadelRoot}.
node {citadelRoot}/scripts/unharness.js
For --export-only:
node {citadelRoot}/scripts/unharness.js --export-only
The script:
.planning/ for valuable content (campaigns, postmortems, research, backlog, discoveries).citadel/project.md and .claude/harness.json for project metadatadocs/citadel/{category}.md files with citadel-archive: true frontmatter.planning/, .citadel/, .claude/agent-context/.claude/settings.json (preserves user hooks)Print the script output verbatim.
After the script completes, print:
If archive was written:
Archive is at docs/citadel/ — commit it, delete it, or leave it.
Run /do setup again anytime to reinstall Citadel.
If you run setup in this project, it will find the archive and offer to restore your history.
If nothing was exported (empty project):
Citadel removed. No history to archive.
Run /do setup again anytime to reinstall.
If --export-only:
Archive written to docs/citadel/. Harness files left in place.
Run /unharness without --export-only to complete the removal.
Script not found:
Report the error and explain the user can run the hook installer manually:
node /path/to/Citadel/scripts/unharness.js
No .planning/ directory (harness was installed but never used): The script handles this gracefully — it skips the export and proceeds to cleanup. Nothing special needed.
docs/citadel/ already exists from a previous unharness:
The script overwrites with the current timestamp. Prior archives are replaced.
If the user wants to keep prior archives, they should commit docs/citadel/ to git first.
User runs unharness on a project that was never set up: The script exits cleanly with "Nothing to export." and nothing is deleted that shouldn't be.
Disclosure: "Removing Citadel from [project]. Exporting state to [path] before deletion. This is irreversible without reinstalling." Reversibility: red — removes hooks, clears .claude/settings.json entries, deletes .planning/. State export is made first, but reinstalling requires /setup. Trust gates:
After the closing message in Step 3, output nothing further. Unharness is a terminal action — no HANDOFF block, no next-step suggestions. The session is now running without hooks.