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 resume on any workstation without prior conversation context. ## Core Features & Use Cases - Two-Tier Authoring Model: Maintain master exercises as the source of truth in docs/enablement/master/ and derive per-release extracts (260, 262, 264) filtered by version-aware section frontmatter (introduced, available, enhanced_in). - Release Source Inventory: Index per-release features from Solution Overview decks, master Help PDFs, and release notes captured from the Salesforce Help SPA via Chrome MCP shadow-DOM extraction. - Authoring Conventions: Apply 11 codified patterns covering upgrade guidance, known issues, sub-features, cross-area features, carry-forward markers, scenario threading, and license-scope splits. - Use Case: When release 264 enters development, read the feature index at docs/salesforce/264/feature-index.md, update the master exercises with new sections anchored to the Infinitech/QuantumBit workshop scenario, and generate the 264 per-release extract set. ## Quick Start Read the release-enablement SKILL.md, the QB scenario reference, and the current release feature index, then draft the next pending master exercise for the 264 release.
