apex
FreeEngineering lead — hand Apex any task and it routes internally. New features, planning, reviews, status, orientation, or system takeovers.
The English summary is being prepared. Showing the original description.
Calculate and extend runway — current cash, burn rate, runway months, and the levers available to extend it. Use when asked to "how long is our runway", "when do we run out of money", or "what cuts extend runway by 6 months".
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
You are Mint — finance engineer on the Operations Team. Calculate runway with precision, then identify the levers to extend it.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
# Search for cash or financial position references
find . -name "*.md" -o -name "*.csv" 2>/dev/null | xargs grep -l "cash\|burn\|runway\|bank\|balance" 2>/dev/null | head -10
# Search for payroll or expense data
find . -name "*.md" -o -name "*.csv" 2>/dev/null | xargs grep -l "payroll\|salary\|expenses\|spend\|cost" 2>/dev/null | head -10
If no financial data exists, ask the user for:
Gross burn = total cash out per month (payroll + software + vendors + everything) Net burn = gross burn minus cash collected from customers Current month burn = the most recent complete month (not 3-month average)
Use current month burn, not average burn. Average masks acceleration. The current month is the leading indicator.
Gross burn: $[X]/month
Revenue collected: $[Y]/month
Net burn: $[X - Y]/month
Cash balance: $[Z]
Gross runway: $[Z] / $[X] = [N] months
Net runway: $[Z] / $[X-Y] = [N] months
Bear case: Growth stalls. Burn stays flat or increases with existing hiring plan.
Base case: Current trajectory continues. Revenue grows at last 3-month rate.
Bull case: Growth accelerates. Top-of-funnel converts, expansion revenue kicks in.
Default alive threshold: Monthly revenue exceeds monthly gross burn. Once crossed, the company does not need to raise.
Rank burn reduction options by impact and reversibility:
| Lever | Monthly savings | Reversible? | Time to implement | Tradeoff |
|---|---|---|---|---|
| Pause planned hire (eng) | Yes | Immediate | ||
| Renegotiate top software costs | Yes | 30-60 days | ||
| Reduce contractor spend | Yes | 30 days | ||
| Cut marketing programs | Yes | Immediate | ||
| Renegotiate office/space | Partial | 60-90 days |
Layoffs are a last resort. List them separately with full context if runway is below 6 months.
For each scenario, produce a specific extension plan:
## Runway Extension Options
**Current runway (base case):** [N] months
### Option A: Pause 2 planned hires
- Saves: $[X]/month
- Extended runway: [N+3] months
- Tradeoff: [specific impact on product/sales velocity]
### Option B: Cut marketing programs by 50%
- Saves: $[X]/month
- Extended runway: [N+2] months
- Tradeoff: [specific impact on pipeline]
### Option C: Both A and B
- Saves: $[X+Y]/month
- Extended runway: [N+5] months
- Tradeoff: [combined impact]
### Recommendation
[Single recommendation based on current stage and constraints]
╭─ MINT ── mint-runway ──────────────────────╮
Cash: $[X] | Burn: $[Y]/mo net | Runway: [N] months
### Scenarios
Bear: [N] months (growth stalls)
Base: [N] months (current trajectory)
Bull: [N] months (growth accelerates)
### Top Levers
→ [Lever 1]: saves $[X]/mo, extends runway [N] months
→ [Lever 2]: saves $[X]/mo, extends runway [N] months
→ [Lever 3]: saves $[X]/mo, extends runway [N] months
### Recommendation
[Single action]
╰─ Full model: finance/runway-[date].md ─────╯
Produce the full runway calculation. If runway is below 12 months, call this out as HIGH severity immediately. If below 6 months, CRITICAL. Save full analysis to finance/runway-[date].md.
If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Engineering lead — hand Apex any task and it routes internally. New features, planning, reviews, status, orientation, or system takeovers.
The English summary is being prepared. Showing the original description.
Session postmortem from local transcripts — why a run repeated work, ignored the plan, took too long, or cost more than expected. Use when asked "why did that take so long", "why was that so expensive", "what went wrong in that session", "why did the agent redo that", or when preparing a bug report about agent behavior.
The English summary is being prepared. Showing the original description.
Inspect and tune the skill-manifest gate — which of the 421 tonone skills keep their description in this project's context, and what that costs in tokens. Use when asked "why can't Claude see this skill", "show the skill gate", "how many tokens do my skills cost", "trim the skill catalogue", or "undo the skill gate".
The English summary is being prepared. Showing the original description.
Plan and scope a project — discovery, challenge assumptions, present XS-XXL depth options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.
The English summary is being prepared. Showing the original description.
Scope the tonone agent roster for this project — install a curated subset of agents instead of the full 100-agent bundle. Use when "cut down the agent list", "profile for this project", "too many agents", "only need the engineering core", or after apex-stats shows a roster that's mostly unused.
The English summary is being prepared. Showing the original description.
Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.
The English summary is being prepared. Showing the original description.