phoenix-reserves-optimizer
Reserve allocation and follow-on optimization for the Phoenix fund model. Use when working on deterministic reserve engine logic and optimal reserves ranking.
When & Why to Use This Skill
The Phoenix Reserves Optimizer is a specialized Claude skill designed for venture capital and fund management. it streamlines the implementation of deterministic reserve engines, enabling precise follow-on investment optimization and 'next dollar' ranking to maximize portfolio returns while maintaining strict capital constraints.
Use Cases
- Automating reserve sizing calculations based on fund size, graduation matrices, and stage-specific investment strategies.
- Optimizing follow-on capital allocation to identify the most impactful 'next dollar' investment opportunities across a diverse portfolio.
- Validating financial logic to ensure total allocated reserves never exceed the configured capital pool, preventing over-allocation.
- Handling complex edge cases in fund modeling, such as proportional scaling of reserves when capital is insufficient for all planned follow-ons.
- Refactoring legacy reserve engine code to improve accuracy in calculating Exit MOIC on planned reserves and opportunity costs.
| name | phoenix-reserves-optimizer |
|---|
Phoenix Reserves Optimizer
You handle reserve sizing and follow-on allocation logic, especially around the deterministic reserve engine and "next dollar" optimization.
When to Use
- When implementing or refactoring:
DeterministicReserveEngine.calculateReserves(...)- Any code that computes or displays optimal reserves or "next dollar" metrics
- When linking reserve logic to:
state.forecastResult.portfoliostate.graduationMatrixstate.stageStrategies
Core Concepts
Inputs:
- Total fund size
- Portfolio companies and their staged investments
- Graduation matrix and stage strategies
- Available reserve pool (e.g., 40% of total capital)
Outputs:
- Per-company reserve recommendations
- Fund-level reserves usage
- Metrics that can underpin:
- "Exit MOIC on planned reserves"
- Opportunity cost of deploying reserves into each company
Workflow
Compute:
totalCapital = fundSize * 1_000_000initialCapitalfrom initial checksavailableReservesfrom user-defined ratio (e.g., 40%)
Call the reserve engine with:
- Portfolio
- Graduation matrix
- Stage strategies
- Available reserves
Verify:
- Sum of allocated reserves ≤ availableReserves
- No negative or NaN allocations
- Edge cases when reserves are insufficient are handled gracefully (e.g., proportional scaling).
Document:
- Any assumptions about prioritization (e.g., later-stage vs earlier-stage deals).
- How reserves are scored/ranked.
Validation Patterns
Edge Cases to Test
- Zero reserves available: Ensure graceful handling (no allocations, not errors)
- Insufficient reserves: Proportional scaling across portfolio
- Single company: All reserves allocated to one deal
- Negative values: Detect and reject invalid inputs
Example Validation
// Reserve allocation constraints
expect(totalAllocated).toBeLessThanOrEqual(availableReserves);
expect(allocations.every((a) => a >= 0)).toBe(true);
expect(allocations.some(isNaN)).toBe(false);
Invariants
- Total reserved capital must never exceed the configured reserves pool.
- Changes to the reserve engine must not break existing reserve analytics or dashboards.