Stats
Actions
Tags
How this command is triggered — by the user, by Claude, or both
Slash command
/thunk:statusThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Check Session Status Check status of session: **$ARGUMENTS** ## Prerequisites If `thunk` is not found (exit code 127), install it first: Then continue with the steps below. ## Steps 1. Run `thunk status --session $ARGUMENTS` 2. Report to the user: - Current turn number - Current phase (drafting, peer_review, synthesizing, user_review, approved) - Path to current plan file if in user_review - Whether there are unanswered questions
Check status of session: $ARGUMENTS
If thunk is not found (exit code 127), install it first:
uv tool install git+https://github.com/gbasin/thunk
Then continue with the steps below.
thunk status --session $ARGUMENTSnpx claudepluginhub gbasin/thunk --plugin thunk/statusChecks current session status and measures goal drift to assess alignment and progress in the conversation.
/statusDisplays detailed status of an s2s session by ID, or the current active session. Shows workflow metadata, timing, agent state, artifacts, agenda, and round history.
/show-planDisplays the current or most recent plan from the session conversation, detecting headers like '## Plan', '### Implementation Details', or numbered steps. Formats and shows content or notifies if none exists.
/statusDisplays progress in the active vibe session: current phase, recent changes, verifications, next steps, and required user actions in plain language.
/show-planDisplays the current or latest executed plan in the session by detecting headings like '## Plan' or '### Implementation Plan'. Notifies if no plan exists.