How this skill is triggered — by the user, by Claude, or both
Slash command
/finance:forecastThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Project the financial forecast for "$ARGUMENTS". Build a driver-based model that translates planning assumptions into monthly revenue, expense, and cash flow projections.
Project the financial forecast for "$ARGUMENTS". Build a driver-based model that translates planning assumptions into monthly revenue, expense, and cash flow projections.
Read .metapowers/finance/$ARGUMENTS/02-plan.md. If this file does not exist, tell the user:
Phase 2 (Plan) has not been completed for "$ARGUMENTS". Run
/finance:plan $ARGUMENTSfirst, or use--skip-checksto bypass.
If --skip-checks is present in $ARGUMENTS, skip this check and log to .metapowers/finance/$ARGUMENTS/skip-log.md.
Read context:
.metapowers/finance/$ARGUMENTS/01-assess.md for baseline data.metapowers/finance/$ARGUMENTS/02-plan.md for assumptions and KPI targetsBuild revenue forecast:
financial-model-template.md for revenue model structureBuild expense forecast:
Build cash flow forecast:
Validate against KPIs:
Write the artifact to .metapowers/finance/$ARGUMENTS/03-forecast.md with sections:
The forecast written to .metapowers/finance/$ARGUMENTS/03-forecast.md. Present a summary highlighting:
npx claudepluginhub bromso/metapowers --plugin financeCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.