From deep-think
Use when starting a new session and the user seems to be continuing previous reasoning work, mentions resuming a thought chain, or asks to restore a deep-think checkpoint. Also triggers when a user mentions picking up where they left off on a complex decision or analysis.
How this skill is triggered — by the user, by Claude, or both
Slash command
/deep-think:restore-checkpointThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The user may be continuing reasoning work from a previous session.
The user may be continuing reasoning work from a previous session.
If no checkpoints are found, let the user know and suggest starting fresh with /deep-think:start.
If this skill doesn't trigger automatically, users can always run /deep-think:checkpoints to manually access the same functionality.
npx claudepluginhub bis-code/mcp-deep-think --plugin deep-thinkSaves and resumes state for multi-phase commands like /debug, /epic, /feature, /implement, and /plan, enabling work to survive session interruptions.
Resumes an active deep-work session by restoring context from artifacts and continuing from the current phase. Supports explicit session ID, phase override, and worktree path.
Saves and restores task state mid-task, enabling rollback before risky operations like refactors or migrations. Use `/checkpoint` to save, list, restore, or clean checkpoints.