How this skill is triggered — by the user, by Claude, or both
Slash command
/session-tools:spawn-sessionThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create a new Claude Code tmux session with `ai-*` prefix to act as a subagent worker.
Create a new Claude Code tmux session with ai-* prefix to act as a subagent worker.
$ARGUMENTS format: [type] [name-suffix] [-- initial prompt]
type - Session type: worker (default), brainstorm, auditorname-suffix - Optional custom suffix (auto-generated if omitted)-- initial prompt - Optional prompt to send after session startsExamples:
/session-tools:spawn-session → ai-worker-001/session-tools:spawn-session worker api → ai-worker-api/session-tools:spawn-session brainstorm design → ai-brainstorm-design/session-tools:spawn-session worker task1 -- Implement the login feature → spawns and sends promptParse arguments:
type = "worker" (default)
suffix = auto-generated or provided
prompt = text after "--" if present
Generate session name:
If no suffix provided, find next available number:
"$PLUGIN_DIR/bin/next-session-name" "<type>"
Returns: ai-<type>-<number> (e.g., ai-worker-003)
If suffix provided: ai-<type>-<suffix>
Validate session doesn't exist:
tmux has-session -t "<session_name>" 2>/dev/null && echo "exists"
If exists, error:
Session '<session_name>' already exists. Choose a different name.
Get working directory:
Use current working directory for the new session:
pwd
Spawn the session:
"$PLUGIN_DIR/bin/spawn-session" "<session_name>" "<working_dir>" ["<initial_prompt>"]
The script:
claude in the sessionVerify session started:
sleep 2
"$PLUGIN_DIR/bin/detect-state" "<session_name>"
Output result:
Spawned session: <session_name>
Working directory: <working_dir>
Status: <state>
To monitor: /session-tools:summarize-session <session_name>
To attach: tmux attach -t <session_name>
| Type | Prefix | Purpose |
|---|---|---|
worker | ai-worker-* | Task execution |
brainstorm | ai-brainstorm-* | Ideation and exploration |
auditor | ai-auditor-* | Code review and verification |
Spawn default worker:
/session-tools:spawn-session
Spawned session: ai-worker-001
Working directory: /Users/you/project
Status: idle - At prompt
To monitor: /session-tools:summarize-session ai-worker-001
To attach: tmux attach -t ai-worker-001
Spawn with task:
/session-tools:spawn-session worker api -- Implement the REST API endpoints for user authentication
Spawned session: ai-worker-api
Working directory: /Users/you/project
Status: working - Processing prompt
To monitor: /session-tools:summarize-session ai-worker-api
To attach: tmux attach -t ai-worker-api
Spawn brainstorm session:
/session-tools:spawn-session brainstorm arch -- What are the best approaches for implementing caching in this codebase?
Spawned session: ai-brainstorm-arch
Working directory: /Users/you/project
Status: working - Analyzing
Spawn workers for parallel tasks:
/session-tools:spawn-session worker auth -- Implement authentication
/session-tools:spawn-session worker api -- Implement API routes
/session-tools:spawn-session worker tests -- Write integration tests
Monitor progress:
/session-tools:list-sessions
Check specific worker:
/session-tools:summarize-session ai-worker-auth
Handle blockers:
/session-tools:approve-action ai-worker-auth approve
/session-tools:unstick-session ai-worker-api auto
Guides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.
npx claudepluginhub shsym/claude-session-tools --plugin session-tools