メニュー
Spawn and manage side-sessions (research/debug) — dedicated fresh-context tabs off the captain's daemon lifecycle. Use when you want to research a topic, discuss an idea, or debug without polluting captain context.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Complete captain playbook — session startup, crew spawning, status writing, group awareness, and learnings. Use this skill at session start and reference it throughout.
Set up and manage the squadrant↔Telegram integration — bot setup, remote control, command-menu registration, and per-project notification tuning (mute, crew tiers, cap). Use when the user asks about Telegram setup, "why don't commands work", registering the /command menu, or muting/tuning notifications.
Add, edit, or remove a leveled crew routing rule in config.json without hand-editing JSON. Routing rules map task-text keywords to a tier → {agent, model}.
Command playbook — invoked on-demand by `squadrant command [--task ...]`. Covers daily briefing, delegation workflow, project registration, status checking, and learnings review. Command is no longer always-on.
Reconcile squadrant config drift that needs human judgment — changed defaults and invalid values surfaced by `squadrant config check`. Use when the drift banner says "items need review" or the user asks to fix config drift.
Four coding principles derived from Andrej Karpathy's observations on LLM pitfalls. Use to reduce wrong assumptions, overengineering, drive-by refactors, and vague execution. Apply to every crew coding task and every captain review.
| name | side-session |
| description | Spawn and manage side-sessions (research/debug) — dedicated fresh-context tabs off the captain's daemon lifecycle. Use when you want to research a topic, discuss an idea, or debug without polluting captain context. |
A side-session is a dedicated tab with fresh context running the captain model (opus), loaded with a role-specific template. It runs outside the crew/daemon lifecycle — no CREW IDLE/DONE noise back to the primary captain. Its only upward signal is an explicit, user-confirmed structured handoff.
# Research a topic, discuss an idea, produce a spec or GH issue
squadrant side spawn <project> "<topic>" --role research
# Debug a bug in an isolated scratch worktree
squadrant side spawn <project> "<topic>" --role debug
Options:
--name <name> — custom tab name (default: auto side-N)--direction <tab|right|down|left|up> — placement (default: tab)--agent <claude|opencode> — agent to use (default: claude)--topic-file <path> — read topic from a filesquadrant side list <project> # see live side tabs
squadrant side send <project> <name> "<follow-up>" # send a follow-up turn
squadrant side close <project> <name> # close when done
Can: Read code/docs, run read-only commands, create GH issues, write specs/plans. Cannot: Edit source code, spawn crews, merge/ship changes.
The session works in fresh context and produces artifacts (specs, GH issues, analysis). When done, it asks the user to confirm before sending a structured handoff to the primary captain.
Can: Read code/docs, run code and tests, edit source — but scratch only in its isolated worktree (instrumentation, logging, a failing test to pinpoint the root cause). Cannot: Edit source outside the scratch worktree, spawn crews, merge/ship changes.
The debug role creates an isolated scratch git worktree on spawn. Edits made there are never shipped — the draft patch lives on the scratch branch and is referenced in the handoff for a crew to implement cleanly. Close prunes the scratch worktree.
Before instrumenting, the debug session gathers from the user:
If the topic already contains all of this, it confirms and proceeds. Otherwise it asks.
1. Side session produces a result (root cause / artifact).
2. Session asks: "Notify the primary captain now? (y/n)"
3. On yes:
- Writes durable record: {spokeVault}/side-handoffs/<topic>.md
- Sends: squadrant runtime send <project> "🗒 Side handoff [<role>] — <topic> ..."
4. Primary captain receives handoff delivered daemon-direct via cmux (#332).
5. Captain does NOT auto-spawn a crew — waits for user's go.
🗒 Side handoff [research] — <topic>
Summary: <one-line summary>
Artifacts: <gh issue #NNN | spec: path/to/file.md | …>
Next: <recommended next action>
🗒 Side handoff [debug] — <topic>
Root cause: <one-line root cause>
Artifacts: <failing test path | instrumentation: <file> | draft patch: scratch branch crew/<name> | issue #NNN>
Next: <what a crew should implement to fix this>
When the user asks you to start a side session, spawn one:
# Research
squadrant side spawn <project> "<the research question or topic>" --role research
# Debug — creates a scratch worktree; pruned automatically on close
squadrant side spawn <project> "<the bug description>" --role debug
Note the session name from the output (e.g. side-1) and tell the user they can steer it with:
squadrant side send <project> side-1 "<follow-up>"
squadrant side close <project> side-1
When the session completes, its handoff is delivered daemon-direct via cmux (#332) with the 🗒 Side handoff prefix.
squadrant side spawn does NOT create a daemon task record. There is no CREW IDLE/DONE event for side-sessions. The only signal path is the explicit squadrant runtime send the side-session sends on user confirmation.
squadrant side close on a debug session automatically prunes its scratch worktree (the branch is preserved so the draft patch survives).