Private Wealth JSON
Use this skill for advisory cases that require one exact JSON object and nothing else.
Workflow
- Read the request memo and answer template first.
- Identify the analysis type, required top-level keys, and any stated planning horizon or dates.
- If source data is needed, use the task-provided advisory API base URL and only the listed endpoints.
- Resolve conflicts by source authority, not by averaging:
- signed profile for goals, beneficiaries, and policy preferences
- attorney memo for legal or planning assumptions and asset facts
- custodian export for balances and holdings
- CRM notes only if nothing better exists
- stale intake only as a last resort
- Populate every required field, keep enum strings exact, round USD to cents, and use ISO
YYYY-MM-DDdates. - Return the final JSON object only. No prose, markdown, or code fences.
Analysis types
Read references/analysis-types.md for the field map and type-specific rules.
Final checks
- Match the template exactly.
- Keep
task_idandclient_idunchanged. - Sort any
action_setalphabetically. - Make
conversion_years_positivematchconversion_years. - Do not add extra keys or commentary.