Feature request: add draft/pending status for human input / open questions

[lastobelus]

Problem

In AI‑assisted workflows, I find I’m often creating tickets before requirements are fully known. It would be helpful to have a first‑class state to mark tickets that require human input (open questions, insufficient context, etc.).

Today the only documented statuses are open | in_progress | closed, so one has to either:

• use open, which makes tickets appear “ready” when they aren’t, or
• invent ad‑hoc tags and remember to exclude them manually.

Request

Add a supported status such as draft or pending (name is up to you) to explicitly represent “needs human input / missing requirements”.

Expected behavior

• tk status <id> <status> should accept the new status.
• tk ready should exclude tickets in draft/pending.
• tk blocked should treat draft/pending as not ready (unless you decide otherwise).
• tk list should filter by the new status.

Why it matters

This would reduce agent churn and prevent “ready” lists from mixing fully spec’d work with tickets that need clarification.

Happy to help test or propose a patch if desired.

[josharian]

FWIW, I vibe-coded up locally:

• tk ask: files an issue assigned to user, blocks until user closes, writes results to stdout
• tk tell: files an issue assigned to user, returns immediately (for "FYI-only")
• tk answer: dumb TUI that i run that watches for new ask/tell and lets me respond

It's working fine so far. I'll probably make a tk answer variant that uses Slack at some point.