.archive/finance-team/skills/financial-modeling/SKILL.md
Financial modeling workflow for DCF, LBO, merger, and operating models. Delivers validated, documented models with sensitivity and scenario analysis.
npx skillsauth add lerianstudio/ring financial-modelingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill provides a structured workflow for building financial models using the financial-modeler agent.
The financial modeling workflow follows 6 phases:
| Phase | Name | Description | |-------|------|-------------| | 1 | Scoping | Define model purpose and requirements | | 2 | Architecture | Design model structure | | 3 | Assumptions | Document all model inputs | | 4 | Build | Construct model with formulas | | 5 | Validation | Test and verify model | | 6 | Documentation | Prepare user guide and audit trail |
MANDATORY: Define model purpose before building
| Question | Purpose | |----------|---------| | What decision does this model support? | Ensures relevance | | What type of model is needed? | Sets approach | | What level of detail is required? | Scopes complexity | | Who will use the model? | Tailors design | | What scenarios are needed? | Plans flexibility |
| Type | Use Case | Key Outputs | |------|----------|-------------| | DCF | Intrinsic valuation | Enterprise Value, Equity Value | | Trading Comps | Relative valuation | Implied multiples | | LBO | PE acquisition | IRR, MOIC, sources/uses | | M&A | Strategic acquisition | Accretion/dilution, synergies | | Three-Statement | Operating projections | IS, BS, CF integrated |
If ANY of these are unclear, STOP and ask:
MANDATORY: Design structure before building
| Principle | Description | |-----------|-------------| | Input separation | All inputs in dedicated section | | No hardcoding | No numbers in formulas | | Consistent formulas | Same formula across row | | Error checks | Validation on each sheet | | Clear flow | Logical left-to-right, top-to-bottom |
| Section | Contents | |---------|----------| | Cover | Model name, version, date, author | | Inputs | All assumptions in one place | | Historical | Historical financial data | | Projections | Projected financials | | Valuation | DCF, comps, or transaction calcs | | Sensitivity | Sensitivity tables | | Output | Summary and key metrics | | Checks | Error checking |
MANDATORY: Document ALL assumptions with sources
| Category | Examples | |----------|----------| | Operating | Revenue growth, margins, CapEx | | Valuation | WACC, terminal growth, multiples | | Transaction | Entry price, financing, fees | | Timing | Projection period, exit year |
| Element | Requirement | |---------|-------------| | Assumption name | Clear description | | Value | Base case value | | Source | Where value came from | | Sensitivity | Range for testing |
MUST get user input on:
Dispatch to specialist with full context
Task tool:
subagent_type: "ring:financial-modeler"
prompt: |
Build financial model per these specifications:
**Purpose**: [decision supported]
**Model Type**: [DCF/LBO/M&A/Operating]
**Architecture**:
[From Phase 2]
**Assumptions**:
[From Phase 3]
**Historical Data**:
[Attach historical financials]
**Required Output**:
- Model structure per architecture
- All assumptions in input section
- Sensitivity analysis
- Scenario analysis (base/upside/downside)
- Error checks
| Element | Requirement | |---------|-------------| | Model Summary | Key outputs and conclusions | | Assumptions | Complete input section | | Model Structure | Per architecture design | | Key Outputs | Valuation, metrics, returns | | Sensitivity | 2x2 tables for key drivers | | Validation | Error checks passing |
MANDATORY: Test model before delivery
| Test | Description | |------|-------------| | Balance Sheet | Assets = Liabilities + Equity | | Cash Flow | CF reconciles to B/S cash | | Circular Control | Circulars iterate and converge | | Formula Audit | No hardcoded values in calcs | | Reasonableness | Results within expected range |
| Test | Purpose | |------|---------| | WACC sensitivity | Valuation impact of discount rate | | Growth sensitivity | Valuation impact of growth | | Margin sensitivity | Valuation impact of profitability | | Exit multiple sensitivity | LBO return sensitivity |
| Rationalization | Why It's WRONG | Required Action | |-----------------|----------------|-----------------| | "Model foots, it's correct" | Footing ≠ correct logic | VALIDATE methodology | | "Sensitivity shows expected range" | Range needs to be appropriate | VERIFY ranges sensible | | "Used industry WACC" | WACC must be calculated | CALCULATE and document |
MANDATORY: Document for future users
| Element | Status | |---------|--------| | Model summary | Required | | Assumption register | Required | | Methodology description | Required | | User instructions | Required | | Error check explanations | Required | | Version history | Required |
See shared-patterns/execution-report.md for base metrics.
Modeling-Specific Metrics:
See shared-patterns/pressure-resistance.md for universal pressures.
| Pressure Type | Request | Agent Response | |---------------|---------|----------------| | "Just give me a valuation" | "Valuations require documented methodology. I'll build proper model." | | "Use 10% WACC" | "WACC must be calculated from components. I'll show the build-up." | | "Skip sensitivity" | "Sensitivity is required for decision support. I'll include key drivers." | | "Copy last model" | "Each model needs fresh design. Prior models are reference, not template." |
See shared-patterns/anti-rationalization.md for universal anti-rationalizations.
| Rationalization | Why It's WRONG | Required Action | |-----------------|----------------|-----------------| | "Quick model doesn't need structure" | ALL models need structure | DESIGN architecture | | "Terminal value is just a plug" | TV often 60%+ of value | CALCULATE properly | | "Industry multiple is obvious" | Multiples need source | CITE and date source | | "Circular doesn't matter" | Circulars affect results | HANDLE explicitly |
Upon completion, report:
| Metric | Value | |--------|-------| | Duration | Xm Ys | | Model Tabs | N | | Assumptions | N documented | | Scenarios | N | | Sensitivity Tests | N | | Validation Tests | N/N passed | | Result | COMPLETE/PARTIAL |
| Indicator | Status | |-----------|--------| | All inputs in input section | YES/NO | | No hardcoded values | YES/NO | | Error checks pass | YES/NO | | Sensitivity included | YES/NO | | Methodology documented | YES/NO |
development
Analyzes a Go service using lib-commons v2/v3 and generates a visual migration report showing every change needed to upgrade to lib-commons v4. Produces an interactive HTML page (via ring:visualize) and optionally generates refactoring tasks for ring:dev-cycle.
documentation
Patterns and structure for writing functional documentation including guides, conceptual explanations, tutorials, and best practices documentation.
development
Patterns and structure for writing API reference documentation including endpoint descriptions, request/response schemas, and error documentation.
documentation
Voice and tone guidelines for technical documentation. Ensures consistent, clear, and human writing across all documentation.