obsidian-para-gtd-ai

KO | EN

gitlite — search

#python #hacktoberfest #typescript #android #machine-learning #rust #nodejs #java #windows #cli #pytorch #mcp #openai #open-source

obsidian-para-gtd-ai

(★ 9)

A complete productivity system combining PARA (Projects, Areas, Resources, Archive) with GTD (Getting Things Done) task management, powered by Claude Code AI skills. Built for busy knowledge workers — founders, managers, PMs — who want a system that actually helps them think, not just store things.

obsidian-para-gtd-ai 최신버젼 다운로드

최종 버전 다운로드 (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Obsidian PARA & GTD powered by Claude Code

A complete productivity system based on **Obsidian** combining **PARA** (Projects, Areas, Resources, Archive) with **GTD** (Getting Things Done) task management, powered by **Claude Code** AI skills. Built for busy knowledge workers — founders, managers, PMs — who want a system that actually helps them think, not just store things.

---

## What this is

This vault is a pre-configured Obsidian workspace that comes with:

- A battle-tested **folder structure** based on PARA
- A **task management system** inspired by GTD, with emoji categories and daily/weekly rhythms
- A set of **Claude Code skills** — AI-powered slash commands for your daily workflow
- **Templates** for daily notes, weekly reviews, meetings, and 1:1s
- **Context files** where you document your company, product, and team — so Claude has real background knowledge, not generic advice

The system is designed to handle the full knowledge work loop: capture → organize → review → act.

---

## Prerequisites

1. **Obsidian** — free desktop app. Download at [obsidian.md](https://obsidian.md)
2. **Claude Code** — Anthropic's CLI. Install with: `npm install -g @anthropic-ai/claude-code`

## Quick Start

1. Open Obsidian → "Open folder as vault" → select this folder
2. Open a terminal in this folder
3. Run `claude` to start Claude Code
4. Type `/setup` — the setup wizard will personalize the vault for you in ~2 minutes
5. Done. Start your first day with `/morning-plan`

---

## Vault Structure

```
obsidian-para-claude-starter/
│
├── 00_INBOX/          Entry point — dump everything here, sort later
├── 01_ACTIVE/         Your operational layer
│   ├── Daily Notes/   One note per day — tasks, meetings, brain dump
│   ├── FOCUS.md       Active strategic themes (not a task list)
│   └── IDEAS.md       Long-horizon ideas and backlog
│
├── 02_PROJECTS/       Time-bound work with a clear goal and deadline
├── 03_AREAS/          Ongoing responsibilities (no deadline)
│   ├── Organization/  Recurring meetings, each in its own subfolder
│   ├── People/        Notes per relationship (team, peers, leadership)
│   └── Learning/      Reading, courses, ongoing learning
│
├── 04_RESOURCES/      Reference material
│   ├── Templates/     Note templates (Daily, Weekly, Meeting, 1:1)
│   ├── Context/       Company, product, and process context files
│   └── Weekly Reviews/ Weekly synthesis notes
│
├── 05_ATTACHEMENTS/   Images, PDFs, binary files
└── 06_ARCHIVE/        Completed projects and inactive items
```

### PARA in 30 seconds

| Folder    | Definition                              | Example                     |
| --------- | --------------------------------------- | --------------------------- |
| Projects  | Has a deadline and a specific end state | "Launch MVP by Q3"          |
| Areas     | Ongoing responsibility you maintain     | "Engineering relationships" |
| Resources | Reference you might need someday        | "Competitor analysis"       |
| Archive   | Inactive, but searchable                | Last year's projects        |

**When in doubt:** Projects = sprint, Areas = marathon, Resources = library.

→ **Learn more:** [The PARA Method by Tiago Forte](https://fortelabs.com/blog/para/)

---

## Task Management System

All tasks follow a pipe-separated format with emoji category prefix. This makes tasks machine-readable and visually scannable.

→ **Learn more:** [Getting Things Done by David Allen](https://gettingthingsdone.com/what-is-gtd/)

### Task Formats

| Category       | Format                                                          |
| -------------- | --------------------------------------------------------------- |
| Urgent / today | `- [ ] 🔴 \| Topic \| Description \| [[Link]] \| Date`          |
| This week      | `- [ ] 📅 \| Topic \| Description \| [[Link]] \| Date`          |
| Waiting For    | `- [ ] ⌛ Name \| Topic \| Description \| [[Link]] \| Due date`  |
| Delegated      | `- [ ] 👥 Name \| Topic \| Description \| [[Link]] \| Due date` |
| Agenda Item    | `- [ ] 📌 @Name \| Topic \| Source \| [[Link]]`                 |
| Someday        | `- Topic: short note` *(no checkbox)*                           |

### Task Sections in Daily Notes

- **🚨 Today** — urgent or due today
- **📅 This Week** — planned this week
- **⏳ Waiting For** — blocked on someone else
- **👥 Delegated** — delegations captured today
- **📌 Agenda Items** — topics to route to a specific meeting
- **✨ Someday** — no pressure; migrate to IDEAS.md if not done in 2 weeks

### Key Files

- **FOCUS.md** — 3–5 active strategic themes. Not a task list — a compass.
- **IDEAS.md** — long-horizon ideas. Review monthly, not daily.

---

## Skills (Slash Commands)

Claude Code skills are AI-powered commands that know your vault structure, templates, and context. They follow strict rules to avoid side effects — no unsolicited rewrites, no TodoWrite, no deleting files.

### Core Workflow Skills

| Command             | What it does                                                                         |
| ------------------- | ------------------------------------------------------------------------------------ |
| `/setup`            | One-time personalization wizard. Run this first.                                     |
| `/morning-plan`     | Builds your daily note from a brain dump. Organizes tasks, links to projects.        |
| `/daily-review`     | Closes out the day. Processes inbox, migrates tasks, writes daily summary.           |
| `/weekly-synthesis` | Reviews the last 7 days. Finds patterns, checks FOCUS alignment, prepares next week. |
| `/inbox-processor`  | Empties 00_INBOX — categorizes and moves everything to the right place.              |

### Thinking Skills

| Command               | What it does                                                                     |
| --------------------- | -------------------------------------------------------------------------------- |
| `/thinking-partner`   | Challenges your thinking. Asks hard questions before helping you produce output. |
| `/research-assistant` | Searches vault + web, synthesizes into a structured report.                      |

### Meeting Skills

| Command            | What it does                                                                       |
| ------------------ | ---------------------------------------------------------------------------------- |
| `/prep-meeting`    | Prepares you for any meeting. Loads context, compiles topics, creates a prep note. |
| `/process-meeting` | Turns a meeting (or transcript) into a structured vault note with tasks.           |

### Utility Skills

| Command           | What it does                                                   |
| ----------------- | -------------------------------------------------------------- |
| `/de-aiify`       | Rewrites AI-sounding text to sound human. Enforces US English. |
| `/create-command` | Builds a new custom skill through a guided interview.          |

---

## Daily Workflow

### Morning (~10 min)

```
/morning-plan
→ Tell Claude your tasks, appointments, and what's on your mind
→ It creates your daily note with organized tasks and links
```

### During the day

- Capture anything new in the `## 📥 Inbox / Brain Dump` section of your daily note
- Drop files into `00_INBOX/` for later processing
- Use `📌 Agenda Items` to route topics to the right person/meeting

### Evening (~15 min)

```
/daily-review
→ Processes your brain dump
→ Handles inbox items
→ Migrates unfinished tasks to tomorrow
→ Writes a daily summary
```

### Friday (~20 min)

```
/weekly-synthesis
→ Analyzes the week
→ Checks FOCUS alignment
→ Prepares next week's priorities
```

---

## Context Files

The `04_RESOURCES/Context/` folder contains three files Claude reads at the start of every session:

| File                 | What to put in it                                                |
| -------------------- | ---------------------------------------------------------------- |
| `company-context.md` | Your company, customers, market position, org structure          |
| `product-context.md` | Your product/service: what it does, key capabilities, value prop |
| `process-context.md` | Your team's rhythm: tools, ceremonies, decision-making process   |

**The more you fill these in, the smarter Claude's output becomes.** A well-filled context means Claude can give you advice specific to your situation, not generic PM/leadership boilerplate.

Run `/setup` first — it will guide you through the basics. Then fill in details over time.

---

## Meeting System

Meetings live in `03_AREAS/Organization/[Thematic-Subfolder]/`.

**Never save meeting notes directly in `03_AREAS/Meetings/`** — always create a thematic subfolder (e.g., `03_AREAS/Organization/Investor-Updates/`, `03_AREAS/Organization/Team-Weeklys/`).

### People Hub Files

For anyone you meet regularly, create a Hub file in `03_AREAS/People/`. Hub files track:

- Topics queued for the next meeting
- Delegated tasks and their status
- Open waiting-fors
- Goals and context

This is how `/prep-meeting` and `/process-meeting` work — they read hub files to know what's pending and write back to them after meetings.

---

## Project Structure

Every project in `02_PROJECTS/` follows a standard structure:

```
02_PROJECTS/My-Project/
├── CLAUDE.md        Project context for Claude
├── PLAN.md          Execution plan, phases, decisions
├── README.md        Human-readable overview
├── context/         Background docs, research inputs
├── resources/       Reference material
├── output/          Deliverables
├── archive/         Superseded versions
└── iterations/      Session logs (iteration-01.md, iteration-02.md, ...)
```

The `iterations/` folder enables multi-session continuity: Claude reads the latest iteration file at session start to restore context without you having to re-explain everything.

---

## Customizing

### Adding your team

After `/setup`, open `CLAUDE.md` and fill in:

- Your direct reports (they get Hub files and integration with meeting skills)
- Your key contacts (peers, leadership, external)

### Adding your meeting rhythm

Open `04_RESOURCES/MEETINGS.md` and document your recurring meetings: participants, purpose, agenda, where notes live.

### Creating new skills

Type `/create-command` — it interviews you about your workflow need and writes the skill file.

### Adapting templates

Edit any file in `04_RESOURCES/Templates/`. All skills read templates before creating notes — changes propagate automatically.

---

## File Handling Rules

These rules prevent data loss and keep the archive searchable:

- **Never delete vault files** — always move to `06_ARCHIVE/`
- **Archive folder structure:** `06_ARCHIVE/YYYY/MM_Month/` with subfolders for `Daily Log/`, `Notes/`, `Transcripts/`
- **Transcripts** are archived with a standardized name: `YYYY-MM-DD_Meeting-Title_Participants.ext`

---

## Obsidian Setup Tips

- Enable **Core Plugins**: Daily Notes, Templates, Backlinks, Outgoing Links
- Set **Daily Notes** folder to `01_ACTIVE/Daily Notes/`
- Set **Templates** folder to `04_RESOURCES/Templates/`
- Install community plugin **Dataview** for task queries across the vault
- Use **Graph View** to see how your notes connect (WikiLinks build this automatically)

---

## Why This System Works

Most productivity systems fail because they separate capture, organization, and action. This vault keeps them together:

1. **PARA** makes organization decisions obvious — you don't have to think where something goes
2. **GTD task format** makes urgency and ownership visible at a glance
3. **Daily/weekly rhythms** ensure nothing falls through the cracks
4. **Claude skills** reduce the friction of each step — the plan writes itself, the review runs itself, the meeting note structures itself

The goal isn't a perfect system — it's a *low-friction* system that you actually use.

---

## Attribution

This starter vault builds on the work of two people:

**Paul O'Malley** created the original Obsidian PARA vault template, shared in [I Built a Second Brain That Organises Itself (and you can too!)](https://www.youtube.com/watch?v=g8hmAjogElQ)

**Dennis Volkmer** ([GitHub](https://github.com/dennisvolkmer)) adapted and extended that template for use with Claude Code and AI-assisted workflows.

Building on both, **Timo Minkus** added a full **GTD task management system** (emoji-categorized task formats, daily/weekly rhythms, inbox processing) and a **meeting tracking system with hub files** (per-person context files, 1:1 notes, agenda routing, delegation tracking).

Shared as a starting point — adapt it to your context.

obsidian-para-gtd-ai

obsidian-para-gtd-ai 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

obsidian-para-gtd-ai

obsidian-para-gtd-ai 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Download README