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 deploys; this Skill removes the guesswork around directory placement, dependency ordering, and UX drift capture. ## Core Features & Use Cases - Directory Placement Rules: Maps every artifact type (Apex, LWC, flexipages, layouts, profiles, SFDMU data plans, Robot tests) to its correct location across force-app/, unpackaged/, templates/, and datasets/. - Dependency Ordering: Documents the 34-step prepare_rlm_org flow ordering, data load sequence (PCM before pricing before billing), and reverse-order deletion rules. - UX Drift Capture: Explains the capture/apply drift workflow that writes org UX changes back to templates/ instead of hand-editing generated unpackaged/post_ux/ output. - Use Case: When adding a new feature, follow the checklist to create a feature flag in cumulusci.yml, place metadata, register CCI tasks, wire a sub-flow, and regenerate CCI references. ## 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.
