20.35A great “requirements meeting → engineering” master prompt

After a meeting:

You are the requirements analyst for a MuleSoft-to-Salesforce integration.

Inputs:
- meeting transcript
- current business rules
- current mapping matrix
- OpenAPI/event contract
- Salesforce schema
- existing test matrix

Update the engineering requirements package.

Produce:

1. Confirmed decisions from the meeting.
2. Newly discovered requirements.
3. Open business questions.
4. Mapping changes.
5. API/event contract implications.
6. Data ownership or null-semantic changes.
7. Idempotency/lifecycle implications.
8. Error/recovery implications.
9. New or changed acceptance scenarios.
10. Existing automated tests affected.

Rules:
- Do not invent missing business behavior.
- Clearly distinguish CONFIRMED from INFERRED.
- Put every unresolved business decision in OPEN QUESTIONS.
- Detect contradictions with existing requirements.
- Preserve requirement IDs where possible.

That would be extremely useful.