Skip to content
| Marketplace
Sign in
Visual Studio Code>Other>SF ERIO — Elevate Requirements Into OutcomesNew to Visual Studio Code? Get it now.
SF ERIO — Elevate Requirements Into Outcomes

SF ERIO — Elevate Requirements Into Outcomes

Krishan Kumar

|
2 installs
| (0) | Free
Elevate Requirements Into Outcomes — turn a Salesforce user story into Draft Flow, Apex, LWC, or Experience Cloud metadata on your machine.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

SF ERIO

Elevate Requirements Into Outcomes

SF ERIO turns a normal Salesforce user story into Draft metadata you can review, validate, and deploy — Flows, Apex, LWC, and Experience Cloud LWR assets — without starting from a blank Setup screen.

Analysis and generation run on your machine. You stay in control of what gets written and what gets pushed to the org.


What you get

  • Story → design — Objects, fields, Flow vs Apex path, and a checklist as you type
  • Intent Mirrors — Pick the builder shape that matches the story before Generate
  • Draft metadata — Auto-Layout Flows stay Draft (SF ERIO never activates Flows)
  • Apex / LWC / Experience when the story needs them
  • Validate & Deploy — Salesforce CLI dry-run first; deploy only what you check
  • Update existing Flow — Retrieve an Active Flow and merge generated elements
  • History — Recent stories and results for quick reload

Engines

Engine When to use
Rules Default. Spec patterns + bundled trained assist. Fully offline for coding assist.
Local LLM Optional on-device 3B/7B model (one-time download). Spec still writes Flow metadata.
Host AI Optional IDE language model (Cursor / Copilot, etc.) to help refine the story.

Tip: On corporate networks that block Hugging Face, keep Rules — you do not need a Local LLM download to generate.


Requirements

  • Visual Studio Code 1.85 or later (or Cursor)
  • An SFDX / Salesforce DX project folder open as the workspace
  • Salesforce CLI (sf) authenticated to a target org for describe, validate, and deploy

Get started

  1. Open your Salesforce project folder.
  2. Click the SF ERIO icon in the activity bar (opens an editor tab).
  3. Choose a Target org in the header (or Connect / Refresh from Salesforce CLI).
  4. Paste the full user story.
  5. When Intent Mirrors appear, select the shape that fits.
  6. Click Generate and validate.

Files are written under your project’s default package directory. Review Generated components, then Deploy when validation succeeds.

Useful commands

  • SF ERIO: Generate from Selection — selection in the editor
  • SF ERIO: Analyze Selection — design only
  • SF ERIO: Generate from File — explorer context menu on .md / .txt
  • SF ERIO: Connect Org — sf org login web

How generation works

  1. Analyze the story (objects, path, mirrors, mockup).
  2. Generate Draft Flow / Apex / LWC / Experience files locally.
  3. Validate with a check-only deploy against the selected org.
  4. Deploy selected members when you are ready — still as Draft where Salesforce allows.

You can uncheck components so they stay local-only.


Settings (optional)

Setting Purpose
salesforceFlow.targetOrg CLI org alias or username (empty = CLI default)
salesforceFlow.engine local (Rules), localLlm, or ai (Host AI)
salesforceFlow.languageModelId Host AI model id (empty = first available)
salesforceFlow.localLlm.size 3b or 7b for optional Local LLM
salesforceFlow.showRevertButtons Show Revert on Advanced fields

Privacy

  • Rules — story and metadata stay on your PC; no cloud model call for Spec generation.
  • Local LLM — model files download once into extension storage; inference stays local.
  • Host AI — only if you choose it; the story may be sent to the IDE’s language-model provider.
  • Org credentials use Salesforce CLI auth you already manage.

License

MIT

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft