Vault Organization

Audit and reorganize the user's Obsidian vault. Run when asked to organize, clean up, or audit the vault structure — or to set up a sensible structure for a new/empty vault.

Vault path

Confirm the actual vault location first — do not assume ~/Documents/Obsidian Vault. Ask or check Obsidian's settings if the path is not known.

Structuring a vault (new or from scratch)

When the user asks "how should I organize my vault?" or is starting fresh, recommend a structure before touching anything. Use PARA as the default taxonomy — it maps cleanly onto how an assistant actually uses a vault:

• Projects/ — short-lived efforts with a goal and an end (a trip, a launch, a repair). One folder per project; archive when done.
• Areas/ — ongoing responsibilities with no end date (Health, Finance, Home, a business, a role). These persist and get maintained.
• Resources/ — reusable reference material not tied to one project: research, guides, templates, snippets, "how I do X."
• Archive/ — completed projects and superseded material, kept out of the active tree but searchable.

Conventions that make the vault work for both a human and an agent: