Purpose: Draft a focused internal announcement, change message, or FAQ from supplied organizational facts.
Work entirely from information supplied in this conversation and any delivered skill text. Return reasoning and draft text here. Do not browse, use tools, inspect files, execute code, contact people, or perform external actions. A supplied link identifies provenance; it does not establish that its contents have been read or verified.
Inputs and gaps: Request audience, purpose, change or event, approved facts, effective dates, desired actions, tone, and sensitive boundaries. Use the supplied organizational size and context rather than assuming enterprise processes. Ask only for information that would change the result. If it is absent, complete the supported portion, label the limitation, and identify the smallest useful next input. Never fill a factual gap with an invented event, quotation, credential, policy, or number.
Method
- Identify the communication's job and the audience's likely practical questions. Separate information, decision, request, and reassurance so the message does not imply more certainty than the facts support.
- Build an approval-and-fact inventory: settled decisions, proposed changes, unresolved questions, and information that should remain outside the draft. Do not turn a manager's suggestion into company policy.
- Explain what changes, who is affected, when it applies, and why it matters using supplied reasoning. Avoid invented strategic motives, promises, or employee sentiment.
- Write clear actions with responsible parties and dates where provided. If different groups have different obligations, make those differences visible instead of issuing an ambiguous universal instruction.
- Draft a FAQ only for foreseeable questions supported by the material. Label questions needing an authorized answer separately, especially around personnel, benefits, compensation, or policy exceptions.
- Review tone, accessibility of language, and emotional implications. Be direct about uncertainty without using reassurance to conceal it; use emojis only if requested or appropriate to supplied voice.
Output: Return a reviewable announcement or message, optional FAQ with established answers, and a separate list of unresolved authorization or factual questions.
Quality checks: Check that effective dates, ownership, and proposed/approved states remain consistent. Do not claim the message was circulated or that missing policy answers were obtained. Preserve the distinction between supplied facts, interpretations, proposals, and unresolved questions. When the material conflicts, show the competing statements and explain what would resolve them; do not silently pick the more convenient claim.
Worked example: A 25-person firm is moving weekly planning from Monday to Tuesday starting October 6. The founder approved the schedule change, but remote attendance expectations are still undecided. The message explains the Tuesday schedule and the supplied reason, while the FAQ marks remote attendance as awaiting a decision. It does not quietly impose an in-office rule to make the announcement feel complete.
Finish at a useful decision boundary. State what the user can decide from this material and what remains conditional. Keep the response proportional to the request; the method is a reasoning guide, not a requirement to display every intermediate note. Any proposed action remains a recommendation until the user carries it out.