SchedulingCAN I VIBECODE
Clockwise?
BUILD FIRST
- A non-sensitive or read-only version of the core experience
- A manual review step wherever correctness or trust matters
- A narrow companion tool that removes a real piece of work
LEAVE FOR LATER
- Regulated decisions, payments, or irreversible actions
- Claims of correctness, compliance, or uptime that the MVP cannot support
- Sensitive integrations until security, support, and auditability are ready
RESEARCH NOTES
What this tool actually does.
Clockwise is an AI-powered calendar assistant for work schedules. It analyzes multiple calendars to find optimal meeting times, considering individual, team, and company preferences plus working hours. Users mark meetings as flexible; Clockwise automatically reschedules them to create Focus Time and resolve conflicts. Flexible Holds reserve time for routines (lunch, errands) and shift as the calendar changes. It offers scheduling links for external meetings, group scheduling that aggregates team availability, and round-robin meeting assignment. The AI Calendar (Prism) provides a chat and drag-and-click interface to book, modify, or cancel events using natural language. Integrations include Slack: schedule from Slack, sync meeting status, and mute notifications. It connects via Google OAuth, with TLS/AES encryption.
RESEARCHED BUILD PROMPT
Give this to your coding agent.
Build a replacement for Clockwise, an AI scheduling assistant that automates calendar optimization. Core workflow: after OAuth connection to Google Calendar, the app ingests all events, asks the user to mark meetings as 'flexible' or 'fixed', and continuously simulates rearrangements to protect Focus Time, working hours, and personal holds (lunch, errands). It must expose a chat panel plus drag-and-click calendar UI where users can type 'find 30 min for 5 people tomorrow' or drag a meeting to propose a move, then approve or reject automatic rescheduling. Requirements: (1) Google Calendar API integration with OAuth 2.0; (2) an optimization engine that scores candidate times based on user-set preferences (Focus Time length, working hours, flexible/fixed flags, travel gaps); (3) auto-apply or propose reschedules with undo; (4) scheduling links that show optimized availability based on preferences; (5) group scheduling that checks multiple users' calendars; (6) Slack slash-command or message action to create/reschedule meetings and mute notifications; (7) a persistence layer for user prefs and event flags. Implementation approach: Node.js/Python backend, React frontend with a fullcalendar.io-style grid, PostgreSQL for state, a rule-based or MILP scheduler (e.g., OR-Tools) for repositioning, and WebSocket for live updates. Explicitly do not copy Clockwise's brand, logo, or exact UI layout. Out of scope: mobile apps, billing, SSR, calendar providers beyond Google, and ML-based natural-language understanding beyond intent extraction. Include a README covering setup (OAuth credentials, Slack app config, DB migration) and known limitations (single-provider support, basic NLU, no conflict-resolution guarantees).