Salesforce
Requirements, specs, Flow logic, and documentation. The parts of the job that happen before anything touches the org.
-
Documenting a validation rule so the next person understands it
The formula says what a validation rule blocks. It doesn't say why. Here's how to turn it into a description someone can act on without opening the builder.
-
Explaining CPQ logic in plain language
A CPQ price rule is unreadable to anyone who didn't build it. Here's how to get it translated for a non-technical approver, and what to verify before trusting the translation.
-
Reviewing SOQL for readability and risk before it ships
A query that runs fine on ten test records can lock up at scale. A checklist for having AI review SOQL for risk, and where to double-check it yourself.
-
Turning business requirements into Salesforce stories
A requirements doc and a story a developer can actually build from are different documents. Here's how to get from one to the other without losing the original ask.
-
Writing a Flow description AI can actually follow
AI can't open your Flow. Here's a plain-text way to describe one that's specific enough to actually get help with it.
-
The spec interrogation prompt
The paste-ready scaffold and interrogation prompt, pulled out of the playbook.