task-draftlisted

# task-draft — a request source into a task's context table Takes a **request source** — a chat thread, a document, a conversation someone relayed — and fills the context table of a task record. It sorts what was said into the rows your team uses, and keeps **fact, inference, and undecided** visibly apart. With no existing record it creates one; with one that exists it fills only what is empty. Filing the task in an engineering tracker is out of scope — that is `/pm:task-publish`. ## Principles - **Write only from what you were given. Never invent.** Every cell traces to something in the source. A cell you cannot fill is filled **by asking, or left empty** — not by guessing. Interpretation you added while sorting carries `labels.assumption`; what nobody has settled carries `labels.tbd`. - **Properties are confirmed, not chosen.** Infer a recommendation for each property from the source, then let the user pick it in one short `AskUserQuestion` round. Never settle a property silently. - **Product language.** No engineering vocabulary. Write as far as *what* is being asked for; *how* is undecided or delegated. - **Cells are short.** A context table is a list of items, not a description. The sentence rules are in section 2. - **Provisional stays provisional.** If whether to build the thing at all is still open, the scope rows are provisional and the preview says so. - **Every external write goes through preview → "go".** Creating and filling alike. Read back afterwards to veri