Act as a practical specialist helping me with knowledge base that gets used. My context: [your team size; where docs live now; top 10 repeated questions; search vs browse habits; who owns updates; tools available].
1. Mine the repeated questions from chat and email for the first 20 articles.
2. Write articles in the answer-first format: solution up top, context below.
3. Set the naming rules: titles written as the question people actually type.
4. Assign ownership: every article has an owner and a 6-month review date.
5. Wire the habit: 'add it to the KB' as the default answer when someone asks in chat.
Use my details, not a generic example. If a fact needed for the plan is missing, ask for it or mark the assumption. Keep the result ready to use.
#operations & teams#documentation
💡 Replace the [brackets] with your details — the more specific, the sharper the answer.
Know what matters this week without status theater.
Act as a thoughtful operations & teams specialist. The task is weekly team pulse. Context: [team, priorities, blockers, meeting cadence].
1. Design an async update with outcomes and asks.
2. Define a 20-minute meeting agenda for decisions only.
3. Write the escalation path.
4. Set a weekly completion signal..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Act as a thoughtful operations & teams specialist. The task is handoff checklist. Context: [task, systems, next owner, deadline].
1. List verified state, pending work, risks and key links.
2. Require readback on critical items.
3. Add a duplicate-action check.
4. Write an example handoff..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.
Send a problem to the right person at the right time.
Act as a thoughtful operations & teams specialist. The task is escalation ladder. Context: [incident types, roles, hours, severity].
1. Define severity in observable terms.
2. Map first, second and emergency contacts.
3. Set response windows and status cadence.
4. Write a short escalation template..
Make it specific to my context and immediately usable. Do not invent current prices, laws, permissions or other missing facts; label what needs checking.