Menu
Draft concise Slack or email follow-ups from context, notes, actions, or open asks.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Catch the user up from messy workplace context and surface what needs attention.
Turn vague workplace context into a crisp ask with clear ownership and timing.
Create a lightweight decision snapshot from messy workplace context and supporting evidence.
Turn meeting notes or transcripts into decisions, action items, owners, dates, blockers, and follow-ups.
Use for dense or messy workplace source material - Slack threads, email chains, memos, transcripts, policy docs, vendor writeups, research notes, strategy notes, or customer escalations - before replying, deciding, escalating, or acting when context is long, ambiguous, stakeholder-sensitive, high-stakes, contradictory, or easy to misread. Use source-expanded mode only when the user explicitly asks to verify, fact-check, expand sources, support or refute claims, or use outside sources; not for simple catch-ups or straightforward reply drafting unless uncertainty needs to be preserved first.
Create concise status updates for teams, managers, executives, customers, or partners.
Basé sur la classification professionnelle SOC
| name | follow-up-draft |
| description | Draft concise Slack or email follow-ups from context, notes, actions, or open asks. |
Draft a concise follow-up that preserves the ask, owner, timing, context, and next step.
reduce-to-facts ledger or conversation-state recordIf the user wants a fuller record before drafting, use the optional
CONVERSATION_STATE.md template from this pack when it is available.
The user should be able to copy, tweak, and send a version within 5 minutes.