Reports, procedures, meeting notes and planning. 44 reviewed prompts for operations.
Operations runs on written routines: meeting notes with clear owners, status reports, procedures, checklists and plans. The prompts and skills here turn messy input into something others can act on, such as a table of decisions with owners and due dates. They work best when you paste in the real notes or figures and ask for a specific format, so nothing is invented to fill a gap.
Builds a phased project plan with milestones, owners, dependencies and schedule risks from a goal and a duration. Use it when kicking off a project or sanity-checking a deadline.
Interviews you about your home and devices, then produces a step-by-step Wi-Fi and network plan with equipment options and tradeoffs. Use when upgrading or building a home network.
Converts a loosely worded business or error report into a clear ticket with problem, impact, steps to reproduce, acceptance criteria and open questions. Use it when business teams send requests to IT or product.
Turns a described situation into objectives, stages, risks and a time-boxed execution plan with owners and checkpoints. Use when you have a goal and a mess of facts and need a clear plan.
Drafts an organizational chart outline and step-by-step workflows for a department from the facts and regulations you provide. Use it when documenting roles, approvals and handoffs.
Produces a complete plan for an online conference, workshop or meeting: concept, agenda, speakers, interaction, tech needs, accessibility and promotion. Use it when you start organizing a remote event.
Turns what you know about a website, tool or process into a handover guide so a newcomer can understand it and use it without you. Use when you are leaving a role, sharing a project or onboarding someone.
Turns logs, alerts and rough notes into a clear network fault report that both technical and non-technical readers can use. Use after an outage, slowdown or recurring connection problem.
Reads a project description and proposes practical implementation approaches, risks and first steps for each module. Use it when a plan lists modules but not how to deliver them.
Drafts a point-by-point appeal for a denied medical claim or prior authorization, maps each denial reason to evidence, and lists missing documents. Use when a denial letter arrives and a deadline is running.
Designs the structure, ownership, page templates, and upkeep routine for a team or company knowledge base so people find answers and content stays current. Use when starting a wiki or help center, or fixing one nobody trusts.
Reviews an AI feature or system for fairness, privacy, transparency, safety, and accountability risks and returns a prioritised mitigation plan. Use before launch or when changing how an AI system makes decisions about people.
