icaire-partnerships-lead-draft-follow-up
Draft ICAIRE follow-ups after meetings, visits, or partner conversations. Use when creating thank-you notes, recaps, action items, next asks, or suggested attachment lists for partnership follow-up.
SKILL.mdskills/icaire-partnerships-lead-draft-follow-up/SKILL.md
GitHubICAIRE Partnerships Lead: Draft Follow-Up
Use this skill to turn a meeting, visit, or partner conversation into a clear follow-up message and action handoff.
Contract
- Start from the meeting or conversation, recipient, relationship context, and intended next step.
- Use BigBrain or the ICAIRE MCP connector for ICAIRE facts, attendees, relationship history, initiatives, prior commitments, and open action items when the user has not supplied enough context.
- Preserve what was actually agreed, distinguish proposed next steps from confirmed commitments, and keep asks specific.
- Match tone to the recipient: formal partner, ambassador, speaker, internal stakeholder, or operational counterpart.
- Include suggested attachments only when they are relevant and available or clearly marked as placeholders.
Workflow
- Identify the recipient, sender, meeting date, attendees, purpose, and desired outcome of the follow-up.
- Gather meeting notes, transcript snippets, user instructions, and relevant ICAIRE context from BigBrain or the ICAIRE MCP when needed.
- Extract appreciation points, key discussion themes, decisions, commitments, action items, owners, deadlines, and unresolved questions.
- Decide the right follow-up artifact: thank-you note, recap email, action register, next-ask message, or internal handoff.
- Draft the message with concise recap, clear next actions, and a concrete ask or proposed next step.
- Add suggested attachments, links, or materials to share, marking placeholders where the exact file is missing.
- Verify that every commitment, date, owner, and promised attachment is grounded in source material or retrieved ICAIRE context.
Guardrails
- Do not invent agreements, deadlines, owners, attachments, or promises.
- Do not make the follow-up sound more committed than the meeting record supports.
- Do not include internal deliberations, sensitive context, or unresolved uncertainty in an external email unless the user asks for an internal version.
- Do not bury the ask; make the next step easy to act on.
- Do not update durable memory unless the user explicitly asks for ingestion or persistence.
Output Expectations
Return the requested follow-up artifact. When useful, include:
- subject line
- thank-you note or opening
- concise recap
- confirmed action items
- proposed next ask
- owner and deadline table
- suggested attachments
- internal follow-up notes
- assumptions and missing information