MindPalaceX · The Workshop
The Idea Wall →

On the Idea Wall · ▲ 0 votes

ClearDay — the spec

ClearDay is an AI agent that takes the chaos out of everyday work for people who are too busy to stay organized. A user dumps a messy task or goal in plain language; ClearDay automatically decomposes it, ranks it, schedules it, and handles the booking and communication legwork — so the user's calendar fills itself and their inbox stops running their day.

---

Decisions locked

QuestionAnswer
ShapeAI agent / automation
AudienceConsumers — everyday people managing personal and work tasks
Core loopUser describes a messy task → AI breaks it into steps → steps get scheduled and tracked automatically
One success metric after 30 daysBookings happen without the user touching them

---

The core loop

  1. Dump — User types or pastes a messy task, goal, or block of email into ClearDay in plain language.
  2. Decompose — The AI breaks the input into concrete subtasks with estimated durations.
  3. Rank — ClearDay generates a priority-ranked daily list, surfacing the highest-leverage items first.
  4. Schedule — Open calendar slots are matched to subtasks; bookings and invites are created automatically.
  5. Sync — Connected email and apps receive any necessary follow-ups or confirmations without user intervention.
  6. Track — As subtasks are completed, ClearDay logs the pattern and adjusts tomorrow's list accordingly.

---

v1 scope

Task decomposition engine — Accepts a free-text task description and returns a structured subtask list with time estimates. Lives on the main task-entry screen.

Auto-generated daily priority list — Every morning, ClearDay compiles open subtasks into a ranked, time-boxed agenda. Lives on the dashboard home screen.

Calendar scheduling — Maps subtasks to available calendar slots and writes events directly, no manual drag-and-drop required. Lives in the scheduling panel, linked from each task card.

Completion tracking and pattern suggestions — Records which tasks get done, skipped, or rescheduled, then surfaces patterns ("You clear admin tasks best before 10 am"). Lives on the insights strip on the dashboard.

Email and app integrations — Connects to email and third-party apps to send confirmations, pull in context, and trigger follow-up actions automatically. Configured in the integrations settings screen.

---

Deliberately later

  • Learns priorities from past choices — requires enough historical data to be meaningful; accuracy improves significantly after the first 60–90 days of usage, making v2 the right entry point.
  • Explains reasoning for recommendations — valuable trust-builder, but reasoning UI adds scope to the core agent before the scheduling loop is stable; ship explainability once the output quality warrants it.
  • Bulk-moves recurring tasks to templates — a power-user workflow best introduced after enough users have accumulated repeating task patterns to validate the template format.

---

Data model sketch

  • users — id, name, email, timezone, onboarding_completed_at, integration_tokens
  • tasks — id, user_id, raw_input, title, status, priority_score, due_date, created_at
  • subtasks — id, task_id, title, duration_estimate_mins, status, completed_at, sequence_order
  • calendar_events — id, user_id, subtask_id, external_event_id, start_at, end_at, provider, booking_status
  • integrations — id, user_id, provider (email/calendar/app), access_token, refresh_token, scopes, last_synced_at
  • daily_priority_lists — id, user_id, date, ranked_subtask_ids (ordered array), generated_at
  • completion_logs — id, subtask_id, user_id, outcome (done/skipped/rescheduled), logged_at
  • file_uploads — id, user_id, task_id, filename, storage_url, uploaded_at

---

Screens

  • Dashboard — ranked daily priority list plus the completion-pattern insights strip; the user's starting point each morning.
  • Task entry — free-text input field where the user dumps a task or goal; triggers decomposition immediately.
  • Task detail — shows the full subtask breakdown, editable fields, and scheduling status for a single task.
  • Scheduling panel — displays calendar availability, confirms auto-scheduled slots, and surfaces any conflicts.
  • Integrations settings — connects and manages email, calendar, and third-party app credentials.
  • User account — timezone, notification preferences, and subscription or plan status.

---

How to use this document

  • Bring it into Mind Palace, where the guided platform and its AI coach pick up from exactly this document and build ClearDay with you step by step.
  • Hand it to a developer as the complete v1 brief — scope, data model, and screens are defined and ready to execute.
  • Keep it as the single source of truth while you build, so every feature decision stays anchored to the core loop and the 30-day success metric.

This is Bukola's. Build yours.

A spec like this is step 3 of Mind Palace's nine — the other six take a weekend: working software, a real offer, first customers.

Want to build this with Bukola?

Tell us who you are and we'll broker the introduction — their contact details stay private until they say yes.