What Should We Do?

**Judgement:** A well-designed, feature-rich activity planner that turns vague boredom into concrete, highly contextual plans. It’s strongest when used regularly by the same person or groups so it can leverage preferences, routines, and history. **Key strengths** - Uses time, calendar, weather, routines, and past behavior to give one confident suggestion instead of long option lists. - Handles both out-of-home (restaurants, movies, local venues) and at-home (streaming, board/card/video games) scenarios. - Thoughtful group modeling (contacts, dietary/alcohol preferences, group sizes) and RSVP tracking make it good for recurring social circles. - Clear separation of logic and data (`skills/whatdo/` vs `data/whatdo/`) supports safe updates and persistent personalization. **Main risks / limitations** - Heavy reliance on web search and external APIs (weather, Google Places, movie showtimes, Google Calendar) can introduce flaky behavior if those services change or rate-limit. - No explicit mention of robust error handling or schema migration for the JSON data files; corruption or format drift could degrade reliability. - Alcohol and adventure/outdoor suggestions aren’t paired with strong safety checks (e.g., no explicit guidance about transportation, local hazards, or age-related constraints). - Google Calendar focus and optional Google Places mean the “full” experience is best where those services are available and configured. **Best-fit scenarios** - Users or small friend groups who frequently say “we’re bored, what should we do?” and are willing to let the system learn their preferences over time. - Regular date nights or standing social routines (game nights, Taco Tuesday, First Friday, seasonal traditions) where context and history matter. - People who like concrete, do-now suggestions more than browsing long lists of venues or activities.