finance-plan

Define the financial plan's horizon, strategic objectives, KPIs with targets and the revenue, cost and capital assumptions behind them. Use when the user has a financial baseline and wants to set fina

SKILL.md

GitHub

Plan

Define the strategic financial plan for "$ARGUMENTS". Set objectives, choose KPIs, and document the assumptions that will drive the forecast and budget.

Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .singularskills/log.jsonl: {"ts":"<ISO timestamp>","skill":"finance-plan","workflow":"finance","phase":2,"project":"<project>","event":"skipped","artifact":"02-plan.md","note":"<reason or \"none given\">"}.

Compute with code. Perform every calculation (totals, balances, ratios, variances, projections) with a script — Bash, Python or a spreadsheet formula written to a file — and include the computation alongside the result. Never do arithmetic mentally.

Prerequisites

Part of a workflow. This skill is phase 2 (Plan) of the FP&A workflow (finance); cross-domain workflows run it too. First check .singularskills/log.jsonl for an open run for this project: a run-started line with "project":"<project>" and no later run-finished line for the same workflow and project. If one exists, the conductor is running you: continue here. Otherwise, if the user asked to start, run, continue or resume a process or workflow rather than this one step, do not continue here: invoke the workflow skill with the workflow the user asked for, or finance when they named none, followed by <project>; it runs this phase in order, asks before it writes and records the run. Otherwise continue here: a later phase runs on its own, behind its gate.

Run this skill's gate before writing: sh <this skill's folder>/scripts/gate.sh <project> <project root>, where <project root> is the folder that contains .singularskills/ (use . when you are already there). If it exits non-zero, stop and tell the user what it printed, unless --skip-checks was given (see Arguments). On a refusal, before you stop, append this line to .singularskills/log.jsonl (create the folder and file if missing): {"ts":"<ISO timestamp>","skill":"finance-plan","workflow":"finance","phase":2,"project":"<project>","event":"refused","artifact":"02-plan.md","note":"<what the gate printed>"}. Once the gate has passed, or under --skip-checks once you have appended the skipped line, append this line before you start work: {"ts":"<ISO timestamp>","skill":"finance-plan","workflow":"finance","phase":2,"project":"<project>","event":"started","artifact":"02-plan.md","note":""}.

Read .singularskills/finance/<project>/01-assess.md. If this file does not exist, tell the user:

Phase 1 (Assess) has not been completed for "<project>". Run /finance-assess <project> first, or use --skip-checks to bypass.

Process

  1. Read context:

    • Read .singularskills/finance/<project>/01-assess.md for baseline metrics and business profile
  2. Define strategic objectives:

    • What is the planning horizon? (quarterly, annual, 3-year)
    • What are the top 3-5 financial goals? (growth rate, profitability, fundraise, break-even)
    • What business milestones are tied to these goals?
    • Are there external deadlines? (fundraise timeline, board commitments)
  3. Select KPIs:

    • Choose 5-10 KPIs aligned with objectives
    • For each KPI: define the metric, target, current value, and measurement frequency
    • Categorize: growth, profitability, efficiency, liquidity
    • Identify leading vs lagging indicators
  4. Document planning assumptions:

    • Revenue assumptions (growth rates, pricing, churn, expansion)
    • Cost assumptions (hiring plan, vendor costs, inflation)
    • Market assumptions (TAM, competitive dynamics, seasonality)
    • Capital assumptions (funding, debt, payment terms)
    • Flag which assumptions carry the most risk
  5. Write the artifact to .singularskills/finance/<project>/02-plan.md with sections:

    • Planning Horizon — timeframe and context
    • Strategic Objectives — prioritized financial goals
    • KPI Dashboard — metrics, targets, current values
    • Planning Assumptions — all assumptions with risk ratings
    • Milestones — key dates and financial triggers

Output

The plan written to .singularskills/finance/<project>/02-plan.md. Present a summary highlighting:

  • Planning horizon and objectives
  • Key KPIs and targets
  • Highest-risk assumptions

Record the run. After you have written the artifact, append this line to .singularskills/log.jsonl (the started line of Prerequisites, with "event":"finished"): {"ts":"<ISO timestamp>","skill":"finance-plan","workflow":"finance","phase":2,"project":"<project>","event":"finished","artifact":"02-plan.md","note":""}.

Open the artifact with this frontmatter (agent is the agent you run in, or unknown; gate is passed when the gate ran clean and skipped under --skip-checks):

---
skill: finance-plan
workflow: finance
phase: 2
project: <project>
started: <ISO timestamp>
finished: <ISO timestamp>
agent: <the agent you run in, or "unknown">
gate: <passed|skipped>
---

End the artifact with ## Decisions and ## Open questions, in this shape:

## Decisions
- <what was chosen> — <why> — <what was rejected>

## Open questions
- <what the next phase or a reviewer must settle>

End the artifact with this paragraph, verbatim:

Not financial or tax advice. This artifact is generated analysis for review by a qualified accountant or financial professional before any filing, reporting or decision relies on it.