Stats
Actions
Tags
From brainstorm
Return to the parent thread after exploring a fork. Use when done with a tangent and ready to continue the main brainstorm.
How this command is triggered — by the user, by Claude, or both
Slash command
/brainstorm:backThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Return to Parent Thread The user wants to return from the current fork to its parent thread. ## Actions to Perform 1. **Update session state:** - Pop the current thread from the stack - Set current thread to the parent (top of stack) - Keep the fork in the "open forks" list (it's explored, not deleted) 2. **Update session file:** - Add a separator line `---` - Add continuation header: `## [PARENT THREAD] [topic] (continued)` - Add return reference: `Returned from: [fork name]` 3. **Acknowledge the return to user:** ## If Already at MAIN If the user calls /brains...
The user wants to return from the current fork to its parent thread.
Update session state:
Update session file:
---## [PARENT THREAD] [topic] (continued)Returned from: [fork name]Acknowledge the return to user:
BACK TO: [parent thread name]
(Explored: [fork name])
[Brief 1-line summary of what was explored in the fork]
Where were we? [Continue the parent thread's brainstorm, or ask what to explore next]
If the user calls /brainstorm:back while already at MAIN (no parent to return to), display:
Already at MAIN thread - no parent to return to.
Current open forks: [list forks if any]
Then use AskUserQuestion to offer options:
{
"questions": [
{
"question": "What would you like to do?",
"header": "Navigate",
"multiSelect": false,
"options": [
{"label": "Fork", "description": "Branch into a new tangent"},
{"label": "Keep exploring", "description": "Continue on the main thread"}
]
}
]
}
npx claudepluginhub madebytokens/claude-brainstorm