How I Turned Tiago Forte's PARA Method Into an AI-Powered Productivity OS With Claude Code + Obsidian

5 commands, 6 folders, and the AI Copilot that runs my week.

I used to start every Monday morning the same way.

Open Notion to check my quarterly roadmap. Switch to Todoist to review my weekly tasks. Open a Google Sheet to see how my revenue numbers tracked against my annual goals. Pull up my content calendar to check what’s publishing this week. Then try to hold all of that in my head while deciding what actually deserves my best hours today.

By the time I finished checking everything, 45 minutes were gone. And here’s the part that frustrated me the most — I still didn’t have clarity. I had information. Tabs full of it. But clarity about what actually matters this week? That required me to mentally cross-reference everything I just looked at and make a judgment call while my coffee was getting cold.

I was spending more time following my plan than executing my plan. And over time, something subtle happened — I started confusing checking my system with making progress:

• Dragging a task card across a Notion board felt productive.

• Color-coding priority labels felt productive.

• Watching a satisfying animation when I checked something off felt productive.

These tools are designed to make organizing feel like doing. The appealing UX — the buttons, the colors, the smooth transitions — rewards you for managing work, not finishing it.

But at the end of the week, when I looked at what actually moved forward... the answer was uncomfortable.

Organized, but not effective. Informed, but not clear.

So I started questioning the whole setup. Not which app to switch to — whether the multi-app approach itself was the problem. Whether the clicking, the tab-switching, the manual cross-referencing was a tax I’d been paying so long I stopped noticing it.

When I started moving everything into Obsidian and connecting it to Claude Code, I wrote about this frustration in my notes. The response made it clear this wasn’t just my problem:

The engagement was wild 🔥 — people wanted to know exactly how it works. What the setup looks like. What Claude actually does inside the vault.

About a month ago, this tweet also proved my frustration — saying his choice to stick with Obsidian “has gotten vindicated” in the Claude Code era.

Arnav Gupta@championswimmer

In the new Claude-Code powered world, my choice to have stuck with Obsidian as a notetaking app (painfully migrated from Evernote many years back) has gotten vindicated. I see friends who are trying to install MCPs of Notion and continue to pay subscription to Notion, or MCPs of

6:50 PM · Jan 21, 2026 · 119K Views

---

66 Replies · 29 Reposts · 793 Likes

He was watching friends scramble to install MCPs for Notion, pay for Notion AI subscriptions, and build middleware just to get AI access to their notes. Meanwhile, Obsidian users just... pointed Claude at their folder.

A recent YouTube video by Greg Isenberg and InternetVin has gotten popular for this, in case you want to see how they use it.

The people who’ve made this switch keep saying the same thing: it’s the best decision they’ve made for their AI workflow. And the people who haven’t are asking how to start.

Look no further, this post is the answer.

I knew in my heart that a better task management app wasn’t going to cut it. That’s what I had been doing all this time. I realized that I needed to remove myself from the progress-tracking loop entirely.

I moved everything into one Obsidian vault — goals, roadmaps, sprints, weekly plans, daily logs — all as plain markdown files. Then I connected Claude Code to it. Not as a chatbot I talk to about productivity. As a copilot that lives inside my files and already understands the full picture.

Now when I start my week, I don’t click through four apps. I ask one question:

“What should I focus on this week?”

And Claude already knows. It reads my quarterly goals, checks my sprint progress, looks at what I actually did last week versus what I planned, and surfaces the priorities that connect to real outcomes — in seconds.

That’s not a second brain. A second brain stores what you know. This is closer to a copilot that tells you what you’re avoiding.

The rest of this post is exactly how I built it — the folder structure, the memory system, the five commands that run my week, and how you can set up your own version.

Before we dive in, let me explain why I turned to Obsidian and left Notion.

Why Obsidian (And Not Notion)

Notion stores your data in a proprietary cloud database. Nothing exists as files on your computer. If you want an AI tool to read your Notion workspace, you need API keys, database queries, and middleware to translate between Notion’s format and something the AI can parse. Every time you want Claude to check your quarterly goals against your weekly plan, that request travels through an API, hits Notion’s servers, and comes back translated.

