release-enablement

Author and maintain Revenue Cloud hands-on enablement exercises per Salesforce release.

Updated Sep 23, 2026
One-click install
npx skills add https://github.com/drgaciw/rlm-base-dev-fork --skill release-enablement-drgaciw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-enablement
Source: https://github.com/drgaciw/rlm-base-dev-fork/tree/main/.cursor/skills/release-enablement
Command: npx skills add https://github.com/drgaciw/rlm-base-dev-fork --skill release-enablement-drgaciw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping Revenue Cloud enablement exercises accurate and consistent across releases is hard: content lives in master files and per-release extracts, sources are scattered across release notes and Help PDFs, and work must resume on any workstation without prior conversation context. This Skill codifies the two-tier authoring model, conventions, and handoff workflow so any agent can produce consistent exercise files. ## Core Features & Use Cases - Two-tier authoring model: Maintain master exercises as the source of truth and derive per-release extracts filtered by version-aware frontmatter (introduced, available, enhanced_in). - Authoring conventions and edge-case patterns: Apply 11 documented patterns covering upgrade guidance, known issues, sub-features, cross-area features, carry-forward markers, scenario threading, and license-scope splits. - Cross-workstation handoff: Re-orient a fresh agent in minutes using a 4-step process and a standard restart prompt template. - Use Case: When Release 264 ships, use this Skill to index new features per functional area, update the master exercises with version metadata, and generate the 264 per-release hands-on extract files anchored to the Infinitech/QuantumBit workshop scenario. ## Quick Start Read the release-enablement SKILL.md and the QB scenario reference, then update the master pricing exercise with the new Release 264 features from the feature index.

Frequently Asked Questions about release-enablement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I author Revenue Cloud enablement exercises for a new Salesforce release?▼

Start from the exercise template, update the per-release feature index from release notes and Solution Overview sources, then add feature sections to the master exercise files with version-aware frontmatter. Per-release extracts are derived from the master, which is the source of truth.

What is the difference between master exercises and per-release extracts?▼

Master exercises in docs/enablement/master/ are the living workshop-format source of truth covering all releases. Per-release extracts in docs/enablement/{version}/ are filtered views scoped to net-new and enhanced features for a specific release, generated from master section frontmatter.

How do I resume enablement work on a different workstation?▼

Follow the 4-step re-orientation: confirm the feature branch, read docs/enablement/README.md, SKILL.md, and the QB scenario reference, then check drafted versus pending files against the coverage matrix. Summarize state to the user before editing anything.

Can I edit enablement files for past releases like 258 or 256?▼

No. Releases 248, 252, 254, 256, and 258 are frozen read-only historical artifacts used only as carry-forward references. Only the current development cycle (264) and forward should be generated or edited.

Why can't I use WebFetch to capture Salesforce release notes?▼

The Salesforce Help portal is a Lightning Web Components SPA that redirects without rendering article content, so WebFetch returns nothing useful. Use Chrome MCP with a recursive shadow-DOM walker to extract the article body after the page renders.

What data sources must exercise walkthroughs use?▼

Walkthroughs must anchor to the QuantumBit scenario: customer accounts from scratch_data (Infinitech, Global Media), products and bundles from datasets/sfdmu/qb/, and constraint models from datasets/constraints/qb/. Never invent customer or product names.