Noah Steiner·
Set up PARA in Obsidian using my real projects, with the exact rules for when stuff migrates
Implements the PARA method (Projects, Areas, Resources, Archives) with specific folder structures and migration rules.
PARA Method Note-Taking System
You are a PARA method specialist trained by Tiago Forte's methodology. Set up a complete PARA system for me in {{note_taking_app}}. My active projects (with deadlines) are: {{active_projects}}. My ongoing areas of responsibility (no deadline) are: {{areas_of_responsibility}}. Resource topics I frequently reference: {{resource_topics}}. My current messy note structure: {{current_note_structure}}. Create: (1) Exact folder/page structure for all 4 PARA categories with names, (2) Decision tree: where a new note goes (5 questions max), (3) Migration rules: when a project becomes an area, when something archives, (4) Naming convention template with examples, (5) Weekly maintenance routine (5 min), (6) Monthly review checklist, (7) Connection strategy: how PARA links to my task manager and calendar. Provide concrete examples using my actual projects and areas.
Ergebnisse
Full PARA setup in Obsidian using your real projects. Tiago Forte's rule: organize by actionability, not topic.
## 1. Folder structure
```
01 Projects/
Website-Relaunch (due Jun 20)/
Q3-Hiring (due Jul 15)/
Conference-Talk (due Jun 28)/
02 Areas/
Team-Management/
Personal-Finance/
Health/
03 Resources/
Marketing/ Design-Inspiration/ Pricing-Models/
04 Archive/
(completed projects + dormant areas)
```
## 2. "Where does this note go?" decision tree
1. Tied to a deadline + outcome? → **Project**.
2. Ongoing standard to maintain, no end date? → **Area**.
3. Topic I reference but isn't actionable now? → **Resource**.
4. Done or no longer alive? → **Archive**.
5. Genuinely unsure? → leave in Inbox, decide at weekly review.
## 3. Migration rules
- A **Project** that loses its deadline but stays relevant → moves to **Areas** (e.g. "Website-Relaunch" → "Web Presence" area after launch).
- Any **Project** completed → **Archive** immediately (keeps active list short).
- An **Area** you stop maintaining → **Archive**.
## 4. Naming convention
`YYYY-MM-DD Topic - context` for notes; `Project-Name (due date)` for folders.
*Example:* `2026-06-01 Relaunch - homepage copy decisions`.
## 5. Weekly maintenance (5 min)
Empty Inbox → file by the tree → archive anything completed this week.
## 6. Monthly review
- [ ] Every Project still active + has a next action?
- [ ] Any Project ready to archive?
- [ ] Areas still reflect real responsibilities?
## 7. Connection strategy
Each Project note links `[[ ]]` to its Todoist project and the relevant calendar week. PARA holds the *why/what*; the task manager holds the *do*.
Modell: Claude Sonnet 4
7 Likes1 SavesScore: 5
1 Kommentar
Felix Bauer·
The delegation breakdown showed me what I should've handed off ages ago.