flux-analysis
Decompose financial variances into underlying drivers and produce narrative explanations with waterfall bridge analysis. Use for budget vs actual analysis, period-over-period comparison, revenue variance decomposition, expense variance analysis, variance commentary, waterfall charts, forecast accuracy measurement, or P&L flux review.
What this skill does
## Decomposition Techniques
### Price x Volume Separation
The foundational split for any metric expressible as unit price multiplied by quantity.
**Two-factor formulas:**
```
Total Movement = Actual Result - Baseline (budget or prior period)
Quantity Component = (Actual Units - Baseline Units) x Baseline Unit Price
Pricing Component = (Actual Unit Price - Baseline Unit Price) x Actual Units
Check: Quantity Component + Pricing Component = Total Movement
(when the interaction term is absorbed into one of the two factors)
```
**Three-factor formulas (isolating composition shifts):**
```
Quantity Component = (Actual Units - Baseline Units) x Baseline Price x Baseline Mix Weights
Pricing Component = (Actual Price - Baseline Price) x Baseline Units x Actual Mix Weights
Composition Component = Baseline Price x Baseline Units x (Actual Mix Weights - Baseline Mix Weights)
```
**Worked example — top-line revenue:**
- Baseline plan: 10,000 units at $50/unit = $500,000
- Actual outcome: 11,000 units at $48/unit = $528,000
- Net movement: +$28,000 favorable
- Quantity uplift: +1,000 units x $50 = +$50,000 (favorable — higher volume)
- Pricing drag: -$2 x 11,000 = -$22,000 (unfavorable — reduced average selling price)
### Blended Rate / Composition Separation
Applicable when aggregated results blend multiple segments with distinct unit economics.
**Formulas:**
```
Rate Component = Sum across segments of [Actual Volume_i x (Actual Rate_i - Baseline Rate_i)]
Composition Component = Sum across segments of [Baseline Rate_i x (Actual Volume_i - Proportional Volume_i at Baseline Mix)]
```
**Worked example — gross margin compression:**
- Segment X earns 60% margin; Segment Y earns 40% margin
- Plan assumed a 50/50 split -> blended 50% margin
- Actual split was 40/60 -> blended 48% margin
- The 2-point margin decline is attributable to the shift toward the lower-margin segment
### People-Cost Decomposition
Purpose-built for analyzing compensation and headcount-driven expense lines.
```
Total Compensation Movement = Actual Spend - Planned Spend
Break into:
1. Staffing level effect = (Actual Headcount - Plan Headcount) x Plan Average Cost
2. Per-capita cost effect = (Actual Average Cost - Plan Average Cost) x Plan Headcount
3. Composition effect = Residual from shifts in seniority, department, or geography mix
4. Phasing effect = Impact of hires arriving earlier or later than the plan assumed
5. Attrition benefit = Savings from unplanned departures (partially offset by replacement and vacancy costs)
```
### Functional Expense Decomposition
For operating cost categories where a price-times-volume model does not apply naturally.
```
Total OpEx Movement = Actual Operating Costs - Planned Operating Costs
Segment into:
1. Headcount-linked costs (wages, benefits, payroll taxes, recruiting fees)
2. Activity-linked costs (cloud hosting, payment processing fees, sales commissions, freight)
3. Discretionary programs (travel, conferences, outside services, campaign spend)
4. Committed / fixed costs (facility leases, insurance, enterprise software licenses)
5. Non-recurring charges (severance, litigation, asset write-downs, project-specific outlays)
6. Timing / phasing differences (spend that shifted between periods relative to the plan)
```
## Significance Thresholds & Prioritization
### Calibrating Thresholds
Thresholds govern which movements warrant formal investigation and written explanation. Base them on:
1. **Overall materiality:** Usually 1-5% of a primary benchmark (revenue, total assets, or net income)
2. **Relative line-item scale:** Apply tighter percentage gates to larger balances
3. **Historical volatility:** Allow wider bands for inherently variable accounts to filter noise
4. **Decision relevance:** Would this size of movement influence a management decision or board discussion?
### Suggested Threshold Grid
| Comparison Basis | Suggested Dollar Gate | Suggested Percentage Gate | Trigger Logic |
|---|---|---|---|
| Actual vs. annual plan | Entity-specific | 10% | Whichever is breached first |
| Actual vs. same period last year | Entity-specific | 15% | Whichever is breached first |
| Actual vs. latest forecast | Entity-specific | 5% | Whichever is breached first |
| Sequential month-over-month | Entity-specific | 20% | Whichever is breached first |
*Set the dollar gate at roughly 0.5-1% of revenue for income-statement lines.*
### Triage Order When Multiple Items Exceed Thresholds
1. **Greatest absolute dollar impact** — largest influence on the bottom line
2. **Greatest percentage deviation** — may signal a process breakdown or data error
3. **Counter-trend movements** — direction opposite to what history or forecasts predicted
4. **Newly emerged variances** — items previously on track that have just diverged
5. **Compounding variances** — gaps that have widened in each of the last several periods
## Writing Effective Variance Narratives
### Recommended Structure
```
[Line Item]: [Favorable / Unfavorable] movement of $[amount] ([X]%)
relative to [budget / prior period / forecast] for [reporting period]
Primary driver: [Brief label]
[Two to three sentences explaining the business cause, quantifying each
contributing factor where possible.]
Outlook: [One-time event / Likely to persist / Improving / Worsening]
Next step: [No action / Monitor / Deeper review / Adjust forecast]
```
### Quality Criteria
Strong narratives consistently satisfy these tests:
- **Precise:** Names concrete factors rather than restating the variance itself
- **Measured:** Attaches dollar or percentage weight to each cited driver
- **Explanatory:** Addresses why the movement occurred, not merely that it did
- **Prospective:** States whether the movement is expected to continue, reverse, or evolve
- **Directive:** Identifies any follow-up action or decision prompted by the finding
- **Compact:** Two to four sentences — not padded filler
### Pitfalls to Avoid
- Restating the outcome as its own cause ("Revenue rose because revenue was higher")
- Labeling a variance as "timing" without specifying what shifted and when normalization is expected
- Calling something "one-time" without describing the actual event
- Sweeping a material movement under "various small items" instead of decomposing further
- Explaining only the dominant driver while ignoring meaningful offsets
- Using vague qualifiers ("elevated," "slightly higher") without attached numbers
## Bridge / Waterfall Presentation
### Concept
A bridge (waterfall) chart traces the path from a starting value to an ending value through a sequence of additive and subtractive contributors. It is the visual companion to variance decomposition.
### Data Architecture
```
Starting point: [Baseline figure — plan, prior period, or forecast]
Contributors: [Ordered list of signed driver amounts]
Ending point: [Actual figure]
Integrity check: Starting point + Sum(all contributors) = Ending point
```
### Text-Format Bridge (When No Charting Tool Is Available)
```
BRIDGE: Operating Expenses — Q4 Actual vs. Q4 Plan
Q4 Planned OpEx $8,000K
|
|--[+] Incremental headcount above plan +$500K
|--[+] Unplanned outside counsel fees +$200K
|--[-] Open-role savings (delayed hiring) -$350K
|--[-] Travel spend below budget -$180K
|--[+] Cloud infrastructure overrun +$130K
|--[-] Marketing program deferrals -$100K
|
Q4 Actual OpEx $8,200K
Net Movement: +$200K (+2.5% unfavorable)
```
### Companion Reconciliation Table
| Driver | Amount | Share of Total Movement | Running Total |
|---|---|---|---|
| Incremental headcount | +$500K | 250% | +$500K |
| Outside counsel | +$200K | 100% | +$700K |
| Open-role savings | -$350K | -175% | +$350K |
| Travel underspRelated 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.