Execute work tracked in beads_rust (`br`) issues — claim a ready issue, do the work, record progress, capture discovered work without derailing, close cleanly, and keep the JSONL/DB pair in sync. Solo-agent and cross-session-by-same-agent only. Use when issues already exist in `.beads/` and an agent needs to work them across one or many sessions. NOT for creating issues from a planning document (use `plan-to-beads` for that) and NOT for multi-agent coordination.
Translate a planning document (markdown spec, design doc, requirements list, brainstorm) into well-structured beads_rust (`br`) issues — epics, tasks, dependencies, and properly-separated fields. Use when an agent has a plan artifact in hand and needs to construct issues from it, when decomposing an epic into child tasks, when populating description/design/acceptance/notes correctly, or when bulk-importing many related issues at once. NOT for working an already-created issue (claim → implement → close); that is a separate concern.
Use when writing sensitive feedback, PRs, reviews, critiques, refusals, corrections, recommendations, or relationship-preserving messages where the response should be candid but collegial, avoid accusatory framing, and never reveal rhetorical stage directions such as saying the tone is being softened or made diplomatic.
Canonical cross-agent protocol for plan documents (storage, naming, YAML schema, dispute tracking, and archive-after-commit workflow).