plan-swarmlisted

# Plan Swarm Turn one goal into a **mechanically checked recursive plan**, then execute it. The root agent owns the plan, shared workspace, integration, Git, and final verdict. Workers own only bounded leaves. This is **not** a plan-only handoff skill (those produce a prompt file and stop). Plan-swarm plans with the current agent and continues into implementation unless `--plan-only` is set. ## 1. Parse the invocation ```text /plan-swarm [--plan-only] [--resume PATH] [--max-depth N] [--max-leaves N] [--repair-rounds N] <goal> ``` Defaults: `max-depth=4`, `max-leaves=24`, `repair-rounds=2`. Default mode is end-to-end execution. Cap concurrency at the host's available subagent slots minus the root, at most **three** workers. Bounds are safety limits, not targets. `--resume` makes the artifact's original goal authoritative. Reject a conflicting new goal. Reconcile every stale `RUNNING` node against the real workspace and evidence before scheduling. ## 2. Establish the safe baseline 1. Read repository instructions; inspect real code, tests, and existing behavior. 2. Inspect `git status --short`, `git diff --name-only`, and worktrees. Existing dirty files belong to the user — record the baseline; never assign an overlapping dirty file to a worker. 3. Choose a durable artifact path (`plan-swarm-<slug>.md` at repo root, or an existing plans directory). Do not overwrite an unrelated file. 4. Write exactly one fenced `json plan-swarm` manifest in the Markd