← fstackCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to fstack
Snapshot Sep 30, 2026 · 23:16 UTC · version 1.1.2
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Weekly founder momentum, engineering velocity, customer feedback, and tech debt review. Keeps founders honest about real progress vs busywork. Use for /retro, \"weekly review\", or team retrospective.",
"included_files": [],
"name": "retro",
"skill_md_contents": "---\nname: retro\ndescription: Weekly founder momentum, engineering velocity, customer feedback, and tech debt review. Keeps founders honest about real progress vs busywork. Use for /retro, \"weekly review\", or team retrospective.\nmenu-description: weekly founder retrospective on momentum, customer reality, and debt\n---\n\n# Founder Retrospective (The Weekly Reality Check)\n\nIt is easy for a founder to feel exhausted on Friday without having moved the business forward. Answering emails, tweaking CSS, and refactoring working code feels like work, but often produces zero user value.\n\n`retro` is a fast, 15-minute weekly checkpoint that audits momentum, customer feedback, accumulated debt, and aligns next week's focus.\n\n---\n\n## When to Invoke\n\n- Every Friday afternoon or Monday morning.\n- At the conclusion of an intense sprint or major launch.\n\n---\n\n## The 4 Audit Sections\n\n### 1. Velocity: What Actually Shipped?\n- Scan git commits and PRs over the last 7 days.\n- Group into:\n - Customer-facing capabilities (Things users noticed).\n - Internal infrastructure / refactors.\n - Bug fixes.\n- **The Honest Ratio**: If customer-facing capabilities were < 40% of the week's output, diagnose why.\n\n### 2. User Reality: What Did Customers Actually Do?\n- What was the qualitative feedback from users/prospects this week?\n- Where did users get stuck or complain?\n- Did any metric move (signups, active runs, revenue, retention)?\n\n### 3. Debt & Slop Audit: What Corners Did We Cut?\n- Check for temporary hacks, missing tests, or unhandled edge cases introduced during fast shipping.\n- Did we add any unnecessary dependencies or layers?\n- Can we delete 200 lines of dead code right now?\n\n### 4. Next Week's Single Needle-Mover:\n- What is the **one thing** that, if accomplished next week, makes everything else easier or unnecessary?\n- Explicitly list 3 things you will **NOT** do next week to protect focus.\n\n---\n\n## The Retro Output Template\n\n```markdown\n# 🏁 Weekly Founder Retro: Week Ending [Date]\n\n### 📦 What Shipped\n1. [Feature 1]: Parallel worker execution (`v1.4.0`).\n2. [Fix 1]: Resolved CSV parsing edge case for customer Acme.\n3. [Doc 1]: Published interactive GEO comparison guide.\n\n### 👥 Customer Reality\n- 3 new paying accounts onboarded.\n- Primary complaint: API documentation was missing TypeScript examples.\n- Inbound interest: 4 qualified inbound leads from X announcement post.\n\n### 🧹 Tech Debt & Simplification\n- Stale branches pruned.\n- Deleted unused legacy analytics script (`-140 LOC`).\n- Open debt item: Add integration tests for OAuth token refresh edge case.\n\n### 🎯 Next Week's Focus\n- **The #1 Needle-Mover**: Ship self-serve Stripe customer portal to unblock annual plan upgrades.\n- **Explicit Anti-Goals (Will NOT do)**:\n - Will not redesign the landing page nav.\n - Will not build Discord notifications until 5 users ask for it.\n```\n"
}SHA-256 of public snapshot: cadcc4651762a2a58b93b0ca90d78fce62af0dae4b91a95b8e7478c95f8489de