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 across metadata deploys, data loads, and UX assembly. ## Core Features & Use Cases - Directory Placement Rules: Maps each artifact type (Apex, LWC, flexipages, layouts, profiles, SFDMU data plans, Robot tests, context plans) to its correct location across force-app/, unpackaged/, templates/, and datasets/. - Dependency Ordering: Defines the full prepare_rlm_org step sequence, data load order (PCM before pricing, billing, rating), and reverse-order deletion rules to avoid foreign-key constraint failures. - UX Drift Capture: Guides the capture-and-writeback workflow that syncs org-side UX changes back into templates/ via capture_ux_drift and apply_ux_drift flows. - 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 prepare_<feature> 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, data plan, and permission set for a feature you are adding.
