An end-to-end delivery workflow for Salesforce work, covering idea generation when needed, planning, research, implementation, review, feedback fixes, testing, and optional deployment. It coordinates the separate stages into one process.

Use it when you want the complete Salesforce development process handled for a feature, from deciding what to build through implementation, review, testing, and possible deployment.

It gives a Salesforce feature a path from an initial idea to verified delivery instead of leaving planning, coding, review, and testing disconnected. Each stage adds checks for quality and correctness before the work is shipped.

sf-lfg — Skill for Claude Code by divingsbysangam

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/divingsbysangam/salesforce-compound-engineering-plugin

agentmods

npx agentmods add skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-lfg

Made for: Claude Code.

Or install sf-compound-engineering, the plugin that ships this one along with the rest of its 68 skills, 1 hook, 2 MCP servers.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-lfg/github.svg)](https://agentmods.dev/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-lfg)

Your own site

<a href="https://agentmods.dev/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-lfg"><img src="https://agentmods.dev/badge/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-lfg/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-lfg"><img src="https://agentmods.dev/badge/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-lfg.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 115 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,531 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00115	$0.01531
Opus 5	$0.00057	$0.00766
Sonnet 5	$0.00023	$0.00306
Haiku 4.5	$0.00012	$0.00153

Measured 9d ago against content hash 7ccd57231dbe, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

sf-lfg scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/sf-lfg/SKILL.md · 102 lines

How it starts

The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/sf-lfg

Persona dispatch. This pipeline dispatches personas as isolated subagents — see the dispatching-parallel-personas skill for the mechanics (isolated subagents, same-response parallelism, same-file-conflict check). The PLAN stage delegates to /sf-plan and the REVIEW stage to /sf-review, which own their personas (research → ../sf-plan/references/personas/, review → ../sf-review/references/personas/).

Principles enforced: all seven, but especially 1 (preserve the quality ceiling) and 2 (verifiability). See PRINCIPLES.md.

Required reads

Procedure lives in sibling files, not only in this orchestrator:

Stage 0: IDEATE & BRAINSTORM (the front "bread" — human-led, conditional) — read references/stage-0-ideate-brainstorm-the-front-bread-human-led-conditional.md before acting on this section.
Stage 1: PLAN — read references/stage-1-plan.md before acting on this section.
Stage 2: DEEPEN — read references/stage-2-deepen.md before acting on this section.
Stage 3: WORK — read references/stage-3-work.md before acting on this section.
Stage 3.5: VERIFY (independent) — read references/stage-3-5-verify-independent.md before acting on this section.
Stage 4: REVIEW — read references/stage-4-review.md before acting on this section.
Stage 5: RESOLVE — read references/stage-5-resolve.md before acting on this section.
Stage 6: POLISH (the back "bread" — conditional, UI surfaces only) — read references/stage-6-polish-the-back-bread-conditional-ui-surfaces-only.md before acting on this section.
Stage 7: TEST — read references/stage-7-test.md before acting on this section.
Stage 8: DEPLOY (conditional) — read references/stage-8-deploy-conditional.md before acting on this section.
Stage 9: COMPOUND — read references/stage-9-compound.md before acting on this section.
Output — read references/output.md before acting on this section.

Copy-paste-to-agent

Run the full Salesforce delivery pipeline: ideate (if needed) → brainstorm (if needed) → plan →
deepen → work → review → resolve → polish (if UI surface) → test → deploy. Each stage has a gate.
Ideate and polish are the human "bread" (Principle 5 — taste over typing); the middle is the
AI loop. Aborts on Critical/High security findings, governor regressions, missing Verification
Strategy, repeated test failures, WCAG A/AA violations on changed UI, or deploy-validation
failures. Honors $ARGUMENTS.deploy = scratch | sandbox | none.

Read the full file on GitHub · 102 lines

Files

What ships with it

12 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

9d ago First seen · 102 lines · 115 tokens per session scan A 7ccd57231dbe

Subscribe to this mod's changes

sf-lfg is a skill published in the GitHub repository divingsbysangam/salesforce-compound-engineering-plugin (10 stars, last pushed 5d ago), licensed MIT. It adds 115 tokens to every session and 1,531 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Project management

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens