Build Agent

Plan with AI. Build with certainty.

From an approved epic, the Build Agent creates a solution plan grounded in industry and Salesforce cloud skills, breaks it into solution tasks, generates the configuration and code, deploys to your sandbox and validates the package so it’s ready for testing.

See a live build workspace See who it helps

Back to Workspace Planning: EPICAutomated Lead Capture ✦ Skills: /sales-cloud · /consumer-goods Session · auto-saved

In scope6 stories · 6 LLS

Lead ManagementAutomated Lead CaptureRelease 1.0

You

Plan the build for Automated Lead Capture. Use standard assignment rules where possible and honour our trigger pattern.

Agent/sales-cloud

Pulled 6 approved stories and their Low-Level Solutions. Architectural Log #3 (one trigger per object) and the Metadata Agent snapshot of Lead (41 fields, 2 existing assignment rules) are in context.

Agent/consumer-goods

Drafted a 5-step plan: extend the Lead model, Region assignment rules with a Flow fallback, dedupe on ABN and trading name, one handler class, then permission set and reporting. Review on the canvas and Execute when ready.

You

Looks right. Execute, then deploy to harbourbrew--uat.

Build ▾Auto ▾+ ContextFiles

Ask the agent…

Automated Lead Capture · Build Plan Draft

Generate Solution

1. Solution plan

Implements six approved stories on Sales Cloud using standard Lead Assignment Rules first, Flow for the fallback path, and a single trigger/handler per Architectural Log #3.

Extend Lead data model

Venue Type, Estimated Monthly Volume and Region picklists with validation rules.

Config

Region-based assignment

Lead Assignment Rules first; Flow fallback routes missing-Region leads to triage queue.

Config

Web-to-Lead and dedupe

Matching and duplicate rules on email and trading name before insert.

Config

LeadAssignmentHandler

Single trigger + handler for cross-object enrichment per Architectural Log #3.

Code

Permission set and reports

Area Lead permission set, lead-source dashboard, Path with stage guidance.

Config

Low-Level Solution · AA-8C81 Region-based assignmentReady

Data model

FieldTypeNotes Region__cPicklist (14)Required when Status = Working Venue_Type__cPicklistBar, Restaurant, Bottle shop, Venue group Estimated_Monthly_Volume__cNumber (kegs)Drives forecast category

Automation

Lead Assignment Rule Region_Routing with 14 entries, evaluated before any Flow.
Record-triggered Flow routes leads with blank Region to the Triage queue and posts to Chatter.
LeadTrigger → LeadAssignmentHandler for partner-code enrichment; bulk-safe, no SOQL in loops.

Implementation tasks6

Create Venue_Type__c, Estimated_Monthly_Volume__c, Region__c on Lead Done

Validation: Region required when Status = Working Done

Lead Assignment Rules by Region (14 entries) Done

Flow: route missing-Region leads to Triage queue Running

LeadAssignmentHandler + LeadTrigger Pending

Area Lead permission set and Lead Source dashboard Pending

Execution trace/sales-cloudrunning
00SKILL/sales-cloud · assignment-rules-first
01readLLS-14 · LLS-15 · Architectural Log #3
02toolmetadata.describe(Lead) → 41 fields
04writeLead.Region__c.field-meta.xml
05writeLead.Venue_Type__c.field-meta.xml
07writeRegion_Routing.assignmentRules-meta.xml (14)
09writeLead_Region_Fallback.flow-meta.xml
12toolapex.generate(LeadAssignmentHandler) · bulk-safe
14thinkinggenerating LeadAssignmentHandlerTest…

Target org

harbourbrew--uat

Sandbox · Connected · API 61.0

Package

Custom fields3

Validation rules1

Flows1

Apex classes / triggers2

Permission sets1

Configuration history

Version 3Success

Version 2Failed

Version 1Success

Deployment · v3Deploying · 4 of 5 components

Validate package against harbourbrew--uat0.8s

Deploy custom fields and validation rule2.1s

Deploy Lead_Region_Fallback flow (active)1.4s

Deploy Apex · run LeadAssignmentHandlerTest12 tests · 96% coverage

Deploy Area_Lead permission setqueued

5/5

components deployed

96%

Apex test coverage

stories ready for testing

80%

less manual configuration

Workbook items and configuration generated from approved Low-Level Solutions.

3×

faster to deployable code

Code Agent writes Apex and LWCs with story, solution and org context attached.

1 click

from solution to sandbox

Plan, generate, deploy and validate an epic without leaving the workspace.

100%

traceable deployments

Configuration History records who deployed what, where and with what result.

Cloud skills

Grounded in Salesforce cloud architecture.

Industry patterns plus product skills for every cloud in scope. No generic configuration, no guessing.

Industry · pick a seat

Sales Cloud lead routing, assignment and Path built the standard way.

Region-based routing as Lead Assignment Rules before any Flow or Apex

Venue Type and volume qualifiers as picklists with validation, not free text

Opportunity Path with stage guidance on both record types

Cloud skills

Sales Cloud

Service Cloud

Experience Cloud

Data 360

Architecture rule applied

“One trigger per object with a handler class; all record-triggered logic ordered in a single Flow orchestration per object.”

What it does

Plan → Solution → Deploy → Validate. One epic at a time.

Plan

Open Plan with AI on an epic. Approved stories, Low-Level Solutions, Architectural Logs and org metadata become a solution plan grounded in cloud architecture best practices.

Solution

The plan breaks down into implementation tasks and workbook items. Execute them to generate metadata, configuration and code as solution files you can review and refine.

Deploy

Connect the sandbox, validate the package and deploy. Individual items, deployment packages or the whole epic, with test runs and coverage reported live.

Validate

Configuration History records every version and outcome. Stories flip to ready for testing and hand off to the Test Agent with test cases already generated.

Traceability

Every deployed component traces back to a requirement.

Theme to Epic to User Story to Low-Level Solution to Workbook Item to Deployment. Architectural Logs and Metadata Agent context carry through automatically.

Theme

Lead Management

Epic

Automated Lead Capture

User Story

AA-8C81

Low-Level Solution

LLS-14

Workbook Item

Lead.Region__c

Deployment

v3 · harbourbrew--uat

Architectural Logs

Approved patterns applied to every generated solution and workbook item.

Metadata Agent context

Generation knows what already exists in the org, so nothing is duplicated.

Configuration History

Version, org, person and outcome for every deployment.

Jira sync

Development status flows to Jira; approvals and deployments stay here.

Who it helps

Built for the people who ship the build.

Four roles, one workspace. Pick a seat.

Consultant / Admin

80%

less time hand-configuring from a workbook

The workbook builds itself, then deploys itself.

Workbook items generated from approved Low-Level Solutions with developer notes

Configuration generated, reviewed and refined in the platform

Deploy individual items or packages to any connected org

Build with certainty

From approved design to a tested, deployed Salesforce build.

Bring one approved epic. We’ll plan it with AI, generate the solution tasks and files, deploy to your sandbox and hand you a package ready for testing.

See a live build workspace

What you get

Workbook items generated from approved Low-Level Solutions

Apex, Triggers and LWCs matched to your existing patterns

Deployment to sandbox with live validation and test coverage

Configuration History for every version and outcome

Stories flip to ready for testing, handed to the Test Agent