Inbox Organizer

Turns your inbox into a Rocks dashboard — every thread becomes a Big or Little Rock with tasks, owners, and dates — after an interview that tailors the triage rules to your business and your role.

Build me an Inbox Organizer: a dashboard that triages my inbox threads into **Rocks** (Traction/EOS) and tracks each to completion. Follow the spec below, but do not build anything until you have finished the interview in the last section. ## 1. Model - **Rock**: any task, to-do, or request, from any source. Links to inbox threads and off-platform log entries. - **Size**: Big or Little. System suggests; I can override anytime without losing data. - **Project type**: one of my team's top project types, or "Other". - **Stage**: one Traction stage tag. ## 2. Tasks - Rock → tasks → subtasks, each with optional owner, goal date, deadline. - Types: one-off, recurring (on a schedule), periodic (once per cycle). - States: Open, In progress, Done, Done for this cycle (recurring/periodic only; reopens next cycle). ## 3. Dashboard - **Fetch new emails** button: on demand only. Assigns each new thread to an existing Rock or proposes a new one; unassigned threads are listed as untriaged. - **Log off-platform action** button: records work done elsewhere against an existing or new Rock. - **Filters**: All Rocks | Big Rocks | Little Rocks. Display only. - **Triage rules**: panel on the right, shown on request. ## 4. Rock views - **Big**: large project-management card with tasks, subtasks, owners, goal dates, and deadlines all visible. - **Little**: one row, one checkbox. Full task management available on expand, hidden by default. - **Done / Done for this cycle**: Rock slides into a dimmed, disabled section; restorable. ## 5. Inbox sync - One inbox folder per Rock, named `Rock Name [Stage]`. - Threads are filed into their Rock's folder on triage. - Folder name updates when the Rock's name or stage changes. Threads are never deleted. ## 6. Before you build: interview me Do not build yet. Interview me first so the organizer is specific to my business and my role. Ask one question at a time, follow up where my answer is vague, and offer a default where one is given. 1. **Business**: What does the business do, who are its customers, and what are its current quarterly priorities? 2. **My role**: What is my role, what am I accountable for, and what decisions land on me? 3. **Team**: Who do I work with, and who can own Rocks or tasks? 4. **Request sources**: Who sends me work, through which channels, and which senders or topics matter most? 5. **Project types**: What are my team's top project types? 6. **Triage rules**: What makes a Rock Big vs Little for me? What should be ignored, delegated, or escalated? 7. **Traction stages**: Which stages should tag each Rock? Default: Backlog / On Track / Off Track / Done. 8. **Cycle**: What counts as a cycle for periodic tasks? Default: the 90-day quarter; alternative: set per Rock. 9. **Mail provider**: Which provider, and does it use folders or labels? 10. **Users**: Just me, or do owners need their own logins and views? When the interview is done, summarize my answers, rewrite this spec with them filled in, and wait for my approval before building.