Stats
Actions
Tags
How this command is triggered — by the user, by Claude, or both
Slash command
/dots-swe:continueThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
<claude-instructions> **IMPORTANT - Check if skill is already loaded:** If you see a `<command-name>` tag in the current conversation turn: - The skill has ALREADY been loaded by the system - DO NOT call the Skill tool - Execute the behavior described below directly If there is NO `<command-name>` tag in the current conversation turn: - Call the Skill tool to load and execute this skill - Check the tool result and follow the behavior described below **Behavior when executing this command:** **If a bead ID is provided** (e.g., `/dots-swe:continue dots-abc`): 1. Run the continue script wi...
If you see a <command-name> tag in the current conversation turn:
If there is NO <command-name> tag in the current conversation turn:
Behavior when executing this command:
If a bead ID is provided (e.g., /dots-swe:continue dots-abc):
If NO bead ID is provided (e.g., /dots-swe:continue):
--format=json to get available sessionsThe script path is: $(ls -td $HOME/.claude/plugins/cache/dots-claude-plugins/dots-swe/*/scripts/continue.sh 2>/dev/null | head -1)
Reattach to an existing work session.
Usage: /dots-swe:continue [bead-id]
Examples:
/dots-swe:continue # Select from available sessions interactively
/dots-swe:continue dots-abc # Continue work on dots-abc
npx claudepluginhub objectiveous/dots-claude-plugins --plugin dots-swe/session-continueLoads and continues working in an existing session using the session-management skill's 'Action: continue' section step by step.
/continueResumes a paused dev workflow or takes over a cloud session from another machine. Optionally accepts --session <id> for cross-machine takeover.
/resumeRestores previous session context and suggests the next action to continue your coding workflow.
/continueResumes a previous Codex session using its thread ID, allowing follow-up prompts like fixing issues, running tests, or drilling deeper.
/continueAdvances the active vibe session by one step: checks status, runs worker and explainer agents, optionally explorer, and displays progress summary with changes, verifications, and next actions.
/continueScans docs/feature/ for feature progress across development waves, displays status summary with symbols and details, detects anomalies, and resumes next wave after confirmation.