Email To Tasks Skill

Long emails and longer threads hide their asks: three requests buried in paragraph four, a soft deadline in the sign-off, an implied "you'll handle this?" nobody confirmed. Until the asks are extracted, the thread itself becomes the task — re-read five times, actioned zero. This skill mines the actual requests (quoted, so nothing is invented), converts each into owner-verb-deadline form with a done-test, and drafts the confirming reply that turns assumptions into commitments.

What This Skill Produces

• The ask extraction — every explicit and implied request, quoted from the source text
• The task list — each: owner · verb-first action · deadline (stated or proposed) · the done-test
• The ambiguity list — asks too vague to action, each with the clarifying question that fixes it
• The confirming reply — the short message that locks owners and dates before anyone's assumption diverges

Required Inputs

Ask for these if not provided:

• The email/thread — verbatim; extraction quotes its sources
• Who the user is in it — extraction is role-relative: their tasks, tasks they're delegating, and tasks that are someone else's problem are three different lists
• The task system — where tasks live (tool or list), so the output lands in import-ready shape

Framework: The Extraction Rules