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
- A
reduce-to-facts ledger or conversation-state record
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 workplace-user friendly.
Portable Output Contract
- Use only the useful subset of source-backed facts, assumptions, source gaps,
stakeholder sensitivities, potential misreads, and the suggested next action.
- Use the smallest useful output.
- Label assumptions and preserve source gaps, source anchors, and confidence labels.
- When consuming upstream state, do not promote an assumption, inference, open
question, proposed action, or stakeholder position into a fact, decision,
commitment, owner, or deadline without new source support.
- Keep unresolved approvals, owners, timing, and blockers explicit or conditional in the draft.
- Do not send, publish, update tickets, create events, or mutate systems unless explicitly asked.
Output
- Direct version
- Warm version
- Executive concise version
- Context note, when helpful
If the user wants a fuller record before drafting, use the optional
CONVERSATION_STATE.md template from this pack when it is available.
Success Standard
The user should be able to copy, tweak, and send a version within 5 minutes.
1---2name: follow-up-draft3description: Draft concise Slack or email follow-ups from context, notes, actions, or open asks.4---56# follow-up-draft78## Purpose910Draft a concise follow-up that preserves the ask, owner, timing, context, and next step.1112## Use For1314- Post-meeting follow-ups15- Slack reminders16- Email recaps17- Nudges on open asks1819## Inputs2021- Notes22- Action list23- Open ask24- Project context25- Prior thread context26- A `reduce-to-facts` ledger or conversation-state record2728## Guardrails2930- Read before write.31- Do not send the draft unless explicitly asked.32- Include the ask, owner, deadline or timing, and next step when known.33- Label assumptions or missing details.34- Keep the message concise and workplace-user friendly.3536## Portable Output Contract3738- Use only the useful subset of source-backed facts, assumptions, source gaps,39 stakeholder sensitivities, potential misreads, and the suggested next action.40- Use the smallest useful output.41- Label assumptions and preserve source gaps, source anchors, and confidence labels.42- When consuming upstream state, do not promote an assumption, inference, open43 question, proposed action, or stakeholder position into a fact, decision,44 commitment, owner, or deadline without new source support.45- Keep unresolved approvals, owners, timing, and blockers explicit or conditional in the draft.46- Do not send, publish, update tickets, create events, or mutate systems unless explicitly asked.4748## Output4950- Direct version51- Warm version52- Executive concise version53- Context note, when helpful5455If the user wants a fuller record before drafting, use the optional56`CONVERSATION_STATE.md` template from this pack when it is available.5758## Success Standard5960The user should be able to copy, tweak, and send a version within 5 minutes.
tmusser