handoff-agent-boardlisted

<purpose> Manage planning in project-root `handoff.xml`. This skill is the board chair / planning manager. Use it to run human/agent or multi-agent discussion, compare approaches, capture detailed planning, resolve proposals, and assign approved work into `<next>` or `<backlog>`. This skill plans and assigns work. It does not implement code and does not resume interrupted implementation work. </purpose> <cross_lab_mode> The board is the shared artifact for semi-automated multi-agent, multi-lab discussion (Claude, Codex, Gemini, etc.). Tom dispatches turns between CLIs manually — no automation layer yet. Core rules: - **Turn tracking.** Each open proposal carries a `next_turn` attribute naming who is expected to act next: - `next_turn="agent"` - `next_turn="user"` - waiting on the user to answer a question or make a decision - **One turn per proposal per invocation.** When invoked as an agent participant (not as chair), inspect the relevant open proposal threads. If multiple proposals are admitted for the current agent, handle each admitted proposal once in the same invocation. Append at most one attributed `<entry>` per proposal thread unless the user explicitly dispatches multiple turns on the same proposal. Do not write turns for other agents. No ventriloquism — do not roleplay `by="codex"` from a Claude session or vice versa. - **Same-agent consecutive turns are fine.** A proposal may have several consecutive turns by the same agent (e.g. Claude thinking aloud acr