// Compute current runway, burn trend, and forecast end-of-runway. Use when boss or bookkeeper is asked for runway, on a scheduled monthly check, or before any fundraising conversation.
| name | runway-check |
| description | Compute current runway, burn trend, and forecast end-of-runway. Use when boss or bookkeeper is asked for runway, on a scheduled monthly check, or before any fundraising conversation. |
A founder should know their runway in months, not "uhhh we have a few months". This skill makes the answer reliable and current.
Pull bank balance:
xero_accounts get_balancewiki/finance/<year>/<month>/bank-balance.mdCompute trailing 3-month average burn:
wiki/finance/<year>/<month>/burn-summary.mdCompute runway:
runway_months = bank_balance / monthly_burnSurface a tighter view:
Surface levers:
Write to wiki/finance/<year>/<month>/runway-check.md with frontmatter kind:runway-check
Flag if runway < 6 months — boss should know
Drafts the monthly investor update — pulls metrics, surfaces wins + struggles, formats per the founder's voice. Use on the 1st of each month, or when boss asks for a draft, or when investor-relations fires a scheduled monthly routine.
After filing a meeting, customer call, investor call, or any conversation entry, scan the body for explicit commitments (I'll ship X by Y, send Z by Friday) and create structured commitment entries in wiki/commitments/. Use whenever a new meeting note lands; also use to retroactively scan an existing entry for missed commitments.
After a customer call (transcribed or hand-noted), file a structured summary to wiki/research/ and trigger extract-commitments. Use when founder finishes a call and says "@customer-success file this call" or similar.
Move a candidate through the hiring pipeline — sourced, contacted, first-call, case-study, offer, hired, passed. Captures notes per stage; never lets a candidate ghost-drift. Use when recruiter advances a candidate or the founder adds a new one.