manage-worklisted

# Manage work conversationally This is the normal entrypoint for Forge. The operator can speak in ordinary language and should not need a skill name, machine id, pane, or attempt id. Classify the request, preserve its authority boundary, and use the smallest landed Beads or Forged operation that owns the requested result. The lead agent owns conversation and judgment. Beads owns the editable plan. Forged owns durable execution and lifecycle after explicit submission. Operations Overview and Work Detail project that truth; App resources are optional views, never another source of state. ## Route one intent Authority is monotonic. Do not let a read become a write, a plan become execution, or an existing-work control become a new submission. | Intent | Route | Authority | | --- | --- | --- | | Observe or explain the portfolio, queue, repository, or what needs attention | `forged operations overview` (deliberately opening the board view routes via `../board/SKILL.md`) | Read only | | Explain one durable run or epic | Resolve one exact WorkIdentity, then `forged work detail` | Read only | | Explore | Discuss or research supplied context | Persist nothing | | Plan or revise | Read and follow `../plan/SKILL.md` | Native Bead writes only | | Configure profiles, rosters, role/model choices, or pricing | Read and follow `../configure/SKILL.md` | Operator authoring config only | | Critique | Read and follow `../critique/SKILL.md` | Its one bounded recommendation comment only | | Ad