Golub Bot
Guides
Thirty practical Bot workflows with copyable prompts, worked examples, and review steps. Start with supplied material, then assess the connections your work needs.
Featured guides
Your first useful Bot workflow: turn notes into an action list
Start with supplied notes, a defined output, and a short review. Build an action list without inventing owners or deadlines.
Prepare a customer meeting brief with evidence and open questions
Build a concise sales meeting brief from approved account material without inventing buyer intent, budget, or commitments.
Build a campaign brief from a real customer problem
Turn approved product facts and audience evidence into a campaign brief with a clear promise, proof, and editorial boundaries.
Prepare an engineering handoff from verified notes
Create a continuation brief with objective, verified state, evidence, unresolved work, and the next action without claiming unrun tests.
Turn scattered design feedback into an actionable review
Group supplied design comments by user problem, evidence, decision, and unresolved question without treating every preference as a requirement.
All guides
Your first useful Bot workflow: turn notes into an action list
Start with supplied notes, a defined output, and a short review. Build an action list without inventing owners or deadlines.
Write a one-page operating brief for your Bot
Give your assistant stable working rules, task boundaries, and a review standard without burying the current job in a long persona.
Build a source pack before asking Bot to research
Prepare an approved source list, a decision question, and a fact-versus-interpretation ledger for a focused research task.
Turn a successful one-off task into a repeatable checklist
Document the inputs, output, stop conditions, and review steps of a working Bot task before considering a schedule.
Draft a support reply from an approved policy
Use a customer message and the relevant policy to prepare a grounded reply, with exceptions and missing information visible.
Triage a small support batch without guessing urgency
Group supplied support messages by issue, evidence, and next action while preserving ambiguity and duplicate reports.
Turn a customer complaint into a reproducible issue brief
Extract the environment, steps, expected behavior, actual behavior, and missing evidence from supplied bug reports.
Find recurring support themes without inventing churn
Cluster a supplied feedback sample by observed issue and evidence, keeping sample limits and customer counts explicit.
Prepare a customer meeting brief with evidence and open questions
Build a concise sales meeting brief from approved account material without inventing buyer intent, budget, or commitments.
Draft a sales follow-up that matches the actual conversation
Prepare a customer recap and next-step email from supplied notes while checking every promise against the source.
Review a proposal for missing scope before sending it
Compare a draft proposal with customer requirements and identify gaps, assumptions, exclusions, and unsupported promises.
Prepare a pipeline review without manufacturing a forecast
Organize supplied deal notes by verified next step, missing evidence, and stale commitments before reviewing revenue expectations.
Build a campaign brief from a real customer problem
Turn approved product facts and audience evidence into a campaign brief with a clear promise, proof, and editorial boundaries.
Build a competitor matrix with comparable claims
Compare selected product sources using consistent criteria and a ledger of published facts, claims, and unknowns.
Write an article brief that answers one reader’s question
Define a reader question, original contribution, evidence, and useful outline before drafting a business article.
Turn campaign data into a report with defensible calculations
Prepare a marketing report from a supplied table while checking denominators, attribution windows, and the difference between observation and cause.
Prepare a document review index for a lawyer
Organize supplied documents into a source-linked review index with dates, parties, missing items, and questions for counsel.
Compare contract versions without turning edits into legal conclusions
Create a clause-linked change table from supplied contract versions, keeping textual differences separate from questions for counsel.
Build a source-linked chronology from a document pack
Arrange explicitly dated events and competing accounts into a reviewable chronology without resolving disputed facts.
Turn customer notes into a problem brief
Create a product problem brief that separates user evidence, proposed solutions, assumptions, and open validation questions.
Draft release notes from verified changes
Prepare reader-focused release notes while preserving rollout limits, known issues, and the difference between merged and available.
Prepare a decision memo with explicit tradeoffs
Compare product options using agreed criteria, evidence, uncertainty, and a reversible next step.
Prepare an engineering handoff from verified notes
Create a continuation brief with objective, verified state, evidence, unresolved work, and the next action without claiming unrun tests.
Organize an incident timeline without jumping to a root cause
Build a timestamped evidence table with observations, hypotheses, actions, and unresolved questions for an incident reviewer.
Turn a feature requirement into reviewable test scenarios
Prepare happy-path, boundary, permission, and recovery scenarios from supplied requirements without claiming test execution.
Prepare an interview brief from a job-relevant rubric
Create structured interview questions and evidence prompts from role requirements while avoiding unsupported candidate inferences.
Organize interview notes into an evidence sheet
Map supplied interview notes to approved criteria while preserving unanswered areas and separating interviewer impressions from evidence.
Rewrite a role description around actual work
Turn a manager’s notes into clear responsibilities, essential requirements, and open questions without adding credentials or employment promises.
Turn scattered design feedback into an actionable review
Group supplied design comments by user problem, evidence, decision, and unresolved question without treating every preference as a requirement.
Write interface copy that matches the real system state
Draft labels, confirmations, and error messages from actual behavior, keeping submitted, pending, completed, and failed states distinct.