Hub / Tech

A team member asked for: [paste request]. Turn it into a short specification: the problem, who uses it, user stories, acceptance criteria, data needed, and open questions to confirm before building. Keep it to one page.

Here are my rough notes on how we [process]: [paste]. Write clear documentation with a purpose line, prerequisites, numbered steps, screenshots to add, common mistakes and who to contact. Use simple language.

Here are this week's support tickets with subject and description: [paste]. Group them by category, rate each as urgent, normal or low with a reason, suggest which team should own each group, and list any repeating issue that needs a permanent fix.

Here are the facts about an incident: [what happened, when, who was affected, what we did]. Write a short incident summary with impact, timeline, root cause as currently known, fix applied, and actions to stop it happening again. Keep it factual and blame-free.

We need a tool for [job] for a team of [size] already using [current tools]. Compare [tool A] and [tool B] on fit for the job, ease of use, integrations with our tools, admin effort and risks. End with the questions to ask each vendor before deciding.

We want a simple internal app for [purpose], used by [who]. List the screens, the data each screen needs, the approval steps, and what to build first in a two-week version. Suggest how it should connect to [tools we use].