openyoko: Skill for Claude Code

/spawn Skill

Spin up a new Claude Code instance in a fresh tmux pane with full context handoff. Use this to delegate work to a parallel session, offload research, or start fresh with a synthesized plan.

Convention:

• Flow, tmux commands, handoff prompts
• Repo/vault paths come from arguments, current directory, or config/vault.json (see CLAUDE.md)

Usage

/spawn                          # Interactive - asks for context
/spawn <repo-path>              # Spawn in specific repo
/spawn <repo-path> "<prompt>"   # Spawn with specific initial prompt

---

Philosophy

Context windows degrade. Fresh sessions are sharp. This skill lets you:

• Hand off a plan to a fresh instance for execution
• Spin up parallel research without polluting your main context
• Delegate a subtask while you continue working
• Start a new session with synthesized context from current work

The default first action for spawned sessions is review and validate - ensuring no discrepancies in the handed-off plan and enforcing best practices.

---

Flow

Phase 1: Preflight Checks

Check tmux is running:

if [ -z "$TMUX" ]; then
  echo "ERROR: Not inside a tmux session"
  exit 1
fi

If not in tmux → STOP and tell user: "You must be inside a tmux session to use /spawn. Run tmux first."

Get current window and pane info:

CURRENT_WINDOW=$(tmux display-message -p '#I')
CURRENT_PANE=$(tmux display-message -p '#P')

Phase 2: Gather Context

If no arguments provided, ask:

1. Target repo path - Where should the new Claude Code run?

   • Default: current working directory ($(pwd))
   • Options: current workspace, vault (from config/vault.json), or another path the user specifies

2. Initial prompt - What should the new instance do first?

   • Default: "Review the current plan and ensure no discrepancies. Validate approach against best practices before proceeding."
   • Custom: User provides specific instructions

3. Context to hand off (optional):

   • Current plan/iteration being discussed
   • Key files to read first
   • Specific constraints or decisions made
   • Skills to invoke (e.g., /daily, /scan)