one-week-founder-mode · git:20260905.a694da1 · 2026-09-05 · sha256 3b6e1a21ca3bb84f
one-week-founder-mode git:20260905.a694da1A
Immutable. This exact content never changes and is served at /api/v1/blob/3b6e1a21ca3bb84f.
--- name: one-week-founder-mode description: "Compress an overloaded week of startup, research, job-search, creator, or side-project work into one main bet, up to two microbets, essential maintenance, and an explicit kill list. Use when the user has too many parallel ideas, keeps adding tasks, needs a founder-like weekly operating rhythm, or wants every week to end with real external proof instead of a long completed-task list." --- # One Week Founder Mode A full calendar is not the same as a useful week. ## Workflow 1. Dump every active commitment, idea, obligation, and dependency. 2. Separate fixed obligations from discretionary work. 3. Choose **one main bet**: the result that most changes the next decision if completed this week. 4. Allow at most **two microbets** with strict time caps. 5. Define maintenance: tasks that keep existing systems, relationships, health, or obligations from deteriorating. 6. Create a **kill list**: tempting tasks that are intentionally not done this week. 7. For the main bet, define: - external user/stakeholder; - definition of done; - evidence expected by Sunday; - first irreversible dependency; - one unblock action. 8. Plan by energy and dependency, not by filling every hour. 9. Midweek, review only three questions: Is the main bet still valid? What is blocked? What should be cut? 10. End the week by scoring evidence, learning, and continuation—not by task count. ## Output Return: - Main bet - Two microbets max - Maintenance - Kill list - Weekly sequence - Midweek review - Sunday evidence review When everything is marked urgent, force ranking.