Produce evidence-based weekly business retros

Produce evidence-based weekly business retrospective

Founders and business owners doing regular business retros grounded in actual disk state (snapshots, learnings, skill usage) rather than memory.

• · Sessions and snapshots for past N days (default 7)
• · Learnings captured in project
• · Skill usage telemetry
• · Optional: revenue data

• · Weekly retro report (decisions, stalled hypotheses, skill usage, recommendations)
• · Comparison to prior retros (trends)
• · Activation candidates (unused but relevant skills)

• · ~/.smtm/sessions/{slug}/ (snapshots with timestamp)
• · ~/.smtm/projects/{slug}/learnings.jsonl (learnings capture)
• · ~/.smtm/analytics/skill-usage.jsonl (telemetry)
• · ~/.smtm/projects/{slug}/retros/ (prior retros for trend)

• · At least one snapshot or learning in the time window
• · ~/.smtm directory structure initialized
• · Regular /money-* skill usage with telemetry enabled

• · No activity in window (no snapshots, learnings, skill usage) → empty retro; honest reporting required
• · Stalled hypotheses misidentified if follow-ups happened but snapshots not captured
• · Skill usage histogram counts calls, not impact; frequent ≠ valuable
• · Revenue data requires manual input; omitted if not provided

• · Four triggers: /money-retro (7 days), --days N (custom window), --slug <project> (different project), --portfolio (all projects)
• · Five data sources: snapshots, learnings, skill usage, prior retros, optional revenue
• · Four-step workflow: aggregate week, identify stalled items, find unused skills, output report
• · Plainly handles empty windows: admits if no activity, does not fabricate narrative
• · Identifies stalled hypotheses (opened ≥14 days ago, no follow-up, no ruling-out learning)
• · References: /money standard skill startup sequence, skill activation recommendations