Asking for work
Specify an outcome, source, account and limits, then steer the work in the thread.
Say what done looks like
Give OpenTag the outcome and what you will use it for:
Look at churn last quarter. I need a board summary of whether the change is concentrated in one plan, with source links and a chart.
That tells it the scope, audience and deliverable. Add a required method when it matters, such as comparing net revenue rather than gross bookings.
Name the source and account
Specify the app when more than one source could answer the question. With multiple connections, name the intended account or organisation too.
Paste a Slack thread link or attach the file when you mean a particular source. OpenTag can use it only if access is available.
Set limits before it acts
“Draft only”, “don't contact anyone”, and “show me the proposed changes first” help define the job. For an enforced limit on tool writes, configure the connection as Read only where offered.
Not every supported write requires a separate approval card. Read Approvals for the actions that do.
Answer clarifying questions
You
@OpenTag follow up on yesterday's customer calls.
Should I draft customer emails, update the CRM action items, or do both?
Answer in the thread. If you have no preference on a minor choice, say so. Specify the important decisions, such as whether anything should be sent.
Follow up while work is running
You can add detail or correct the scope before the result arrives. Keep related work in the thread so the correction has context. Mention OpenTag when you explicitly need another response.
For a repeated method, create a skill. For a repeating job, create a routine. For a personal preference, say that it should be remembered for you.