follow-up-draftlisted

# follow-up-draft ## Purpose Draft a concise follow-up that preserves the ask, owner, timing, context, and next step. ## Use For - Post-meeting follow-ups - Slack reminders - Email recaps - Nudges on open asks ## Inputs - Notes - Action list - Open ask - Project context - Prior thread context ## Guardrails - Read before write. - Do not send the draft unless explicitly asked. - Include the ask, owner, deadline or timing, and next step when known. - Label assumptions or missing details. - Keep the message concise and business-user friendly. ## Shared Output Expectations When context is messy or multi-source, include only the useful subset of: - Source-backed facts - Assumptions - Source gaps - Stakeholder sensitivities - Potential misread - Suggested next response or next action Do not include every field mechanically. Use the smallest useful output. ## Output - Direct version - Warm version - Executive concise version - Context note, when helpful If the user wants a fuller record before drafting, map the source state into [CONVERSATION_STATE.md](../../templates/CONVERSATION_STATE.md). ## Success Standard The user should be able to copy, tweak, and send a version within 5 minutes.