Design a PARA Folder and Tag Structure for Your Personal Knowledge System

Get a ready-to-build PARA folder tree, one file naming convention, a short tag list with rules, and a 10-minute weekly upkeep routine for your tools.

You getFolder tree, naming convention with examples and tag table

Prompt

Prompt
Act as a personal knowledge management coach who sets up PARA systems (Projects, Areas, Resources, Archive) for busy people.

Before building anything, ask me these questions in one message and wait for my answers:
1. Which note and file tools do I use (e.g. Notion, Obsidian, Google Drive, Apple Notes)?
2. What active projects do I have, each with a goal or deadline?
3. What ongoing areas of responsibility do I manage (work roles, health, home, money)?
4. What topics do I save reference material on?

Then design my system with these rules:
- Every project folder name includes an outcome and an end month; anything without an end date goes in Areas.
- Number the top-level folders so they sort in order, and go no deeper than 3 levels.
- Give one naming convention for files and notes, with 3 examples drawn from my answers.
- Use at most 10 tags, each with a one-line rule for when to apply it; no tag repeats a folder name.
- The weekly routine fits in 10 minutes, with minutes assigned to each step.

Output format:
1. Folder tree (in a code block)
2. Naming convention with examples
3. Tag table: Tag | Use when | Example
4. 10-minute weekly routine (numbered steps with minutes)
5. First 3 moves to migrate my existing notes

End with one line naming any assumption you made about my tools or the biggest risk of the system drifting.

Example output

Example for: a product marketer using Obsidian for notes and Google Drive for files, with 3 active projects and a home renovation.

1. Folder tree

1-Projects/
  2025-06 Launch Pricing Page v2/
  2025-04 Q2 Customer Interview Report/
  2025-09 Kitchen Renovation Done/
2-Areas/
  Product Marketing Role/
  Health/
  Home and Finances/
3-Resources/
  Positioning and Messaging/
  Copywriting Swipe File/
  Cooking/
4-Archive/
  2025/

Mirror the same four top-level folders in Google Drive so a project lives in the same place in both tools.

2. Naming convention

Format: YYYY-MM-DD Type - Short topic

  • 2025-03-14 Meeting - Pricing page kickoff with design
  • 2025-03-20 Draft - Interview report outline
  • 2025-03-22 Quote - Cabinet installer Ridgeway

Types allowed: Meeting, Draft, Notes, Quote, Reference, Decision.

3. Tags

TagUse whenExample
#todoThe note has an open actionFollow up on pricing copy review
#waitingYou are blocked on someone elseContractor quote pending
#decisionA choice was made and should be findableChose 3-tier pricing
#ideaUnproven thought worth revisitingComparison table for enterprise
#quote-worthyA customer line you may reuseInterview 4 on onboarding pain
#evergreenInsight still true in a yearRules for pricing page headlines
#reviewNeeds a second read before filingMessy call notes

4. 10-minute weekly routine (Friday, 4:30 pm)

  1. 2 min – Empty the Obsidian inbox and Drive Downloads into the right PARA folder.
  2. 2 min – Search #todo and #waiting; close or move anything finished.
  3. 2 min – Check each project end month; move completed projects to 4-Archive/2025.
  4. 2 min – Clear #review notes: rename them to the convention or delete.
  5. 2 min – Write one line in each active project: next action for Monday.

5. First 3 migration moves

  1. Create the four top-level folders in both tools; don't touch old files yet.
  2. Move only notes for your 3 active projects into 1-Projects.
  3. Drop everything else into 4-Archive/Unsorted and pull items out only when you need them.

Assumption: you use Obsidian tags rather than nested tag folders; the biggest drift risk is projects that never get an archive date.

Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • Asking about tools and projects first means the folder tree uses your real project names instead of generic examples.
  • Forcing an end month in every project name enforces the core PARA rule that separates Projects from Areas.
  • Capping tags at 10 with a usage rule each prevents the tag sprawl that makes most systems collapse.

Use when your notes and files are scattered across apps. Paste into ChatGPT, Claude or Gemini and have a quick list of your tools, current projects and recurring responsibilities ready.

Common edits

  • Ask for a version that works only in Notion, using databases and properties instead of folders.
  • Change the weekly routine to a 30-minute monthly review if you prefer fewer, longer sessions.

Prompt details

By
Prompts-GPT editors
Published

Did this prompt work?

Keep exploring

More in Productivity