Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →toddkasper/salesforce-business-analyst
Salesforce business-analysis work — eliciting and documenting requirements, writing and sizing user stories (INVEST, Given/When/Then, MoSCoW), facilitating stakeholder workshops and discovery, mapping current/future-state processes (swimlanes, RACI, RAID), defect triage, and running user acceptance testing to a go/no-go decision.
Passed 20 of 22 test cases with the skill, and 19 of 22 without it.
1 fixed19 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
A test case the skill fixed. Same model, same prompt, with and without the skill.
Write the Apex trigger code and developer unit test class for an after insert trigger on Opportunity that creates a Task record when the Stage is set to 'Closed Won'.
| Checked | Without skill | With skill |
|---|---|---|
| Explain that writing Apex triggers and developer tests is a developer task outside the BA scope. | Missed | Passed |
The instructions your model reads when the skill loads.
Operational playbook for the Salesforce BA discipline. Credential background, study path, and skill orientation: references/study-resources.md.
Load this skill when… eliciting or documenting requirements for a Salesforce project; writing or reviewing user stories and acceptance criteria; facilitating a discovery or UAT session; mapping as-is/to-be processes including automation implications. Not this skill: building the declarative config (fields, flows, layouts) → see
salesforce-administrator; writing Apex, LWC, or integration code → seesalesforce-platform-developer-1/salesforce-platform-developer-2.
Deeper context: Study resources live in references/study-resources.md (loaded on demand). For org-specific applications of these rules, see a per-org appendix you maintain in your own project, referenced from a CLAUDE.md. For NPSP/nonprofit-specific guidance, see salesforce-nonprofit-cloud-consultant.
Verify steps assume nothing about your tooling — use your project's Salesforce MCP connection, the Salesforce CLI (
sf), or the Salesforce setup UI, in that order of preference.
Credential logistics and study path: see references/study-resources.md.
[volatile — verify live] items include: BA-201 blueprint topic weights and question counts, specific org edition/license feature availability, and managed-package automation behavior (NPSP, Nonprofit Cloud) across package versions.[volatile — verify live] or [opinion — house style].Volatile tag index: The specific items tagged
[volatile — verify live]in this skill (blueprint weights, NPSP package behavior) are annotated in references/study-resources.md — load that file when verifying exam logistics or planning a study pass.
Map stakeholders before the first workshop, not after. Build a power/interest grid: high-power/high-interest = manage closely (project lead, executive board); high-power/low-interest = keep satisfied (executive sponsor); low-power/high-interest = keep informed (end users whose daily work changes); low-power/low-interest = monitor. Decision rule: the person who can say "no, ship it differently" is a primary stakeholder and must sign off; everyone else is consulted or informed.
Use a RACI matrix to kill the "who decides?" ambiguity. Exactly one Accountable per decision. If two people are Accountable for the same decision, that is a red flag — escalate to make it one. Responsible can be many; Consulted before; Informed after.
Pick the elicitation method to fit the source, not your habit:
| Situation | Method | Why |
|---|
test cases passed, vs 19 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.