What problem does it solve? Adding new features to a Salesforce Revenue Cloud repository requires knowing exactly where each artifact belongs and in what order it must deploy. This Skill removes the guesswork by mapping every artifact type to its correct directory and enforcing dependency ordering rules. ## Core Features & Use Cases - Directory Placement Rules: Maps metadata, data plans, Apex scripts, Robot tests, and UX templates to their correct repository locations such as force-app/, unpackaged/post_*/, and templates/. - Dependency Ordering: Defines deploy and data-load sequences, including the 34-step prepare_rlm_org flow and reverse-order deletion rules. - UX Drift Capture: Guides capture and writeback of org UX changes into templates using capture_ux_drift and apply_ux_drift flows. - Use Case: When adding a new feature, follow the checklist to create a feature flag, place metadata, register CCI tasks, build a data plan, and wire a sub-flow into prepare_rlm_org. ## Quick Start Ask the agent to read the repo-integration skill and tell you where to place a new flexipage and its data plan for a new Revenue Cloud feature.
