Reports, procedures, meeting notes and planning. 44 reviewed prompts for operations.
Scores a list of feature requests or tasks against value, effort and risk, then selects what fits a short cycle and explains what was cut. Use it for sprint planning or when requests exceed capacity.
Diagnoses a slow, costly or error-prone business process and returns root causes, prioritised fixes, a 30/60/90-day plan and the metrics to track. Use it when a workflow is hurting cost, quality or speed.
Turns a feature idea, user evidence and constraints into a buildable requirements document with goals, stories, risks and a rollout plan. Use before design or engineering work starts.
Interviews you briefly about skills, interests and constraints, then shapes three or four realistic business ideas and a one-page plan for the best one. Use it when you want to start something but lack a concrete idea.
Creates a one-week launch checklist and 30-day plan for a print-on-demand online shop, covering niche, products, listings and first sales. Use it when starting a small online shop.
Helps you decide whether a household problem is a safe do-it-yourself fix, a job for a professional, or an emergency, then gives a step list. Use it before starting any repair.
Designs a time-boxed retrospective from your sprint notes, with an agenda, discussion questions, a way to spot recurring problems and a template for owned action items. Use before your next retro.
Diagnoses why a project is late, over budget, or stuck and produces a recovery plan with options, a re-baselined timeline, governance, team support, and a stakeholder message. Use when a project needs a credible reset.
Writes a short, engaging script to raise safety awareness among workers for a campaign, toolbox talk or safety week. Use when you must brief a shop floor team in plain language.
Builds a program charter and execution plan for a multi-team technical initiative: scope, milestones, dependencies, risks, decision rights, and status cadence. Use when kicking off or re-planning a large engineering program.
Plans a digital health or clinical IT project, from workflow and stakeholder analysis to data needs, privacy, patient safety checks, rollout, and success measures. Use when introducing a clinical tool, integration, or AI feature in a care setting.
Interviews you about a recurring task, then rates how well an AI assistant could support or automate it, with risks and a pilot plan. Use it before investing time in automating a workflow.
