flow

/flow

Work with Salesforce Flows using --new, --review, --refine, or --explain.

Usage

/flow --new         Design a new Flow blueprint from requirements
/flow --review      Review an existing Flow for best practices and issues
/flow --refine      Modify an existing Flow
/flow --explain     Explain what a Flow does step by step

---

--new: Design a New Flow

Gather Requirements

Ask the user:

1. What should the Flow do? (business process description)
2. What type? (Record-Triggered, Screen Flow, Schedule-Triggered, Platform Event-Triggered, Autolaunched)
3. Which object and trigger event? (for Record-Triggered: before/after save, before delete)
4. What records does it access or update?
5. Are there decision branches or conditions?
6. Does it need to call Apex actions or send emails?

Flow Type Selection

Type	Use When
Record-Triggered (Before Save)	Update fields on the same record — no DML cost, runs synchronously
Record-Triggered (After Save)	Related record operations, callouts (via async), email alerts
Screen Flow	Guided user interactions, multi-step wizards
Schedule-Triggered	Batch operations on a schedule (small to medium datasets)
Platform Event-Triggered	React to events published to the event bus
Autolaunched	Called from Apex, other flows, or external (no user interaction)

Flow Design Blueprint

Generate a text-based design document:

## Flow: [Name]
**Type:** Record-Triggered — After Save
**Object:** Account
**Trigger:** Created or Updated

### Entry Criteria
- Run when: Record is created OR Account.Industry changes

### Flow Elements (in execution order)
1. **Decision: Industry Changed?**
   - Outcome YES: {!$Record.Industry} != {!$Record__Prior.Industry}
   - Default: End

2. **Get Records: Active Contacts**
   - Object: Contact
   - Filter: AccountId = {!$Record.Id}, IsActive__c = true
   - Store: contactsCollection (All records)

3. **Loop: For each contact**
   - Collection: contactsCollection
   - Variable: currentContact

   3a. **Update Records: Set Industry**
       - Record: currentContact
       - Field: Industry__c = {!$Record.Industry}

4. **Fault Path: Handle Errors**
   - Create Log_Error__c record with error message

### Variables
| Name | Type | Input/Output | Purpose |
|------|------|--------------|---------|
| contactsCollection | SObject Collection | — | Contacts to update |
| currentContact | SObject | — | Loop variable |

### Governor Limit Considerations
- DML inside loop — CRITICAL issue. Use Collection Update instead of updating inside loop.
  Fix: Collect updates into a collection, then use one Update Records element outside the loop.