{
  "source_file": "0930",
  "source_platform": "Medium",
  "author": "Ivo Bernardo",
  "title_listed": "Building My Own Personal AI Assistant: A Chronicle, Part 2",
  "keywords": "",
  "domain": "大模型算法",
  "content_type": "深度技术解析",
  "is_paid_flag": "否",
  "url": "https://towardsdatascience.com/building-my-own-personal-ai-assistant-a-chronicle-part-2/",
  "publish_date": "2026-04-16",
  "corpus_stage": "",
  "notes": "",
  "id": "bf47253b2fbd",
  "collected_at": "2026-10-02T05:33:22",
  "title": "Building My Own Personal AI Assistant: A Chronicle, Part 2 | Towards Data Science",
  "body_markdown": "![Revisit consent button](../images/body-df29beacd7496220cc94.svg)\nWe value your privacy\nWe use cookies to enhance your browsing experience, serve personalised ads or content, and analyse our traffic. By clicking \"Accept All\", you consent to our use of cookies.\nCustomise Reject All Accept All\nCustomise Consent Preferences ![](../images/body-2159bb67f3de8ad870eb.svg)\nWe use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.\nThe cookies that are categorised as \"Necessary\" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... Show more\nNecessaryAlways Active\nNecessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.\n  * Cookie\nBCTempID\n  * Duration\n10 minutes\n  * Description\nNo description available.\n\n\n  * Cookie\n__cf_bm\n  * Duration\n1 hour\n  * Description\nThis cookie, set by Cloudflare, is used to support Cloudflare Bot Management. \n\n\n  * Cookie\nAWSALBCORS\n  * Duration\n7 days\n  * Description\nAmazon Web Services set this cookie for load balancing.\n\n\n  * Cookie\n_cfuvid\n  * Duration\nsession\n  * Description\nCloudflare sets this cookie to track users across sessions to optimize user experience by maintaining session consistency and providing personalized services\n\n\n  * Cookie\nli_gc\n  * Duration\n6 months\n  * Description\nLinkedin set this cookie for storing visitor's consent regarding using cookies for non-essential purposes.\n\n\n  * Cookie\n__hssrc\n  * Duration\nsession\n  * Description\nThis cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session.\n\n\n  * Cookie\n__hssc\n  * Duration\n1 hour\n  * Description\nHubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie.\n\n\n  * Cookie\nwpEmojiSettingsSupports\n  * Duration\nsession\n  * Description\nWordPress sets this cookie when a user interacts with emojis on a WordPress site. It helps determine if the user's browser can display emojis properly.\n\n\n  * Cookie\nBCSessionID\n  * Duration\n1 year 1 month 4 days\n  * Description\nBlueconic sets this cookie as a unique identifier for the BlueConic profile.\n\n\n  * Cookie\n_octo\n  * Duration\n1 year\n  * Description\nNo description available.\n\n\n  * Cookie\nlogged_in\n  * Duration\n1 year\n  * Description\nNo description available.\n\n\n  * Cookie\n__Secure-YEC\n  * Duration\npast\n  * Description\nYouTube sets this cookie to stores the user's video player preferences using embedded YouTube video\n\n\n  * Cookie\n__eoi\n  * Duration\n6 months\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nAWSALBTGCORS\n  * Duration\n7 days\n  * Description\nNo description available.\n\n\n  * Cookie\nlogin-status-p\n  * Duration\npast\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nAWSALBTG\n  * Duration\n7 days\n  * Description\nNo description available.\n\n\n  * Cookie\ncsrf_token\n  * Duration\nsession\n  * Description\nNo description available.\n\n\n  * Cookie\ntoken_v2\n  * Duration\n1 day\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nD\n  * Duration\n1 year\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nPHPSESSID\n  * Duration\nsession\n  * Description\nThis cookie is native to PHP applications. The cookie stores and identifies a user's unique session ID to manage user sessions on the website. The cookie is a session cookie and will be deleted when all the browser windows are closed.\n\n\n  * Cookie\nVISITOR_PRIVACY_METADATA\n  * Duration\n6 months\n  * Description\nYouTube sets this cookie to store the user's cookie consent state for the current domain. \n\n\n  * Cookie\ncookietest\n  * Duration\nsession\n  * Description\nThe cookietest cookie is typically used to determine whether the user's browser accepts cookies, essential for website functionality and user experience.\n\n\n  * Cookie\n__Host-airtable-session\n  * Duration\n1 year\n  * Description\nThis cookie is used to enable us to integrate the services of Airtable.\n\n\n  * Cookie\n__Host-airtable-session.sig\n  * Duration\n1 year\n  * Description\nThis cookie is used to enable us to integrate the services of Airtable.\n\n\n  * Cookie\nm\n  * Duration\n1 year 1 month 4 days\n  * Description\nStripe sets this cookie for fraud prevention purposes. It identifies the device used to access the website, allowing the website to be formatted accordingly.\n\n\n  * Cookie\nBIGipServer*\n  * Duration\nsession\n  * Description\nMarketo sets this cookie to collect information about the user's online activity and build a profile about their interests to provide advertisements relevant to the user. \n\n\n  * Cookie\n__cfruid\n  * Duration\nsession\n  * Description\nCloudflare sets this cookie to identify trusted web traffic.\n\n\n  * Cookie\n_GRECAPTCHA\n  * Duration\n6 months\n  * Description\nGoogle Recaptcha service sets this cookie to identify bots to protect the website against malicious spam attacks.\n\n\n  * Cookie\n__Secure-YNID\n  * Duration\n6 months\n  * Description\nGoogle cookie used to protect user security and prevent fraud, especially during the login process.\n\n\n  * Cookie\ncookieyes-consent\n  * Duration\n1 year\n  * Description\nCookieYes sets this cookie to remember users' consent preferences so that their preferences are respected on subsequent visits to this site. It does not collect or store any personal information about the site visitors.\n\n\nFunctional\nFunctional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.\n  * Cookie\nlidc\n  * Duration\n1 day\n  * Description\nLinkedIn sets the lidc cookie to facilitate data center selection.\n\n\n  * Cookie\nbrw\n  * Duration\n1 year\n  * Description\nNo description available.\n\n\n  * Cookie\nbrwConsent\n  * Duration\n5 minutes\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nWMF-Uniq\n  * Duration\n1 year\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nloom_anon_comment\n  * Duration\n1 year\n  * Description\nNo description available.\n\n\n  * Cookie\nloom_referral_video\n  * Duration\nsession\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nVISITOR_INFO1_LIVE\n  * Duration\n6 months\n  * Description\nA cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface.\n\n\n  * Cookie\nyt-remote-connected-devices\n  * Duration\nNever Expires\n  * Description\nYouTube sets this cookie to store the user's video preferences using embedded YouTube videos.\n\n\n  * Cookie\nytidb::LAST_RESULT_ENTRY_KEY\n  * Duration\nNever Expires\n  * Description\nThe cookie ytidb::LAST_RESULT_ENTRY_KEY is used by YouTube to store the last search result entry that was clicked by the user. This information is used to improve the user experience by providing more relevant search results in the future.\n\n\n  * Cookie\nyt-remote-device-id\n  * Duration\nNever Expires\n  * Description\nYouTube sets this cookie to store the user's video preferences using embedded YouTube videos.\n\n\n  * Cookie\nyt-remote-session-name\n  * Duration\nsession\n  * Description\nThe yt-remote-session-name cookie is used by YouTube to store the user's video player preferences using embedded YouTube video.\n\n\n  * Cookie\nyt-remote-fast-check-period\n  * Duration\nsession\n  * Description\nThe yt-remote-fast-check-period cookie is used by YouTube to store the user's video player preferences for embedded YouTube videos.\n\n\n  * Cookie\nyt-remote-session-app\n  * Duration\nsession\n  * Description\nThe yt-remote-session-app cookie is used by YouTube to store user preferences and information about the interface of the embedded YouTube video player.\n\n\n  * Cookie\nyt-remote-cast-available\n  * Duration\nsession\n  * Description\nThe yt-remote-cast-available cookie is used to store the user's preferences regarding whether casting is available on their YouTube video player.\n\n\n  * Cookie\nyt-remote-cast-installed\n  * Duration\nsession\n  * Description\nThe yt-remote-cast-installed cookie is used to store the user's video player preferences using embedded YouTube video.\n\n\n  * Cookie\ncp_session\n  * Duration\n3 months\n  * Description\nCodepen sets this cookie for Help systems found in the website.\n\n\n  * Cookie\nloid\n  * Duration\n1 year 1 month 4 days\n  * Description\nThis cookie is set by the Reddit. The cookie enables the sharing of content from the website onto the social media platform.\n\n\nAnalytics\nAnalytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.\n  * Cookie\n__hstc\n  * Duration\n6 months\n  * Description\nHubspot set this main cookie for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session).\n\n\n  * Cookie\nhubspotutk\n  * Duration\n6 months\n  * Description\nHubSpot sets this cookie to keep track of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts.\n\n\n  * Cookie\n_ga\n  * Duration\n1 year 1 month 4 days\n  * Description\nGoogle Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors.\n\n\n  * Cookie\n_ga_*\n  * Duration\n1 year 1 month 4 days\n  * Description\nGoogle Analytics sets this cookie to store and count page views.\n\n\n  * Cookie\n__Host-psifi.analyticsTrace\n  * Duration\n6 hours\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\n__Host-psifi.analyticsTraceV2\n  * Duration\n6 hours\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\n_gh_sess\n  * Duration\nsession\n  * Description\nGitHub sets this cookie for temporary application and framework state between pages like what step the user is on in a multiple step form.\n\n\n  * Cookie\nYSC\n  * Duration\nsession\n  * Description\nYSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages.\n\n\n  * Cookie\najs_anonymous_id\n  * Duration\n1 year\n  * Description\nThis cookie is set by Segment to count the number of people who visit a certain site by tracking if they have visited before.\n\n\n  * Cookie\nvuid\n  * Duration\n1 year 1 month 4 days\n  * Description\nVimeo installs this cookie to collect tracking information by setting a unique ID to embed videos on the website. \n\n\nPerformance\nPerformance cookies are used to understand and analyse the key performance indexes of the website which helps in delivering a better user experience for the visitors.\n  * Cookie\nAWSALB\n  * Duration\n7 days\n  * Description\nAWSALB is an application load balancer cookie set by Amazon Web Services to map the session to the target.\n\n\n  * Cookie\nacq\n  * Duration\npast\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nacq.sig\n  * Duration\npast\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nptc\n  * Duration\n2 years\n  * Description\nNo description available.\n\n\nAdvertisement\nAdvertisement cookies are used to provide visitors with customised advertisements based on the pages you visited previously and to analyse the effectiveness of the ad campaigns.\n  * Cookie\nmuc_ads\n  * Duration\n1 year 1 month 4 days\n  * Description\nTwitter sets this cookie to collect user behaviour and interaction data to optimize the website.\n\n\n  * Cookie\nguest_id_marketing\n  * Duration\n1 year 1 month 4 days\n  * Description\nTwitter sets this cookie to identify and track the website visitor.\n\n\n  * Cookie\nguest_id_ads\n  * Duration\n1 year 1 month 4 days\n  * Description\nTwitter sets this cookie to identify and track the website visitor.\n\n\n  * Cookie\npersonalization_id\n  * Duration\n1 year 1 month 4 days\n  * Description\nTwitter sets this cookie to integrate and share features for social media and also store information about how the user uses the website, for tracking and targeting.\n\n\n  * Cookie\nguest_id\n  * Duration\n1 year 1 month 4 days\n  * Description\nTwitter sets this cookie to identify and track the website visitor. It registers if a user is signed in to the Twitter platform and collects information about ad preferences.\n\n\n  * Cookie\nbcookie\n  * Duration\n1 year\n  * Description\nLinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser IDs.\n\n\n  * Cookie\n__Secure-ROLLOUT_TOKEN\n  * Duration\n6 months\n  * Description\nYouTube sets this cookie to manage feature rollout and experimentation. It helps Google control which new features or interface changes are shown to users as part of testing and staged rollouts, ensuring consistent experience for a given user during an experiment.\n\n\n  * Cookie\nyt.innertube::nextId\n  * Duration\nNever Expires\n  * Description\nYouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen.\n\n\n  * Cookie\nyt.innertube::requests\n  * Duration\nNever Expires\n  * Description\nYouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen.\n\n\n  * Cookie\nsession_tracker\n  * Duration\nsession\n  * Description\nThis cookie is set by the Reddit. This cookie is used to identify trusted web traffic. It also helps in adverstising on the website.\n\n\n  * Cookie\nedgebucket\n  * Duration\nsession\n  * Description\nReddit sets this cookie to save the information about a log-on Reddit user, for the purpose of advertisement recommendations and updating the content.\n\n\n  * Cookie\ndid\n  * Duration\n1 year\n  * Description\nArbor sets this cookie to show targeted ads to site visitors.This cookie expires after 2 months or 1 year.\n\n\nUncategorised\nOther uncategorised cookies are those that are being analysed and have not been classified into a category as yet.\nNo cookies to display.\nReject All Save My Preferences Accept All\nToggle Search[](https://towardsdatascience.com/)Toggle Mobile Navigation\n[](https://towardsdatascience.com/)\nPublish AI, ML & data-science insights to a global community of data professionals.\nSign in[Submit an Article](https://write.insightmediagroup.io)\n[Latest](https://towardsdatascience.com/latest/)[Editor's Picks](https://towardsdatascience.com/tag/editors-pick/)[Newsletter](https://towardsdatascience.com/tag/the-variable/)[ShipAI](https://towardsdatascience.com/shipai/)\n* * *\n[Write For TDS](https://towardsdatascience.com/submissions/)\n[LinkedIn](https://www.linkedin.com/company/towards-data-science/)[X](https://x.com/TDataScience)Toggle Search\n[Agentic AI](https://towardsdatascience.com/category/artificial-intelligence/agentic-ai/)\n# Building My Own Personal AI Assistant: A Chronicle, Part 2\nImproving Fernão: Building a personal AI assistant is rarely a single, monolithic effort\n[Ivo Bernardo](https://towardsdatascience.com/author/ivopbernardo/)\nApril 16, 20268 min read\n![](../images/000.jpg)\nYou probably remember the [first part of my journey](https://towardsdatascience.com/building-a-personal-ai-agent-in-a-couple-of-hours/) building _Fernão_ , my personal AI agent. Now it’s time to continue the story and let’s dive into the second part!\nIn this post, I’ll walk you through the latest improvements to _Fernão_ , refining existing features and adding new capabilities to the agent. Let’s start with what changed.\n···\nRemember the function that fetched the calendar through ICS (the universal calendar format) and extracted my calendar tasks?\nThat function was a mess and it reflected a poor architectural decision. ICS calendars don’t support native filtering, which means every request required pulling all events from the calendar and filtering them afterward. In practice,  _Fernão_ was downloading my entire schedule just to extract a few relevant meetings.\nLearn this step by step with the interactive [AI Agents](https://roadmap.sh/ai-agents) roadmap.\nThis was like bringing home an entire library just to look up a single sentence in one book.\nThe more I tried to optimize the function, the less I would get anywhere, because I needed a new system solution. I needed to change the way the system was getting the calendar and I would NEVER get around this bottleneck with ICS.\nSo I dug deeper and found that Google provides calendar access through an API that supports native filtering. _Fernão_ now only retrieves the events it actually needs. This improved the schedule generation, that dropped from nearly five minutes to about twenty seconds.\nWith this new pipeline in place, I also refactored the surrounding logic. The entire function is now significantly cleaner and faster. We now have a beautiful way to fetch the calendar events via API:\npython\n\n```\ndef get_events_for_date(target_date=None, use_api=True):\n    \"\"\"\n    Fetches events for a specific date from Google Calendar.\n    Tries API first (if use_api=True), falls back to ICS if API fails.\n    \n    Args:\n        target_date: datetime.date object for the target day. If None, uses today.\n        use_api: If True, try Google Calendar API first. If False, use ICS only.\n    \n    Returns:\n        List of event dictionaries.\n    \"\"\"\n    if use_api and GCAL_API_AVAILABLE:\n        print(\"[GCal] Attempting to use Google Calendar API...\")\n        try:\n            events = get_events_for_date_api(target_date)\n            if events is not None:\n                print(f\"[GCal] Successfully fetched {len(events)} events via API\")\n                return events\n            else:\n                print(\"[GCal] API returned None. Falling back to ICS...\")\n        except Exception as e:\n            print(f\"[GCal] API failed with error: {e}\")\n            print(\"[GCal] Falling back to ICS...\")\n    \n    # Fallback to ICS\n    print(\"[GCal] Using ICS feed method...\")\n    return get_events_for_date_ics(target_date)\n```\n\n.. and here is our API fetch:\npython\n\n```\ndef get_events_for_date_api(target_date=None):\n    \"\"\"\n    Fetches events for a specific date from Google Calendar using the Calendar API.\n    \n    Args:\n        target_date: datetime.date object for the target day. If None, uses today.\n    \n    Returns:\n        List of event dictionaries, or None if API call fails.\n    \"\"\"\n    service = get_calendar_service()\n    if not service:\n        return None\n    \n    day_start, day_end, target_date, tz_name, local = _get_local_time_range(target_date)\n    \n    print(f\"\\n[GCal API] Fetching events for {target_date.strftime('%Y-%m-%d')}\")\n    print(f\"  Timezone: {tz_name}\")\n    \n    # Get calendar IDs from environment, or use primary\n    calendar_ids_str = os.getenv('GCAL_CALENDAR_IDS', '')\n    if calendar_ids_str:\n        calendar_ids = [cid.strip() for cid in calendar_ids_str.split(',')]\n    else:\n        calendar_ids = ['primary']\n    \n    all_events = []\n    \n    # Fetch from each calendar\n    for calendar_id in calendar_ids:\n        try:\n            print(f\"[GCal API] Fetching from calendar: {calendar_id}\")\n            \n            # Call the Calendar API with timeoutlobally\n            old_timeout = socket.getdefaulttimeout()\n            socket.setdefaulttimeout(10)\n            \n            try:\n                events_result = service.events().list(\n                    calendarId=calendar_id,\n                    timeMin=day_start.isoformat(),\n                    timeMax=day_end.isoformat(),\n                    singleEvents=True,\n                    orderBy='startTime'\n                ).execute()\n            finally:\n                socket.setdefaulttimeout(old_timeout)\n            \n            events = events_result.get('items', [])\n            print(f\"[GCal API] Found {len(events)} event(s) in {calendar_id}\")\n            \n            # Parse events\n            for event in events:\n                # Get start time\n                start = event['start'].get('dateTime', event['start'].get('date'))\n                end = event['end'].get('dateTime', event['end'].get('date'))\n                \n                # Parse datetime\n                if 'T' in start:  # DateTime\n                    start_dt = datetime.fromisoformat(start.replace('Z', '+00:00'))\n                    end_dt = datetime.fromisoformat(end.replace('Z', '+00:00'))\n                    \n                    # Convert to local timezone\n                    start_local = start_dt.astimezone(local)\n                    end_local = end_dt.astimezone(local)\n                    \n                    start_str = start_local.strftime(\"%H:%M\")\n                    end_str = end_local.strftime(\"%H:%M\")\n                else:  # All-day event\n                    start_str = \"00:00\"\n                    end_str = \"23:59\"\n                \n                all_events.append({\n                    \"title\": event.get('summary', 'Untitled Event'),\n                    \"start\": start_str,\n                    \"end\": end_str,\n                    \"location\": event.get('location', ''),\n                    \"description\": event.get('description', '')\n                })\n        \n        except Exception as e:\n            print(f\"[GCal API] Error fetching from {calendar_id}: {e}\")\n            continue\n    \n    # Sort by start time\n    all_events.sort(key=lambda x: x[\"start\"])\n    \n    print(f\"[GCal API] Total events: {len(all_events)}\")\n    return all_events\n```\n\nBeyond the back-end improvements, I’ve also added new features to the assistant.\nIn the schedule view, I can now mark tasks as completed. The cool thing is that and when I do it, they’re automatically synced with _Microsoft To-Do app_.\n![](../images/001.png)\nChecking tasks in the App - Image by Author\n![](../images/body-446199773e5859285f61.png)\nChecking tasks in the App - Image by Author\nMarvelous!\nIt makes me think that, over time, many of us will end up building our own “personal operating systems”, assembling workflows from our preferred tools, integrating what we need, and replacing components whenever better options appear. If features become easy to replicate, loyalty to specific platforms will weaken.\nThis also raises an interesting question: will companies eventually try to lock down their systems by restricting APIs and external integrations? Possibly. But isolating themselves is unlikely to work in the long run. If users can’t connect tools to their own workflows, they’ll simply move elsewhere (… and will this be a behavior only done by power users?)\nWith this new capability in the Schedule Maker, I went on to implement another feature for _Fernão_ , suggested by one of the readers.\nIntroducing: _**the Task Breaker.**_\n![](../images/body-4b7e4534602f2a4f1d68.png)\nThe new Fernão role is to break tasks - Image by Author - Generated by Gemini\n···\nThe _**Task Breaker**_ follows a simple workflow:\n  * Start with a large, generic task in _Microsoft To Do_ ;\n  * Add context on how the task should be broken down;\n  * Fernão decomposes the task and builds a plan;\n  * The resulting tasks are saved back to To-Do with due dates, and later appear in the daily assistant;\n\n\n![](../images/body-02138c0e1d1567f8eb2f.png)\nFernão Task Breaker - Image by Author\nHere’s how the Task Breaker appears in the sidebar:\n![](../images/body-df141b636285eec363c6.png)\nTask Breaker Module - Image by Author\nAnd here’s the current (still rough) front end for the _Task Breaker_ :\n![](../images/body-afba01a3a9d8fe0eec56.png)\nTask Breaker Module - Image by Author\nLet’s take a real example. One of the larger tasks sitting in my To Do list is **“** _Project Documentation at DareData._**”** This isn’t a small operational task, it’s a structural project.\nThe goal is to consolidate and formalize the internal knowledge of the company in Notion, making sure the main questions about the enterprise are clearly answered in our _Knowledge Hub_. That means reviewing every department, identifying gaps, creating or refining pages, structuring information properly, and assigning clear ownership for each section.\nIn practice, this requires auditing, writing, and governance decisions. It’s not something you “just do” in one sitting and I want to complete this within three weeks. Realistically, I can dedicate between 30 minutes to one hour per day.\nThis is exactly the kind of task that benefits from decomposition, so I’ll use some context information in the Task Breaker and turn this giga-task into an actionable plan:\nmarkup\n\n```\nI’m currently building our Knowledge Hub in Notion. Here’s the current structure of Notion and Departments:# DareData Hub## Handbook for Network Members[DareData Network Member Handbook ]## Teams### Sales & Partnerships### Marketing (Brand and Gen-OS)### Finance### Delivery[Tech Specialists][Principals][Account Managers]I’ll need to:- Go Through Every department and create the pages that make sense (search the web for more context on what DareData is if you need ideas of the pages I need to create on every department or use your knowledge on what definitely needs to be documented in a 130 people B2B company).- Make sure that every page has an Owner- Revisit the Suggestions recorded by my team in the suggestions, I can probably pick one or two suggestions every day- Add some departments that are not in there: Admin, Core Members, Finance, ProductI have around 30 minutes to 1 hour to work every day and want to complete this project by 7 March 2026.\n```\n\nAfter hitting \"breakdown\", _Fernão_ will start to forge:\n![](../images/body-6b75a39ed4650fb69f0d.png)\nFernão Forging the Task - Image by Author\nMarvelous x2!\n![](../images/body-ba5d831b929bb1bebed0.png)\nTask Breakdown - Image by Author\nWe can now review the tasks and plan generated and submit them to my Microsoft To-Do. I also need to assign which list on Microsoft To-Do they will be assigned to:\n![](../images/body-6a99906db2dc2f81dc79.png)\nDestination List in Microsoft To-Do - Image by Author  \n\nCool! Let’s see how it looks in Microsoft app:\n![](../images/body-3e77dcfb8f9884f6dcea.png)\nPerfecto.\nWhile testing this, I realised I want to adjust two things.\n  * First, _Fernão_ is meant to be a medieval chronicler, not a fantasy warrior, so I’ll change the forging design. His clothing should feel medieval.\n\n\n  * Second, on a more practical note, I need a “ _Submit All_ ” button. Submitting tasks one by one is tedious, especially when breaking down larger projects.\n\n\nLet's break another task after making these changes:\n![](../images/body-36e5de7bf7365ce45ad5.png)\n_Fernão_ now forges in a proper medieval vest:\n![](../images/body-0267183be79d97edf9da.png)\nFernão is forging again - Image by Author\nAnd now we can also use the nice “ _Submit All_ ” button:\n![](../images/body-f2e4e271c316b0b366bd.png)\nSubmit new tasks in To-Do - Image by Author\nI’ll likely remove the emoji. That kind of “ _emojification_ ” is very typical of LLM-generated code in the front-end, and it really annoys me.\nAnyway, building this new feature for _Fernão_ was genuinely satisfying. If you have ideas for additional features, I’m open to suggestions!\nBelow is the current prompt I’m using for task breakdown. I’ll continue refining it as I experiment and observe how it performs in real use cases.\nyaml\n\n```\nname: task_breakdown\ndescription: Break down a task into 20-minute actionable subtasks\nmax_tokens: 4096\n\nvariables:\n- task_name\n- task_context\n- current_date\ntemplate: |\nYou are a productivity expert helping break down complex tasks into manageable 20-minute chunks.\n\n**CURRENT DATE:** {current_date}\n**TASK TO BREAK DOWN:**\n{task_name}\n**CONTEXT PROVIDED BY USER:**\n{task_context}\n\n**YOUR JOB:**\n\nBreak this task into specific, actionable subtasks that can each be completed in approximately 20 minutes.\n**RULES:**\n1. Each subtask should be concrete and actionable (starts with a verb)\n2. Each subtask should take ~20 minutes (can be 15-25 min, but aim for 20)\n3. Subtasks should follow a logical order\n4. Be specific - avoid vague tasks like “work on X”\n5. If the task is already small enough, you can create 1-3 subtasks\n6. If it’s large, create > 5 subtasks\n7. Consider the context provided - use it to make subtasks relevant and specific\n8. **SCHEDULING:** Based on the user’s context (e.g., “every other day”, “weekends only”), suggest a specific Due Date for each task starting from the Current Date.\n\n**OUTPUT FORMAT:**\n\nReturn ONLY a markdown list of subtasks in this format:\n- {task_name} - [Subtask description] (20 min) [Due: YYYY-MM-DD]\n\nExample:\n- {task_name} - Create project repository (20 min) [Due: 2026-02-13]\n- {task_name} - Configure CI/CD pipeline (20 min) [Due: 2026-02-15]\nDo NOT include any other text or explanations. Just the list.\n```\n\nIn parallel, I’m already working on several new modules:\n  * A _Dividend Analyzer_ to project income from my stocks and ETFs\n  * A _Writing Assistant_ to create an editorial plan for my writings.\n  * A _Discounts_ module to check relevant promotions when I’m planning a purchase\n  * A _Guitar Organizer_ to structure and schedule practice sessions whenever I pick up my guitar\n\n\nStay tuned for the next modules and hope this inspires you for your personal projects as well!\n## Register Now to Continue Reading\n### Unlock Towards Data Science with a Free Account\nAll articles on Towards Data Science are available to registered users. Create a free account today to access this article and thousands more.\nRegister for freeSign in to your account\n* * *\n![](../images/body-6f351be10c9e83aa9f9d.jpeg)\nWritten By\n## [Ivo Bernardo](https://towardsdatascience.com/author/ivopbernardo/)\n[See all from Ivo Bernardo](https://towardsdatascience.com/author/ivopbernardo/)\n[Ai Agent](https://towardsdatascience.com/tag/ai-agent/)[Ai Assistant](https://towardsdatascience.com/tag/ai-assistant/)[Ai Product Management](https://towardsdatascience.com/tag/ai-product-management/)[Artificial Intelligence](https://towardsdatascience.com/tag/artificial-intelligence/)[Programming](https://towardsdatascience.com/tag/programming/)\nShare This Article\n  * [](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Ftowardsdatascience.com%2Fbuilding-my-own-personal-ai-assistant-a-chronicle-part-2%2F&title=Building%20My%20Own%20Personal%20AI%20Assistant%3A%20A%20Chronicle%2C%20Part%202)\n  * [](https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Ftowardsdatascience.com%2Fbuilding-my-own-personal-ai-assistant-a-chronicle-part-2%2F&title=Building%20My%20Own%20Personal%20AI%20Assistant%3A%20A%20Chronicle%2C%20Part%202)\n  * [](https://x.com/share?url=https%3A%2F%2Ftowardsdatascience.com%2Fbuilding-my-own-personal-ai-assistant-a-chronicle-part-2%2F&text=Building%20My%20Own%20Personal%20AI%20Assistant%3A%20A%20Chronicle%2C%20Part%202)\n\n\nTowards Data Science is a community publication. Submit your insights to reach our global audience and earn through the TDS Author Payment Program.\n[Write for TDS](https://towardsdatascience.com/submissions/)\n## Related Articles\n  * [![](../images/002.jpg)](https://towardsdatascience.com/tool-calling-explained-how-ai-agents-decide-what-to-do-next/)\n## [Tool Calling, Explained: How AI Agents Decide What to Do Next](https://towardsdatascience.com/tool-calling-explained-how-ai-agents-decide-what-to-do-next/)\n[Agentic AI](https://towardsdatascience.com/category/artificial-intelligence/agentic-ai/)\nUnderstanding how LLMs interact with the world around them, from returning data to taking action\n[Maria Mouschoutzi](https://towardsdatascience.com/author/m.mouschoutzi/)\nJune 21, 202611 min read\n  * [![](../images/003.jpeg)](https://towardsdatascience.com/code-is-cheap-engineering-judgement-is-now-the-scarce-resource/)\n## [Code Is Cheap. Engineering Judgement Is Now the Scarce Resource](https://towardsdatascience.com/code-is-cheap-engineering-judgement-is-now-the-scarce-resource/)\n[Agentic AI](https://towardsdatascience.com/category/artificial-intelligence/agentic-ai/)\nThe barriers to building have collapsed. That shifts the bottleneck to ownership, validation, taste, and deciding what should actually exist\n[Clara Chong](https://towardsdatascience.com/author/clarachong13/)\nJune 2, 20266 min read\n  * [![](../images/004.jpg)](https://towardsdatascience.com/6-tips-to-complete-udacitys-data-scientist-nanodegree-in-1-month-b5f7351f22b3/)\n## [6 Tips to Complete Udacity's Data Scientist Nanodegree in 1 month](https://towardsdatascience.com/6-tips-to-complete-udacitys-data-scientist-nanodegree-in-1-month-b5f7351f22b3/)\n[Artificial Intelligence](https://towardsdatascience.com/category/artificial-intelligence/)\nMaximize your learning with minimal time and cost\n[Louis Teo](https://towardsdatascience.com/author/louisteo9/)\nFebruary 4, 20216 min read\n  * [![](../images/005.png)](https://towardsdatascience.com/dealing-with-categorical-variables-by-using-target-encoder-a0f1733a4c69/)\n## [Target-encoding Categorical Variables](https://towardsdatascience.com/dealing-with-categorical-variables-by-using-target-encoder-a0f1733a4c69/)\n[Artificial Intelligence](https://towardsdatascience.com/category/artificial-intelligence/)\nOne nice alternative to One-hot encoding your categories\n[Vinicius Trevisan](https://towardsdatascience.com/author/vinicius_trevisan/)\nMarch 17, 20227 min read\n  * [![](../images/006.png)](https://towardsdatascience.com/how-to-build-your-own-agentic-ai-system-using-crewai/)\n## [How to Build Your Own Agentic AI System Using CrewAI](https://towardsdatascience.com/how-to-build-your-own-agentic-ai-system-using-crewai/)\n[Agentic AI](https://towardsdatascience.com/category/artificial-intelligence/agentic-ai/)\nStep-by-Step Guide to Developing a Multi-Agent System for Social Media Marketing\n[Destin Gong](https://towardsdatascience.com/author/destingong/)\nNovember 9, 202511 min read\n  * [![](../images/007.jpg)](https://towardsdatascience.com/how-to-organize-all-of-your-coding-agent-tasks/)\n## [How to Organize All of Your Coding Agent Tasks](https://towardsdatascience.com/how-to-organize-all-of-your-coding-agent-tasks/)\n[Agentic AI](https://towardsdatascience.com/category/artificial-intelligence/agentic-ai/)\nOptimise how you interact with your coding agents\n[Eivind Kjosbakken](https://towardsdatascience.com/author/oieivind/)\nJuly 30, 202611 min read\n  * [![](../images/008.jpg)](https://towardsdatascience.com/vibe-coding-with-ai-best-practices-for-human-ai-collaboration-in-software-development/)\n## [Vibe Coding with AI: Best Practices for Human-AI Collaboration in Software Development](https://towardsdatascience.com/vibe-coding-with-ai-best-practices-for-human-ai-collaboration-in-software-development/)\n[Agentic AI](https://towardsdatascience.com/category/artificial-intelligence/agentic-ai/)\nAccelerate coding with AI while staying in control and building reliable, production-ready software.\n[Partha Sarkar](https://towardsdatascience.com/author/partha_sarkar/)\nMarch 19, 202614 min read\n  * [![](../images/009.jpeg)](https://towardsdatascience.com/hello-i-am-pami-937439c7984d/)\n## [Hello! I am PAMI](https://towardsdatascience.com/hello-i-am-pami-937439c7984d/)\n[Programming](https://towardsdatascience.com/category/programming/)\nA new Pattern Mining Python library for Data Science\n[Uday Kiran RAGE](https://towardsdatascience.com/author/uday.rage/)\nNovember 18, 20215 min read\n  * [![](../images/body-63beb50f664a055ed739.jpg)](https://towardsdatascience.com/python-lists-are-overrated-776e87cda3e5/)\n## [Python Lists Are Overrated](https://towardsdatascience.com/python-lists-are-overrated-776e87cda3e5/)\n[Programming](https://towardsdatascience.com/category/programming/)\nConsider these potentially superior alternatives\n[Aashish Nair](https://towardsdatascience.com/author/aashishnair/)\nOctober 4, 20215 min read\n\n\n  * [YouTube](https://www.youtube.com/c/TowardsDataScience)\n  * [X](https://x.com/TDataScience)\n  * [LinkedIn](https://www.linkedin.com/company/towards-data-science/)\n  * [Threads](https://www.threads.net/@towardsdatascience)\n  * [Bluesky](https://bsky.app/profile/towardsdatascience.com)\n\n\n[](https://towardsdatascience.com/)\nYour home for data science and AI. The world's leading publication for data science, data analytics, data engineering, machine learning, and artificial intelligence professionals.\nSubscribe to Our Newsletter[Write For TDS](https://towardsdatascience.com/submissions/)•[About](https://towardsdatascience.com/about-towards-data-science-d691af11cc2f/)•[Advertise](https://contact.towardsdatascience.com/advertise-with-towards-data-science)•[Privacy Policy](https://towardsdatascience.com/privacy-policy/)•[Terms of Use](https://towardsdatascience.com/website-terms-of-use/)\n© Insight Media Group, LLC 2026•[The New Stack](https://thenewstack.io)•[roadmap.sh](https://roadmap.sh)•[Creator Network](https://insightmediagroup.io/creator-network)\n####  Recommended Articles \nClose\n  * [ ![](https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/607686/image?etag=1782161464448&width=500&height=500) How Relevance Models Foreshadowed Transformers for NLP ](https://towardsdatascience.com/how-relevance-models-foreshadowed-transformers-for-nlp/ \"How Relevance Models Foreshadowed Transformers for NLP\")\n  * [ ![](https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/607639/image?etag=1781250125848&width=500&height=500) Javascript Fatigue: HTMX Is All You Need to Build ChatGPT — Part 1 ](https://towardsdatascience.com/javascript-fatigue-you-dont-need-js-to-build-chatgpt/ \"Javascript Fatigue: HTMX Is All You Need to Build ChatGPT — Part 1\")\n  * [ ![](https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/607930/image?etag=1782124566054&width=500&height=500) The Subset Sum Problem Solved in Linear Time for Dense Enough Inputs ](https://towardsdatascience.com/subset-sum-problem-solved-in-linear-time-for-dense-enough-inputs/ \"The Subset Sum Problem Solved in Linear Time for Dense Enough Inputs\")\n  * [ ![](https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/3660/image?etag=1780176246070&width=500&height=500) Does Your Company Have a Data Strategy? ](https://towardsdatascience.com/does-your-company-have-a-data-strategy-e8944dbec4ae/ \"Does Your Company Have a Data Strategy?\")\n\n\n",
  "metadata": {
    "title": "Building My Own Personal AI Assistant: A Chronicle, Part 2 | Towards Data Science",
    "description": "Improving Fernão: Building a personal AI assistant is rarely a single, monolithic effort",
    "keywords": null,
    "author": "Ivo Bernardo",
    "og:locale": "en_US",
    "og:type": "article",
    "og:title": "Building My Own Personal AI Assistant: A Chronicle, Part 2",
    "og:description": "Improving Fernão: Building a personal AI assistant is rarely a single, monolithic effort",
    "og:url": "https://towardsdatascience.com/building-my-own-personal-ai-assistant-a-chronicle-part-2/",
    "og:site_name": "Towards Data Science",
    "og:image": "https://assets.insightmediagroup.io/media/wp-content/uploads/2026/04/Screenshot-from-2026-04-12-18-54-01.jpg",
    "og:image:width": "1934",
    "og:image:height": "1381",
    "og:image:type": "image/jpeg",
    "twitter:card": "summary_large_image",
    "twitter:site": "@TDataScience",
    "twitter:creator": "@TDataScience",
    "twitter:label1": "Written by",
    "twitter:data1": "Ivo Bernardo",
    "twitter:label2": "Est. reading time",
    "twitter:data2": "8 min read",
    "article:published_time": "2026-04-16T09:00:08.000Z",
    "article:modified_time": "2026-04-16T09:00:08.000Z",
    "article:author": "https://towardsdatascience.com/author/ivopbernardo/"
  },
  "paywall": {
    "listed_paid": false,
    "detected": false,
    "marker": "",
    "public_only": false,
    "policy": "付费/会员内容只保留页面公开可见部分，不绕过付费墙"
  },
  "crawl": {
    "success": true,
    "status_code": 200,
    "error": ""
  },
  "code_blocks": [
    {
      "language": "txt",
      "file": "attachments/bf47253b2fbd/code/block_000.txt",
      "chars": 1111
    },
    {
      "language": "txt",
      "file": "attachments/bf47253b2fbd/code/block_001.txt",
      "chars": 3388
    },
    {
      "language": "txt",
      "file": "attachments/bf47253b2fbd/code/block_002.txt",
      "chars": 961
    },
    {
      "language": "txt",
      "file": "attachments/bf47253b2fbd/code/block_003.txt",
      "chars": 1459
    }
  ],
  "images": [
    {
      "status": "http_404",
      "url": "https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/607686/image?etag=1782161464448&width=500&height=500",
      "src": "https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/607686/image?etag=1782161464448&width=500&height=500",
      "alt": "",
      "downloaded": false,
      "discovery": "saved_markdown",
      "retried_at": "2026-10-20T17:49:32Z"
    },
    {
      "status": "http_404",
      "url": "https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/607639/image?etag=1781250125848&width=500&height=500",
      "src": "https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/607639/image?etag=1781250125848&width=500&height=500",
      "alt": "",
      "downloaded": false,
      "discovery": "saved_markdown",
      "retried_at": "2026-10-20T17:49:33Z"
    },
    {
      "status": "http_404",
      "url": "https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/607930/image?etag=1782124566054&width=500&height=500",
      "src": "https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/607930/image?etag=1782124566054&width=500&height=500",
      "alt": "",
      "downloaded": false,
      "discovery": "saved_markdown",
      "retried_at": "2026-10-20T17:49:33Z"
    },
    {
      "status": "http_404",
      "url": "https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/3660/image?etag=1780176246070&width=500&height=500",
      "src": "https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/3660/image?etag=1780176246070&width=500&height=500",
      "alt": "",
      "downloaded": false,
      "discovery": "saved_markdown",
      "retried_at": "2026-10-20T17:49:33Z"
    }
  ],
  "audio": [],
  "videos": [
    {
      "url": "https://www.youtube.com/c/TowardsDataScience",
      "kind": "channel_reference",
      "status": "reference_only"
    }
  ],
  "links": [
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/latest/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/tag/editors-pick/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/tag/the-variable/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/shipai/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/submissions/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/category/artificial-intelligence/agentic-ai/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/author/ivopbernardo/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/building-a-personal-ai-agent-in-a-couple-of-hours/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/tag/ai-agent/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/tag/ai-assistant/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/tag/ai-product-management/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/tag/artificial-intelligence/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/tag/programming/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/tool-calling-explained-how-ai-agents-decide-what-to-do-next/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/author/m.mouschoutzi/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/code-is-cheap-engineering-judgement-is-now-the-scarce-resource/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/author/clarachong13/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/6-tips-to-complete-udacitys-data-scientist-nanodegree-in-1-month-b5f7351f22b3/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/category/artificial-intelligence/"
    },
    {
      "type": "external",
      "href": "https://write.insightmediagroup.io"
    },
    {
      "type": "external",
      "href": "https://www.linkedin.com/company/towards-data-science/"
    },
    {
      "type": "external",
      "href": "https://x.com/TDataScience"
    },
    {
      "type": "external",
      "href": "https://roadmap.sh/ai-agents"
    },
    {
      "type": "external",
      "href": "https://www.facebook.com/sharer/sharer.php?title=Building+My+Own+Personal+AI+Assistant%3A+A+Chronicle%2C+Part+2&u=https%3A%2F%2Ftowardsdatascience.com%2Fbuilding-my-own-personal-ai-assistant-a-chronicle-part-2%2F"
    },
    {
      "type": "external",
      "href": "https://www.linkedin.com/shareArticle?mini=true&title=Building+My+Own+Personal+AI+Assistant%3A+A+Chronicle%2C+Part+2&url=https%3A%2F%2Ftowardsdatascience.com%2Fbuilding-my-own-personal-ai-assistant-a-chronicle-part-2%2F"
    },
    {
      "type": "external",
      "href": "https://x.com/share?text=Building+My+Own+Personal+AI+Assistant%3A+A+Chronicle%2C+Part+2&url=https%3A%2F%2Ftowardsdatascience.com%2Fbuilding-my-own-personal-ai-assistant-a-chronicle-part-2%2F"
    },
    {
      "type": "external",
      "href": "https://www.youtube.com/c/TowardsDataScience"
    },
    {
      "type": "external",
      "href": "https://www.threads.net/@towardsdatascience"
    },
    {
      "type": "external",
      "href": "https://bsky.app/profile/towardsdatascience.com"
    },
    {
      "type": "external",
      "href": "https://thenewstack.io"
    },
    {
      "type": "external",
      "href": "https://roadmap.sh"
    },
    {
      "type": "external",
      "href": "https://insightmediagroup.io/creator-network"
    }
  ],
  "repair_version": 2,
  "repaired_at": "2026-10-20T17:27:02Z",
  "source_url": "https://towardsdatascience.com/building-my-own-personal-ai-assistant-a-chronicle-part-2/",
  "delivery_status": "unverified",
  "discovery_status": "http_403",
  "missing_reason": "源页面未重新核验:http_403；已按保留正文补采图片",
  "repair_error": "",
  "actual_video_files": [],
  "expected_saved_body_images": 4,
  "image_discovery": "saved_markdown",
  "source_body_markdown": "![Revisit consent button](https://cdn-cookieyes.com/assets/images/revisit.svg)\nWe value your privacy\nWe use cookies to enhance your browsing experience, serve personalised ads or content, and analyse our traffic. By clicking \"Accept All\", you consent to our use of cookies.\nCustomise Reject All Accept All\nCustomise Consent Preferences ![](https://cdn-cookieyes.com/assets/images/close.svg)\nWe use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.\nThe cookies that are categorised as \"Necessary\" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... Show more\nNecessaryAlways Active\nNecessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.\n  * Cookie\nBCTempID\n  * Duration\n10 minutes\n  * Description\nNo description available.\n\n\n  * Cookie\n__cf_bm\n  * Duration\n1 hour\n  * Description\nThis cookie, set by Cloudflare, is used to support Cloudflare Bot Management. \n\n\n  * Cookie\nAWSALBCORS\n  * Duration\n7 days\n  * Description\nAmazon Web Services set this cookie for load balancing.\n\n\n  * Cookie\n_cfuvid\n  * Duration\nsession\n  * Description\nCloudflare sets this cookie to track users across sessions to optimize user experience by maintaining session consistency and providing personalized services\n\n\n  * Cookie\nli_gc\n  * Duration\n6 months\n  * Description\nLinkedin set this cookie for storing visitor's consent regarding using cookies for non-essential purposes.\n\n\n  * Cookie\n__hssrc\n  * Duration\nsession\n  * Description\nThis cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session.\n\n\n  * Cookie\n__hssc\n  * Duration\n1 hour\n  * Description\nHubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie.\n\n\n  * Cookie\nwpEmojiSettingsSupports\n  * Duration\nsession\n  * Description\nWordPress sets this cookie when a user interacts with emojis on a WordPress site. It helps determine if the user's browser can display emojis properly.\n\n\n  * Cookie\nBCSessionID\n  * Duration\n1 year 1 month 4 days\n  * Description\nBlueconic sets this cookie as a unique identifier for the BlueConic profile.\n\n\n  * Cookie\n_octo\n  * Duration\n1 year\n  * Description\nNo description available.\n\n\n  * Cookie\nlogged_in\n  * Duration\n1 year\n  * Description\nNo description available.\n\n\n  * Cookie\n__Secure-YEC\n  * Duration\npast\n  * Description\nYouTube sets this cookie to stores the user's video player preferences using embedded YouTube video\n\n\n  * Cookie\n__eoi\n  * Duration\n6 months\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nAWSALBTGCORS\n  * Duration\n7 days\n  * Description\nNo description available.\n\n\n  * Cookie\nlogin-status-p\n  * Duration\npast\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nAWSALBTG\n  * Duration\n7 days\n  * Description\nNo description available.\n\n\n  * Cookie\ncsrf_token\n  * Duration\nsession\n  * Description\nNo description available.\n\n\n  * Cookie\ntoken_v2\n  * Duration\n1 day\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nD\n  * Duration\n1 year\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nPHPSESSID\n  * Duration\nsession\n  * Description\nThis cookie is native to PHP applications. The cookie stores and identifies a user's unique session ID to manage user sessions on the website. The cookie is a session cookie and will be deleted when all the browser windows are closed.\n\n\n  * Cookie\nVISITOR_PRIVACY_METADATA\n  * Duration\n6 months\n  * Description\nYouTube sets this cookie to store the user's cookie consent state for the current domain. \n\n\n  * Cookie\ncookietest\n  * Duration\nsession\n  * Description\nThe cookietest cookie is typically used to determine whether the user's browser accepts cookies, essential for website functionality and user experience.\n\n\n  * Cookie\n__Host-airtable-session\n  * Duration\n1 year\n  * Description\nThis cookie is used to enable us to integrate the services of Airtable.\n\n\n  * Cookie\n__Host-airtable-session.sig\n  * Duration\n1 year\n  * Description\nThis cookie is used to enable us to integrate the services of Airtable.\n\n\n  * Cookie\nm\n  * Duration\n1 year 1 month 4 days\n  * Description\nStripe sets this cookie for fraud prevention purposes. It identifies the device used to access the website, allowing the website to be formatted accordingly.\n\n\n  * Cookie\nBIGipServer*\n  * Duration\nsession\n  * Description\nMarketo sets this cookie to collect information about the user's online activity and build a profile about their interests to provide advertisements relevant to the user. \n\n\n  * Cookie\n__cfruid\n  * Duration\nsession\n  * Description\nCloudflare sets this cookie to identify trusted web traffic.\n\n\n  * Cookie\n_GRECAPTCHA\n  * Duration\n6 months\n  * Description\nGoogle Recaptcha service sets this cookie to identify bots to protect the website against malicious spam attacks.\n\n\n  * Cookie\n__Secure-YNID\n  * Duration\n6 months\n  * Description\nGoogle cookie used to protect user security and prevent fraud, especially during the login process.\n\n\n  * Cookie\ncookieyes-consent\n  * Duration\n1 year\n  * Description\nCookieYes sets this cookie to remember users' consent preferences so that their preferences are respected on subsequent visits to this site. It does not collect or store any personal information about the site visitors.\n\n\nFunctional\nFunctional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.\n  * Cookie\nlidc\n  * Duration\n1 day\n  * Description\nLinkedIn sets the lidc cookie to facilitate data center selection.\n\n\n  * Cookie\nbrw\n  * Duration\n1 year\n  * Description\nNo description available.\n\n\n  * Cookie\nbrwConsent\n  * Duration\n5 minutes\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nWMF-Uniq\n  * Duration\n1 year\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nloom_anon_comment\n  * Duration\n1 year\n  * Description\nNo description available.\n\n\n  * Cookie\nloom_referral_video\n  * Duration\nsession\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nVISITOR_INFO1_LIVE\n  * Duration\n6 months\n  * Description\nA cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface.\n\n\n  * Cookie\nyt-remote-connected-devices\n  * Duration\nNever Expires\n  * Description\nYouTube sets this cookie to store the user's video preferences using embedded YouTube videos.\n\n\n  * Cookie\nytidb::LAST_RESULT_ENTRY_KEY\n  * Duration\nNever Expires\n  * Description\nThe cookie ytidb::LAST_RESULT_ENTRY_KEY is used by YouTube to store the last search result entry that was clicked by the user. This information is used to improve the user experience by providing more relevant search results in the future.\n\n\n  * Cookie\nyt-remote-device-id\n  * Duration\nNever Expires\n  * Description\nYouTube sets this cookie to store the user's video preferences using embedded YouTube videos.\n\n\n  * Cookie\nyt-remote-session-name\n  * Duration\nsession\n  * Description\nThe yt-remote-session-name cookie is used by YouTube to store the user's video player preferences using embedded YouTube video.\n\n\n  * Cookie\nyt-remote-fast-check-period\n  * Duration\nsession\n  * Description\nThe yt-remote-fast-check-period cookie is used by YouTube to store the user's video player preferences for embedded YouTube videos.\n\n\n  * Cookie\nyt-remote-session-app\n  * Duration\nsession\n  * Description\nThe yt-remote-session-app cookie is used by YouTube to store user preferences and information about the interface of the embedded YouTube video player.\n\n\n  * Cookie\nyt-remote-cast-available\n  * Duration\nsession\n  * Description\nThe yt-remote-cast-available cookie is used to store the user's preferences regarding whether casting is available on their YouTube video player.\n\n\n  * Cookie\nyt-remote-cast-installed\n  * Duration\nsession\n  * Description\nThe yt-remote-cast-installed cookie is used to store the user's video player preferences using embedded YouTube video.\n\n\n  * Cookie\ncp_session\n  * Duration\n3 months\n  * Description\nCodepen sets this cookie for Help systems found in the website.\n\n\n  * Cookie\nloid\n  * Duration\n1 year 1 month 4 days\n  * Description\nThis cookie is set by the Reddit. The cookie enables the sharing of content from the website onto the social media platform.\n\n\nAnalytics\nAnalytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.\n  * Cookie\n__hstc\n  * Duration\n6 months\n  * Description\nHubspot set this main cookie for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session).\n\n\n  * Cookie\nhubspotutk\n  * Duration\n6 months\n  * Description\nHubSpot sets this cookie to keep track of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts.\n\n\n  * Cookie\n_ga\n  * Duration\n1 year 1 month 4 days\n  * Description\nGoogle Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors.\n\n\n  * Cookie\n_ga_*\n  * Duration\n1 year 1 month 4 days\n  * Description\nGoogle Analytics sets this cookie to store and count page views.\n\n\n  * Cookie\n__Host-psifi.analyticsTrace\n  * Duration\n6 hours\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\n__Host-psifi.analyticsTraceV2\n  * Duration\n6 hours\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\n_gh_sess\n  * Duration\nsession\n  * Description\nGitHub sets this cookie for temporary application and framework state between pages like what step the user is on in a multiple step form.\n\n\n  * Cookie\nYSC\n  * Duration\nsession\n  * Description\nYSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages.\n\n\n  * Cookie\najs_anonymous_id\n  * Duration\n1 year\n  * Description\nThis cookie is set by Segment to count the number of people who visit a certain site by tracking if they have visited before.\n\n\n  * Cookie\nvuid\n  * Duration\n1 year 1 month 4 days\n  * Description\nVimeo installs this cookie to collect tracking information by setting a unique ID to embed videos on the website. \n\n\nPerformance\nPerformance cookies are used to understand and analyse the key performance indexes of the website which helps in delivering a better user experience for the visitors.\n  * Cookie\nAWSALB\n  * Duration\n7 days\n  * Description\nAWSALB is an application load balancer cookie set by Amazon Web Services to map the session to the target.\n\n\n  * Cookie\nacq\n  * Duration\npast\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nacq.sig\n  * Duration\npast\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nptc\n  * Duration\n2 years\n  * Description\nNo description available.\n\n\nAdvertisement\nAdvertisement cookies are used to provide visitors with customised advertisements based on the pages you visited previously and to analyse the effectiveness of the ad campaigns.\n  * Cookie\nmuc_ads\n  * Duration\n1 year 1 month 4 days\n  * Description\nTwitter sets this cookie to collect user behaviour and interaction data to optimize the website.\n\n\n  * Cookie\nguest_id_marketing\n  * Duration\n1 year 1 month 4 days\n  * Description\nTwitter sets this cookie to identify and track the website visitor.\n\n\n  * Cookie\nguest_id_ads\n  * Duration\n1 year 1 month 4 days\n  * Description\nTwitter sets this cookie to identify and track the website visitor.\n\n\n  * Cookie\npersonalization_id\n  * Duration\n1 year 1 month 4 days\n  * Description\nTwitter sets this cookie to integrate and share features for social media and also store information about how the user uses the website, for tracking and targeting.\n\n\n  * Cookie\nguest_id\n  * Duration\n1 year 1 month 4 days\n  * Description\nTwitter sets this cookie to identify and track the website visitor. It registers if a user is signed in to the Twitter platform and collects information about ad preferences.\n\n\n  * Cookie\nbcookie\n  * Duration\n1 year\n  * Description\nLinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser IDs.\n\n\n  * Cookie\n__Secure-ROLLOUT_TOKEN\n  * Duration\n6 months\n  * Description\nYouTube sets this cookie to manage feature rollout and experimentation. It helps Google control which new features or interface changes are shown to users as part of testing and staged rollouts, ensuring consistent experience for a given user during an experiment.\n\n\n  * Cookie\nyt.innertube::nextId\n  * Duration\nNever Expires\n  * Description\nYouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen.\n\n\n  * Cookie\nyt.innertube::requests\n  * Duration\nNever Expires\n  * Description\nYouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen.\n\n\n  * Cookie\nsession_tracker\n  * Duration\nsession\n  * Description\nThis cookie is set by the Reddit. This cookie is used to identify trusted web traffic. It also helps in adverstising on the website.\n\n\n  * Cookie\nedgebucket\n  * Duration\nsession\n  * Description\nReddit sets this cookie to save the information about a log-on Reddit user, for the purpose of advertisement recommendations and updating the content.\n\n\n  * Cookie\ndid\n  * Duration\n1 year\n  * Description\nArbor sets this cookie to show targeted ads to site visitors.This cookie expires after 2 months or 1 year.\n\n\nUncategorised\nOther uncategorised cookies are those that are being analysed and have not been classified into a category as yet.\nNo cookies to display.\nReject All Save My Preferences Accept All\nToggle Search[](https://towardsdatascience.com/)Toggle Mobile Navigation\n[](https://towardsdatascience.com/)\nPublish AI, ML & data-science insights to a global community of data professionals.\nSign in[Submit an Article](https://write.insightmediagroup.io)\n[Latest](https://towardsdatascience.com/latest/)[Editor's Picks](https://towardsdatascience.com/tag/editors-pick/)[Newsletter](https://towardsdatascience.com/tag/the-variable/)[ShipAI](https://towardsdatascience.com/shipai/)\n* * *\n[Write For TDS](https://towardsdatascience.com/submissions/)\n[LinkedIn](https://www.linkedin.com/company/towards-data-science/)[X](https://x.com/TDataScience)Toggle Search\n[Agentic AI](https://towardsdatascience.com/category/artificial-intelligence/agentic-ai/)\n# Building My Own Personal AI Assistant: A Chronicle, Part 2\nImproving Fernão: Building a personal AI assistant is rarely a single, monolithic effort\n[Ivo Bernardo](https://towardsdatascience.com/author/ivopbernardo/)\nApril 16, 20268 min read\n![](https://assets.insightmediagroup.io/media/wp-content/uploads/2026/04/Screenshot-from-2026-04-12-18-54-01.jpg)\nYou probably remember the [first part of my journey](https://towardsdatascience.com/building-a-personal-ai-agent-in-a-couple-of-hours/) building _Fernão_ , my personal AI agent. Now it’s time to continue the story and let’s dive into the second part!\nIn this post, I’ll walk you through the latest improvements to _Fernão_ , refining existing features and adding new capabilities to the agent. Let’s start with what changed.\n···\nRemember the function that fetched the calendar through ICS (the universal calendar format) and extracted my calendar tasks?\nThat function was a mess and it reflected a poor architectural decision. ICS calendars don’t support native filtering, which means every request required pulling all events from the calendar and filtering them afterward. In practice,  _Fernão_ was downloading my entire schedule just to extract a few relevant meetings.\nLearn this step by step with the interactive [AI Agents](https://roadmap.sh/ai-agents) roadmap.\nThis was like bringing home an entire library just to look up a single sentence in one book.\nThe more I tried to optimize the function, the less I would get anywhere, because I needed a new system solution. I needed to change the way the system was getting the calendar and I would NEVER get around this bottleneck with ICS.\nSo I dug deeper and found that Google provides calendar access through an API that supports native filtering. _Fernão_ now only retrieves the events it actually needs. This improved the schedule generation, that dropped from nearly five minutes to about twenty seconds.\nWith this new pipeline in place, I also refactored the surrounding logic. The entire function is now significantly cleaner and faster. We now have a beautiful way to fetch the calendar events via API:\npython\n\n```\ndef get_events_for_date(target_date=None, use_api=True):\n    \"\"\"\n    Fetches events for a specific date from Google Calendar.\n    Tries API first (if use_api=True), falls back to ICS if API fails.\n    \n    Args:\n        target_date: datetime.date object for the target day. If None, uses today.\n        use_api: If True, try Google Calendar API first. If False, use ICS only.\n    \n    Returns:\n        List of event dictionaries.\n    \"\"\"\n    if use_api and GCAL_API_AVAILABLE:\n        print(\"[GCal] Attempting to use Google Calendar API...\")\n        try:\n            events = get_events_for_date_api(target_date)\n            if events is not None:\n                print(f\"[GCal] Successfully fetched {len(events)} events via API\")\n                return events\n            else:\n                print(\"[GCal] API returned None. Falling back to ICS...\")\n        except Exception as e:\n            print(f\"[GCal] API failed with error: {e}\")\n            print(\"[GCal] Falling back to ICS...\")\n    \n    # Fallback to ICS\n    print(\"[GCal] Using ICS feed method...\")\n    return get_events_for_date_ics(target_date)\n```\n\n.. and here is our API fetch:\npython\n\n```\ndef get_events_for_date_api(target_date=None):\n    \"\"\"\n    Fetches events for a specific date from Google Calendar using the Calendar API.\n    \n    Args:\n        target_date: datetime.date object for the target day. If None, uses today.\n    \n    Returns:\n        List of event dictionaries, or None if API call fails.\n    \"\"\"\n    service = get_calendar_service()\n    if not service:\n        return None\n    \n    day_start, day_end, target_date, tz_name, local = _get_local_time_range(target_date)\n    \n    print(f\"\\n[GCal API] Fetching events for {target_date.strftime('%Y-%m-%d')}\")\n    print(f\"  Timezone: {tz_name}\")\n    \n    # Get calendar IDs from environment, or use primary\n    calendar_ids_str = os.getenv('GCAL_CALENDAR_IDS', '')\n    if calendar_ids_str:\n        calendar_ids = [cid.strip() for cid in calendar_ids_str.split(',')]\n    else:\n        calendar_ids = ['primary']\n    \n    all_events = []\n    \n    # Fetch from each calendar\n    for calendar_id in calendar_ids:\n        try:\n            print(f\"[GCal API] Fetching from calendar: {calendar_id}\")\n            \n            # Call the Calendar API with timeoutlobally\n            old_timeout = socket.getdefaulttimeout()\n            socket.setdefaulttimeout(10)\n            \n            try:\n                events_result = service.events().list(\n                    calendarId=calendar_id,\n                    timeMin=day_start.isoformat(),\n                    timeMax=day_end.isoformat(),\n                    singleEvents=True,\n                    orderBy='startTime'\n                ).execute()\n            finally:\n                socket.setdefaulttimeout(old_timeout)\n            \n            events = events_result.get('items', [])\n            print(f\"[GCal API] Found {len(events)} event(s) in {calendar_id}\")\n            \n            # Parse events\n            for event in events:\n                # Get start time\n                start = event['start'].get('dateTime', event['start'].get('date'))\n                end = event['end'].get('dateTime', event['end'].get('date'))\n                \n                # Parse datetime\n                if 'T' in start:  # DateTime\n                    start_dt = datetime.fromisoformat(start.replace('Z', '+00:00'))\n                    end_dt = datetime.fromisoformat(end.replace('Z', '+00:00'))\n                    \n                    # Convert to local timezone\n                    start_local = start_dt.astimezone(local)\n                    end_local = end_dt.astimezone(local)\n                    \n                    start_str = start_local.strftime(\"%H:%M\")\n                    end_str = end_local.strftime(\"%H:%M\")\n                else:  # All-day event\n                    start_str = \"00:00\"\n                    end_str = \"23:59\"\n                \n                all_events.append({\n                    \"title\": event.get('summary', 'Untitled Event'),\n                    \"start\": start_str,\n                    \"end\": end_str,\n                    \"location\": event.get('location', ''),\n                    \"description\": event.get('description', '')\n                })\n        \n        except Exception as e:\n            print(f\"[GCal API] Error fetching from {calendar_id}: {e}\")\n            continue\n    \n    # Sort by start time\n    all_events.sort(key=lambda x: x[\"start\"])\n    \n    print(f\"[GCal API] Total events: {len(all_events)}\")\n    return all_events\n```\n\nBeyond the back-end improvements, I’ve also added new features to the assistant.\nIn the schedule view, I can now mark tasks as completed. The cool thing is that and when I do it, they’re automatically synced with _Microsoft To-Do app_.\n![](https://assets.insightmediagroup.io/media/wp-content/uploads/2026/04/image-109-1024x72.png)\nChecking tasks in the App - Image by Author\n![](https://assets.insightmediagroup.io/media/wp-content/uploads/2026/04/image-110-1024x100.png)\nChecking tasks in the App - Image by Author\nMarvelous!\nIt makes me think that, over time, many of us will end up building our own “personal operating systems”, assembling workflows from our preferred tools, integrating what we need, and replacing components whenever better options appear. If features become easy to replicate, loyalty to specific platforms will weaken.\nThis also raises an interesting question: will companies eventually try to lock down their systems by restricting APIs and external integrations? Possibly. But isolating themselves is unlikely to work in the long run. If users can’t connect tools to their own workflows, they’ll simply move elsewhere (… and will this be a behavior only done by power users?)\nWith this new capability in the Schedule Maker, I went on to implement another feature for _Fernão_ , suggested by one of the readers.\nIntroducing: _**the Task Breaker.**_\n![](https://assets.insightmediagroup.io/media/wp-content/uploads/2026/04/image-111-1024x683.png)\nThe new Fernão role is to break tasks - Image by Author - Generated by Gemini\n···\nThe _**Task Breaker**_ follows a simple workflow:\n  * Start with a large, generic task in _Microsoft To Do_ ;\n  * Add context on how the task should be broken down;\n  * Fernão decomposes the task and builds a plan;\n  * The resulting tasks are saved back to To-Do with due dates, and later appear in the daily assistant;\n\n\n![](https://assets.insightmediagroup.io/media/wp-content/uploads/2026/04/image-112-1024x428.png)\nFernão Task Breaker - Image by Author\nHere’s how the Task Breaker appears in the sidebar:\n![](https://assets.insightmediagroup.io/media/wp-content/uploads/2026/04/image-115.png)\nTask Breaker Module - Image by Author\nAnd here’s the current (still rough) front end for the _Task Breaker_ :\n![](https://assets.insightmediagroup.io/media/wp-content/uploads/2026/04/image-116-1024x703.png)\nTask Breaker Module - Image by Author\nLet’s take a real example. One of the larger tasks sitting in my To Do list is **“** _Project Documentation at DareData._**”** This isn’t a small operational task, it’s a structural project.\nThe goal is to consolidate and formalize the internal knowledge of the company in Notion, making sure the main questions about the enterprise are clearly answered in our _Knowledge Hub_. That means reviewing every department, identifying gaps, creating or refining pages, structuring information properly, and assigning clear ownership for each section.\nIn practice, this requires auditing, writing, and governance decisions. It’s not something you “just do” in one sitting and I want to complete this within three weeks. Realistically, I can dedicate between 30 minutes to one hour per day.\nThis is exactly the kind of task that benefits from decomposition, so I’ll use some context information in the Task Breaker and turn this giga-task into an actionable plan:\nmarkup\n\n```\nI’m currently building our Knowledge Hub in Notion. Here’s the current structure of Notion and Departments:# DareData Hub## Handbook for Network Members[DareData Network Member Handbook ]## Teams### Sales & Partnerships### Marketing (Brand and Gen-OS)### Finance### Delivery[Tech Specialists][Principals][Account Managers]I’ll need to:- Go Through Every department and create the pages that make sense (search the web for more context on what DareData is if you need ideas of the pages I need to create on every department or use your knowledge on what definitely needs to be documented in a 130 people B2B company).- Make sure that every page has an Owner- Revisit the Suggestions recorded by my team in the suggestions, I can probably pick one or two suggestions every day- Add some departments that are not in there: Admin, Core Members, Finance, ProductI have around 30 minutes to 1 hour to work every day and want to complete this project by 7 March 2026.\n```\n\nAfter hitting \"breakdown\", _Fernão_ will start to forge:\n![](https://assets.insightmediagroup.io/media/wp-content/uploads/2026/04/image-117-1024x324.png)\nFernão Forging the Task - Image by Author\nMarvelous x2!\n![](https://assets.insightmediagroup.io/media/wp-content/uploads/2026/04/image-118-1024x705.png)\nTask Breakdown - Image by Author\nWe can now review the tasks and plan generated and submit them to my Microsoft To-Do. I also need to assign which list on Microsoft To-Do they will be assigned to:\n![](https://assets.insightmediagroup.io/media/wp-content/uploads/2026/04/image-119-1024x169.png)\nDestination List in Microsoft To-Do - Image by Author  \n\nCool! Let’s see how it looks in Microsoft app:\n![](https://assets.insightmediagroup.io/media/wp-content/uploads/2026/04/image-120-1024x621.png)\nPerfecto.\nWhile testing this, I realised I want to adjust two things.\n  * First, _Fernão_ is meant to be a medieval chronicler, not a fantasy warrior, so I’ll change the forging design. His clothing should feel medieval.\n\n\n  * Second, on a more practical note, I need a “ _Submit All_ ” button. Submitting tasks one by one is tedious, especially when breaking down larger projects.\n\n\nLet's break another task after making these changes:\n![](https://assets.insightmediagroup.io/media/wp-content/uploads/2026/04/image-121-1024x621.png)\n_Fernão_ now forges in a proper medieval vest:\n![](https://assets.insightmediagroup.io/media/wp-content/uploads/2026/04/image-122-1024x198.png)\nFernão is forging again - Image by Author\nAnd now we can also use the nice “ _Submit All_ ” button:\n![](https://assets.insightmediagroup.io/media/wp-content/uploads/2026/04/image-123-1024x198.png)\nSubmit new tasks in To-Do - Image by Author\nI’ll likely remove the emoji. That kind of “ _emojification_ ” is very typical of LLM-generated code in the front-end, and it really annoys me.\nAnyway, building this new feature for _Fernão_ was genuinely satisfying. If you have ideas for additional features, I’m open to suggestions!\nBelow is the current prompt I’m using for task breakdown. I’ll continue refining it as I experiment and observe how it performs in real use cases.\nyaml\n\n```\nname: task_breakdown\ndescription: Break down a task into 20-minute actionable subtasks\nmax_tokens: 4096\n\nvariables:\n- task_name\n- task_context\n- current_date\ntemplate: |\nYou are a productivity expert helping break down complex tasks into manageable 20-minute chunks.\n\n**CURRENT DATE:** {current_date}\n**TASK TO BREAK DOWN:**\n{task_name}\n**CONTEXT PROVIDED BY USER:**\n{task_context}\n\n**YOUR JOB:**\n\nBreak this task into specific, actionable subtasks that can each be completed in approximately 20 minutes.\n**RULES:**\n1. Each subtask should be concrete and actionable (starts with a verb)\n2. Each subtask should take ~20 minutes (can be 15-25 min, but aim for 20)\n3. Subtasks should follow a logical order\n4. Be specific - avoid vague tasks like “work on X”\n5. If the task is already small enough, you can create 1-3 subtasks\n6. If it’s large, create > 5 subtasks\n7. Consider the context provided - use it to make subtasks relevant and specific\n8. **SCHEDULING:** Based on the user’s context (e.g., “every other day”, “weekends only”), suggest a specific Due Date for each task starting from the Current Date.\n\n**OUTPUT FORMAT:**\n\nReturn ONLY a markdown list of subtasks in this format:\n- {task_name} - [Subtask description] (20 min) [Due: YYYY-MM-DD]\n\nExample:\n- {task_name} - Create project repository (20 min) [Due: 2026-02-13]\n- {task_name} - Configure CI/CD pipeline (20 min) [Due: 2026-02-15]\nDo NOT include any other text or explanations. Just the list.\n```\n\nIn parallel, I’m already working on several new modules:\n  * A _Dividend Analyzer_ to project income from my stocks and ETFs\n  * A _Writing Assistant_ to create an editorial plan for my writings.\n  * A _Discounts_ module to check relevant promotions when I’m planning a purchase\n  * A _Guitar Organizer_ to structure and schedule practice sessions whenever I pick up my guitar\n\n\nStay tuned for the next modules and hope this inspires you for your personal projects as well!\n## Register Now to Continue Reading\n### Unlock Towards Data Science with a Free Account\nAll articles on Towards Data Science are available to registered users. Create a free account today to access this article and thousands more.\nRegister for freeSign in to your account\n* * *\n![](https://assets.insightmediagroup.io/media/1787657081760_wqdt7l.jpeg)\nWritten By\n## [Ivo Bernardo](https://towardsdatascience.com/author/ivopbernardo/)\n[See all from Ivo Bernardo](https://towardsdatascience.com/author/ivopbernardo/)\n[Ai Agent](https://towardsdatascience.com/tag/ai-agent/)[Ai Assistant](https://towardsdatascience.com/tag/ai-assistant/)[Ai Product Management](https://towardsdatascience.com/tag/ai-product-management/)[Artificial Intelligence](https://towardsdatascience.com/tag/artificial-intelligence/)[Programming](https://towardsdatascience.com/tag/programming/)\nShare This Article\n  * [](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Ftowardsdatascience.com%2Fbuilding-my-own-personal-ai-assistant-a-chronicle-part-2%2F&title=Building%20My%20Own%20Personal%20AI%20Assistant%3A%20A%20Chronicle%2C%20Part%202)\n  * [](https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Ftowardsdatascience.com%2Fbuilding-my-own-personal-ai-assistant-a-chronicle-part-2%2F&title=Building%20My%20Own%20Personal%20AI%20Assistant%3A%20A%20Chronicle%2C%20Part%202)\n  * [](https://x.com/share?url=https%3A%2F%2Ftowardsdatascience.com%2Fbuilding-my-own-personal-ai-assistant-a-chronicle-part-2%2F&text=Building%20My%20Own%20Personal%20AI%20Assistant%3A%20A%20Chronicle%2C%20Part%202)\n\n\nTowards Data Science is a community publication. Submit your insights to reach our global audience and earn through the TDS Author Payment Program.\n[Write for TDS](https://towardsdatascience.com/submissions/)\n## Related Articles\n  * [![](https://assets.insightmediagroup.io/media/wp-content/uploads/2026/06/Capture.jpg)](https://towardsdatascience.com/tool-calling-explained-how-ai-agents-decide-what-to-do-next/)\n## [Tool Calling, Explained: How AI Agents Decide What to Do Next](https://towardsdatascience.com/tool-calling-explained-how-ai-agents-decide-what-to-do-next/)\n[Agentic AI](https://towardsdatascience.com/category/artificial-intelligence/agentic-ai/)\nUnderstanding how LLMs interact with the world around them, from returning data to taking action\n[Maria Mouschoutzi](https://towardsdatascience.com/author/m.mouschoutzi/)\nJune 21, 202611 min read\n  * [![](https://assets.insightmediagroup.io/media/wp-content/uploads/2026/06/AIEconference160526_1155_DB6_0727.jpeg)](https://towardsdatascience.com/code-is-cheap-engineering-judgement-is-now-the-scarce-resource/)\n## [Code Is Cheap. Engineering Judgement Is Now the Scarce Resource](https://towardsdatascience.com/code-is-cheap-engineering-judgement-is-now-the-scarce-resource/)\n[Agentic AI](https://towardsdatascience.com/category/artificial-intelligence/agentic-ai/)\nThe barriers to building have collapsed. That shifts the bottleneck to ownership, validation, taste, and deciding what should actually exist\n[Clara Chong](https://towardsdatascience.com/author/clarachong13/)\nJune 2, 20266 min read\n  * [![](https://assets.insightmediagroup.io/media/wp-content/uploads/2021/02/0zq6z2BKfxJi5r-Hk-scaled.jpg)](https://towardsdatascience.com/6-tips-to-complete-udacitys-data-scientist-nanodegree-in-1-month-b5f7351f22b3/)\n## [6 Tips to Complete Udacity's Data Scientist Nanodegree in 1 month](https://towardsdatascience.com/6-tips-to-complete-udacitys-data-scientist-nanodegree-in-1-month-b5f7351f22b3/)\n[Artificial Intelligence](https://towardsdatascience.com/category/artificial-intelligence/)\nMaximize your learning with minimal time and cost\n[Louis Teo](https://towardsdatascience.com/author/louisteo9/)\nFebruary 4, 20216 min read\n  * [![](https://assets.insightmediagroup.io/media/wp-content/uploads/2022/03/1fu9aFquMfd5jrYtIsIz5ww.png)](https://towardsdatascience.com/dealing-with-categorical-variables-by-using-target-encoder-a0f1733a4c69/)\n## [Target-encoding Categorical Variables](https://towardsdatascience.com/dealing-with-categorical-variables-by-using-target-encoder-a0f1733a4c69/)\n[Artificial Intelligence](https://towardsdatascience.com/category/artificial-intelligence/)\nOne nice alternative to One-hot encoding your categories\n[Vinicius Trevisan](https://towardsdatascience.com/author/vinicius_trevisan/)\nMarch 17, 20227 min read\n  * [![](https://assets.insightmediagroup.io/media/wp-content/uploads/2025/11/Screenshot-2025-11-07-at-6.34.37-PM.png)](https://towardsdatascience.com/how-to-build-your-own-agentic-ai-system-using-crewai/)\n## [How to Build Your Own Agentic AI System Using CrewAI](https://towardsdatascience.com/how-to-build-your-own-agentic-ai-system-using-crewai/)\n[Agentic AI](https://towardsdatascience.com/category/artificial-intelligence/agentic-ai/)\nStep-by-Step Guide to Developing a Multi-Agent System for Social Media Marketing\n[Destin Gong](https://towardsdatascience.com/author/destingong/)\nNovember 9, 202511 min read\n  * [![](https://assets.insightmediagroup.io/media/wp-content/uploads/2026/07/task-management-coding-agents_cover.jpg)](https://towardsdatascience.com/how-to-organize-all-of-your-coding-agent-tasks/)\n## [How to Organize All of Your Coding Agent Tasks](https://towardsdatascience.com/how-to-organize-all-of-your-coding-agent-tasks/)\n[Agentic AI](https://towardsdatascience.com/category/artificial-intelligence/agentic-ai/)\nOptimise how you interact with your coding agents\n[Eivind Kjosbakken](https://towardsdatascience.com/author/oieivind/)\nJuly 30, 202611 min read\n  * [![](https://assets.insightmediagroup.io/media/wp-content/uploads/2026/03/Gemini_Generated_Image_yf9qdlyf9qdlyf9q-scaled-1.jpg)](https://towardsdatascience.com/vibe-coding-with-ai-best-practices-for-human-ai-collaboration-in-software-development/)\n## [Vibe Coding with AI: Best Practices for Human-AI Collaboration in Software Development](https://towardsdatascience.com/vibe-coding-with-ai-best-practices-for-human-ai-collaboration-in-software-development/)\n[Agentic AI](https://towardsdatascience.com/category/artificial-intelligence/agentic-ai/)\nAccelerate coding with AI while staying in control and building reliable, production-ready software.\n[Partha Sarkar](https://towardsdatascience.com/author/partha_sarkar/)\nMarch 19, 202614 min read\n  * [![](https://assets.insightmediagroup.io/media/wp-content/uploads/2021/11/1HJQnWK6ioH_YcrWj_XQ1KQ-scaled.jpeg)](https://towardsdatascience.com/hello-i-am-pami-937439c7984d/)\n## [Hello! I am PAMI](https://towardsdatascience.com/hello-i-am-pami-937439c7984d/)\n[Programming](https://towardsdatascience.com/category/programming/)\nA new Pattern Mining Python library for Data Science\n[Uday Kiran RAGE](https://towardsdatascience.com/author/uday.rage/)\nNovember 18, 20215 min read\n  * [![](https://towardsdatascience.com/images/fallback-image.jpg)](https://towardsdatascience.com/python-lists-are-overrated-776e87cda3e5/)\n## [Python Lists Are Overrated](https://towardsdatascience.com/python-lists-are-overrated-776e87cda3e5/)\n[Programming](https://towardsdatascience.com/category/programming/)\nConsider these potentially superior alternatives\n[Aashish Nair](https://towardsdatascience.com/author/aashishnair/)\nOctober 4, 20215 min read\n\n\n  * [YouTube](https://www.youtube.com/c/TowardsDataScience)\n  * [X](https://x.com/TDataScience)\n  * [LinkedIn](https://www.linkedin.com/company/towards-data-science/)\n  * [Threads](https://www.threads.net/@towardsdatascience)\n  * [Bluesky](https://bsky.app/profile/towardsdatascience.com)\n\n\n[](https://towardsdatascience.com/)\nYour home for data science and AI. The world's leading publication for data science, data analytics, data engineering, machine learning, and artificial intelligence professionals.\nSubscribe to Our Newsletter[Write For TDS](https://towardsdatascience.com/submissions/)•[About](https://towardsdatascience.com/about-towards-data-science-d691af11cc2f/)•[Advertise](https://contact.towardsdatascience.com/advertise-with-towards-data-science)•[Privacy Policy](https://towardsdatascience.com/privacy-policy/)•[Terms of Use](https://towardsdatascience.com/website-terms-of-use/)\n© Insight Media Group, LLC 2026•[The New Stack](https://thenewstack.io)•[roadmap.sh](https://roadmap.sh)•[Creator Network](https://insightmediagroup.io/creator-network)\n####  Recommended Articles \nClose\n  * [ ![](https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/607686/image?etag=1782161464448&width=500&height=500) How Relevance Models Foreshadowed Transformers for NLP ](https://towardsdatascience.com/how-relevance-models-foreshadowed-transformers-for-nlp/ \"How Relevance Models Foreshadowed Transformers for NLP\")\n  * [ ![](https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/607639/image?etag=1781250125848&width=500&height=500) Javascript Fatigue: HTMX Is All You Need to Build ChatGPT — Part 1 ](https://towardsdatascience.com/javascript-fatigue-you-dont-need-js-to-build-chatgpt/ \"Javascript Fatigue: HTMX Is All You Need to Build ChatGPT — Part 1\")\n  * [ ![](https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/607930/image?etag=1782124566054&width=500&height=500) The Subset Sum Problem Solved in Linear Time for Dense Enough Inputs ](https://towardsdatascience.com/subset-sum-problem-solved-in-linear-time-for-dense-enough-inputs/ \"The Subset Sum Problem Solved in Linear Time for Dense Enough Inputs\")\n  * [ ![](https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/3660/image?etag=1780176246070&width=500&height=500) Does Your Company Have a Data Strategy? ](https://towardsdatascience.com/does-your-company-have-a-data-strategy-e8944dbec4ae/ \"Does Your Company Have a Data Strategy?\")\n\n\n",
  "body_base_path": "attachments/bf47253b2fbd/pages/",
  "body_markdown_path": "attachments/bf47253b2fbd/pages/archived-body.md",
  "local_html": "attachments/bf47253b2fbd/pages/archived-body.html",
  "body_source": "prior_capture"
}