>
> 
>
> > [!info] Video not downloaded
> > Khiip kept the link to the original. Enable `[media] download_videos` to fetch the video file.
> > Watch at [https://www.youtube.com/watch?v=AogwEfWZVds](https://www.youtube.com/watch?v=AogwEfWZVds)
>
> ## Description
>
> Get the full step-by-step project guide here:
> https://learn.nextwork.org/projects/ai-second-brain-claude-code-2?utm_source=youtube
>
> Project 1 is here: https://learn.nextwork.org/projects/ai-second-brain-claude-code?utm_source=youtube
>
> Welcome to the Automate Your AI Second Brain project!
>
> Turn your Obsidian vault into a daily operating system with Claude Code.
>
> What you'll learn today:
>
> ๐ A private GitHub repository backing up your vault with automatic syncing via the Obsidian Git plugin.
> ๐ MCP Connectors linking Claude Code to your everyday tools like Google Calendar, Linear, and Notion.
> ๐ A /pull-sources slash command that auto-ingests Claude Code sessions, Gmail, and Granola transcripts straight into your vault.
> โ๏ธ /briefing and /debrief slash commands that generate a personalized morning brief from your wiki, calendar, and priorities, then capture your day each evening.
>
> TIMESTAMPS
> 00:00:00 - Welcome to this project!
> 02:59 - Step #1: Get Your Vault Ready
> 09:24 - Step #2: Back Up and Connect Your Tools
> 26:14 - Step #3: Auto-Ingest Your Sources
> 38:48 - Step #4: Create Your Priorities Document
> 44:38 - Step #5: Build and Run Your Daily Loop
> 1:00:42 - Secret Mission
> 1:08:37 - Before you go: Clean Up Your Resources
> 1:09:59 - Mission Accomplished!
>
> #claudecode #obsidian #nextwork #learnwithnextwork
>
> Want to join our community?
> https://community.nextwork.org/
>
> ### Chapters
>
> - [0:00](https://www.youtube.com/watch?v=AogwEfWZVds&t=0s) โ Welcome to this project!
> - [2:59](https://www.youtube.com/watch?v=AogwEfWZVds&t=179s) โ Step #1: Get Your Vault Ready
> - [9:24](https://www.youtube.com/watch?v=AogwEfWZVds&t=564s) โ Step #2: Back Up and Connect Your Tools
> - [26:14](https://www.youtube.com/watch?v=AogwEfWZVds&t=1574s) โ Step #3: Auto-Ingest Your Sources
> - [38:48](https://www.youtube.com/watch?v=AogwEfWZVds&t=2328s) โ Step #4: Create Your Priorities Document
> - [44:38](https://www.youtube.com/watch?v=AogwEfWZVds&t=2678s) โ Step #5: Build and Run Your Daily Loop
> - [1:00:42](https://www.youtube.com/watch?v=AogwEfWZVds&t=3642s) โ Secret Mission
> - [1:08:37](https://www.youtube.com/watch?v=AogwEfWZVds&t=4117s) โ Before you go: Clean Up Your Resources
> - [1:09:59](https://www.youtube.com/watch?v=AogwEfWZVds&t=4199s) โ Mission Accomplished!
>
> ## Transcript
>
> ### Welcome to this project!
>
> **[0:00](https://www.youtube.com/watch?v=AogwEfWZVds&t=0s)** Now, if your social media is anything like mine, you're seeing all of these people building Claude Code and Obsidian second brains. Now, this became extremely popular because of this man, Andre Kaparthy, who was one of the early OpenAI researchers. He put out this methodology on GitHub on how to create your own LLM knowledge base, became
>
> **[0:18](https://www.youtube.com/watch?v=AogwEfWZVds&t=18s)** super popular, and a bunch of people started trying it out saying that it was absolutely life-changing. Now, me, I've been using a second brain in Notion for about the last year. So, I wanted to try this out. So, last week I built a part one of this project series where I built a second brain with Claude Code and
>
> **[0:35](https://www.youtube.com/watch?v=AogwEfWZVds&t=35s)** Obsidian, and we went through and we actually created exactly what you see right here. Now, I got a lot of comments, feedback, people being like, "Oh, how can I improve this? What are some other things that I can do here?" So, me, I wanted to experiment on the second brain see if it was actually useful cuz I think there's
>
> **[0:53](https://www.youtube.com/watch?v=AogwEfWZVds&t=53s)** a lot of people on social media who just put this out and then they say it's life-changing, the best thing ever, but they never actually use it. So, I wanted to see if this is actually useful and something that I can actually get value out of. Um and then hopefully you guys can get value out of and build things for yourself as well. So, in this project, we are not going to be using the terminal cuz that was one of the
>
> **[1:11](https://www.youtube.com/watch?v=AogwEfWZVds&t=71s)** most common things that I got. We're going to be using the Claude Code desktop UI, which is very, very nice. We're also going to be looking at different things like routines so that we can schedule tasks to run in the cloud instead of leaving our laptop on the whole time. We're going to look at token efficiency, and we're going to just make our second brain a lot better.
>
> **[1:29](https://www.youtube.com/watch?v=AogwEfWZVds&t=89s)** And let's the end if we actually build something that is worthwhile. This is only going to take about an hour to do. Uh I'd recommend doing part one of the project series if you haven't, but you can actually do part one within this step-by-step guide as well. You don't have to have any experience, and by the end of this project, you're going to have a private GitHub repo that's going to back up your uh all of the work that
>
> **[1:48](https://www.youtube.com/watch?v=AogwEfWZVds&t=108s)** you're doing, and it's going to plug into Obsidian. We're going to use MCP connectors, which are going to connect different tools, so things like Google Calendar, Linear, Notion, Slack, all of these different areas going to connect into your brain so that you can run these pull sources and auto ingest all the information that
>
> **[2:05](https://www.youtube.com/watch?v=AogwEfWZVds&t=125s)** you want. You're going to learn how to customize that. You're going to learn how to also create some briefing commands and debrief commands so you will get an entire automated schedule of your day, and at the end of the day, you'll run through what you've actually done so that you can adjust things and tick things off as you go. Now, the most important part in this project, or the
>
> **[2:24](https://www.youtube.com/watch?v=AogwEfWZVds&t=144s)** part that I think is most valuable, is actually the power of cloud routines. This is something that was released by Anthropic like about a week ago now, I'd say, maybe a week and a half. And what this is going to let you do is run daily tasks in the cloud so you don't have to keep your laptop on, and actually get these things to run
>
> **[2:42](https://www.youtube.com/watch?v=AogwEfWZVds&t=162s)** anytime that you want. Now, this is a free project. You can get this entire guide for free. I'll leave it in the link down below. But, all you need is a Claude Pro or Claude Max subscription. So, let's go ahead and get started with this project. As you can
>
> **[2:58](https://www.youtube.com/watch?v=AogwEfWZVds&t=178s)** So, let's go ahead and do step one here,
>
> ### Step #1: Get Your Vault Ready
>
> **[3:01](https://www.youtube.com/watch?v=AogwEfWZVds&t=181s)** and that is getting our vault ready. So, in the first part of the project, we did the project in our terminal. In this part, we're going to connect in all of these MCP connectors to calendar, chat, docs, all these different different areas. And by the end of this step, we're actually going to be in the same part uh that we were in part one, but
>
> **[3:18](https://www.youtube.com/watch?v=AogwEfWZVds&t=198s)** we're going to be connected in with those MCPs. So, in this step, I am setting up Claude Code desktop, uh and I'm also going to bring in part one of the vault, and scaffold a new Claude MD file with four {slash} commands. Then, I'm going to verify that
>
> **[3:37](https://www.youtube.com/watch?v=AogwEfWZVds&t=217s)** everything works, and this will get me to the point where I should have been if I had done part one. There we go. So, let's go ahead done here, and and in case you've never done a Next.js project before, as you do the project right here, just click this documentation button, and you actually see all of your work getting live added in, and this is very, very useful
>
> **[3:55](https://www.youtube.com/watch?v=AogwEfWZVds&t=235s)** because you can showcase your work to recruiters or to your friends or anyone else who wants to do this. Now, I have actually already installed Claude desktop, which you see right here. But, in case you haven't, you can click this tab right here, and it'll run you through all the steps that you need to be able to install Claude desktop. Now,
>
> **[4:14](https://www.youtube.com/watch?v=AogwEfWZVds&t=254s)** I have, so I'm going to go here, and I'm going to make sure that I go into this this code tab right here. Now, the code tab is one that I was already selected in. Yours might look something like this. Don't worry. Click this tab right here. Those two little What are they called? I don't know. I always call them
>
> **[4:31](https://www.youtube.com/watch?v=AogwEfWZVds&t=271s)** crocodiles. The crocodiles, and you'll see something that looks like this. Now, the first thing I'm going to do, I'm running Opus 4.7. I'm just going to change this to Sonnet 4.6. Sonnet 4.6 is going to be more than powerful enough to handle what we're going to do in this project, and we don't want you spending
>
> **[4:48](https://www.youtube.com/watch?v=AogwEfWZVds&t=288s)** too many credits. Uh of course, if you're on a Claude Pro or Max plan, you're not going to be charged anything for every usage that you have, but you may run into sessions session limits. Uh but, in this project, we're actually going to show you how to optimize your token efficiency as well. So, that is something we're going to do as well. So, let's go back to the guide
>
> **[5:06](https://www.youtube.com/watch?v=AogwEfWZVds&t=306s)** here. I'm going to scroll down. We're running this in the desktop because so many people spam me saying they didn't want to use the terminal. So, >> [laughter] >> that's the reason we're doing this in the desktop. It is also a lot easier to use uh this interface as well. Now, again, I have already done part one of this project, but if you're starting from
>
> **[5:24](https://www.youtube.com/watch?v=AogwEfWZVds&t=324s)** scratch, you can do a really quick version over here, and this is going to walk you through the Obsidian setup. But, I have completed part one, so I'm going to make sure that I follow these steps right here. We're going to set local as our environment, and we're going to navigate to our second brain folder, which is in our documents. So, I can go into local here.
>
> **[5:43](https://www.youtube.com/watch?v=AogwEfWZVds&t=343s)** That's exactly what we want. And I'm going to go to the second brain folder. I've already done this, obviously, but I'm going to go into here, go documents, and this is the second brain that I want to open up, and this is from our last project. So, you should see something that looks like this, and make sure you deselect work tree. Uh work tree is
>
> **[6:01](https://www.youtube.com/watch?v=AogwEfWZVds&t=361s)** going to create an isolated copy of this repo, and that's not what we want. We want to be working on the main branch here. So, let's go back to the project guide. We will scroll down here once it loads, and we're going to set the permissions to ask permissions. Uh you can either set it to ask or auto accept um the
>
> **[6:19](https://www.youtube.com/watch?v=AogwEfWZVds&t=379s)** edits. I like to set it to uh to ask permissions at first if I'm trying to understand something new that I'm doing. In this case, I've already done this project, so I'm going to leave this as auto edits um or accept edits. But, if you have ask permissions, it'll always ask you to uh for permission essentially before Claude goes ahead and does
>
> **[6:39](https://www.youtube.com/watch?v=AogwEfWZVds&t=399s)** things. So, let's scroll down here. I'm going to take a screenshot of the second brain vault, and we're going to put this in here. So, go into here. I'm going to take a screenshot of this, and then I'm going to drag the screenshot into here, hit done, and you
>
> **[6:56](https://www.youtube.com/watch?v=AogwEfWZVds&t=416s)** will see the screenshot populating in here looking beautiful, which is nice. Now, let's scroll down here. Let's verify that everything is working. So, last check whether you bought your part one vault or scaffolded a new one, and we're going to run these four {slash} commands. Now, these are slash
>
> **[7:13](https://www.youtube.com/watch?v=AogwEfWZVds&t=433s)** commands we created last time. So, we're going to go ahead into here. We're going to say list the commands available in this vault and summarize the Claude MD in one paragraph each. So, I'm going to hit done here. Now, let's see what Claude is doing here. All right, looking beautiful.
>
> **[7:32](https://www.youtube.com/watch?v=AogwEfWZVds&t=452s)** Yep, this is looking right. I already actually have these commands in here, which I don't want. I'm going to say, "Can you please delete the {slash} briefing and the {slash} debrief commands uh and the {slash} pull resources so that I just have the first four commands as this is where I want to start the
>
> **[7:51](https://www.youtube.com/watch?v=AogwEfWZVds&t=471s)** project." Nice. Of course, when you're doing demos like this live, things like this are going to happen, but I want to get to the exact same point that everyone is at so that we can all do this together. Now, it might take some time to do this, so I'll join you back when it's all done. All right, so it's all looking done now. I'm actually going to just
>
> **[8:09](https://www.youtube.com/watch?v=AogwEfWZVds&t=489s)** rerun this right here, and I will go into a new session. So, I can just go up to the top left just here, click new session, and I'm going to run this again. Hopefully, we've got the right thing. So, 1 2 3 4, that is perfect. These are the four things we want. Ingest is going to process new
>
> **[8:26](https://www.youtube.com/watch?v=AogwEfWZVds&t=506s)** files from raw into wiki pages. We've got answer questions by synthesizing wiki content, health checks for broken links, orphans, and stale pages plus contradictions, and then log, which is kind of like a log of all the things that we're doing. So, this is perfect. This is exactly what we want.
>
> **[8:44](https://www.youtube.com/watch?v=AogwEfWZVds&t=524s)** I'm going to go back into here. I'm going to scroll down, and we can see these four commands right here, which is nice. So, I can go ahead, and I can take a screenshot of this, and I'm going to paste it into this box here. And now it says, "Which four {slash} commands are you carrying into the rest
>
> **[9:02](https://www.youtube.com/watch?v=AogwEfWZVds&t=542s)** of the part two, and what is each one for?" I'm carrying in {slash} ingest, {slash} query, {slash} lint, and {slash} log.
>
> **[9:22](https://www.youtube.com/watch?v=AogwEfWZVds&t=562s)** Amazing. So, let's go ahead. Yeah, and
>
> ### Step #2: Back Up and Connect Your Tools
>
> **[9:24](https://www.youtube.com/watch?v=AogwEfWZVds&t=564s)** that brings us onto step two. All right, so in step two, what we're going to do is back up and connect our tools. Now, our vault is loaded with {slash} ingest, and it stitched your raw materials into a proper wiki. Now, this is obviously something we did in part one. If you
>
> **[9:42](https://www.youtube.com/watch?v=AogwEfWZVds&t=582s)** haven't, make sure you go up and you do that. But, beautiful. Uh this is what we want, but everything is still living on our laptop. Now, Claude still only knows what is inside that folder. So, next we're going to give our second brain a home on the internet. We're going to use GitHub to do this, and we're going to automate
>
> **[9:59](https://www.youtube.com/watch?v=AogwEfWZVds&t=599s)** this as well. We're going to use a plugin with Obsidian to auto sync every 10 minutes in the background so that uh GitHub and our Obsidian are always in sync. And then lastly, we're going to wire at least one MCP connector so Claude can read our calendar, chats, or docs. So, in this step, I'm
>
> **[10:18](https://www.youtube.com/watch?v=AogwEfWZVds&t=618s)** going to create a private GitHub repo to push our vault to. I'm also going to connect our Obsidian uh plugin so that we can auto sync every 10 minutes, and I will connect my Google Calendar MCP. Beautiful.
>
> **[10:36](https://www.youtube.com/watch?v=AogwEfWZVds&t=636s)** Let's go ahead and hit done here. And now we're going to do we're going to check uh if we have Git installed. If you don't, let's actually go into the Claude desktop version right here. Let's see what I've never actually done this. But, uh I've always used the terminal,
>
> **[10:55](https://www.youtube.com/watch?v=AogwEfWZVds&t=655s)** but you can see that you can run to terminal commands in this UI, which is beautiful. So, our Git version is this right here. That's exactly what we want. So, we have Git installed. If you don't, make sure to click this, and you can go ahead and do this. Now, next we're going to add in uh username. This is a username for our
>
> **[11:14](https://www.youtube.com/watch?v=AogwEfWZVds&t=674s)** GitHub account. Um if you don't have a GitHub account installed, you're going to make sure that you create one as well, which you can do in here. Um but, make sure that you have a GitHub account created. I have already set this up, but essentially all I would do here is go username, and I'd put in my GitHub
>
> **[11:31](https://www.youtube.com/watch?v=AogwEfWZVds&t=691s)** username, which is minimus7, and then I would put my user email, which is maximus@next.org. Now, the reason we do this is because Git is going to attach a name and email to every commit or save that we make to this vault, and it's going to show who made the change. So, even if we're on a solo repo, it's still good practice to
>
> **[11:49](https://www.youtube.com/watch?v=AogwEfWZVds&t=709s)** do that. But, now what we're going to do is go ahead and create a repo. So, let's go to GitHub right here. I'm going to open up this. I'm going to choose myself as an owner cuz I'm in a few different organizations, and I'm going to name this second brain. Perfect. Now, let's go back to
>
> **[12:11](https://www.youtube.com/watch?v=AogwEfWZVds&t=731s)** the guide right here. Description, my AI second brain vault synced with Claude code. That's beautiful. And we're going to actually change this to private. We don't want people to see this. We're not going to add in a read me or a get ignore or anything like that, and we're going to go ahead and
>
> **[12:28](https://www.youtube.com/watch?v=AogwEfWZVds&t=748s)** create our repository here. Now, let's go back to the guide. We'll scroll down a bit. And now that the empty remote repository is waiting, swing back to your terminal and add in a get ignore, and push your first commit. So, before the first commit, tell get
>
> **[12:46](https://www.youtube.com/watch?v=AogwEfWZVds&t=766s)** which files to skip. Some files inside your vault are specific device specific noise that would only cause merge conflicts across machines. So, let's go to our terminal. We're going to CD into documents in our second brain folder. And I have never actually done this. I
>
> **[13:03](https://www.youtube.com/watch?v=AogwEfWZVds&t=783s)** actually did this firstly in the terminal, but I'm kind of interested to see if this works. So, it's going to Oh my gosh. Let's go. Such a clean UI. I think the future is going to be very little terminals, to be honest. Same with this. I wonder what will happen if we run this command. So, we're opening up our get
>
> **[13:22](https://www.youtube.com/watch?v=AogwEfWZVds&t=802s)** ignore now. Perfect. This is exactly what we want to see in here. So, if we go back to the guide right now, um you can see that it is already pasted in these right here. Um if you're not seeing that, just copy this, and I think this is also because I had a get ignore running. And
>
> **[13:41](https://www.youtube.com/watch?v=AogwEfWZVds&t=821s)** you want to press command save to make sure that we save this or control S if you're on Windows. We're going to save that file right there. And essentially what we're excluding is this workspace JSON from Obsidian, and then the mobile JSON. So, we're going to save your personal Obsidian layout and
>
> **[14:00](https://www.youtube.com/watch?v=AogwEfWZVds&t=840s)** like which notes are open, how your panes are arranged, and where your cursor is. So, that is specific to our device and that we're on, so syncing it would just override our layout every single time that we switch machines. So, we don't want to do that. We don't want to save all of these random things that we don't need to do every time that we're on a different machine.
>
> **[14:17](https://www.youtube.com/watch?v=AogwEfWZVds&t=857s)** Now, lastly, we also included trash in our get ignore, and this is Obsidian's recycling bin for deleted notes. We don't want to push our deleted notes. We want to delete them forever, so that makes sense. Now, let's go initialize your vault as a Git repo and make your first commit. So,
>
> **[14:36](https://www.youtube.com/watch?v=AogwEfWZVds&t=876s)** in our terminal, we're going to go ahead and do this. I'm going to go into here. I'm going to go get commit. So, we're initializing, we're adding, and then we're committing. So, I will allow this. And that is beautiful. Amazing.
>
> **[14:55](https://www.youtube.com/watch?v=AogwEfWZVds&t=895s)** Now, let's scroll down here. And we can do this. So, go back to your second brain repo on GitHub and copy the commands or push and um for this right here. And if you've already initialized the repo in a previous project or you've done this um before, then this is going to
>
> **[15:13](https://www.youtube.com/watch?v=AogwEfWZVds&t=913s)** help you out right here. Um if not, you're completely fine. So, let's go ahead and run this right now. And we're going to run these commands. This is the remote origin. Perfect. It's all looking beautiful.
>
> **[15:32](https://www.youtube.com/watch?v=AogwEfWZVds&t=932s)** This is exactly what we want to see. Push successfully. Branch main is now tracking the right branch that we want. That is beautiful. So, let's go scroll down here, and we're going to go back to GitHub here, and if I hit this refresh button, you should see
>
> **[15:50](https://www.youtube.com/watch?v=AogwEfWZVds&t=950s)** all of these files. How magical. Let's go ahead and take a screenshot of this, and I'm going to go back into here, and I'm going to paste this into this box right now. Now, what we're going to do
>
> **[16:09](https://www.youtube.com/watch?v=AogwEfWZVds&t=969s)** is set up an auto sync with Obsidian Git. So, pushing once is nice, but pushing every 10 minutes forever without thinking about it, that is a pretty cool thing to do. Now, this is what uh the Obsidian Git plugin does. So, let's go ahead and do that. So, we're going to go into
>
> **[16:26](https://www.youtube.com/watch?v=AogwEfWZVds&t=986s)** Obsidian now. I'm going to open this up. Obsidian. And we're going to go to this toggle window right here. I'm going to click into settings, and I actually already have this installed, but I'm going to show you how to do it. Go to community plugins right here. I'll
>
> **[16:43](https://www.youtube.com/watch?v=AogwEfWZVds&t=1003s)** delete it so that I don't have it installed. And now, we want to go to this browse tab right here. We're going to go type in Git. Click on that, and then install Git. Now, we're not actually done here. We need to click enable, and this is going
>
> **[17:01](https://www.youtube.com/watch?v=AogwEfWZVds&t=1021s)** to enable us uh to connect to the GitHub repo that we want. So, let's go back to the project guide here. We will scroll down, and we are up to here. We've enabled it. Now, we want to go ahead and change some settings. So, we're going to go to the settings tab. We're going to set up auto
>
> **[17:20](https://www.youtube.com/watch?v=AogwEfWZVds&t=1040s)** commit and sync interval to every 10 minutes, and we're going to also going to choose auto commit and sync after file edits, and also pull on startup. Plus push and commit on sync. A lot of things. Don't worry if you didn't catch that. We will do it slowly. So, you can go settings right here.
>
> **[17:37](https://www.youtube.com/watch?v=AogwEfWZVds&t=1057s)** If you didn't know how to do that, and you're lost on this page, just go back into settings, go to Git, and then we need to enable a few things here. So, let's scroll up. We will scroll down a little bit. What am I looking for? Wait. Let's go back to the project
>
> **[17:59](https://www.youtube.com/watch?v=AogwEfWZVds&t=1079s)** guide. Even I forgot. We want to have uh settings Git, and then we want auto commit and sync interval. So, let's look at that. Auto commit and sync interval. Where is it? I just had this before.
>
> **[18:18](https://www.youtube.com/watch?v=AogwEfWZVds&t=1098s)** That's so interesting. Give me 1 second. I'm just going to have a look. Oh, it wasn't working because I have disabled on this device, so it's going to take a little bit of time. I will uh I'll join you back when this is all set up. Okay. So, now it's looking a bit better. This is what we want. So, we want to enable this. That's the first
>
> **[18:37](https://www.youtube.com/watch?v=AogwEfWZVds&t=1117s)** one we want. And we're going to do auto commit after 10 uh 10 minutes right there. That's what we want. We will also auto pull interval. Let's go 10 minutes as well. We don't need to uh sync on stage files. Commit messages is fine.
>
> **[18:58](https://www.youtube.com/watch?v=AogwEfWZVds&t=1138s)** Let's scroll down here. We want to pull on startup, so every time that we uh open up Obsidian, it's going to pull from our vault. And push and commit on sync. That's beautiful. Pull and commit on sync. That's what we want as well. So, if we run these sync commands, it will all work with our GitHub
>
> **[19:17](https://www.youtube.com/watch?v=AogwEfWZVds&t=1157s)** repo, which is beautiful. So, that's all we need. We'll go back to the project guide right here. We're going to scroll down, and we will go into this section right here, which is uh running our own get commit and sync. So, if we go command P,
>
> **[19:35](https://www.youtube.com/watch?v=AogwEfWZVds&t=1175s)** that's going to open up this command palette, and we can go and get com um commit. Oh, maybe I need to restart this um because it hasn't pulled in the latest changes. Yeah, so if your if yours isn't coming
>
> **[19:53](https://www.youtube.com/watch?v=AogwEfWZVds&t=1193s)** up with get commit and sync there, often one of the things I find is that you need to run you need to essentially close the application and run it again. So, restart it. So, I'm going to go shift P right here. You can see get commit and sync is at the top. And I will run this here. There's nothing that we actually need to
>
> **[20:10](https://www.youtube.com/watch?v=AogwEfWZVds&t=1210s)** change right now. Um but if we go to our GitHub repo, because what it's done is it's pushed and pulled on sync when I opened it up again, you can see that we've made those changes. So, let's go to our repo. And you can see there was a commit 6 minutes ago, which is exactly when this
>
> **[20:28](https://www.youtube.com/watch?v=AogwEfWZVds&t=1228s)** happened, which is beautiful. Um let's double-check. Nice. There we go. So, it was like 6 minutes ago. I don't think that actually happened 6 minutes ago. It happened 1 minute ago, which is what we wanted. So, we can see our commit is in there once we refreshed our page, and we can go back to the project guide right here.
>
> **[20:47](https://www.youtube.com/watch?v=AogwEfWZVds&t=1247s)** If you don't see a commit on GitHub, you can click this tab right here, and there's a few different things that you can run through. But, it can be a little bit frustrating when you haven't closed your Obsidian and then restarted it again, cuz you're not going to see those changes. Now, let's take a screenshot of that commit
>
> **[21:05](https://www.youtube.com/watch?v=AogwEfWZVds&t=1265s)** right here. I'm going to go screenshot this. I will go into here and click done. And then we will add in our connectors now. So, our vault is versioned and
>
> **[21:23](https://www.youtube.com/watch?v=AogwEfWZVds&t=1283s)** safe, and we're going to let Claude we're going to now give Claude a window into the world outside of our vault. And this is where MCP connectors are super super important. If you're wondering what MCP is, it stands for model context protocol. And essentially, I like to think about it as a way for AI tools a a simple workflow for them to connect to
>
> **[21:44](https://www.youtube.com/watch?v=AogwEfWZVds&t=1304s)** other AI tools. Kind of like we have HTTPS for the internet. It's a standard. It's a framework for the internet to essentially people know the rules of websites. What this is doing, it's it's allowing AI tools to know the rules so that they can connect with other AI tools.
>
> **[22:02](https://www.youtube.com/watch?v=AogwEfWZVds&t=1322s)** So, we're going to go to Claude desktop. We're going to click the plus and we're going to select a MCP connectors in here. Let's go to Claude desktop. We'll click this plus and we're going to go connectors. And we will go add connectors. So, what do we want to add in here? The question to that is
>
> **[22:20](https://www.youtube.com/watch?v=AogwEfWZVds&t=1340s)** what do you want to have in your second brain? Do you want to have Google Calendar in here? Do you want to have linear? Do you want to have Slack? You can add in whatever you want. And in this case, I'm going to add in Google Calendar. And you may see that mine doesn't have a plus yet because I've already added this in, but I can go into here.
>
> **[22:38](https://www.youtube.com/watch?v=AogwEfWZVds&t=1358s)** I'll disconnect it. I'll remove it so that I can show you guys how to do it. You're going to go connect and it's going to go ahead and connect you to your Google Calendar. Now, you'll see that mine comes up with an error there, cuz it's already done this before and I can see Google Calendar is already enabled here.
>
> **[22:56](https://www.youtube.com/watch?v=AogwEfWZVds&t=1376s)** But, there's all these different tools that I have as MCPs that I don't use in my second brain that I use for other things here. Um but let's say I want Google Calendar, linear, Notion. Maybe my Gmail, too. These are things that I would probably want in my second brain to give it context. Now, we can go back to the project guide
>
> **[23:15](https://www.youtube.com/watch?v=AogwEfWZVds&t=1395s)** right here. We're going to uh have different settings and that we can actually control. So, in our Google Calendar, if I wanted to give it access to only certain things, I could go into connectors. I could go to manage connectors here. I'll go to Google Calendar.
>
> **[23:32](https://www.youtube.com/watch?v=AogwEfWZVds&t=1412s)** And there's some things that I I've I've given Claude the MCP connector always the ability to read use read-only tools, but things like creating calendar events, deleting calendar events, responding or updating, I need approval. So, uh the MCP tooling will stop and it
>
> **[23:51](https://www.youtube.com/watch?v=AogwEfWZVds&t=1431s)** will ask me for approval before it actually goes ahead and does these things. Now, we can go ahead, we can customize all of these different things for our Gmail, Google, linear, whatever you want. Take your time here. Look through all of the settings so that you can get to a place where you're actually happy with the accessibility
>
> **[24:09](https://www.youtube.com/watch?v=AogwEfWZVds&t=1449s)** that you've given these tools. So, let's go back to customize here. I will go back to the project guide and I will scroll down to here. Now, I will copy this in and I'm going to go to the Claude desktop session that I have running here in Claude code.
>
> **[24:27](https://www.youtube.com/watch?v=AogwEfWZVds&t=1467s)** I'm going to go what meetings do I have today? And you're going to watch the MCP tool get called here. So, let's see. Using tool search, and you can see it's actually searching for events in my calendar. Uh and it's using that Google Calendar MCP. Now, I can see that I have five meetings right now. It's actually
>
> **[24:46](https://www.youtube.com/watch?v=AogwEfWZVds&t=1486s)** currently 3:20 p.m., so I'm missing my one-on-one with my boss, which is kind of bad, but she's outside and I think she's going to be cool with it because I'm trying to record this project for you guys. So, you can see that now I have my Google Calendar synced to my Claude account, which is crazy cool,
>
> **[25:03](https://www.youtube.com/watch?v=AogwEfWZVds&t=1503s)** right? Now, we will go back to the project guide because this is just the start. This is literally just the start of the things that we can do. So, I'm going to take a screenshot of Claude code desktop running and we will answer the question as well. So, Claude code going to be able to do this. Beautiful.
>
> **[25:22](https://www.youtube.com/watch?v=AogwEfWZVds&t=1522s)** I will paste this into here. And I connected my Google Calendar to Claude and pulled in my meetings for the day. Now, of course, like I said, you can pull in all of these different resources. You can add in your Notion.
>
> **[25:39](https://www.youtube.com/watch?v=AogwEfWZVds&t=1539s)** You can add in your linear. You can add in your Google Calendar. The more things you add in, the more context you will use. And we will show you how to optimize and make this efficient, but it is something worth noting that if you're building a second brain and you are building it with a lot of different connectors, it is going to be expensive
>
> **[25:57](https://www.youtube.com/watch?v=AogwEfWZVds&t=1557s)** to run. It's going to use up a lot of tokens and it may be something that you are cautious about. Um but again, we can always customize things and I think the the purpose of this project is to teach you how to do these things so that you can go ahead and customize them yourself.
>
> ### Step #3: Auto-Ingest Your Sources
>
> **[26:14](https://www.youtube.com/watch?v=AogwEfWZVds&t=1574s)** Now, this actually brings us on to step project. Now, in step three, what we're going to do is auto ingest our sources. So, obviously it is tough to do this manually, and now we have our vault backed up. We can also reach our different tools with MCP connectors. But right now, the reach is read-only. Every briefing still starts with a cold vault
>
> **[26:33](https://www.youtube.com/watch?v=AogwEfWZVds&t=1593s)** unless you drop a fresh note from raw yourself. Now, this is exactly what the copy-paste version of this of of essentially creating a second brain would look like. We don't want this. We want to automate it. So, let's run a slash command here that is going to capture from our real sources on demand and ingest them using
>
> **[26:53](https://www.youtube.com/watch?v=AogwEfWZVds&t=1613s)** the slash ingest command. Now, that is what takes our wiki from something you maintain to something that maintains itself, which is beautiful. That's what we want, right? So, in this step, what are we doing? I'm building a pull sources command that is going to
>
> **[27:12](https://www.youtube.com/watch?v=AogwEfWZVds&t=1632s)** capture Claude code sessions. It's going to pull in different tools that I wanted. And we're also going to look at uh triaging the pull sources captured by skimming the one-liner headings and deleting anything that doesn't belong in our wiki so that we don't waste tokens. Then we'll run a slash ingest command on
>
> **[27:32](https://www.youtube.com/watch?v=AogwEfWZVds&t=1652s)** the ones that we want and confirm new materials that are going to flow into our wiki. Remember, our wiki is where the information that we want to query will live. So, firstly, how much does it cost to do this step? Both the pull and the
>
> **[27:50](https://www.youtube.com/watch?v=AogwEfWZVds&t=1670s)** slash are going to run through our Claude subscriptions. They're not an API bill. So, they spend against your limit. You may run into session limits depending on how much you're trying to pull in, but I think it's good to actually understand that so that you can see what this is going to look like for you moving forward. Now, I'm on a max plan, so I'm not going
>
> **[28:07](https://www.youtube.com/watch?v=AogwEfWZVds&t=1687s)** to run into these issues, but if you're on a pro plan, you may. So, pull sources is light. It's mostly going to read local files and then MCP data. Um if you are running a large MCP port, it may actually require a lot of tokens. Ingest is going to be heavier. This is going to read every file in raw.
>
> **[28:25](https://www.youtube.com/watch?v=AogwEfWZVds&t=1705s)** It's going to dedupe it. What a weird word. Cross-reference and write new wiki pages. Expect it to eat a noticeable chunk of your daily quota when you first run it because it's going to be expensive. So, let's go ahead and build our pull sources.
>
> **[28:43](https://www.youtube.com/watch?v=AogwEfWZVds&t=1723s)** Slash commands are just uh files that live in our commands folder within Claude. So, we're going to write one to spell out where to look, what to write, and how to hand off to slash ingest. So, before we write the prompt, let's skim the sources you're starting starting with so we know what command is reaching to.
>
> **[29:00](https://www.youtube.com/watch?v=AogwEfWZVds&t=1740s)** And we can add more later as well. So, let's pull what we will read, not what's available. Every file your command pulls becomes a flat a file that slash ingest processes. So, wiki page it might create in any context a future slash briefing might read. The default
>
> **[29:19](https://www.youtube.com/watch?v=AogwEfWZVds&t=1759s)** posture here is selective, which is not greedy, but when you set up each source below, pick a realistic volume cap and name what to skip. Widing the net is later easy on. Shrinking a bloated wiki is harder. So, let's go ahead and do this.
>
> **[29:36](https://www.youtube.com/watch?v=AogwEfWZVds&t=1776s)** Rather than filling in the placeholders yourself in the prompt below, ask Claude to interview you about the sources, and then we can do that as well. So, let's go ahead. We'll copy this into Claude and and go into our desktop and we will paste this in. Now, what this is going to do is it's
>
> **[29:53](https://www.youtube.com/watch?v=AogwEfWZVds&t=1793s)** first going to interview us on different things and different questions that we have within here. So, we'll see here additional sources beyond Claude code Claude code sessions, which will always be source one. Which one of these do you want to pull from? So, again, if you don't want Claude's code sessions in your second brain, you don't need to have that in
>
> **[30:12](https://www.youtube.com/watch?v=AogwEfWZVds&t=1812s)** you can tell Claude this and that's the way that I've set up this project so that you can customize it yourself. So, I'm going to say I actually just want to have my calendar in here um and Claude code as well. I don't want anything else at the moment. You know what?
>
> **[30:31](https://www.youtube.com/watch?v=AogwEfWZVds&t=1831s)** Yeah, I think that's good for now. I don't want too much in here. I'm going to leave it pretty bare-bones and over time I will add to things if I want that um or not. What to pull? Just today's events, a rolling window. Um I think it actually makes sense cuz I'm going to do this daily. I just want
>
> **[30:49](https://www.youtube.com/watch?v=AogwEfWZVds&t=1849s)** today's events cuz I'm going to do this daily. Uh max number of events I'm not going to have that many meetings in a day, so it can just be the amount that are in a day. Uh only events where I have I am an attendee. Uh
>
> **[31:07](https://www.youtube.com/watch?v=AogwEfWZVds&t=1867s)** That's fine. I don't really care about this, only my calendar. And let's Yeah, you can leave public holidays and that kind of stuff. I'm happy with that naming convention. And the extra front matter keys
>
> **[31:25](https://www.youtube.com/watch?v=AogwEfWZVds&t=1885s)** uh let's just leave it as you suggest. Beautiful. So, it's going to ask us questions. Just make sure you take your time to fill these in. I'm going to go ahead and do this and it will uh be building something in the background here, which is what we want. So, I'll update you when we are done
>
> **[31:43](https://www.youtube.com/watch?v=AogwEfWZVds&t=1903s)** here. Amazing. So, this is looking good now. And this is Yep, this is exactly what I want. Cool. All good. Now, Claude is going to go ahead and it's going to create the file here. You can see it is creating a commands
>
> **[32:01](https://www.youtube.com/watch?v=AogwEfWZVds&t=1921s)** folder. Let's go ahead and allow that. And it is creating the MD file for our command that we want. Again, might take a little bit of time, but I'll join you back when it's all done. Amazing. Claude has already finished and it has created this file here. If we
>
> **[32:19](https://www.youtube.com/watch?v=AogwEfWZVds&t=1939s)** click into here, we can see the file that it's created. It's going to have detailed instructions on what the slash command is going to do. And we will go uh we'll actually take a screenshot of this. Beautiful. And we'll go back to the project guide.
>
> **[32:38](https://www.youtube.com/watch?v=AogwEfWZVds&t=1958s)** Scroll down. And I will go get that from my desktop. Oh, no. This is embarrassing. You're going to see my thousand screenshots. Anyway, we go which source are you most excited to auto ingest and what would you add in the add your own source here block first?
>
> **[32:57](https://www.youtube.com/watch?v=AogwEfWZVds&t=1977s)** Now, the most uh the source I'm most excited about is Google Calendar. For now, I want to keep things simple. Uh eventually, I will add in probably Linear because that is where we have all of our tasks as a team and I want to be able to keep up to date and also update
>
> **[33:15](https://www.youtube.com/watch?v=AogwEfWZVds&t=1995s)** Linear from my second brain. Amazing. Let's go ahead done here. We're going to scroll down and run {slash} pull resources and verify. So, running the command end to end is where the second brain is going to capture itself uh and the story is going to stop being theoretical. So, you might want to see
>
> **[33:33](https://www.youtube.com/watch?v=AogwEfWZVds&t=2013s)** the new files land in {slash} raw uh and then watch the ingest turn them into real pages. So, thing with Claude code uh and any desktop application really is that we need to close this before we can run this again. So, I'm going to go out of here. I'll type in Claude.
>
> **[33:51](https://www.youtube.com/watch?v=AogwEfWZVds&t=2031s)** And now, when we go to the code tab, we should be able to type in uh the command that we need to run, which is pull sources, if you haven't seen it before. Going to run pull sources here and this is going to allow us to be able to pull in our sources.
>
> **[34:09](https://www.youtube.com/watch?v=AogwEfWZVds&t=2049s)** So, we can go ahead, hit enter. It's going to take some time. May take around an estimate Let's say two to three minutes, depending on how many sources you have. But what it's going to do is it's going to find the last seven days for calendar cuz that's what we put our instructions in as and we will go from there. So, I'm going
>
> **[34:27](https://www.youtube.com/watch?v=AogwEfWZVds&t=2067s)** to hit uh always allow here and I'll join back with you once this is done. All right. We're looking like Claude is cooked, which is nice. And you can see this note here. Before running {slash} ingest, let's have a look at these uh files that we have in the Obsidian repo. So, let's go into here.
>
> **[34:46](https://www.youtube.com/watch?v=AogwEfWZVds&t=2086s)** Go into raw because this is where our files are going to live. We've just pulled in these sources. They're raw right now. We want them to be ingested into our wiki. So, let's go into here. I'm going to go into calendar. And as we talked about, this is only going to pull in my calendar events for today. So, I have my one-on-one with
>
> **[35:04](https://www.youtube.com/watch?v=AogwEfWZVds&t=2104s)** Amber, which is my boss. I'm sorry, Amber. We've got lunch. We've got town hall. Um we've got two of them actually today. And then a weekly demo and retro, which is in 22 minutes, so I need to get this done really fast. So, we've got our four different sources right here. And that's what we want. Let's say I want to delete one. I don't want to have
>
> **[35:22](https://www.youtube.com/watch?v=AogwEfWZVds&t=2122s)** this in here. I am actually going to go ahead and delete this town hall. Uh and I have these four meetings in here. Again, if you did this with other things like your Claude exports or your um maybe you did it with your granola meetings or your Linear issues, these are all things you could do as well. Um but for this, I'm going to going to show
>
> **[35:40](https://www.youtube.com/watch?v=AogwEfWZVds&t=2140s)** you how to do this with the calendar and then you can pull in more resources as you go as well. So, I will scroll into here and I'm going to go down. We have in our settings right here, which is beautiful. That's what we want. We want the files to look like this as well,
>
> **[35:58](https://www.youtube.com/watch?v=AogwEfWZVds&t=2158s)** um which we saw. And then we're going to look at uh deleting what we need. I've just gone ahead. I've deleted what I wanted to. And now we can go ahead and run ingest. And ingest, what is that going to do? Ingest is going to we need tokens,
>
> **[36:16](https://www.youtube.com/watch?v=AogwEfWZVds&t=2176s)** right? To to ingest everything that we have deleted in this raw file. Um not everything we've deleted, everything that remains in this raw file. So, if you don't do this, then running ingest is going to convert everything in these files into our wiki and we don't want to do that. So, I'm going to go into here. I'm going to run ingest. Make
>
> **[36:34](https://www.youtube.com/watch?v=AogwEfWZVds&t=2194s)** sure you're going to say run ingest on just the calendar files. {slash} ingest on just the calendar files in raw. Beautiful. Uh obviously, if I wanted to, I could run this on everything, but in here, I
>
> **[36:52](https://www.youtube.com/watch?v=AogwEfWZVds&t=2212s)** just want to do this so I can show you guys the example of what this looks like. So, now again, it might take a little bit of time, so I'm just going to leave it for now and I will join back with you once it's done. So, you can see that right now what it's doing is ingesting the calendar files.
>
> **[37:09](https://www.youtube.com/watch?v=AogwEfWZVds&t=2229s)** It's then going to update the person pages. So, it's probably going to be updating Amber's files, which we saw. That's my boss. And then all of the other files that I'm in, people like Maya or Krishna, people in the team, it's going to update this with those people as well so that we can connect all of these different meetings
>
> **[37:27](https://www.youtube.com/watch?v=AogwEfWZVds&t=2247s)** to different people. Again, this is where this the power of a second brain really starts to come in. And now it's going to update the index um and it's going to actually log in something as well into our log.md file. So, let's wait for that to do that. Might take a little bit of time.
>
> **[37:45](https://www.youtube.com/watch?v=AogwEfWZVds&t=2265s)** So, now we can see a summary of what it's done. Four source summary pages created, the four meetings that I that we just saw. And it's also updated two people's pages, one with a recurring cadence for Amber and then also Maya as well.
>
> **[38:01](https://www.youtube.com/watch?v=AogwEfWZVds&t=2281s)** And we can go back to the project guide here. I'm going to scroll down and I'm going to take a photo, sorry, of this right here. Let's take a photo. Add it in here and we will hit done. So, our vault is now going to capture
>
> **[38:18](https://www.youtube.com/watch?v=AogwEfWZVds&t=2298s)** itself on your terms and you can run this whenever you want uh so that you don't have to manually be doing this all the time, ingesting uh essentially going to these different sources, exporting it out daily, ingesting it like that. You can run this manually um without actually having to do it
>
> **[38:36](https://www.youtube.com/watch?v=AogwEfWZVds&t=2316s)** by hand. So, the good thing about this as well is that you can delete the sources that you don't want so that you don't ingest them and then don't use too many tokens up.
>
> ### Step #4: Create Your Priorities Document
>
> **[38:48](https://www.youtube.com/watch?v=AogwEfWZVds&t=2328s)** But this leads us on to step four. And in step four, we're going to create our priorities.md. Now, the vault captures itself now, but Claude code sessions, inbox threads, and meeting transcripts and more all flow into raw on demand. So, when you run that command, pull
>
> **[39:06](https://www.youtube.com/watch?v=AogwEfWZVds&t=2346s)** sources, and ingest promotes them into wiki. But a vault full of context is still not a vault that knows what you actually care about. So, if you ask Claude code for a morning briefing right now, it would pull in every single event, which is not what we want. We don't want all these bits of context in
>
> **[39:23](https://www.youtube.com/watch?v=AogwEfWZVds&t=2363s)** here cuz it's going to be really crowded for our week. So, now, uh AI second brain, what does it need? It needs a steering wheel. It needs something to actually give it direction. So, a place that our real priorities are for the week. So, in this step, we're going to create a priorities.md with five sections and we're going to give Claude
>
> **[39:40](https://www.youtube.com/watch?v=AogwEfWZVds&t=2380s)** a clean way to separate deadlines from long-term responsibilities in the background. So, in this step I'm creating a priorities.md folder that is going to give context to what is actually important for me, so that when I run my briefings it is something that I care about. Go ahead and I'm going to hit
>
> **[39:59](https://www.youtube.com/watch?v=AogwEfWZVds&t=2399s)** enter there. Scroll down. We're going to open Claude code desktop with our second brain vault, and we're going to paste this prompt into our chat. So, I'm going to actually run a new session here. Make sure that we have second brain selected, work tree off. I'm going to paste this in, and it's going to create
>
> **[40:17](https://www.youtube.com/watch?v=AogwEfWZVds&t=2417s)** a priorities.md at the vault root, so next to the Claude MD files, and it's going to ask us some questions. So, it says, "What projects are you working on at the moment?" I am working on making sure that Next Work has 15% week-on-week growth every single week of our user base.
>
> **[40:37](https://www.youtube.com/watch?v=AogwEfWZVds&t=2437s)** Uh and we are doing this for the entirety of the year. In terms of areas, uh I am across content creation. I also in my personal life uh have finances to take care of, plus fitness, uh and I'm also working across the team. So, I have team management in there.
>
> **[40:56](https://www.youtube.com/watch?v=AogwEfWZVds&t=2456s)** Resources. Mainly looking at uh What do I look at the most? The best place to to learn in the world. learn.nextwork.org is the resource that I use basically to learn everything. So, that's what I do, and then the key people I work with are Amber, John,
>
> **[41:14](https://www.youtube.com/watch?v=AogwEfWZVds&t=2474s)** Maya, Pano, Krishna, and Natasha. I'm also going to say in here, "I don't want you to put anything that would be private information in my daily brief, uh because I'm running this demo for a YouTube video."
>
> **[41:32](https://www.youtube.com/watch?v=AogwEfWZVds&t=2492s)** Nice. So, this is just going to give a priorities document, so when we run our commands later on, it knows exactly what we should be looking after, uh and I don't want you to see anything private, because then I will get fired. I don't want to get fired. Anyway, it's going to take some time to do this, and
>
> **[41:49](https://www.youtube.com/watch?v=AogwEfWZVds&t=2509s)** I'll join back with you when it's all done. Great. So, now our priorities.md file is created right here. I can click into this, and we can see what it looks like. First thing it's going to say at the top is, "Edit this file weekly." Our priorities are going to change every single week, so this file is something
>
> **[42:07](https://www.youtube.com/watch?v=AogwEfWZVds&t=2527s)** that we want to look at every single week. Now, project that is ongoing for me is the 15% growth. We've been hitting that, which is good, but our content engine is also a project that uh is going to probably change as we hire more people.
>
> **[42:23](https://www.youtube.com/watch?v=AogwEfWZVds&t=2543s)** I have different areas, I have resources, and I have people in here as well, just for context when we run the next parts of our uh of the project right here. So, take a screenshot here. I'm going to scroll down, and I'm going to pop this into here. Now, let's go ahead
>
> **[42:41](https://www.youtube.com/watch?v=AogwEfWZVds&t=2561s)** and answer this question. My most specific priority is the 15% week-on-week growth. We have to hit that as a team. Uh and the specificity matters because we don't want Claude to go ahead and look at everything. We want it to be specific
>
> **[42:59](https://www.youtube.com/watch?v=AogwEfWZVds&t=2579s)** with what it's looking for, so it doesn't overload its context window and then charge us too much money, so we'll be broke. >> [sighs] >> Let's go ahead, hit done here. And we're going to update our Claude MD file to reference priorities now. So, uh at the moment, if we go to
>
> **[43:18](https://www.youtube.com/watch?v=AogwEfWZVds&t=2598s)** our folder right here, you can see the Claude MD file. Um That's kind of awkward. I didn't delete this. You can see our Claude MD file doesn't reference priorities right now. >> [laughter] >> Yeah. Let's go ahead, delete these, so that I'm on the same page as you. Let's
>
> **[43:37](https://www.youtube.com/watch?v=AogwEfWZVds&t=2617s)** go copy this in. We're going to go back to Claude code right here. Paste this in. Actually, always a good idea to start a new session, so that you're clearing your context window. You're not spending more and more each time that uh you don't clear your context window, it is going to cost you more in terms of
>
> **[43:53](https://www.youtube.com/watch?v=AogwEfWZVds&t=2633s)** tokens to run the next prompt. So, make sure you get into that habit. If you're doing a different task, make sure it is in a different session. But, what this is going to do is just update our Claude MD files. So, it's super simple. Um hopefully it has done that now, which is beautiful. And we can
>
> **[44:11](https://www.youtube.com/watch?v=AogwEfWZVds&t=2651s)** go back to the project guide. We'll scroll down, and oh my gosh, our files should look like that. Hopefully. So, if I go back to here, you can see that it's back in here, which is beautiful. Uh isn't that beautiful how things just sync up so beautifully? I said beautiful a lot of times there.
>
> **[44:30](https://www.youtube.com/watch?v=AogwEfWZVds&t=2670s)** Now, we see the files in here. We also see the tree diagram, and we can move on to step This is where we're going to
>
> ### Step #5: Build and Run Your Daily Loop
>
> **[44:38](https://www.youtube.com/watch?v=AogwEfWZVds&t=2678s)** actually create our diagrams. And by diagrams, I mean our daily loop. I don't know why I said diagrams. I'm pretty tired, guys. Anyway, we're going to create I or we're going to use our priorities.md uh which we need here to essentially create these two {slash} commands that we're
>
> **[44:56](https://www.youtube.com/watch?v=AogwEfWZVds&t=2696s)** going to be running. Now, uh MCPs are connected up. Now, we need to lay the groundwork for our daily operating system. This is a morning {slash} command that hands you your day, and an evening {slash} command that captures what happened, and one full run end-to-end to actually prove that this works.
>
> **[45:13](https://www.youtube.com/watch?v=AogwEfWZVds&t=2713s)** So, in this step, I'm building two {slash} commands, one for the start of my day, and one for the end of my day to check in what I've done. And we will run this entirety loop-to-loop, so that we can uh get a simulation of what a day would look like. I'll go ahead, I'll hit done here, and
>
> **[45:31](https://www.youtube.com/watch?v=AogwEfWZVds&t=2731s)** we will move on to the next step. So, we're going to build and test uh our {slash} briefing command here. And {slash} commands in Claude code are just markdown files living in the commands. When you type {slash} briefing, Claude code is going to read the matching briefing.md file that we create in commands, like we did just before for
>
> **[45:50](https://www.youtube.com/watch?v=AogwEfWZVds&t=2750s)** pull sources. And it's going to run it as a prompt. So, we can spec this out exactly how we want. We're going to open up Claude code, go to code the code tab, select the folders as we have before, and then we're going to paste in this prompt. So, we already have this open. I'm going to run a new session here, paste in this prompt, and
>
> **[46:09](https://www.youtube.com/watch?v=AogwEfWZVds&t=2769s)** it's going to check the priorities for my current focus, check today's calendar, scan the log for the last three entries, gen- uh reads the wiki pages related to my active projects, and then it's going to generate a brief with sections today's schedule, active threads, priority reminders, and suggested actions. It's going to append
>
> **[46:28](https://www.youtube.com/watch?v=AogwEfWZVds&t=2788s)** a timestamp uh entry to the wiki.log.md. And we can go ahead and run this. We also figure out a way to make this more effective, right? Because this Claude MD file where we're running the commands in, uh we can go ahead and we can change those. We can make this completely specked out
>
> **[46:45](https://www.youtube.com/watch?v=AogwEfWZVds&t=2805s)** to exactly what you want. Now, it will take some time again, so I'll see you back in a little bit. Great. So, we are all done here, but let's go back to the project guide to check what we're going to do next. This {slash} command uh is working the exact same way as what we've done before. Again, you might need to quit Claude
>
> **[47:02](https://www.youtube.com/watch?v=AogwEfWZVds&t=2822s)** desktop here. Like, if I go into Claude right now, and I run {slash} briefing, you're not going to see it in the terminal, so we need to go ahead, quit Claude, run this up again, and now we should be able to hit {slash} briefing just like that. Let's go back here just to double-check if we have to
>
> **[47:21](https://www.youtube.com/watch?v=AogwEfWZVds&t=2841s)** do anything, uh but we will go ahead and run this. Let's go run {slash} briefing here. Now, this is what it's going to do is it's going to create a brief for our daily uh log. This is what we're going to get at the start of the day, but again, like I said, we can change this up if we
>
> **[47:39](https://www.youtube.com/watch?v=AogwEfWZVds&t=2859s)** don't like it. We can make this look a little bit different. So, let's wait for it to do its thing, and hopefully it shouldn't actually take too long. This should be a relatively small uh task to do. But, you can also take a look at the amount of tokens it's going to use, so you can see what is efficient and what's
>
> **[47:56](https://www.youtube.com/watch?v=AogwEfWZVds&t=2876s)** not. So, it's run its course now, and you can see this is what our daily briefing would look like. You've got our calendar events right here. You've got our active threads, so what are we working on? What is What is things that we need to look into here? And then we've got priority reminders and suggested actions as well. So,
>
> **[48:14](https://www.youtube.com/watch?v=AogwEfWZVds&t=2894s)** if we go back into our log right here in Obsidian, we can see that hopefully this debrief should be in here as well. So, let's go to our wiki. We'll go to our log, and you can see that give it a second. It might take a little bit here.
>
> **[48:32](https://www.youtube.com/watch?v=AogwEfWZVds&t=2912s)** Uh if I search debrief. Let's give it some time. Give it some time, guys. Let's Obsidian do its thing. You can see that it's actually run the log over here. Normally, I'd expect it to say {slash} debrief, so if I wanted
>
> **[48:49](https://www.youtube.com/watch?v=AogwEfWZVds&t=2929s)** to, I would change the way that this log is actually outputting, so that I know exactly what I'm doing here. Um but in this case, I don't really actually care about seeing my {slash} debrief in here. Um I don't need to to do this, but uh you could if you wanted to. Now, I will go ahead, and I'll take a
>
> **[49:09](https://www.youtube.com/watch?v=AogwEfWZVds&t=2949s)** screenshot of the {slash} briefing command and the output that is generated. So, let's go ahead, run this right here. I'll paste this in, and I will hit done. It asks to build and test {slash} debrief. So, with building and testing our debrief,
>
> **[49:26](https://www.youtube.com/watch?v=AogwEfWZVds&t=2966s)** briefing is a one-shot read that's going to uh hand you context. The {slash} debrief is a different command. So, it's actually a conversation. It's going to ask us a few short questions at the end of the day and we can actually go ahead and answer those questions and then /debrief is going to propose updates to
>
> **[49:44](https://www.youtube.com/watch?v=AogwEfWZVds&t=2984s)** other pages before we can make these changes. So, let's go into our desktop code desktop and we're going to paste in this command here. I'm going to start a new session here. Always get in that habit and I will go ahead and press enter here. And Claude is going to go ahead and it's going to ask us some questions. This is going to simulate us having the end of
>
> **[50:03](https://www.youtube.com/watch?v=AogwEfWZVds&t=3003s)** the day uh and before we actually do that, it's going to ask us some questions about this file right here. So, we can see here that our file is ready. It's gone ahead and created this command file for us. So, here is the file right here. We can expand this out.
>
> **[50:21](https://www.youtube.com/watch?v=AogwEfWZVds&t=3021s)** We can read the different steps here, but it's going to ask us these four questions. So, let's go ahead. We'll go back to the project guide here. We'll scroll down a little bit. And we will quit Claude code as we normally do. And then we can run this debrief command right here. So, let's go
>
> **[50:38](https://www.youtube.com/watch?v=AogwEfWZVds&t=3038s)** here. We're going to quit. Going to open up Claude again. Oops. I mean, there we go. And now we can run /debrief. So, let's go /debrief. Hit enter. And Claude is going to ask us some
>
> **[50:54](https://www.youtube.com/watch?v=AogwEfWZVds&t=3054s)** questions. So, let's see. It's going to first read the priorities.md. What did we accomplish today? Today I am filming a YouTube video. Finished the project on building a second brain. And I also looked at some data work. I updated some standards for the team
>
> **[51:13](https://www.youtube.com/watch?v=AogwEfWZVds&t=3073s)** for different asset flows and then also uh we worked on a team retro just now as well. Cool. So, that has been my day so far. Conversations that mattered the most were what we were going to do when we
>
> **[51:31](https://www.youtube.com/watch?v=AogwEfWZVds&t=3091s)** release a new feature next week that will allow students to create their own projects. We decided on how we want to market this and what this is going to look like. By the way, that's a plug for new feature that's coming out. You'll be able to create your own projects.
>
> **[51:49](https://www.youtube.com/watch?v=AogwEfWZVds&t=3109s)** Anyway, that is something I probably shouldn't have said on a YouTube video that is not going to be out uh that is going to be out before then. Anyway, that sounds like a significant decision. Did any priorities shift or surface today? Next week I will be on content for Monday and Tuesday to make sure that we are marketing this for the launch.
>
> **[52:08](https://www.youtube.com/watch?v=AogwEfWZVds&t=3128s)** So, that has changed. Uh previously I thought I'd be writing projects Monday, Tuesday, but we've changed over to this. So, now it's going to go ahead and check the wiki index before writing the log entry. Uh so, it's going ahead. It's reading the index.md. It's now writing an entry into our log.md. So, we'll be able to
>
> **[52:27](https://www.youtube.com/watch?v=AogwEfWZVds&t=3147s)** check that over. And uh what is it saying here? New wiki page. You mentioned a feature students being able to create their own projects and the marketing strategy was decided for it. Sounds like substantial. Do you want me to create a wiki page for feature launch priority shift? Yep, let's go ahead. Yes, you can create a
>
> **[52:46](https://www.youtube.com/watch?v=AogwEfWZVds&t=3166s)** wiki page for the feature launch. Call it learner generated content. And for priority shift that's yeah, for for next week's priorities uh I do want a priority shift for the learner generated content that will be released.
>
> **[53:04](https://www.youtube.com/watch?v=AogwEfWZVds&t=3184s)** Nice. Let's go ahead and do that. Now, what this is doing is every day at the end of the day you will go through this file right here once you run /debrief and it will update your second brain to update all the things that have happened throughout the day and update all the different tasks that
>
> **[53:21](https://www.youtube.com/watch?v=AogwEfWZVds&t=3201s)** we're working on so we always stay up to date with what we're doing. And that's exactly what we want. So, saying I'll create the wiki page, update the index, and update priorities.md all at once. Beautiful. I'll link them because they're the same initiative. So, that's that linking that
>
> **[53:39](https://www.youtube.com/watch?v=AogwEfWZVds&t=3219s)** we see on uh in Obsidian in the open graph. That is beautiful. Everyone loves that, eh? Everyone wants to Everyone just wants to see the Where is it? Everyone wants to see this right here. Wow. How stunning. Everyone wants that in their life.
>
> **[53:58](https://www.youtube.com/watch?v=AogwEfWZVds&t=3238s)** So, if we go here you're back to here and we can see that three different files were created. So, we got uh priorities.md was updated. Uh LGC launch was updated um which is learner generated content. And then we have a learner generated content section as
>
> **[54:15](https://www.youtube.com/watch?v=AogwEfWZVds&t=3255s)** well. So, that is beautiful. We can go back to the project guide right here. And we can go and check the log.md file in Obsidian to check if anything has been updated. Uh obviously this can take some time as we noticed last time, but you'll see that this beautiful debrief
>
> **[54:34](https://www.youtube.com/watch?v=AogwEfWZVds&t=3274s)** has been shipped in right here of all the things that we did and then key decisions for the day so we can always see a daily record of what we have done. To be honest, if I was to do this I would build this log or like my journal into its own section. Uh that's what I want to do and that's what I have
>
> **[54:53](https://www.youtube.com/watch?v=AogwEfWZVds&t=3293s)** been doing on my own second brain on Notion for the last year and a half. Uh I prefer to have a journal within a laptop because it it can help me index and query different ideas. Uh and my handwriting sucks. To be honest, that's the main point. I can't read my own handwriting. So, I have my journal on a machine.
>
> **[55:12](https://www.youtube.com/watch?v=AogwEfWZVds&t=3312s)** But we can go ahead and actually run this again. We can try the arguments feature and this is a bit of a faster way to do this. You may think, "Oh, that takes too long." And that's correct. So, what we can do is we can run /debrief. But we're going to do this like this. So, we're going to say /debrief and then
>
> **[55:29](https://www.youtube.com/watch?v=AogwEfWZVds&t=3329s)** we're going to say these different things that we've done in the day. This is another way to run this so that we don't need to go through all the questions. This is all we want to write today. And sometimes time and stuff, you know, little time big problems. Now, it's going to go ahead and do the same thing.
>
> **[55:47](https://www.youtube.com/watch?v=AogwEfWZVds&t=3347s)** But we'll see in log that it's going to update with the changes that we made. It's going to also update the uh relevant wiki pages as well. But it's a lot faster. It's going to probably use less tokens as well um because we know exactly what we're getting out of this. So, let's give it some time and we'll
>
> **[56:05](https://www.youtube.com/watch?v=AogwEfWZVds&t=3365s)** let it do its thing. Okay, beautiful. It's already done here. So, we can go into here and we will see that everything is in here. Beautiful. That's exactly what we want. We've just added in a quick log of the day and that is our debrief. It's also updated the relevant pages. We can go in here.
>
> **[56:24](https://www.youtube.com/watch?v=AogwEfWZVds&t=3384s)** We can take a screenshot of this. We can post it in here. We can also say I'd use quick mode when I don't have much time and I can't go through all of the questions and I know exactly what I have done that day.
>
> **[56:42](https://www.youtube.com/watch?v=AogwEfWZVds&t=3402s)** Uh sometimes I won't want to use quick mode because I want to go into a bit more detail and update the different uh indexes in more clarity. With more clarity. Beautiful. And now let's confirm everything is synced to GitHub. So, you've just
>
> **[56:59](https://www.youtube.com/watch?v=AogwEfWZVds&t=3419s)** written new entries to wiki log.md from both briefings and the debrief. Obsidian get plugin should be pushing those changes to our second brain repository automatically. So, let's go back to GitHub. Right over here. I'm going to go to this repository.
>
> **[57:17](https://www.youtube.com/watch?v=AogwEfWZVds&t=3437s)** I'm going to refresh my page and some of these changes should be linking in here. But I can see that it hasn't actually pushed those last changes as of yet. So, let's go check that out in here. So, at the bottom here we can press this. Ooh, this is interesting. Let's Let Let me troubleshoot this real quick
>
> **[57:36](https://www.youtube.com/watch?v=AogwEfWZVds&t=3456s)** and I'll get back to you. I think honestly the reason this isn't working right now is because we've set our interval for 10 minutes. But what I could do is actually just go ahead and quit Obsidian and then open it up again and because we did push and pull on open, you should see that in the right hand corner there
>
> **[57:55](https://www.youtube.com/watch?v=AogwEfWZVds&t=3475s)** where it will commit things. So, let's go back to our vault here. Still not seeing any updates. Log should be updating which is kind of interesting to me that it's not. I guess this is
>
> **[58:12](https://www.youtube.com/watch?v=AogwEfWZVds&t=3492s)** This is the fun part about live demos. Things like this are going to happen. So, let's go ahead. We will start a new session here. I'm going to say Currently what would I need to do to get Obsidian to automatically ingest and push my changes from the
>
> **[58:31](https://www.youtube.com/watch?v=AogwEfWZVds&t=3511s)** log.md into GitHub? I'm kind of interested to to figure this out and I will let you know what we can do. So, honestly this is probably quite relevant. I I
>
> **[58:48](https://www.youtube.com/watch?v=AogwEfWZVds&t=3528s)** think most likely what I did do is just not follow the instructions and I didn't even put push interval on. So, definitely need to do that. Um I'm going to run this. Go into settings. Go into get. And we're going to make sure So, auto sync is every 10 minutes. Got
>
> **[59:07](https://www.youtube.com/watch?v=AogwEfWZVds&t=3547s)** auto commit after file edits. Auto pull every 10. Commit. Pull on startup. Push and get commit. Hmm.
>
> **[59:25](https://www.youtube.com/watch?v=AogwEfWZVds&t=3565s)** Interesting. I wonder if I was to run this? Okay, so I just fixed it. I just had one setting messed up
>
> **[59:43](https://www.youtube.com/watch?v=AogwEfWZVds&t=3583s)** and that was in Git. [clears throat] I should have had uh this switched off. I had this that was sent auto commit and sync only staged files, which if you're not the smartest like me, you will only stage files that are committed or commit and sync if turned off all files are
>
> **[1:00:01](https://www.youtube.com/watch?v=AogwEfWZVds&t=3601s)** committed, which is actually what we wanted. So, now if we go to GitHub, we hit refresh, you can see that there is a commit that is made. Nice. Problem solving. Let's go back to the project guide right here.
>
> **[1:00:19](https://www.youtube.com/watch?v=AogwEfWZVds&t=3619s)** I'm going to scroll back down to step five. Let's keep going down here. And I think we're almost at the end of step five actually. Take a screenshot of your Git um nice. We'll do that. >> [snorts] >> Let's take a screenshot of this right here.
>
> **[1:00:38](https://www.youtube.com/watch?v=AogwEfWZVds&t=3638s)** We will drag it into here and we'll hit done.
>
> ### Secret Mission
>
> **[1:00:42](https://www.youtube.com/watch?v=AogwEfWZVds&t=3642s)** And that actually takes us to the secret mission. So, our daily operating system is live. Each morning we can run briefing. We can run a debrief at the end of the day. And in the secret mission, we're going to do something pretty damn cool. So, let's get into that. So, this part of the project I am actually most excited for and this is scheduling your briefing as
>
> **[1:01:01](https://www.youtube.com/watch?v=AogwEfWZVds&t=3661s)** a cloud routine. Now, your daily work loop works when you open Claude code and run {slash} briefing yourself. Now, this is fine as a prototype, but realistically we want to kind of automate this stuff, right? Like this is the whole reason we're doing it. So, in the secret mission, you're going to hand {slash} briefing over to cloud routines so I can set up a daily morning
>
> **[1:01:21](https://www.youtube.com/watch?v=AogwEfWZVds&t=3681s)** briefing for you. So, this project so I can get my morning briefing questions automatically done for me. Beautiful. So, let's go in here. We're going to set it up with the UI. So, we're going to go into Claude code
>
> **[1:01:39](https://www.youtube.com/watch?v=AogwEfWZVds&t=3699s)** desktop. We're going to go to routines and then we're going to click remote and start creating our own session here. So, let's go routines. We're going to go into remote here or routines, sorry, and then click remote. And here we're going to call this What are we going to call this? Second brain.
>
> **[1:01:57](https://www.youtube.com/watch?v=AogwEfWZVds&t=3717s)** Morning briefing. We're going to add in this prompt here, which we'll read over. So, this prompt is saying run the {slash} briefing {slash} command against this repository, read priorities.md, scan wiki login scan wiki {slash} log.md and read the wiki pages relevant to my
>
> **[1:02:15](https://www.youtube.com/watch?v=AogwEfWZVds&t=3735s)** active projects. It's going to say generate this from today's schedule. And then also show me the things that we those questions that we looked at before. Saying do not create a branch or pull request. This is a personal vault does not require a code review flow. Now, we need to select a repository, but
>
> **[1:02:33](https://www.youtube.com/watch?v=AogwEfWZVds&t=3753s)** most likely what you are actually seeing in here is something that says set up. So, let's say I archive this. It'll probably say set up over here. I've already set this up, so I'm going to see something slightly different to you. When I click set up like that, it's going to refresh my page for me. I go back to routines, go back to remote. I'm
>
> **[1:02:53](https://www.youtube.com/watch?v=AogwEfWZVds&t=3773s)** going to have to put this in again. Uh morning briefing. And I'm pasting this in. Once you've set this up, if you're a bit confused and you're like, "What does this mean?" Go through this project guide. It'll show you how to set it up with your GitHub account. We need to only allow access to the second brain
>
> **[1:03:12](https://www.youtube.com/watch?v=AogwEfWZVds&t=3792s)** repo. I mean, that's just best security, but you can give it access to all repos if let's say you only have one. Um but best security is just giving it access to only that one repo unless you want to connect to others. Now, we're going to select our repo here. It's going to look something like this. And we're going to schedule in our task.
>
> **[1:03:30](https://www.youtube.com/watch?v=AogwEfWZVds&t=3810s)** So, I'm still using Sonnet right here. Uh if we go back to the guide, you will see the schedule button. We're going to set it for 2 minutes past what the time is right now. So, right now for me it is 5:40 It's 5:40 p.m. So, I'm going to set it
>
> **[1:03:49](https://www.youtube.com/watch?v=AogwEfWZVds&t=3829s)** to 5:42 p.m. Add the trigger. And I can give it access to certain tools. I actually only want this one to have access to my uh Gmail. I've synced in nothing else, so I don't need all these different connectors for this task. So, it can just have access to my Google calendar
>
> **[1:04:08](https://www.youtube.com/watch?v=AogwEfWZVds&t=3848s)** and go from there. So, we can click create. And what you will see is we'll wait a couple minutes for this to actually run. And we can click in here. It's going to be active. It's saying its next run is at 5:42 p.m. And it's going to run the exact {slash} briefing that we needed from before and we'll go ahead
>
> **[1:04:26](https://www.youtube.com/watch?v=AogwEfWZVds&t=3866s)** and see the results there. So, I'm going to wait a little bit and we will get into this shortly. In the meantime, we can actually just go ahead and we'll take a screenshot of this. And we will paste this into our guide right here and hit done. And in case you're wondering, where is this going to show up? Like if I'm not
>
> **[1:04:44](https://www.youtube.com/watch?v=AogwEfWZVds&t=3884s)** typing in {slash} briefing into Claude desktop, where is it going to show it? And where this is going to show is at the bottom of your log.md file. So, of course we can change the the structure, the formatting if you want. It just depends on the prompt that you give it. But for us, it's going to be simple and it's going to be in the log.md file.
>
> **[1:05:02](https://www.youtube.com/watch?v=AogwEfWZVds&t=3902s)** Again, you could do this in your daily journal if you wanted to. It's up to you. But when you open Obsidian and the Obsidian plugin, it's going to pull in the latest commit and you're going to see the new briefing at the bottom of your log ready with your coffee or in my case probably a nice chai. So, what time is it? It's 5:43, which means
>
> **[1:05:23](https://www.youtube.com/watch?v=AogwEfWZVds&t=3923s)** if we go back here, it should actually be running, which we can see right here. So, it's going to take some time. It's probably going to take I'd say at least 3 minutes to run this, kind of similar to the command or the terminal that we were looking at before. Not the terminal, the Claude code desktop view. So, it's going to take some time and we
>
> **[1:05:40](https://www.youtube.com/watch?v=AogwEfWZVds&t=3940s)** can return here and have a look at the results. In the meantime, I'll actually just show you what's at the bottom of the Obsidian log right here. And that is the last thing that we saw. So, just keep an eye on this, remember this, and we'll have a look at what actually pops up in a bit. So, now if we're in GitHub, you can see that there was a commit 2
>
> **[1:05:59](https://www.youtube.com/watch?v=AogwEfWZVds&t=3959s)** minutes ago, which is beautiful. And we can go into wiki. Then we will go into log and you can see at the bottom here this briefing actually ran. So, briefing ran, cycle two wraps tomorrow LGC beta. Exactly what we want. We want that briefing at the start of
>
> **[1:06:19](https://www.youtube.com/watch?v=AogwEfWZVds&t=3979s)** the day. Obviously, we're not going to look at it in GitHub, right? We're going to look at it in Obsidian. So, Obsidian is going to take about 10 minutes to sync this in, but obviously we've run it overnight. So, by the time we come here in the morning, we should see the latest changes here.
>
> **[1:06:37](https://www.youtube.com/watch?v=AogwEfWZVds&t=3997s)** Let's go. So, we got cycle two wraps tomorrow with LGC beta live and editor pipeline. So, these are the things that I need to do. And we're seeing it at the bottom of our log right here. So, we get that daily sort of task. Now, obviously I would kind of want this to look different. Probably want this to be in check boxes and want it to be
>
> **[1:06:56](https://www.youtube.com/watch?v=AogwEfWZVds&t=4016s)** a little bit more user-friendly so it looks nice. And we can change the the way that this lays out, the way this it looks, but it's all in that prompt. We can change this in the prompt itself and this is why I wanted you to get the idea that you can change anything in this project to be the way that you want because it
>
> **[1:07:13](https://www.youtube.com/watch?v=AogwEfWZVds&t=4033s)** is your second brain. That's what I want to get across the line. It is your second brain. And if we go back here, we can change the settings here so we can go into here. We can run this daily, so I'm going to run this at 8:00 a.m. my time. [snorts] Hit done.
>
> **[1:07:31](https://www.youtube.com/watch?v=AogwEfWZVds&t=4051s)** And I'm going to save it. If you're running a Claude max plan, you'll notice that you can run 15 daily runs. If you're running a pro, I think it's five. Um that is at the time of recording this video, but we can go from there. Now, I'm going to take a screenshot of this.
>
> **[1:07:50](https://www.youtube.com/watch?v=AogwEfWZVds&t=4070s)** I'm going to go back into [clears throat] the project and I will actually take I'm just going to take another one so it's easier. Screenshot. I'll paste this in and I'll say
>
> **[1:08:06](https://www.youtube.com/watch?v=AogwEfWZVds&t=4086s)** morning habit will be I'll check my Obsidian, go over my task for the day, make any adjustment as needed, and I will also go over my {slash} debrief at the end of the day so I can make sure that I'm not missing anything
>
> **[1:08:25](https://www.youtube.com/watch?v=AogwEfWZVds&t=4105s)** either. Now, we've gone ahead with switched it to the time that we actually want and we can clean up our resources. So, this is not the end of the project. If
>
> ### Before you go: Clean Up Your Resources
>
> **[1:08:37](https://www.youtube.com/watch?v=AogwEfWZVds&t=4117s)** you want to, you can go ahead, you can delete your GitHub repository if you are not interested in this or you want to just clean that up, but obviously this is not going to cost you anything. Go ahead and delete your different routines here. So, what you would do, go double click on this or
>
> **[1:08:55](https://www.youtube.com/watch?v=AogwEfWZVds&t=4135s)** right click, hit delete routine. That would delete your routine right there. And if you wanted to delete your GitHub repository, you would go ahead, go up to settings in your repo, go down to the bottom here and delete this repo. And I don't actually want to do this,
>
> **[1:09:13](https://www.youtube.com/watch?v=AogwEfWZVds&t=4153s)** but you would just press delete though. Now, the cool thing about next week projects is that at the end here, it will say The key tools I have used include Claude code desktop, Obsidian, and my own brain,
>
> **[1:09:30](https://www.youtube.com/watch?v=AogwEfWZVds&t=4170s)** which is great. Uh this project, I think it's taken me about an hour, an hour and 15 minutes. Nice. And I did this project to learn how to upgrade my second brain.
>
> **[1:09:48](https://www.youtube.com/watch?v=AogwEfWZVds&t=4188s)** Additionally, I want to work on the formatting of this to see how useful it can be. Uh but honestly, I'm a little bit skeptical, maybe. Maybe I'm just old-fashioned.
>
> ### Mission Accomplished!
>
> **[1:09:59](https://www.youtube.com/watch?v=AogwEfWZVds&t=4199s)** I can go ahead, scroll to the bottom, and now I can click this mission accomplished button, and I can share my documentation. At any point in the project, you can share your documentation, but here you can share it to LinkedIn, the community, so we have a community of learners all around the world where you can get help, feedback, ideas from, and share it to X,
>
> **[1:10:18](https://www.youtube.com/watch?v=AogwEfWZVds&t=4218s)** copy this live URL, you can download it as a readme, PNG, PDF, all these different formats. And it looks like this. It's so beautiful. And you can change the theme to dark, light mode, all of these different different ones, and you can share this to anyone in the world. So, as always, leave a like, subscribe, do
>
> **[1:10:37](https://www.youtube.com/watch?v=AogwEfWZVds&t=4237s)** all that cool stuff, and I will join you in the next one. Peace.