Follow-up Draft

Drafting follow-ups from meeting notes or messy threads usually leads to bloated messages that stakeholders ignore. This skill extracts the core asks and owners to produce concise Slack or email drafts that get responses.

What it does

• Action extraction identifies specific tasks, owners, and deadlines from provided context.
• Multi-tone drafting provides direct, warm, and executive-concise versions of every message.
• Assumption tracking labels missing details or guesses to prevent sending inaccurate information.
• Context mapping organizes raw notes into a structured state before generating drafts.

How it works

1. Provide the raw input such as meeting notes, an action list, or a link to a prior thread.
2. The skill analyzes the context to identify the specific ask and the responsible party.
3. Review the three generated versions and the context notes for any missing info.
4. Select the preferred version to copy, tweak, and send.

Frameworks & tools

This skill is platform-agnostic and works for Slack, Microsoft Teams, and email clients.

Why this beats prompting it yourself

Generic prompts often result in wordy, polite filler that hides the actual request. This skill enforces a strict structure that prioritizes the owner and the deadline, ensuring the recipient knows exactly what is expected without reading a wall of text.

Use cases

• Sending a post-meeting recap to a project team.
• Nudging a stakeholder on a late deliverable via Slack.
• Drafting a high-level executive summary of an open thread.
• Turning messy brainstorming notes into a clear list of action items.

Known limitations

Does not automatically send messages to third-party apps. Requires manual review of labeled assumptions before sending.