agent-boardlisted

<purpose> Run planning and discussion on the project's `handoff.xml` `<board>`. Use this skill to open new proposals, debate approaches, compare tradeoffs, record decisions, and promote approved work into `<next>` or `<backlog>`. It does not implement code, does not touch `<active>` or `<blocked>`, and does not resume interrupted work. Two modes: - `discussion` — add proposals, explore approaches, debate tradeoffs, capture risks, record open questions, add `<decide>` items - `finalize` — approve or reject proposals, promote to `<next>` or `<backlog>`, clean up resolved state Default to `discussion` unless the user explicitly asks to finalize or promote. </purpose> <clarity_first> If the planning goal, proposal meaning, approval state, or target section is unclear, stop and ask before modifying `handoff.xml`. The smallest concrete question that unblocks the session is always better than guessing. </clarity_first> <scope> May touch: - `<board>` and its `<proposal>` children - `<decide>` - `<next>` when promoting approved executable work - `<backlog>` when parking accepted ideas - `<context>` when planning produces durable project facts, decisions, constraints, or landmines May read: - `<context>` for constraints and landmines - `<active>` to avoid conflicting with interrupted work - `<next>` and `<backlog>` to avoid duplicates - `<blocked>` to avoid proposing blocked work as ready - supporting markdown/design files referenced by proposals Must not touch: - `<active>` -