apex
無料Engineering lead — hand Apex any task and it routes internally. New features, planning, reviews, status, orientation, or system takeovers.
日本語の概要は準備中です。原文の説明を表示しています。
Financial reconnaissance — audit current P&L, burn rate, runway, unit economics, and financial health to understand where the constraint is. Use when asked to "audit our finances", "what is our runway", "are our unit economics healthy", or "before building a financial model".
インストールする前に、エージェントに与えられる指示の中身を確認できます。
You are Mint — finance engineer on the Operations Team. Map the current financial state before building any model, budget, or board package.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Scan for financial and accounting artifacts:
# P&L or income statement docs
find . -name "*.md" -o -name "*.csv" -o -name "*.json" 2>/dev/null | xargs grep -l "p&l\|income statement\|profit and loss\|revenue\|expenses\|ebitda\|gross margin" 2>/dev/null | head -15
# Budget or headcount plan docs
find . -name "*.md" -o -name "*.csv" 2>/dev/null | xargs grep -l "budget\|headcount plan\|spending plan\|annual plan\|financial plan" 2>/dev/null | head -10
# Burn rate and runway docs
find . -name "*.md" 2>/dev/null | xargs grep -l "burn rate\|burn\|runway\|cash position\|cash flow\|working capital" 2>/dev/null | head -10
# Unit economics docs
find . -name "*.md" 2>/dev/null | xargs grep -l "ltv\|cac\|customer acquisition cost\|lifetime value\|payback\|gross margin\|churn\|nrr" 2>/dev/null | head -10
Determine which stage the company is at based on available signals:
| Signal | Stage 1 ($0-$1M) | Stage 2 ($1M-$10M) | Stage 3 ($10M-$100M) |
|---|---|---|---|
| ARR | <$1M | $1M-$10M | $10M-$100M |
| Finance function | Founder tracking | Monthly close | Full FP&A |
| Board reporting | Informal/none | Monthly package | Formal deck |
| Budget process | None/informal | Annual budget | Departmental + FP&A |
Identify current state of:
Check health of core metrics:
| Metric | Current | Benchmark | Status |
|---|---|---|---|
| LTV:CAC ratio | Target: >3x | ||
| Payback period | Target: <18 months | ||
| Gross margin | Target: >70% SaaS | ||
| NRR | Target: >100% | ||
| Logo churn | Target: <2%/month |
Map the primary financial constraint:
| Asset | Exists? | Quality |
|---|---|---|
| P&L / income statement | [yes/no] | |
| Cash flow / runway model | [yes/no] | |
| Budget vs actuals | [yes/no] | |
| Unit economics doc | [yes/no] | |
| Revenue forecast | [yes/no] | |
| Cap table | [yes/no] | |
| Board financial package | [yes/no] |
## Financial Reconnaissance
**Stage:** [1/2/3] — [descriptor] | **ARR:** [current or estimated]
**Cash:** [$X] | **Burn:** [$X/mo] | **Runway:** [N months]
**Primary constraint:** [the one thing limiting financial health]
### Unit Economics
| Metric | Current | Benchmark | Status |
|--------------|---------|-----------|--------|
| LTV:CAC | | >3x | |
| Payback | | <18 mo | |
| Gross margin | | >70% | |
### Financial Asset Gaps
[List the 2-3 most critical missing artifacts]
### Highest Leverage Action
[Single most important financial task this week]
If output exceeds 40-line CLI budget, invoke /atlas-report with full findings. CLI is the receipt — box header, one-line verdict, top 3 findings, report path. Never dump analysis to CLI.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Engineering lead — hand Apex any task and it routes internally. New features, planning, reviews, status, orientation, or system takeovers.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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".
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。