rlm-base-dev

Revenue Cloud (RLM) data model reference covering 263 objects across 9 domains. Use when working with Revenue Cloud objects, understanding object relationships, writing SOQL queries, building data plans, or answering questions about the RLM schema. Covers PCM, Pricing, Rates, Configurator, Transactions, DRO, Usage, Billing, and Approvals domains.

SFDMU v5 data plan authoring and review for Revenue Cloud. Use when creating, modifying, or reviewing export.json files, CSV data files, or SFDMU data plans. Covers v5 rules, known bugs, externalId patterns, operation selection, deleteOldData safety, and cross-plan dependencies.

Ground product claims about Salesforce Revenue Cloud (Agentforce Revenue Management) — Billing, Pricing, Quoting, Orders, Contracts, Assets, Usage, DRO — against the captured Salesforce Help portal snapshots at `docs/salesforce/{release}/help/`. Use before authoring or accepting any Trailhead module passage, enablement exercise, internal doc, or SME review response that asserts how a Revenue Cloud feature works. Use when verifying object names, field labels, feature behavior, or terminology against the current release's Help articles. Use when refreshing the snapshot for a new Salesforce release (264 and later) via the `snapshot_{area}_help_{release}` CCI tasks. The snapshot replaces the unwieldy per-release PDF compendiums with grep-friendly, diffable per-article markdown that AI agents can read surgically.

Cross-repo skill manifest pattern connecting Foundations (rlm-base-dev) and PMOS (pmos-revenue-cloud). Use when a skill needs to read content from the other repo (PRDs, demo scripts, capability roadmap, schema, Help articles, scenario reference) without forking or duplicating it. Documents the temporal split (PMOS = future state, Foundations = current state), the resolver, and when each side is canonical.

Author and maintain Revenue Cloud (Agentforce Revenue Management) Hands-On Enablement Exercises per release. Use when updating exercises for a new release (260, 262, …), authoring the journey map index document, indexing release-note features per functional area, or implementing the auto-gen pipeline that produces distribution artifacts. Catalog target lives at docs/enablement/{version}/. Per-release source PDFs and feature indexes live at docs/salesforce/{version}/.

Validate, refresh, and certify the Revenue Cloud ERD against live Salesforce orgs and the Core UDD source. Use when refreshing erd-data.json after a release, certifying a new release upgrade (e.g. 260 → 262), diffing schemas across releases, removing orphan/artifact fields, or investigating whether a field is a real RC platform field vs a custom or other-cloud field.

Run, resume, report, test, or update the local build harness for prepare_rlm_org profiling and the CCI Build Manager TUI. Use when working with scripts/build_harness, .harness run artifacts, harness scenarios, checkpoint resume behavior, TUI scratch org creation, or build-harness tests.

Revenue Cloud Business API reference for RLM v67.0 (Summer '26 / Release 262). Use when working with Revenue Cloud REST APIs, building integrations, writing Apex callouts, or answering questions about RLM API endpoints. Covers PCM, Product Discovery, Configurator, Pricing, Rate Management, Transaction Management, Usage Management, Billing, and Context Service APIs.