◆ Salesforce

Delete triggers or classes from production

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskRemove the 'UpdateOpportunityStage' trigger from the Opportunity object and the…+
Remove the 'UpdateOpportunityStage' trigger from the Opportunity object and the 'OpportunityStageUpdater' Apex class from our production environment by end of day Friday, ensuring no data loss.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I remove these triggers and classes, make sure we understand all their dependencies and…+
Before I remove these triggers and classes, make sure we understand all their dependencies and potential impacts on our sales process. Highlight any automated flows or reports that might break, and suggest a rollback plan if something goes wrong.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI just got an urgent message from Sarah in sales saying a critical automation stopped working…+
I just got an urgent message from Sarah in sales saying a critical automation stopped working after I deployed a new package.
I just got an urgent message from Sarah in sales saying a critical automation stopped working after I deployed a new package. I'm afraid I might have inadvertently disabled a trigger or class that was essential. I don't know which one, or how to quickly diagnose the impact without causing more disruption. What's the fastest way to pinpoint the broken automation and restore it before our Q3 reports are due on Monday?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep breaking existing automations when I deploy new features, leading to frantic calls from…+
I keep breaking existing automations when I deploy new features.
I keep breaking existing automations when I deploy new features, leading to frantic calls from sales and finance. It feels like I'm always guessing what might be impacted. What habit should I change to gain a clearer understanding of existing dependencies before I touch anything, so I stop causing these production outages?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Salesforce's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.