Leads Implementation Guidance
Purpose
Provides CX Sales implementation guidance for the Leads functional area.
When to Use
Use this functional-area skill after Sales scope is confirmed and the project needs leads setup planning, baseline export, import sequencing, or validation checkpoints.
Catalog Metadata
- Pillar:
CX - Offering:
Sales(ORA_MIDSIZE_SALES) - Functional area / Setup Object:
Leads(ORA_LDS_LEADS)
Setup Tasks
- Manage Sales Lead Qualification Template (
MKL_MANAGE_SALES_LEAD_QUALIFICATION_TEMPLATE) - Manage Sales Lead Profile Options (
MKL_MANAGE_SALES_LEAD_PROFILE_OPTIONS) - Manage Sales Lead Standard Lookups (
MKL_MANAGE_SALES_LEAD_STANDARD_LOOKUPS)
Task Routing
- Route Lead qualification-template creation, copying, inventory, review, or deployment-readiness requests to Manage Sales Lead Qualification Template.
- Route any request to list Sales Lead profile options, return current or configured values, review an exact profile-option code, or create, update, set, remove, or delete configured profile-option values to Manage Sales Lead Profile Options. This includes short follow-ups such as "what is the current value?" when the immediately preceding context contains one exact profile-option code. Do not answer these requests from Oracle documentation or delivered defaults.
- Route Sales Lead lookup inventory, code review, or lookup-code create, update, disable, or safe delete to Manage Sales Lead Standard Lookups.
After routing, load and execute the selected nested task skill and its compiled task graph. Do not return a functional-area summary as the terminal response to a task-specific environment request.
Runtime Interface Efficiency
Prefer the declared skill interfaces during routine execution. Treat existing
core and shared utilities as callable implementations: use the owning
SKILL.md contract first and the utility's --help output when invocation
syntax remains unclear. Avoid proactively enumerating implementation scripts,
searching for alternative execution paths, or reading implementation and test
source to rediscover an interface that the selected skills already document.
Load task-local rule sources as their graph nodes become relevant. Load only the
executor declared by the selected child task. Profile-option value CRUD uses
core.fusion-api.apps-common; Sales Lead standard lookup-code CRUD uses the
same core route. Do not load Data Loader or build FSM packages for either task.
Other nested tasks may still declare Data Loader for their own mutations.
Inventory and Review do not need mutation-executor details.
When a declared command fails unexpectedly, rejects documented inputs, or returns an undocumented shape, keep source inspection available as a diagnostic step. Inspect the smallest relevant function or module, use tests only when the framework behavior itself is under diagnosis, record the resolved interface, and reuse it for the remainder of the run instead of rereading the same code.
Nested Sales Lead tasks provide business evidence and documented handoff fields only. Leave authentication, HTTP/loader transport, and executor-specific representations to the owning core skill instead of reconstructing them from source.
Inputs
implementation_objectiveproject_contextleads_scopeleads_requirements
Outputs
functional_area_setup_planconfiguration_guidancevalidation_checkpointsskill_run_recordtoken_usage_record
Implementation Notes
Use the generated nested setup-task skills for task-level planning, sequencing, setup-data routing, and validation. Track token usage for any generated project artifact or skill-run record using the manifest policy.