Sales Orchestration Question Routing and Implementation Guidance
Purpose
Answer and route source-backed questions about the CX Sales Orchestration
functional area, and provide functional-area implementation guidance without
bypassing the nested task skills' execution boundaries.
When to Use
Use this functional-area skill for a Sales Orchestration overview, a comparison
or dependency spanning tasks, task selection, setup sequencing, support-boundary
questions, or functional-area implementation planning. Route a question owned
by one task to that task's nested skill.
General Question Router
Read references/sales-orchestration-question-routing.md before answering a
general, ambiguous, cross-task, support, or help-source question.
- Classify the request by subject and question class before loading API or
authentication resources.
- For a functional-area definition, business-value, capability, or trust and
security question, read
references/sales-orchestration-overview.md.
For a question such as "What is Sales Orchestration?", give the complete
agentic seller-experience definition and its seller outcomes and capabilities;
do not reduce the answer to Sales Motions, Sales Plays, and Data Capture.
- Select
EXPLAIN, READ, CLARIFY, ROUTE, GAP, or REFUSE as the
answer mode.
- Route single-task questions to the owning nested skill.
- For a multi-task question, obtain a source-backed result from each relevant
task skill and synthesize only the supported facts.
- Return
SOURCE_GAP for behavior that the approved task sources do not
establish. Identify the exact missing Oracle source or SME decision; do not
invent a product rule.
- Do not authenticate, call Fusion, refresh OAuth, or create a project artifact
for an explanation-only question.
Task Routing
| Subject |
Nested skill |
| Sales Motion, objective, or high-value activity |
cx.sales.sales-orchestration.sales-motions |
| Sales Play, content bundle or packet, content artifact, or Sales Play Content Intelligence |
cx.sales.sales-orchestration.sales-plays-and-content |
| Data Capture Rule or rule attribute |
cx.sales.sales-orchestration.data-capture-rules |
| Explicit Sales Orchestration Pre-requisites setup task |
cx.sales.sales-orchestration.pre-requisites |
Ask one short clarification when a term such as "content" or "data" could map
to more than one task and that choice changes the answer.
Cross-Task and Support Questions
- Use the parent skill to explain the catalog hierarchy, task ownership,
sequence, dependencies, and differences between tasks.
- Use the selected child skill for concepts, metadata, lifecycle, setup,
security, endpoints, live reads, troubleshooting, and help sources specific
to one task.
- Preserve each child's read-only execution boundary. The parent must not
generate a mutation blueprint, call a direct BOSS endpoint, select a browser,
or substitute another loader for an unsupported task operation.
- Data Loader does not currently support the applicable BOSS REST endpoints.
Create, Update, and Delete may be added only after that support and the
repository's write contracts are reviewed.
Execution Safety
Preflight
Before producing a durable plan, configuration blueprint, or validation result,
confirm the requested answer mode, question classification, owning task skill,
and project workspace path. For any child-skill live-read request, the selected
child workflow must additionally confirm the target environment, acting-user
context, required privileges, and bounded read inputs before authentication or
an external call. This parent skill has no direct Fusion, browser, OAuth, or
configuration-mutation path.
Failure Handling
Classify an unclear question or missing supported source as SOURCE_GAP and
state the exact Oracle source or SME decision required. Stop on an ambiguous
task classification until it is clarified. For a selected child workflow,
preserve that child's failure classification, retry limits, and sanitized
diagnostics; do not retry, broaden a query, substitute an endpoint, or bypass
an unsupported operation. When a durable artifact is in scope, record only the
safe status, failure class, recommended action, target environment identifier,
and artifact reference under the selected project workspace.
Redaction
Never request, display, log, or persist passwords, OAuth tokens, client
secrets, private keys, token-cache contents, full authorization headers, or
sensitive customer data. Configuration guidance may identify a setting or
whether a value is present, but must not copy secret values into an answer,
diagnostic, or project artifact.
Catalog Metadata
- Pillar:
CX
- Offering:
Sales (ORA_MIDSIZE_SALES)
- Functional area / Setup Object:
Sales Orchestration (CUSTOM_SALES_ORCHESTRATION)
Setup Tasks
- Sales Motions (
CUSTOM_SALES_MOTIONS)
- Sales Plays and Content (
CUSTOM_SALES_PLAYS_AND_CONTENT)
- Data Capture Rules (
CUSTOM_DATA_CAPTURE_RULES)
- Pre-requisites (
CUSTOM_PRE_REQUISITES): baseline
readiness plus first-time validation of signals, Microsoft Outlook and email
integration, and Dispatcher routing.
Inputs
implementation_objective
project_context
sales_orchestration_scope
sales_orchestration_requirements
sales_orchestration_question
requested_answer_mode: EXPLAIN, READ, CLARIFY, ROUTE, GAP, or REFUSE
Outputs
question_classification
sourced_answer
operation_support_status
source_gap
functional_area_setup_plan
configuration_guidance
validation_checkpoints
skill_run_record
token_usage_record
Implementation Notes
Use the generated nested setup-task skills for task-level questions, planning,
sequencing, setup-data routing, and validation. Track token usage for any
generated project artifact or skill-run record using the manifest policy. Do
not persist an answer-only response unless the active project workflow requires
a durable artifact.
Help Source
- Functional-area definition, business value, capabilities, and trust model:
references/sales-orchestration-overview.md
- Cross-task question classification and response contract:
references/sales-orchestration-question-routing.md
- First-time environment readiness validation:
pre-requisites/references/sales-orchestration-prerequisites.md
1---2skill_id: "cx.sales.sales-orchestration"3name: sales-orchestration-question-routing-and-implementation-guid4description: "Answers and routes source-backed questions about the CX Sales Orchestration functional area and its Sales Motions, Sales Plays and Content, Data Capture Rules, and Pre-requisites tasks. Use for functional-area concepts, first-time readiness validation, task comparisons, setup sequencing, dependencies, security, object metadata, lifecycle, API capabilities, troubleshooting, import/export or mutation support, help sources, and implementation planning; classify task-level requests before routing them to a nested skill and never use the parent to bypass a child skill's execution boundary."5layer: "pillar"6pillar: "CX"7offering: "Sales"8functional_area: "Sales Orchestration"9functional_area_code: "CUSTOM_SALES_ORCHESTRATION"10type: "planning"11execution_mode: "assisted"12owner_team: "CX sales pillar team"13version: "0.5.1"14inputs:15 - "implementation_objective"16 - "project_context"17 - "sales_orchestration_scope"18 - "sales_orchestration_requirements"19 - "sales_orchestration_question"20 - "requested_answer_mode"21outputs:22 - "question_classification"23 - "sourced_answer"24 - "operation_support_status"25 - "source_gap"26 - "functional_area_setup_plan"27 - "configuration_guidance"28 - "validation_checkpoints"29 - "skill_run_record"30 - "token_usage_record"31depends_on:32 - "shared.implementation-planning.offering-task-map-builder"33 - "shared.implementation-planning.task-dependency-resolver"34 - "shared.setup-export.functional-area-export"35uses_core:36 - "core.project-mgmt.artifact-version-manager"37 - "core.project-mgmt.artifact-registry-manager"38 - "core.project-mgmt.project-state-manager"39 - "core.diagnostics.role-access-check"40persists_project_state: true41token_usage_tracking:42 enabled: true43 granularity: "per_skill_run"44 artifact_type: "token_usage_record"45 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"46 estimation_method: "chars/4 estimate unless exact tokenizer or API accounting is available"47 required_fields:48 - "activity_start_time"49 - "skill_id"50 - "task"51 - "trigger"52 - "artifacts_written"53 - "files_read"54 - "estimated_input_tokens"55 - "estimated_output_tokens"56 - "estimated_total_tokens"57 - "estimation_method"58 - "notes"59state_updates:60 - "setup_task_sequence"61 - "design_decisions"62 - "configuration_blueprints"63 - "validation_results"64 - "token_usage_records"65workspace_outputs:66 - artifact_type: "setup_task_sequence"67 default_location: "project/{project_id}/artifacts/pillars/cx/sales/sales-orchestration/current/"68 versioning_policy: "major-new-version-minor-confirm-update"69 - artifact_type: "configuration_blueprint"70 default_location: "project/{project_id}/artifacts/pillars/cx/sales/sales-orchestration/current/"71 versioning_policy: "major-new-version-minor-confirm-update"72 - artifact_type: "design_decision"73 default_location: "project/{project_id}/decisions/"74 versioning_policy: "append-only"75 - artifact_type: "validation_result"76 default_location: "project/{project_id}/artifacts/pillars/cx/sales/sales-orchestration/current/"77 versioning_policy: "major-new-version-minor-confirm-update"78 - artifact_type: "skill_run"79 default_location: "project/{project_id}/state/runs/"80 versioning_policy: "append-only"81 - artifact_type: "token_usage_record"82 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"83 versioning_policy: "append-only"84required_setup_tasks:85 - "CUSTOM_SALES_MOTIONS"86 - "CUSTOM_SALES_PLAYS_AND_CONTENT"87 - "CUSTOM_DATA_CAPTURE_RULES"88 - "CUSTOM_PRE_REQUISITES"89applicability:90 industries:91 - "All"92 countries:93 - "All"94 fusion_releases:95 - "Current Oracle Fusion Cloud release"96side_effects: []97required_privileges: []98metadata:99 source: https://skillmd.com/skills/oracle/sales-orchestration-question-routing-and-implementation-guid100---101102# Sales Orchestration Question Routing and Implementation Guidance103104## Purpose105106Answer and route source-backed questions about the CX Sales Orchestration107functional area, and provide functional-area implementation guidance without108bypassing the nested task skills' execution boundaries.109110## When to Use111112Use this functional-area skill for a Sales Orchestration overview, a comparison113or dependency spanning tasks, task selection, setup sequencing, support-boundary114questions, or functional-area implementation planning. Route a question owned115by one task to that task's nested skill.116117## General Question Router118119Read `references/sales-orchestration-question-routing.md` before answering a120general, ambiguous, cross-task, support, or help-source question.1211221. Classify the request by subject and question class before loading API or123 authentication resources.1242. For a functional-area definition, business-value, capability, or trust and125 security question, read `references/sales-orchestration-overview.md`.126 For a question such as "What is Sales Orchestration?", give the complete127 agentic seller-experience definition and its seller outcomes and capabilities;128 do not reduce the answer to Sales Motions, Sales Plays, and Data Capture.1293. Select `EXPLAIN`, `READ`, `CLARIFY`, `ROUTE`, `GAP`, or `REFUSE` as the130 answer mode.1314. Route single-task questions to the owning nested skill.1325. For a multi-task question, obtain a source-backed result from each relevant133 task skill and synthesize only the supported facts.1346. Return `SOURCE_GAP` for behavior that the approved task sources do not135 establish. Identify the exact missing Oracle source or SME decision; do not136 invent a product rule.1377. Do not authenticate, call Fusion, refresh OAuth, or create a project artifact138 for an explanation-only question.139140## Task Routing141142| Subject | Nested skill |143|---|---|144| Sales Motion, objective, or high-value activity | `cx.sales.sales-orchestration.sales-motions` |145| Sales Play, content bundle or packet, content artifact, or Sales Play Content Intelligence | `cx.sales.sales-orchestration.sales-plays-and-content` |146| Data Capture Rule or rule attribute | `cx.sales.sales-orchestration.data-capture-rules` |147| Explicit Sales Orchestration Pre-requisites setup task | `cx.sales.sales-orchestration.pre-requisites` |148149Ask one short clarification when a term such as "content" or "data" could map150to more than one task and that choice changes the answer.151152## Cross-Task and Support Questions153154- Use the parent skill to explain the catalog hierarchy, task ownership,155 sequence, dependencies, and differences between tasks.156- Use the selected child skill for concepts, metadata, lifecycle, setup,157 security, endpoints, live reads, troubleshooting, and help sources specific158 to one task.159- Preserve each child's read-only execution boundary. The parent must not160 generate a mutation blueprint, call a direct BOSS endpoint, select a browser,161 or substitute another loader for an unsupported task operation.162- Data Loader does not currently support the applicable BOSS REST endpoints.163 Create, Update, and Delete may be added only after that support and the164 repository's write contracts are reviewed.165166## Execution Safety167168### Preflight169170Before producing a durable plan, configuration blueprint, or validation result,171confirm the requested answer mode, question classification, owning task skill,172and project workspace path. For any child-skill live-read request, the selected173child workflow must additionally confirm the target environment, acting-user174context, required privileges, and bounded read inputs before authentication or175an external call. This parent skill has no direct Fusion, browser, OAuth, or176configuration-mutation path.177178### Failure Handling179180Classify an unclear question or missing supported source as `SOURCE_GAP` and181state the exact Oracle source or SME decision required. Stop on an ambiguous182task classification until it is clarified. For a selected child workflow,183preserve that child's failure classification, retry limits, and sanitized184diagnostics; do not retry, broaden a query, substitute an endpoint, or bypass185an unsupported operation. When a durable artifact is in scope, record only the186safe status, failure class, recommended action, target environment identifier,187and artifact reference under the selected project workspace.188189### Redaction190191Never request, display, log, or persist passwords, OAuth tokens, client192secrets, private keys, token-cache contents, full authorization headers, or193sensitive customer data. Configuration guidance may identify a setting or194whether a value is present, but must not copy secret values into an answer,195diagnostic, or project artifact.196197## Catalog Metadata198199- Pillar: `CX`200- Offering: `Sales` (`ORA_MIDSIZE_SALES`)201- Functional area / Setup Object: `Sales Orchestration` (`CUSTOM_SALES_ORCHESTRATION`)202203## Setup Tasks2042051. [Sales Motions](sales-motions/SKILL.md) (`CUSTOM_SALES_MOTIONS`)2062. [Sales Plays and Content](sales-plays-and-content/SKILL.md) (`CUSTOM_SALES_PLAYS_AND_CONTENT`)2073. [Data Capture Rules](data-capture-rules/SKILL.md) (`CUSTOM_DATA_CAPTURE_RULES`)2084. [Pre-requisites](pre-requisites/SKILL.md) (`CUSTOM_PRE_REQUISITES`): baseline209 readiness plus first-time validation of signals, Microsoft Outlook and email210 integration, and Dispatcher routing.211212## Inputs213214- `implementation_objective`215- `project_context`216- `sales_orchestration_scope`217- `sales_orchestration_requirements`218- `sales_orchestration_question`219- `requested_answer_mode`: EXPLAIN, READ, CLARIFY, ROUTE, GAP, or REFUSE220221## Outputs222223- `question_classification`224- `sourced_answer`225- `operation_support_status`226- `source_gap`227- `functional_area_setup_plan`228- `configuration_guidance`229- `validation_checkpoints`230- `skill_run_record`231- `token_usage_record`232233## Implementation Notes234235Use the generated nested setup-task skills for task-level questions, planning,236sequencing, setup-data routing, and validation. Track token usage for any237generated project artifact or skill-run record using the manifest policy. Do238not persist an answer-only response unless the active project workflow requires239a durable artifact.240241## Help Source242243- Functional-area definition, business value, capabilities, and trust model:244 `references/sales-orchestration-overview.md`245- Cross-task question classification and response contract:246 `references/sales-orchestration-question-routing.md`247- First-time environment readiness validation:248 `pre-requisites/references/sales-orchestration-prerequisites.md`