What problem does it solve? Keeping Revenue Cloud (Agentforce Revenue Management) hands-on enablement exercises accurate and consistent across releases is hard: content lives in master exercises and per-release extracts, sources are scattered across Help PDFs and release notes, and work must hand off cleanly between workstations. This Skill codifies the two-tier authoring model, conventions, and workflows so any agent can produce or update the catalog without losing coherence. ## Core Features & Use Cases - Two-tier authoring model: Maintain master exercises in docs/enablement/master/ as the source of truth and derive per-release extracts (e.g., 260, 262, 264) filtered by version-aware section frontmatter (introduced, available, enhanced_in). - Authoring conventions and edge-case patterns: Eleven documented patterns covering upgrade guidance, known issues, sub-features, cross-area features, carry-forward markers, scenario threading, and license-scope splits. - Cross-workstation handoff: A resume guide with a 4-step re-orientation, tool grants checklist, and restart prompt template so a fresh agent picks up mid-cycle work in minutes. - Use Case: When release 264 enters development, use this Skill to update the feature index, author new master sections anchored to the Infinitech/QuantumBit workshop scenario, and generate the 264 per-release extract files. ## Quick Start Read the release-enablement SKILL.md and the QB scenario reference, then update the 264 feature index and draft the next master exercise for the current release.
