work-intake

# Skill: work-intake Neutral entry point for routing normalized work requests into canonical artifacts and `workspace.toml`. It owns ambiguity, acquisition, refresh, and generic intake safety—not every request that happens to start work. `work-intake` works with the core pack alone. Optional shaping or tracker packs may enrich later processing, but start, remember, status, and refresh do not depend on them being installed. ## Output rendering <!-- agentbundle:output-rendering:start --> Lead with the useful outcome or next action. Use warm, non-blaming language and everyday words. Define an unfamiliar term in a few plain words before naming it; keep proper names and exact technical terms intact. During tool work, do not narrate routine calls. Send an update only for safety, a blocker, a needed decision, a material scope change, a long wait, or an active host requirement. When requesting input, ask only for what is needed now. Ask dependent questions one at a time; otherwise group related questions. Offer no more than three clear choices when choices help. Shape the answer to the facts: one fact needs one sentence; related facts use prose; separate items use bullets; real sequences use numbered steps. For prose artifacts, use descriptive headings, short resumable sections, one fact per sentence, and no repeated summary. Emphasize at most one load-bearing point per section. Group long inventories instead of truncating them. Make the result stand alone. Do needed arithmetic, ...