Currently, all work items originate from the planner agent decomposing an approved spec. There's no way to create a work item without writing a spec first — this makes quick tasks
(refactoring, one-off fixes, small improvements) unnecessarily heavyweight.
Add support for creating work items directly, either through:
- A TUI command that opens an input form (title, description, optional spec reference)
- A human-created GitHub issue with the right labels that the poller picks up
- A TUI action that attaches a free-text "human directive" prompt to a work item
Ad-hoc work items should flow through the same dispatch pipeline (readiness check, implementor, reviewer) — they just skip the planning phase. The key question is what goes in the work item
body: the planner normally writes structured content (objective, scope, acceptance criteria). For ad-hoc items, the human provides this, so the TUI input or issue template needs to guide
them toward the same structure.
