home / skills / lerianstudio / ring / cash-flow-analysis

This skill helps you perform comprehensive cash flow analysis and treasury optimization by coordinating position, forecast, liquidity, risk, and

npx playbooks add skill lerianstudio/ring --skill cash-flow-analysis

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
6.9 KB
---
name: cash-flow-analysis
description: |
  Cash flow analysis and treasury management workflow covering liquidity assessment,
  cash forecasting, working capital optimization, and treasury operations.

trigger: |
  - Cash flow forecasting (13-week, monthly)
  - Liquidity assessment
  - Working capital analysis
  - Treasury operations review

skip_when: |
  - Financial statement analysis → use financial-analysis
  - Creating budgets → use budget-creation
  - Building valuation models → use financial-modeling

related:
  similar: [financial-analysis, budget-creation]
  uses: [treasury-specialist]
---

# Cash Flow Analysis Workflow

This skill provides a structured workflow for cash flow analysis and treasury management using the `treasury-specialist` agent.

## Workflow Overview

The cash flow analysis workflow follows 5 phases:

| Phase | Name | Description |
|-------|------|-------------|
| 1 | Position Assessment | Establish current cash position |
| 2 | Forecasting | Build cash flow forecast |
| 3 | Liquidity Analysis | Assess liquidity and runway |
| 4 | Risk Identification | Identify cash flow risks |
| 5 | Recommendations | Provide actionable guidance |

---

## Phase 1: Position Assessment

**MANDATORY: Establish current position before forecasting**

### Position Requirements

| Item | Description |
|------|-------------|
| Bank balances | All accounts, same day |
| Credit availability | Undrawn facilities |
| Restricted cash | Identify any restrictions |
| Intercompany | IC positions and netting |

### Verification Checklist

| Check | Validation |
|-------|------------|
| All accounts included | Complete bank list |
| Same-day balance | No stale data |
| Reconciled | Ties to bank statement |
| FX converted | Consistent currency |

### Blocker Check

**If ANY of these are unclear, STOP and ask:**
- Current cash position
- Credit facility terms
- FX rate source for conversion
- Restricted cash items

---

## Phase 2: Forecasting

**MANDATORY: Build forecast with documented methodology**

### Forecast Types

| Type | Horizon | Granularity | Use Case |
|------|---------|-------------|----------|
| 13-Week | 13 weeks | Weekly | Short-term liquidity |
| Monthly | 12 months | Monthly | Operating planning |
| Annual | 1-5 years | Annual | Strategic planning |

### Forecast Components

| Component | Description |
|-----------|-------------|
| Opening balance | Current position |
| Operating receipts | Customer collections, other |
| Operating disbursements | Payroll, vendors, other |
| Investing | CapEx, acquisitions |
| Financing | Debt, equity, dividends |
| Closing balance | Calculated position |

### Methodology Options

| Method | Description |
|--------|-------------|
| Receipts/Disbursements | Bottom-up from transactions |
| Adjusted Net Income | Top-down from P&L |
| Balance Sheet Method | From B/S changes |

---

## Phase 3: Agent Dispatch

**Dispatch to specialist with full context**

### Agent Dispatch

```
Task tool:
  subagent_type: "ring:treasury-specialist"
  model: "opus"
  prompt: |
    Perform cash flow analysis per these specifications:

    **Current Position**: [from Phase 1]
    **Forecast Type**: [13-week/monthly/annual]
    **Methodology**: [receipts-disbursements/adjusted NI]

    **Data Provided**:
    - Bank balances as of [date]
    - Credit facility details
    - AR aging
    - AP aging
    - Payroll schedule
    - Known commitments

    **Required Output**:
    - Current position summary
    - Cash flow forecast
    - Liquidity analysis
    - Risk assessment
    - Recommendations
```

### Required Output Elements

| Element | Requirement |
|---------|-------------|
| Treasury Summary | Current position and highlights |
| Cash Position | All accounts with reconciliation |
| Forecast | Period-by-period projection |
| Liquidity Analysis | Runway and ratios |
| Risk Assessment | Identified risks and mitigations |
| Recommendations | Actionable next steps |

---

## Phase 4: Liquidity Analysis

**MANDATORY: Assess liquidity comprehensively**

### Liquidity Metrics

| Metric | Formula | Threshold |
|--------|---------|-----------|
| Cash Runway | Cash / Monthly Burn | >6 months |
| Current Ratio | Current Assets / Current Liabilities | >1.5x |
| Quick Ratio | (CA - Inventory) / CL | >1.0x |
| Cash Ratio | Cash / Current Liabilities | >0.5x |

### Stress Testing

| Scenario | Description |
|----------|-------------|
| Base Case | Expected forecast |
| Delayed Receipts | AR delayed 30 days |
| Accelerated Payments | AP paid early |
| Revenue Shortfall | 10-20% revenue decline |
| Combined Stress | Multiple adverse factors |

