Ask for work

State the outcome. Add the context and limits that affect the work.

A useful request

A request can include four parts:

1. Outcome. State what must be true when the work is complete.
2. Context. Name the repository, document, customer, date range, or system to inspect.
3. Limits. State what your UFO must not change or publish.
4. Checks. State how to check the result.

For example:

Find why workspace invitations fail for addresses outside the company domain. Use the testing environment. Fix the cause, add the test that would have caught it, and open a draft pull request. Do not deploy or merge.

Give it the source material

Attach a file, paste a link, name a connected record, or point to a synced source. State which source is authoritative when two sources can disagree.

If access is missing, ask your UFO to connect the service. Follow the connection steps in its reply. Do not paste secrets into the conversation.

Set limits

State which actions your UFO may take. Set clear limits for work that can affect customers, production, money, or another person.

Diagnose the production alert and give me the evidence. Do not change production.

Update the draft in Notion. Do not send it to the customer.

Ask for evidence

Say how you want UFO to check its work. Examples include a test result, a browser check, a fresh query, a source link, or the result of a change.

Use the same conversation to refine the result:

Make the report shorter. Keep the table and remove the forecast.

Check the pull request again after CI finishes. Fix only failures caused by this branch.

See Recipes for complete requests you can adapt.