money-retro

Consolidate weekly project data into an evidence-based retro markdown file.

799|127|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/iamzifei/show-me-the-money --skill money-retro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: money-retro
Source: https://github.com/iamzifei/show-me-the-money/tree/main/skills/money-retro
Command: npx skills add https://github.com/iamzifei/show-me-the-money --skill money-retro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly retros help founders convert scattered weekly data into actionable insights, surfacing decisions, progress, and focus for the next week.

Core Features & Use Cases

  • Aggregates weekly project data from local stores to generate a concise, evidence-based retro.
  • Identifies decisions made, items that stalled, and surface activation prompts for the next sprint.
  • Writes a retro markdown file under the project's retros directory to keep a longitudinal record.

Quick Start

Run /money-retro at the end of the week to generate a data-backed retro.

Frequently Asked Questions about money-retro

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate weekly retrospectives for my startup project?

Weekly retrospectives aggregate project snapshots, learnings, and telemetry into a markdown file, surfacing decisions and progress. This helps founders convert scattered weekly data into actionable insights for the next sprint.

How do I generate a data-backed retro from snapshots and telemetry?

A data-backed retro aggregates local project snapshots, learnings, and telemetry over a 7-day window to compute decisions and trends. It then writes a new retro markdown file under the project's retros directory.

Can I use automated retrospectives for a solo founder workflow?

Automated retrospectives apply directly to solo founders reviewing project snapshots and learnings. The process aggregates weekly local data to surface decisions, stalled items, and activation prompts without requiring a team.

What do I need to generate a weekly project retro from local data?

Generating a weekly project retro requires disk-based stores of snapshots, learnings, and telemetry under your project directory. It processes these local files over a 7-day window to output a longitudinal markdown record.

How does a weekly retro identify what stalled and what to focus on next?

A weekly retro identifies stalled items and next focus areas by computing decisions and trends from project telemetry and learnings. It surfaces activation prompts for the next sprint directly within the generated markdown file.