Obsidian is the opposite. Everything is a plain markdown file in a folder on your computer. Claude Code reads and writes files directly — no API, no middleware. I point it at my vault folder and it sees everything I see.

More importantly, it’s not just about access, it’s also about format. Markdown is the native language of LLMs. It’s the format they were trained on. When Claude reads a markdown file, there’s no translation layer. Headings, bullet points, wiki-links, plain text — it understands the structure the way you wrote it. When it reads from Notion’s API, it’s parsing JSON objects and database schemas. That’s overhead between the AI and your thinking.

That’s why the AI community has been gravitating toward Obsidian: your notes are already in the language AI speaks.

But the difference that actually matters for this system is the knowledge graph.

Obsidian has a Graph View that visualizes every connection between your files as a live network. When you link one note to another with [[double brackets]], that link goes both ways automatically. The sprint file knows which weekly plans reference it. The quarterly goals file knows which roadmaps point to it.

Notion doesn’t have this. No graph, no automatic backlinks. Notion is hierarchical — pages inside pages inside databases. Obsidian is a network — everything connected to everything through explicit links.

When Claude reads my vault, instead of navigating a hierarchy, it’s traversing a network. It can start at my weekly plan, follow a link to a sprint, follow another to the quarterly goal, and trace all the way to my annual targets — in one read. The graph structure lets Claude see relationships that would take me five clicks to piece together in Notion. And the speed is second to none.

What’s Inside This Post

This guide is the complete blueprint for building the Obsidian system I just described. Not the theory — the exact folder structure, the memory files, the commands, and the step-by-step setup process.

Here’s what you’ll walk away with:

1. The Folder Structure — My modified PARA system with six folders that connect daily tasks to annual goals through explicit wiki-links. I’ll show you every folder, what goes inside, and how the “strategic cascade” works — the chain from your 3-year vision all the way down to today’s task list.

2. The Memory Layer — Three files that give Claude persistent awareness across sessions: CLAUDE.md (the operating manual that teaches Claude your system), VAULT-INDEX.md (the live dashboard Claude reads first every session), and the SessionStart hook that loads your full vault structure automatically.

3. The Five Commands That Run My Week — The exact slash commands I use: /plan-week, /daily-prep, /process-inbox, /end-day, and `/review-week. Each one with the full step-by-step logic Claude follows — what it reads, what it checks, and what it outputs.

4. 7 Moments Where the Copilot Was Smarter Than Me — Real examples from the last two weeks where Claude caught patterns I missed, flagged blockers I forgot about, and pushed back on my priorities when I was avoiding the hard work.

5. The Complete Starter Kit + Setup Guide — A downloadable starter kit with the entire system pre-built: folder structure, slash commands, templates, memory layer, hooks — plus a three-phase guide to customize it for your projects, your goals, and your schedule. One Sunday afternoon to set up. After that, the system runs itself.

By the end of this post, you’ll have the exact system I use to run my week — from Sunday planning to Friday review — without opening a single project management app.

---

🚨Before we go further: This system runs on Claude Code — Anthropic’s AI tool that works directly with files on your computer. If you’re not familiar with it yet, I’d recommend reading my beginner’s guide to Claude Code first for the basics, or my ultimate guide to Claude Code if you want the full picture of what it can do. You don’t need to be a developer to use it — but you do need to be comfortable with a terminal.

The daily workflow looks like this: Obsidian open on one side of your screen for viewing and editing your notes, Claude Code running in the terminal on the other side. You type commands, Claude reads and writes your files, and you see the results update in Obsidian in real time.

If working in a terminal isn’t your thing, there’s an alternative — you can use the Claude Code extension inside VS Code or Cursor instead. Same functionality, but inside an IDE with a more familiar interface. Either way works.

---

Let’s dive in 🔥

The Folder Structure

I use a modified version of Tiago Forte’s PARA method. If you’re not familiar, PARA stands for Projects, Areas, Resources, Archives — a way to organize information by actionability rather than topic. I adapted it to match how I actually work.

Here’s my full structure: