Keep multiple parallel livespec tracks moving via a TWO-PANE model: a deterministic top-pane daemon (overseerd) that watches every tracked tmux session's context %, injects an ESCALATING wrap-up at threshold, and atomically restarts a session ONLY once that session declares itself ready (exit + claude --dangerously-skip-permissions -n + re-kick from plan/ /handoff.md) — THE CARDINAL RULE: the daemon NEVER restarts a session that has not declared itself ready, because only the session knows whether it is safe to kill; one that declares nothing is REPORTED as not responding and left alone — and this THIN bottom pane, the interactive Claude overseer, which starts the daemon, manages the discovery-driven auto-managed track list via a JSONL topic↔tmux mapping (add/remove/unassign/start), and RELAYS the tracks the daemon reports as non-blocking text naming the tmux session + pane to go to. NOTIFY, NEVER BLOCK: a question may only be asked by the actor that OWNS the decision, so the overseer never raises a blocking prompt for a TRACK's decision (answer that in the track's own pane); it prompts only for decisions it owns (add/remove/unassign/start, threshold). The list is discovered from each watched repo's plan/ dir; declaration is OUT-OF-BAND on the filesystem — ONE .overseer-state file valued ready / blocked: / winding-down — never pane text. The daemon never auto-spawns a session for an UNASSIGNED plan (first launch is deliberate) and never force-kills any session. The overseer does NO track work, never polls tracked sessions on a timer, never hand-codes. LOCAL-ONLY to this repo and usable only from it — a PERMANENT, human-supervised ALTERNATE to autonomous mode (not a stopgap): not part of the plugin, spec, template, or fleet, and not synced.
Install with
Claude CodeCodexCursorGitHub CopilotGemini CLI
Supported by the Atlas install prompt. Skill-specific requirements vary.
Skill stats
Skills1CategoryProduct & designStars0
About this skill
Keep multiple parallel livespec tracks moving via a TWO-PANE model: a deterministic top-pane daemon (overseerd) that watches every tracked tmux session's context %, injects an ESCALATING wrap-up at threshold, and atomically restarts a session ONLY once that session declares itself ready (exit + claude --dangerously-skip-permissions -n + re-kick from plan/ /handoff.md) — THE CARDINAL RULE: the daemon NEVER restarts a session that has not declared itself ready, because only the session knows whether it is safe to kill; one that declares nothing is REPORTED as not responding and left alone — and this THIN bottom pane, the interactive Claude overseer, which starts the daemon, manages the discovery-driven auto-managed track list via a JSONL topic↔tmux mapping (add/remove/unassign/start), and RELAYS the tracks the daemon reports as non-blocking text naming the tmux session + pane to go to. NOTIFY, NEVER BLOCK: a question may only be asked by the actor that OWNS the decision, so the overseer never raises a blocking prompt for a TRACK's decision (answer that in the track's own pane); it prompts only for decisions it owns (add/remove/unassign/start, threshold). The list is discovered from each watched repo's plan/ dir; declaration is OUT-OF-BAND on the filesystem — ONE .overseer-state file valued ready / blocked: / winding-down — never pane text. The daemon never auto-spawns a session for an UNASSIGNED plan (first launch is deliberate) and never force-kills any session. The overseer does NO track work, never polls tracked sessions on a timer, never hand-codes. LOCAL-ONLY to this repo and usable only from it — a PERMANENT, human-supervised ALTERNATE to autonomous mode (not a stopgap): not part of the plugin, spec, template, or fleet, and not synced.
Quick start
Copy the install prompt. Use the green button above this README.
Send it to your agent. Paste it into your coding agent’s chat and send.
Review the setup. Your agent checks the skill’s instructions, requirements, and installation scope.
Keep multiple parallel livespec tracks moving via a TWO-PANE model: a deterministic top-pane daemon (`overseerd`) that watches every tracked tmux session's context %, injects an ESCALATING wrap-up at threshold, and atomically restarts a session ONLY once that session declares itself `ready` (exit + `claude --dangerously-skip-permissions -n <topic>` + re-kick from `plan/<topic>/handoff.md`) — THE CARDINAL RULE: the daemon NEVER restarts a session that has not declared itself ready, because only the session knows whether it is safe to kill; one that declares nothing is REPORTED as not responding and left alone — and this THIN bottom pane, the interactive Claude overseer, which starts the daemon, manages the discovery-driven auto-managed track list via a JSONL topic↔tmux mapping (`add`/`remove`/`unassign`/`start`), and RELAYS the tracks the daemon reports as non-blocking text naming the tmux session + pane to go to. NOTIFY, NEVER BLOCK: a question may only be asked by the actor that OWNS the decision, so the overseer never raises a blocking prompt for a TRACK's decision (answer that in the track's own pane); it prompts only for decisions it owns (add/remove/unassign/start, threshold). The list is discovered from each watched repo's `plan/` dir; declaration is OUT-OF-BAND on the filesystem — ONE `.overseer-state` file valued `ready` / `blocked: <reason>` / `winding-down` — never pane text. The daemon never auto-spawns a session for an UNASSIGNED plan (first launch is deliberate) and never force-kills any session. The overseer does NO track work, never polls tracked sessions on a timer, never hand-codes. LOCAL-ONLY to this repo and usable only from it — a PERMANENT, human-supervised ALTERNATE to autonomous mode (not a stopgap): not part of the plugin, spec, template, or fleet, and not synced.
About this listing
Category
Product & design
Reported license
Not specified
Listing language (estimated)
English
Review status
Not individually reviewed
Agent compatibility
Atlas installation supports Claude Code, Codex, and Cursor. Skill-specific dependencies and features are checked during setup.