# Manage Sales Status Setup Task Guidance

> Provides task-specific setup guidance for Manage Sales Status under the Opportunities functional area.

- Skill: `oracle/manage-sales-status-setup-task-guidance` (Agent Skill, multi-file: 7 files)
- Install (CLI): `npx get-skill add oracle/manage-sales-status-setup-task-guidance`
- Raw SKILL.md: https://api.skillmd.com/api/skills/oracle/manage-sales-status-setup-task-guidance/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: Oracle (https://skillmd.com/u/oracle)
- Updated: 2026-11-18
- Page: https://skillmd.com/skills/oracle/manage-sales-status-setup-task-guidance

---


# Manage Sales Status Setup Task Guidance

## FSM Task Identity Policy

Require exact task code/name, selected task `SKILL.md`, target environment, and
immutable archive SHA-256 throughout review, export, package preparation, and
validation.

- Review, export, and package preparation do not require Data Loader task context.
- Every Core Data Loader mutation handoff requires a persisted project
  `TaskContextPath`, exact `TaskName`, and positive `TaskSequence`.
- The selected context entry must resolve to this task's exact skill path,
  `TaskCode`, `TaskName`, offering, and functional area.

The persisted context may be generated from the project's resolved setup-task
plan without creating an Oracle Run Book. Never hand-author, infer, or
synthesize a context entry merely to satisfy Data Loader.

## Purpose

Provides task-specific setup planning, routing, export, import, and validation guidance for `Manage Sales Status` under `Opportunities`.

## Setup Task Skill Contract

- task_code: `MOO_MANAGE_SALES_STATUS`
- task_name: `Manage Sales Status`
- parent_skill_id: `cx.sales.opportunities`
- pillar: `CX`
- offering: `Sales`
- functional_area: `Opportunities`
- functional_area_code: `ORA_MOO_OPPORTUNITIES`
- available_flag: `Y`
- export_import_supported_flag: `Y`
- csv_export_import_supported_flag: `Y`
- dataloader_import_mode: `FSM`
- businessObject: ``
- source_catalog: `knowledge/setup-task-catalog/effective/setupTasksAll.json`

## Usage

Use this skill when planning, sequencing, exporting, importing, or validating setup data for `Manage Sales Status` under `Opportunities`.

## Setup Task Metadata

- Task name: `Manage Sales Status`
- Task code: `MOO_MANAGE_SALES_STATUS`
- Available: `Y`
- Export/import supported: `Y`
- CSV export/import supported: `Y`
- CSV export/import routing: `supported`
- Data Loader import mode: `FSM`
- Business Object: ``

## CSV Export, Import, and Validation Workflow

`CSVExportImportSupportedFlag` is `Y` for this task, so route task setup data work through the relevant skills:

1. Export setup task data with `shared.setup-export.task-level-export`.
2. Validate setup task data with `shared.validation.setup-data-validator`.
3. Validate reference data with `shared.validation.reference-data-validator`.
4. Verify fresh-export and immutable-package readiness with the task-local
   `verify_sales_status_package_readiness` resolver.
5. Hand the validated immutable setup package to `core.data-loader`.

This child skill ends when the exact package, task identity, environment,
proposed delta, validation evidence, path, and SHA-256 are ready for handoff;
A persisted project `TaskContextPath`, exact `TaskName`, and positive
`TaskSequence` are required for every Data Loader mutation handoff and must
resolve to this exact skill/task, offering, and functional area.
It must not create an approval preview, request or accept approval, upload, or
initiate the import. `core.data-loader` invokes Task Hook against the unchanged
package, creates its own immutable preview, stops, and requests a later
standalone user message exactly `approve` before any upload or initiation.
When Data Loader later returns accepted initiation, resume this child graph at
its `accepted_initiation` terminal and end the request. Status, ProcessLog,
results, and live verification require a later explicit user request.

This is the only supported automated route for a setup-data mutation. Use
read-only discovery only to prepare or later verify the package; direct REST
mutation is unsupported for this task.

Use this task metadata when invoking those skills:

- Offering: `Sales`
- Functional area / Setup Object: `Opportunities`
- Setup task name: `Manage Sales Status`
- Setup task code: `MOO_MANAGE_SALES_STATUS`




## Data Loader Failure Handling

`core.data-loader` remains the only import orchestration route. If it returns a
Content ID, import Request ID, or any evidence that upload or initiation may
have been accepted, reconcile that attempt through its status workflow before
any new package is considered. If it fails before acceptance, re-export and
revalidate the package, then hand the new immutable package to Data Loader.
Data Loader must create a new Task Hook preview and request a later standalone
`approve`; this child must not request or reuse approval. Do not bypass the
loader with `shared.setup-import.task-level-import` or `setupTaskCSVImports`.

## Oracle Resource Read Order

1. [ora_input_validation.md](ora-resource/ora_input_validation.md)
2. [ora_dependency_readiness.md](ora-resource/ora_dependency_readiness.md)
3. [ora_reference_lookups.md](ora-resource/ora_reference_lookups.md)
4. [ora_design_enforcement.md](ora-resource/ora_design_enforcement.md)
5. [ora_error_handling.md](ora-resource/ora_error_handling.md)
6. [ora_rule_registry.json](ora-resource/ora_rule_registry.json) for the compiled task-node graph

## Inputs

- `implementation_objective`
- `project_context`
- `setup_task_scope`
- `setup_data_artifacts`

## Outputs

- `setup_task_plan`
- `setup_data_routing`
- `validation_checkpoints`
- `skill_run_record`
- `token_usage_record`

## Implementation Notes

Use the parent functional-area skill `cx.sales.opportunities` for functional-area sequencing and scope decisions. Track token usage for any generated project artifact or skill-run record using the manifest policy.

