Sphere BotResearch, writing and code.
Start with a clear brief.
Sphere Bot brings the conversation, tools and computer work into one workspace on Windows and the web. These sample briefs show how to give a work companion a useful outcome and keep the result easy to review.
Research you can trace back to the source.
A comparison with source links, dates and unanswered questions, ready for your decision.
What to prepare
Use the browser on your Sphere computer. Supply your criteria and starting links; connect a service only if the task needs information from that service.
A brief to adapt
Compare these three project-management tools for a five-person studio. Use their official pricing and help pages. Compare guest access, file storage and export options. Include a source URL and date checked for every claim. Mark anything you cannot verify. Return a comparison table and a short list of questions I should ask before choosing.
Before you use the result
Open the sources yourself. Check that prices, limits and quoted capabilities still match, and that the comparison uses your criteria. Missing evidence should remain visible.
A first draft with the context already attached.
A structured document or message draft you can edit before sharing.
What to prepare
Attach the relevant notes and examples to the conversation. If you need a connected document service, install its connector and authorize the permissions the task needs.
A brief to adapt
Turn the attached meeting notes into a project update for the client. Use the headings Progress, Open questions and Next steps. Keep the tone direct and friendly. Separate confirmed decisions from suggestions. Do not invent dates, commitments or figures. Return a draft here for me to review before anything is sent.
Before you use the result
Check names, commitments, dates and factual claims against the notes. Remove private information the recipient does not need. You decide when the draft is ready to share.
Investigate a change with the evidence beside it.
A proposed code change with an explanation of what was checked and what still needs testing.
What to prepare
Make the project files available on the Sphere computer or through an authorized connector. Use a separate working branch and provide the project’s own instructions.
A brief to adapt
Investigate the scrolling issue described in this report. Read the project instructions and trace the relevant code before changing it. Work on a separate branch. Propose the smallest change that addresses the cause, run the relevant checks and explain any remaining uncertainty. Show the change for review before merging or releasing.
Before you use the result
Read the diff, inspect check output and try the affected behavior. Keep deployment and merge decisions explicit. A passing isolated check does not establish every production scenario.
Make the brief specific.
Include the outcome, source material, constraints and the form you want back. Say which actions need your review. If the task changes, add context in the same conversation so the work stays connected.
Prepare the workspace first.
An account, configured model routing and computer access are required. Available connectors and features depend on your account or team. The web app uses your cloud computer; local Docker and personal Codex access use Windows. These are example workflows, not guaranteed outputs.