client-review-prep
Prepare advisors for client review meetings by assembling context packages, performance summaries, drift analysis, talking points, and meeting agendas. Use when the user asks about preparing for a client review, building a pre-meeting checklist, generating talking points for an upcoming meeting, identifying allocation drift before a review, automating review prep workflows, or assembling a meeting package with exhibits. Also trigger when users mention 'client meeting prep', 'review preparation', 'what should I discuss with my client', 'proactive recommendations', 'life event triggered review', 'meeting agenda', or 'compliance pre-check before review'.
What this skill does
# Client Review Preparation ## Purpose Guide the end-to-end workflow for preparing a wealth management advisor to conduct a client review meeting. This skill covers assembling the client context package, summarizing investment performance, identifying allocation drift, generating tailored talking points and proactive recommendations, building a structured meeting agenda with supporting exhibits, and completing a compliance pre-check before the meeting. It enables a user or agent to orchestrate all the data gathering, analysis, and document assembly steps required to walk into a review meeting fully prepared, with no manual scrambling. ## Layer 10 — Advisory Practice (Front Office) ## Direction both ## When to Use - An advisor asks to prepare for an upcoming client review meeting (annual, quarterly, or triggered) - A practice manager is building or standardizing the firm's review preparation workflow - Someone needs a checklist of what to gather and analyze before a client meeting - An advisor wants proactive recommendation ideas tailored to a specific client - The firm is automating review prep by integrating CRM, PMS, and planning data into a meeting package - A review is triggered by a life event, market event, or regulatory change rather than the regular cadence - An advisor needs to assemble a meeting agenda and supporting exhibits for a specific client ## Core Concepts ### Client Context Assembly The foundation of review preparation is assembling everything the advisor needs to know about the client before the meeting. This context package draws from multiple systems and should be gathered systematically rather than ad hoc. **Data to assemble:** 1. **Client profile and household** -- pull from CRM: names, ages, employment status, retirement dates, household members, service tier, assigned advisor, communication preferences 2. **Investment Policy Statement (IPS)** -- the governing document for the relationship: stated objectives, risk tolerance, time horizon, return targets, asset allocation targets with tolerance bands, investment restrictions, benchmark selections, liquidity constraints 3. **Account inventory** -- all accounts in the household: account types (taxable, IRA, Roth, trust, etc.), custodians, current market values, cash positions, cost basis summary 4. **Recent life events** -- any changes since the last review: job change, retirement, marriage, divorce, inheritance, birth of child, health event, home purchase or sale, business sale. These come from CRM notes, advisor logs, and financial planning system updates. 5. **Prior meeting notes** -- what was discussed at the last review, what action items were assigned, which items were completed. Unresolved items carry forward to the agenda. 6. **Financial plan status** -- if the client has a financial plan: probability of success, progress toward goals (retirement funding, education, legacy), any goals that have drifted off track since the last review 7. **Compliance and administrative status** -- date of last IPS update, date of last suitability questionnaire, advisory agreement renewal date, fee schedule, any pending compliance items Assemble this data into a one-page client context summary that the advisor can review in under five minutes before the meeting. ### Performance Review Preparation Performance data is the centerpiece of most review conversations. The goal is not to re-create a full performance report (that is the domain of performance reporting and client reporting delivery), but to extract the key numbers and narratives the advisor needs for the discussion. **Data to collect:** - Period returns for each account and the consolidated household: quarter-to-date, year-to-date, trailing 1-year, since inception (or since last review date) - Benchmark comparison: portfolio return versus the IPS-designated benchmark for each period - Attribution highlights: which asset classes or positions contributed most to outperformance or underperformance. Focus on the two or three largest contributors and detractors -- the client does not need a 50-line attribution table in a meeting. - Fees paid: advisory fees, fund expense ratios, transaction costs. Summarize total cost in dollars and as a percentage of AUM for the review period. - Income generated: dividends and interest received during the period, withdrawal activity **Prepare the narrative:** Translate raw numbers into a short (3-5 sentence) performance summary the advisor can use as a talking point. Example: "The consolidated household returned 4.2% for the quarter versus the benchmark's 3.8%, primarily driven by overweight exposure to international equities. Fixed income underperformed as rates rose, but the short-duration tilt limited the drag. Total fees for the quarter were $3,750 (0.15% of AUM)." ### Allocation Drift Analysis Before the meeting, compare each account's current allocation to its IPS target and identify any positions that have drifted beyond tolerance bands. This analysis feeds directly into rebalancing discussion points but does not re-derive the rebalancing math (see the rebalancing skill for methodology). **Steps:** 1. Pull current holdings and market values by asset class from the PMS 2. Calculate current allocation percentages for each asset class 3. Compare to IPS target allocation 4. Flag any asset class where the drift exceeds the tolerance band (e.g., target 60% equity with +/-5% band; current 67% equity is 2% beyond the upper band) 5. Summarize drift in a simple table: asset class, target, current, drift, in/out of tolerance If drift is beyond tolerance, prepare a rebalancing recommendation as a talking point. Include the estimated tax impact of rebalancing (realized gains or losses) for taxable accounts. ### Talking Points Generation Talking points are the structured notes the advisor uses to guide the meeting conversation. They should be specific to this client, not generic market commentary. **Categories of talking points:** 1. **Market commentary relevant to the portfolio** -- select 2-3 market developments that directly affect the client's holdings or strategy. If the client is overweight technology, discuss tech sector trends. If the client holds municipal bonds, discuss the muni market environment. Avoid generic "the market was up 5%" statements. 2. **Rebalancing needs** -- if drift analysis identified out-of-tolerance positions, frame the rebalancing conversation: what to trim, what to add, estimated tax impact, rationale tied to the IPS. 3. **Upcoming events** -- RMD deadlines, estimated tax payment dates, option expirations, bond maturities, CD renewals, vesting events for RSUs or stock options, trust distribution dates 4. **Action item follow-up** -- status of any actions agreed upon at the last meeting: was the beneficiary update completed? Was the insurance review done? Was the estate plan referral followed through? 5. **Life event implications** -- if any life events have occurred, prepare talking points on financial implications: new retirement date changes the distribution strategy, inheritance needs to be integrated into the portfolio and plan, divorce requires account retitling and beneficiary updates ### Proactive Recommendations A well-prepared review goes beyond reporting what happened and proactively identifies optimization opportunities. The advisor should walk into the meeting with 2-3 specific, actionable recommendations tailored to the client's situation. **Common proactive recommendation categories:** - **Tax-loss harvesting opportunities** -- identify positions with unrealized losses that could be harvested before year-end. Note wash sale considerations and replacement security options. Reference the tax-loss-harvesting and tax-efficiency skills for methodology; do not re-derive here. - **Roth conversion windows** -- if the client has a low-income year (early retirement, sabbatical, gap between retirement and Social Security), flag the opportunit
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.