Stats
Actions
Tags
From clp
Reset CLP state for a fresh start. Clears handoffs, session memory, and optionally the skill registry. This skill should be used when starting a completely new task unrelated to previous work, or when handoff state has become stale or corrupted.
How this skill is triggered — by the user, by Claude, or both
Slash command
/clp:clp-resetThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
<instructions>
<reset_levels>
Clear only the handoff state:
- Delete all files in .claude/handoffs/
- The skill registry and configuration are preserved
- Session memory files are preserved
- Use when: switching to a new task but same project
Always confirm the reset level with the user before executing. After reset, run /clp:doctor to verify the installation is healthy.
- Always ask for confirmation before any destructive action. - Never delete hook scripts, settings.json, or CLAUDE.md. - After reset, suggest running /clp:status to verify clean state. - If $ARGUMENTS specifies a level, use it. Otherwise default to "soft".npx claudepluginhub ryannle1/clp --plugin clpResets DevTeam sessions, clears history and state, aborts stuck processes, and recovers from errors via /devteam:reset command with options like --full, --clear-history.
Resets Hypo-Workflow runtime artifacts (state, logs, reports) safely without deleting core project instructions. Supports full and hard reset modes with safety confirmations.
Resets FPF reasoning cycle: archives sessions, clears/moves knowledge files in L0-L2 directories, or reverts decisions. Invoke manually via /fpf:reset.