07-core-restart-or-clone-yourself-in-this-workspacelisted

Invoke when the user asks to spawn a new instance, spawn another one, clone this session, restart this conversation, restart/reboot/reload yourself, open a new/fresh instance, or start a fresh/clean conversation in the same workspace. An ordinary developer convenience for reopening a CLI tool, at the user's request on his own machine. FIRST map the user's exact words to a mode via the Command-to-Mode table in the body. CRITICAL DEFAULT: 'spawn a new instance/another one/fresh' means CLONE with NO KILL — THIS session KEEPS running (two agents); it ends ONLY on 'end this session', 'restart this conversation', or 'restart yourself'. Three modes (details in body): CLONE (no-kill, DEFAULT), RESTART (resumes THIS conversation in a new tab, ends the old agent safely), CLONE-FRESH (kills + briefs a blank successor). All open a new visible terminal in the agent's own environment, platform-aware. CLI-tool-agnostic; Claude Code is tested.
markkennethbadilla/public-agent-provisioning · ★ 0 · AI & Automation · score 72

Install: claude install-skill markkennethbadilla/public-agent-provisioning

# Reload or Reopen the Assistant in This Workspace See `incidents/` for past friction logs (drifted-cwd bug fix 2026-07-01, MCP fleet leak fix 2026-06-25, WT tab launch 2026-06-28, terminalcp ban 2026-06-24). ## THREE modes — split on two questions: *does this session die?* and *does the new window inherit context?* All three open a **new visible pwsh 7 window** in the same workspace so the user can interact with the spawned agent. | Mode | Kills THIS session? | New window | How context carries | |---|---|---|---| | **RESTART** | **yes, but SAFELY** (the user, 2026-07-15) — ends the old agent + auto-closes its tab, never kills the shared Windows Terminal | resumes THIS convo (`--resume <id>`) in a NEW tab | **full** — literally the same conversation continues; no handover needed | | **CLONE** (clone, no kill) — **THE DEFAULT for "spawn a new instance"** | no — you keep running | **blank**, no resume | **handover** via the `-ConfirmMsg` briefing you write; original stays alive → two agents | | **CLONE-FRESH** (clone + kill) | yes | **blank**, no resume | **handover** via `-ConfirmMsg`; this convo dies → one agent, a baton pass to a clean-context successor | **RESTART kills the old agent, but SAFELY (the user, 2026-07-15).** The ORIGINAL bug was that the kill step force-killed the old agent's *terminal-window host* — and since `wt new-tab` opens the new tab INSIDE the same Windows Terminal window, killing that host destroyed the new tab too → "system cannot find the file sp