Skip to content

PranavNagrecha/AwesomeSalesforceSkills / skills/admin/financial-planning-process

financial-planning-process

Verified

Use this skill when configuring FSC financial planning objects, designing periodic review cycles, modeling risk assessment workflows, or tracking goal progress in Financial Services Cloud. Trigger keywords: FinancialGoal, FinancialPlan, goal tracking, risk tolerance, review cycle, financial planning workflow, Discovery Framework, Revenue Insights. NOT for wealth management process discovery — use admin/wealth-management-requirements. NOT for Action Plan template mechanics — use admin/fsc-action-plans.

templates/financial-planning-process-template.md

View on GitHub
# Financial Planning Process — Work Template

Use this template when configuring FSC financial planning objects, designing a review cycle, modeling risk tolerance data, or validating goal progress tracking.

## Scope

**Skill:** `financial-planning-process`

**Request summary:** (fill in what the user asked for)

## Org Context

Before working, confirm and record the following:

| Item | Value |
|---|---|
| Org type | Managed-package FSC (FinServ__ namespace) / FSC Core (Summer 2025+ standard objects) |
| FSC license | Confirm in Setup > Installed Packages or Company Information |
| Revenue Insights licensed? | Yes / No — confirm in Setup > Company Information > Feature Licenses |
| FinancialGoal API name | `FinServ__FinancialGoal__c` (managed) OR `FinancialGoal` (Core) |
| FinancialPlan API name | `FinServ__FinancialPlan__c` (managed) OR `FinancialPlan` (Core) |
| Goal → Plan lookup field | `FinServ__FinancialPlan__c` (managed) OR `FinancialPlanId` (Core) |
| ActualValue field API name | `FinServ__ActualValue__c` (managed) OR `ActualValue` (Core) |
| TargetValue field API name | `FinServ__TargetValue__c` (managed) OR `TargetValue` (Core) |

## Risk Tolerance Approach

Record the chosen risk tolerance modeling method:

- [ ] Discovery Framework (questionnaire delivery + custom scoring logic)
- [ ] Custom fields on Account/Household (Risk_Profile__c picklist + Risk_Tolerance_Score__c number)
- [ ] Third-party integration (tool name: ____________, output field: ____________)

## Review Cycle Design

| Item | Value |
|---|---|
| Review cadence | Annual / Semi-annual / Quarterly |
| Action Plan target object | FinancialAccount / Account / FinancialGoal |
| TaskDeadlineType | Calendar / BusinessDays |
| Plan launch mechanism | Manual / Flow / Batch process |
| Template name convention | e.g., "Annual Client Review v1" |

### Task Sequence Draft

| # | Task Subject | DaysFromStart | AssignedTo | Required? |
|---|---|---|---|---|
| 1 | | | | |
| 2 | | | | |
| 3 | | | | |
| 4 | | | | |
| 5 | | | | |
| 6 | | | | |
| 7 | | | | |

## Goal Progress Tracking

Record the goal status update mechanism:

- [ ] Record-Triggered Flow on ActualValue change
- [ ] Nightly scheduled batch
- [ ] Integration process updates Status during custodial sync
- [ ] Manual advisor update (not recommended — document reason)

Progress formula field installed: `Goal_Progress_Pct__c` — Yes / No

## Revenue Insights Decision

If analytics dashboards for goal progress are in scope:

- [ ] Revenue Intelligence for Financial Services license confirmed in production org
- [ ] CRM Analytics for Financial Services enabled in Setup
- [ ] Pre-built "Goals" dashboard reviewed and meets requirements
- [ ] Custom dashboard design documented (if pre-built is insufficient)

## Checklist

Copy from SKILL.md Review Checklist and tick as completed:

- [ ] Correct API names confirmed for this org type (managed-package vs. FSC Core)
- [ ] FinancialPlan-to-FinancialGoal relationship populated for all active goals
- [ ] Goal ActualValue and Status fields have a defined update mechanism
- [ ] Action Plan template TargetEntityType matches the intended FSC object and Status is Active
- [ ] DaysFromStart offsets verified with a test plan launch
- [ ] Risk tolerance capture method selected and fields/framework configured
- [ ] Revenue Insights license confirmed before building analytics dependencies
- [ ] No mixed-namespace API name references in any metadata or code artifact

## Deviations from Standard Pattern

Record any departures from the standard skill guidance and the reason:

(fill in as needed)

## Notes

(free-form notes, decisions, and open items)
brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).Stars: 323kUpdated Claude CodeCodexVerifiedInstall
brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).Stars: 198kUpdated Claude CodeCodexVerifiedInstall