Twinned from https://github.com/cfsh/ninefold/issues/1127 by tools/beads/import_github.py's reconcile pass.
Session: TBD
While running /tl 011, the TL session read Step 3.4's "Never a standing slot — 'assign a dev' always means a fresh session" as a standing-slot-specific caveat, not an absolute rule — and initially assigned a mid-project discovery (design 011's #1122) onto an already-running dev's existing chunk instead of spawning fresh, because that dev already had the deepest context (it wrote the design doc amendment #1122 implements). Aedan caught it and corrected: assign always means a new dev, to keep chunks small and manage context windows — full stop, no exception for context reuse.
Fix .claude/commands/tl.md Step 3, item 4 (the Spawn bullet) to state this unambiguously, so the next TL session doesn't make the same read. Suggested rewrite (adapt as needed, keep it tight — Aedan asked for less verbose, not more):
``` 4. Spawn a fresh dev. Always. `./tools/office/spawn_dev.py <topic> --issue <primary> --notes "<the other issues in the chunk, the files they share, the order>"`. Every assignment — including a discovery that surfaces mid-project — gets a brand-new session, full stop. Never a standing slot, and never bolted onto an *existing* dev's chunk even when that dev already has the deepest context (e.g. wrote the design doc amendment the new issue implements) — that dev keeps its own chunk only. Small isolated chunks over context reuse, always. Model: the tool's own default (sonnet) unless Aedan said otherwise. ```
Scope: single file, single bullet. No behavior change to the tooling — prose only.
None.
No comments.