BookatlasTwo-Day MuleSoft → Salesforce Bootcamp
17 / 18 · Module 20 — AI-Assisted Requirements, Development, and Testing · filtered: cheatsheet← prev⊞ allnext →

20.36And the implementation master prompt

Once approved:

Implement only the CONFIRMED requirements in this change.

Before coding:
1. List the BR-* requirements being implemented.
2. Identify affected mappings, flows, Salesforce fields and tests.
3. Flag unresolved requirements that block implementation.

During implementation:
- preserve documented null/omission semantics.
- preserve field ownership boundaries.
- use documented stable keys.
- evaluate every retry for idempotency.
- avoid N+1 Salesforce calls.
- never introduce undocumented business behavior.

After implementation:
1. Run targeted MUnit tests.
2. Run affected integration tests.
3. Review changes against the mapping matrix.
4. Perform regression impact analysis.
5. Report remaining risks and untested infrastructure assumptions.

That is the kind of prompt I would genuinely use with Claude Code/Codex.