Salesforce Capabilities Strategy

Salesforce Capabilities Strategy

This skill owns the reasoning and design logic. Do not duplicate capability catalog content here.

Required Dependency

Before generating any map, taxonomy, or phase plan:

1. Load salesforce-capabilities-catalog.
2. Reuse its canonical domains, acronyms, and names.
3. Keep this skill focused on transformation logic, sequencing, and narrative.

Primary Use Cases

• Executive capability maps across the business lifecycle.
• Multi-phase expansion paths (for example Siemens EDA style: integration first, then asset/financial visibility, then platform intelligence).
• Capability traceability from pain point to platform feature.

Strategy Workflow

1. Frame the business motion
   Define the target outcomes, constraints, and current-state systems (for example SAP preservation with Salesforce expansion).

2. Map capabilities
   Select the minimum viable capabilities from the catalog and state why each one matters.

3. Sequence by dependency
   Put integration and data foundations before higher-order AI and autonomous operations.

4. Present rollout phases
   Group capabilities into 2-4 phases with clear value milestones.

5. State assumptions and risks
   Call out dependencies (data quality, ownership model, integration readiness, governance).

Output Template

Use this default structure:

## Capability Map
- Domain | Acronym | Capability | Why it matters now

## Phased Expansion Path
- Phase 1: [name] -> capabilities
- Phase 2: [name] -> capabilities
- Phase 3: [name] -> capabilities

## Design Considerations
- Data and trust
- Integration and orchestration
- Operating model and governance

## Risks and Assumptions
- ...

Design Rules

• Keep capability names and acronyms aligned to the catalog skill.
• Prioritize reuse over reinvention: if the catalog changes, this strategy skill should still work without content rewrites.
• Optimize for executive readability: short rationale lines, explicit trade-offs, and phased outcomes.

Capability Search Interaction Pattern

When the experience includes capability search, default to a floating results card to minimize navigation overhead.

Use this pattern:

1. Keep results in a non-blocking floating card anchored to the search input.
2. Let users pick a capability without leaving current context.
3. Support close/dismiss via Esc, click-away, and explicit close action.
4. Preserve query and result state when the card is dismissed and reopened.
5. Support keyboard-first interaction (arrow navigation + Enter select).
6. After selection, close the card and show the chosen capability inline in the host view.

Use full-page results only when the task requires complex filtering, deep comparisons, or multi-step editing.