What problem does it solve? Automating a Salesforce Revenue Cloud environment requires orchestrating hundreds of CumulusCI tasks, flows, feature flags, and org aliases, where mistakes like mixing CCI and SF CLI aliases or misplacing when: guards cause silent failures and broken builds. ## Core Features & Use Cases - CCI CLI and org identity guidance: Explains task, flow, and org commands plus the critical distinction between CCI aliases (beta) and SF CLI aliases (rlm-base__beta) to prevent "org not found" errors. - Project configuration reference: Documents the cumulusci.yml structure with ~197 tasks, 41+ flows, 36 feature flags, and the 34-step prepare_rlm_org build sequence. - Custom task authoring patterns: Provides base class selection rules (BaseTask, SFDXBaseTask, SFDXOrgTask), the salesforce_task flag pitfall, REST API patterns, and Robot Framework wrapper conventions. - Use Case: You need to add a new data-load step to the org build. The skill tells you to register the task in cumulusci.yml with group: and description:, gate it with a when: clause on the task step (never on a flow step), then regenerate the reference docs with python scripts/ai/generate_cci_reference.py. ## Quick Start Ask the agent to read the cci-orchestration skill and explain how to run the prepare_rlm_org flow against the beta org with the billing feature flag disabled.