---

## Phase 5: Risk Identification

**MANDATORY: Document all cash flow risks**

### Risk Categories

| Category | Examples |
|----------|----------|
| Collection Risk | Customer concentration, aging |
| Payment Risk | Vendor demands, timing |
| Operational Risk | Seasonality, cyclicality |
| Financing Risk | Covenant compliance, renewal |
| FX Risk | Currency exposure |

### Risk Assessment Framework

| Element | Documentation |
|---------|---------------|
| Risk description | Clear statement |
| Probability | High/Medium/Low |
| Impact | Quantified if possible |
| Mitigation | Specific action |

---

## Pressure Resistance

See [shared-patterns/pressure-resistance.md](../shared-patterns/pressure-resistance.md) for universal pressures.

### Cash Flow-Specific Pressures

| Pressure Type | Request | Agent Response |
|---------------|---------|----------------|
| "Use yesterday's balance" | "Treasury needs current data. I'll get today's position." |
| "Skip the forecast, just need position" | "Position without forecast lacks context. I'll include projections." |
| "Estimate the AR collections" | "Collections forecast needs AR aging basis. I'll use actual data." |
| "We never have liquidity issues" | "Past performance ≠ future results. I'll assess current risk." |

---

## Anti-Rationalization Table

See [shared-patterns/anti-rationalization.md](../shared-patterns/anti-rationalization.md) for universal anti-rationalizations.

### Cash Flow-Specific Anti-Rationalizations

| Rationalization | Why It's WRONG | Required Action |
|-----------------|----------------|-----------------|
| "Cash is cash, simple analysis" | Cash has many components | **ANALYZE by category** |
| "Forecast is same as last month" | Each forecast is independent | **BUILD fresh forecast** |
| "We always collect in 45 days" | Actual may differ | **USE actual aging** |
| "Covenant is not close" | Still needs monitoring | **CALCULATE covenant** |

---

## Execution Report

Upon completion, report:

| Metric | Value |
|--------|-------|
| Duration | Xm Ys |
| Accounts Reconciled | N |
| Forecast Periods | N |
| Risks Identified | N |
| Recommendations | N |
| Result | COMPLETE/PARTIAL |

### Quality Indicators

| Indicator | Status |
|-----------|--------|
| Position same-day | YES/NO |
| All accounts included | YES/NO |
| Forecast documented | YES/NO |
| Risks assessed | YES/NO |
| Covenants calculated | YES/NO |

Overview

This skill provides a mandatory, structured cash flow analysis and treasury management workflow for assessing liquidity, building forecasts, identifying risks, and delivering actionable recommendations. It enforces verification and quality gates so outputs are reconciled, documented, and ready for treasury decision-making. The workflow is organized into five phases from position assessment through recommendations.

How this skill works

The workflow requires establishing a same-day cash position, then building a documented forecast (13-week, monthly, or annual) using a selected methodology. It dispatches a treasury specialist agent with full context and data inputs to produce a reconciled position summary, period-by-period forecast, liquidity metrics, stress tests, risk assessment, and prioritized recommendations. Completion includes an execution report and quality indicators.

When to use it

  • Prepare short-term liquidity plans (13-week cash needs)
  • Monthly operating or annual strategic cash planning
  • Before covenant reviews, refinancing, or credit renewals
  • When cash position or FX exposures are unclear or unreconciled
  • Stress-testing scenarios for downside planning and runway estimation

Best practices

  • Always verify same-day bank balances and reconcile to statements before forecasting
  • Document forecast methodology and assumptions (receipts/disbursements, adjusted NI, or balance-sheet)
  • Include AR/AP aging, payroll schedule, and credit facilities as mandatory inputs
  • Run base and stressed scenarios (delayed receipts, revenue shortfall, combined stress)
  • Quantify probability and impact for each identified risk and specify concrete mitigations

Example use cases

  • Produce a 13-week weekly forecast to determine minimum cash buffer and borrowing needs
  • Create a 12-month monthly forecast to support operating planning and working capital optimization
  • Run stress tests to determine runway and covenant headroom under a 20% revenue decline
  • Assess FX exposure and recommend hedging actions when multiple currency accounts are active
  • Prepare an execution report for senior management showing reconciled accounts, risks, and prioritized recommendations

FAQ

What data is mandatory before starting a forecast?

Same-day bank balances for all accounts, credit facility terms, AR/AP aging, payroll schedule, and any restricted cash or intercompany positions are mandatory.

Which forecast horizon should I choose?

Use a 13-week weekly forecast for short-term liquidity, a 12-month monthly forecast for operating planning, and an annual (1–5 year) forecast for strategic decisions.

What if account balances are stale or unreconciled?

Stop the workflow and request current reconciled balances. Forecasts built on stale data are unreliable and must be avoided.