money-retro
Weekly business retrospective. Reads all snapshots, learnings, skill-usage telemetry, and (if provided) revenue data from the past week. Outputs: what got decided, what shipped, what's stalled, skill activity, suggested next focus. Surfaces unused skills as activation prompts. Use at end of week or end of sprint. Triggered by: 'weekly retro', 'business retro', 'what did we ship', 'how's the week going', '周复盘', '业务回顾', '本周复盘'.
- Installs
- 43
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/iamzifei/show-me-the-money --skill money-retro- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads money-retro automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
/money-retro — Weekly Business Retrospective
Standard startup: before producing output, run the 5-step startup sequence per
/money§ Standard Skill Startup (resolve slug → telemetry write → /money-retro reads from telemetry rather than auto-loading learnings, since it's analyzing usage patterns themselves → surface project-local skills if any → load ALL atom categories so retro recommendations can cite the founder principles they reflect).
Your job is to read the week's accumulated state from disk and produce a sharp, evidence-based retrospective. This is not a pep talk. It surfaces what actually happened, what stalled, and what should change for the coming week.
The retro is informed entirely by what's on disk — sessions, learnings, skill-usage telemetry, and any revenue data the user provides. Do not improvise narrative beyond what the evidence supports.
Triggers
| Command | Behavior |
|---|---|
/money-retro | Retro for the past 7 days, current project |
/money-retro --days N | Custom window (e.g., --days 30 for monthly) |
/money-retro --slug <project> | Retro for a different project |
/money-retro --portfolio | Aggregate retro across ALL projects in ~/.smtm/sessions/ |
Natural-language equivalents:
- "Weekly retro", "Business retro", "What did we ship", "How's the week going"
- "周复盘", "业务回顾", "本周怎么样"
What to load
For the time window (default 7 days, sliding from now):
- Snapshots at
~/.smtm/sessions/{slug}/— filter by filename timestamp ≥ window start - Learnings added at
~/.smtm/projects/{slug}/learnings.jsonl— filter bycaptured_at≥ window start - Skill-usage telemetry at
~/.smtm/analytics/skill-usage.jsonl— filter by ts ≥ window start, group by skill - Optional: revenue data — if user provides numbers (e.g., "MRR went from $X to $Y"), incorporate. Otherwise omit revenue section.
- Prior retros at
~/.smtm/projects/{slug}/retros/— for trend comparison
If the window is empty (no snapshots, no learnings, no skill usage), say so plainly:
No activity recorded in
{project}for the past {N} days. Either you weren't running money-* skills with~/.smtm/enabled, or this project was dormant. Either is fine — but there's nothing to retro.
Workflow
Step 1 — Aggregate the week
For the time window, compute:
- Snapshots in window: count, with each snapshot's title and status
- Decisions made: pull from each snapshot's
Confirmed conclusionssection - Things ruled out: pull from each snapshot's
Ruled outsection - Open hypotheses: pull from each snapshot's
Open hypothesessection - Stalled hypotheses: open hypotheses from snapshots ≥14 days old without a follow-up snapshot
- Learnings added: count + categories
- Skills used: histogram, sorted by frequency
Step 2 — Identify "stalled" items
A hypothesis is "stalled" if:
- It was opened in a snapshot ≥14 days ago
- No subsequent snapshot in the same project has either confirmed it or ruled it out
- No learning has been added that addresses it
These are the highest-value findings — usually founders forget about hypotheses they meant to test.
Step 3 — Find unused skills
From skill-usage.jsonl, list skills the user has NEVER run for this project, OR has run but not in the past 30 days. These are activation candidates.
Don't preach about every unused skill — pick the 1-2 most relevant given the current project state. If they have a shipped product but never run /money-ads, that's a candidate. If they have no product yet, /money-ads is correctly unused; don't surface it.
Step 4 — Output
# Weekly Business Retro — {project}
**Window**: {start date} → {end date} ({N} days)
**Generated**: {now}
---
## What you decided this week
{For each snapshot's "Confirmed conclusions" — list with snapshot title and date.}
If no snapshots: "No new decisions checkpointed. Either nothing was decided, or `/money-save` wasn't run."
---
## What you ruled out
{Aggregated from snapshots' "Ruled out" sections, deduplicated.}
If empty: "Nothing was explicitly ruled out this week."
---
## Stalled hypotheses (action required)
These hypotheses were opened ≥14 days ago and never tested:
| Opened | Days stalled | Hypothesis | From |
|---|---|---|---|
| 2026-04-15 | 18 | Reddit r/SaaS will convert at >2% | snapshot:wedge-locked |
| ... | | | |
For each stalled item, suggest the cheapest test to resolve it.
If empty: "All open hypotheses are <14 days old. No stalls."
---
## Learnings captured
{Show recent learnings added in the window, with category and confidence.}
If empty: "No new learnings captured. If you observed any patterns this week, run `/money-learn add`."
---
## Skill activity
| Skill | Runs this week | Trend vs prior week |
|---|---|---|
| /money-discover | 3 | ↑ (was 1) |
| /money-content | 8 | → (was 7) |
| /money-ads | 0 | — (never run) |
| ... | | |
---
## Activation candidates (skills you haven't used)
Pick 1-2 high-relevance unused skills. Frame as a question:
> 💡 You've shipped the product and run `/money-content` 8 times — but never `/money-ads`. With your current MRR trajectory, paid ads might be the next leverage point. Want me to walk you through `/money-ads` next session?
---
## Revenue (only if user provided)
Show MRR/revenue if the user shared numbers. Otherwise omit.
---
## Recommended focus for next week
ONE thing. Not three. The single highest-leverage move based on what the retro surfaced.
Format: "**Focus**: {one sentence}. **First action**: {today or tomorrow specific step}."
---
## Snapshot of project state
- Total snapshots in project — {N}
- Total learnings — {N} ({validated} validated, {emerging} emerging, {hypothesis} hypothesis)
- Project age — {months since first snapshot}
- Open hypotheses — {N}
Step 5 — Save the retro
Write the retro itself to ~/.smtm/projects/{slug}/retros/{YYYYMMDD-HHMMSS}-retro.md. Each retro is a new file (never overwrite). This builds a longitudinal record of how the project is moving.
Confirm to the user:
✅ Retro saved to
~/.smtm/projects/{slug}/retros/{filename}.mdCompare to last week's retro:~/.smtm/projects/{slug}/retros/{prior filename}.md
Portfolio mode (--portfolio)
If invoked with --portfolio, aggregate across ALL projects in ~/.smtm/sessions/. Output is similar but adds a top-level "Project rollup" table:
| Project | Snapshots this week | New learnings | Stalled | Status (most recent snapshot) |
|---|---|---|---|---|
| musicapi | 3 | 2 | 0 | in-progress |
| kolfind | 0 | 0 | 4 | ⚠️ stalled |
| ccapi | 1 | 0 | 1 | in-progress |
The "stalled" surface here is especially valuable — solo founders often have one product that's silently dying while they pour attention into the noisier one.
Principles
- Evidence-only narrative — If it's not in a snapshot, learning, or telemetry log, it's not in the retro. No improvised storytelling.
- Stalled hypotheses are the highest-leverage finding — Most founders will skim the activity section but stop cold at "you never tested this thing you planned to test 3 weeks ago."
- One focus, not five — Recommendations dilute as they multiply. Pick the single highest-leverage move.
- Trend over snapshot — Show comparison to prior weeks where possible. Trend reveals what point-in-time can hide.
- Don't moralize unused skills — Surface 1-2 high-relevance ones, but don't shame the user for not running everything.
After the retro
Always recommend one of:
/money-learn addif the retro surfaced an obvious pattern that wasn't yet logged/money-saveafter acting on the recommended focus/money-panelif multiple stalled hypotheses suggest the plan itself needs re-review/money-diagnoseif stalled items are stalled because of an execution blocker, not lack of time
Value Quantification (Required at End of Output)
- ⏱ Time saved — ~1-2 hours of digging through old chats, snapshots, and trying to remember what you decided
- ⚠️ Risks avoided — (1) Stalled hypotheses going untested for months; (2) running the same activity (e.g.,
/money-content12x) without checking ROI; (3) ignoring a quietly-dying side project while focusing on the noisy one; (4) repeating the same week-over-week without intentional course correction - ✅ What you got — Decisions / ruled-out / stalled / learnings / skill activity, plus ONE recommended focus and a portfolio rollup if multi-project
- 🚧 Without this skill — You'd reach the end of the quarter unable to articulate what changed, and at least one hypothesis would have silently aged out without ever being tested
FAQ
What does the money-retro skill do?
Weekly business retrospective. Reads all snapshots, learnings, skill-usage telemetry, and (if provided) revenue data from the past week. Outputs: what got decided, what shipped, what's stalled, skill activity, suggested next focus. Surfaces unused skills as activation prompts. Use at end of week or end of sprint. Triggered by: 'weekly retro', 'business retro', 'what did we ship', 'how's the week going', '周复盘', '业务回顾', '本周复盘'.
How do I install money-retro?
Run npx skills add https://github.com/iamzifei/show-me-the-money --skill money-retro in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/money-retro/ (personal) or .claude/skills/money-retro/ (project).
Which AI agents can use money-retro?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is money-retro safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains money-retro?
It is published by iamzifei in iamzifei/show-me-the-money. It has 43 recorded installs.
More from iamzifei/show-me-the-money
money-discover
iamzifei/show-me-the-money
Discover profitable business ideas from scratch. Analyzes market gaps, trending niches, user skills, and competitive landscapes with a competitive intelligence protocol including 4-filter benchmark stress test and Blue Ocean differentiation grid. Use when the user has no idea what to build, wants to explore opportunities, needs market research, competitive benchmarking, or says 'find me a business idea', 'what should I build', 'market research', 'find opportunities', or 'competitive analysis'.
money
iamzifei/show-me-the-money
Main entry point for the Show Me The Money business automation suite. Dual mode: pre-task routing (which skill fits your problem) + post-task navigation (a skill just finished — what's next). Use when the user wants to start a business, automate operations, generate revenue, find product ideas, set up marketing, or run any business function autonomously. Also use when the user says 'show me the money', '来财' (the suite's Chinese name), 'make money', 'start a business', 'automate my business', 'build a company', 'what's next', or '下一步怎么走'. Includes a beginner tutorial mode triggered by '/money onboarding', '/money tutorial', '/money 新手', '/money 教程', 'how do I use this', or '这个怎么用' — a zero-input guided walkthrough that produces a demo business brief.
money-strategy
iamzifei/show-me-the-money
Create comprehensive business strategy with premise deconstruction, business model stress test, pricing, go-to-market plan, and competitive positioning. Runs a 4-layer premise audit before strategy, then generates a full market research report with SWOT, 4P, 10-point business model validation, and constraint analysis. Use when the user has an idea and needs a strategic plan, competitive analysis, pricing strategy, GTM plan, or says 'business plan', 'strategy', 'pricing', 'go-to-market', or 'competitive analysis'.
money-outreach
iamzifei/show-me-the-money
Open the skill to read its SKILL.md instructions.
money-finance
iamzifei/show-me-the-money
Open the skill to read its SKILL.md instructions.
Popular business & finance skills
sales-enablement
coreyhaines31/marketingskills
When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'battle card,' 'battlecard,' 'competitive one-pager,' 'win-loss analysis,' 'why are we losing deals,' 'loss reasons,' 'how do I respond to this objection,' 'prospect just said,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps,' 'cold call script,' or 'voicemail script.' Use this for any document or asset that helps a sales team close deals. For public competitor comparison pages, see competitors. For running buyer interviews or churn research, see customer-research. For marketing website copy, see copywriting. For cold outreach emails, see cold-email. For the offer being sold (bonuses, guarantees, pricing structure),
revops
coreyhaines31/marketingskills
When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'outbound pipeline stages,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see emails. For pricing decisions, see pricing.
sales-funnel-blueprint
autonnel/autonnel-skills
Turn an offer into a concrete multi-step sales funnel spec - page-by-page structure, price ladder, copy outline and the metrics each step must hit. Use when asked to build a sales funnel, marketing funnel, landing page flow, lead magnet funnel, webinar funnel, tripwire or VSL funnel, when planning a product launch page flow, or when someone asks "what pages do I need" for selling something online.
pricing
coreyhaines31/marketingskills
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' 'should I offer a free plan,' 'pricing page teardown,' 'pricing page audit,' 'is my pricing page AI-readable,' or 'can AI read my pricing.' Use this whenever someone is figuring out what to charge, how to structure their plans, or wants to audit a pricing page (for humans and for the AI agents that shortlist tools). For in-app upgrade screens, see paywalls. For offer construction (bonuses, guarantees, value framing, naming) on services/courses/coaching/high-ticket B2B, see offers.
cross-border-ecommerce
nexscope-ai/ecommerce-skills
Cross-border e-commerce expansion advisor. Scores target markets on 8 weighted dimensions (market size, ecommerce penetration, competition, regulatory complexity, logistics infrastructure, payment ecosystem, cultural distance, IP protection), compares 5 fulfillment models with cost and transit data, provides country-by-country tax/duty compliance guides (EU VAT/IOSS, UK VAT, US sales tax, CA GST, AU GST, JP consumption tax), maps local payment preferences by market, and builds a phased expansion roadmap. No API key required.
pricing-strategy
coreyhaines31/marketingskills
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' or 'should I offer a free plan.' Use this whenever someone is figuring out what to charge or how to structure their plans. For in-app upgrade screens, see paywall-upgrade-cro.