How to automate the PARA method.

PARA is one of the most durable ideas in personal organization. Created by Tiago Forte as the backbone of Building a Second Brain, it throws out the instinct to file things by topic and replaces it with a single question: how actionable is this? That one shift collapses the endless folder trees most people build into exactly four buckets.

It works across every tool you use — notes, cloud drives, and the plain old folders on your computer. The catch is the same everywhere: PARA is easy to understand and tedious to maintain. This guide is about removing the tedium for the files on your disk.

The four buckets, briefly

• Projects — active efforts with a goal and an end. “Launch the site,” “plan the trip,” “Q3 report.” When a project finishes, it leaves.
• Areas — ongoing responsibilities you maintain with no end date. Finances, Health, Home, a job role. You never “finish” an area; you keep it in good standing.
• Resources — topics and reference material you may want later. Templates, manuals, books, design assets, things you’re simply interested in.
• Archives — inactive items from the other three. Nothing is deleted; it’s cold storage you can always recover from.

The genius of PARA is the demotion path: when something stops being actionable, it moves toward Archives. That single habit keeps the system from rotting.

Why the upkeep defeats people

The buckets are easy. What’s hard is the constant, low-grade maintenance: noticing that a project finished three months ago, that a folder hasn’t been opened since last year, that a download belongs in Resources, not on your Desktop. None of those decisions is difficult — there are just hundreds of them, forever, and they never feel urgent. So they don’t happen, and the landfill returns.

This is exactly the kind of work a computer should do. Most of it comes down to signals a tool can read: when was this last modified? What kind of file is it? What folder did you already put it in? Is it part of a code or media project that should move as a unit?

Automating PARA with FileMayor

FileMayor is a free, local-first file organizer that builds PARA into the engine. It never sends your file contents anywhere, and every move it makes is journaled so a single command reverses the whole session.

1. Scaffold the structure

One command creates the four folders — each with a short README explaining what belongs in it, so the system teaches itself to anyone who opens it — plus a tuned config file.

$ filemayor init --para

  ✓ Created .filemayor.yml
  ✓ Scaffolded PARA folders: Projects, Areas, Resources, Archives
    8 item(s) created (folders + READMEs)

  Next:  filemayor para .   then  filemayor apply

2. Sort by actionability — and see why

filemayor para classifies every file from the signals it can actually read and shows you the plan before touching anything. Crucially, it labels each move with its reason — no black box.

$ filemayor para .

  Into PARA buckets:
    Projects 14   Areas 6   Resources 23   Archives 41

  tax-return-2024.pdf   →  Areas/finances/      (matched "finances")
  client-acme/          →  Projects/client-acme  (active project — moved intact)
  old-receipts.zip      →  Archives/             (not modified in 19 months)
  swipe-file.pdf        →  Resources/reference/  (matched "reference")

  Review the plan, then run 'filemayor apply' to execute (reversible).

The logic is intent-first: if you already filed something under finances/ or templates/, FileMayor honors that meaning instead of fragmenting your folder by date. The headline automation — “not touched in N months → Archives” — is reserved for the loose, unfiled clutter where it actually helps. Where a file has no clear signal, it says so and sets it aside for you to review, rather than guessing confidently.

3. Apply, with an undo

$ filemayor apply
  ✓ Applied! 84 files moved, journaled.

$ filemayor undo        # changed your mind? reverse the whole session

Active code and project folders (anything with a .git, package.json, or similar marker) move intact into Projects — never shredded file by file. And because every move is written to a journal first, filemayor undo always has your back.

Deterministic vs. semantic PARA

There’s an honest limit to what any tool can infer. Whether a document is an active Project or an ongoing Area responsibility is sometimes a genuine judgement call. FileMayor handles this with two modes:

• Deterministic (the para command) — fast, free, private, and transparent. Great for the bulk pass and the auto-archiving.
• Semantic — when you use FileMayor through Claude via the MCP server, the AI reasons about true actionability per file and proposes the buckets, then hands the moves to the same reversible engine. You confirm; it applies.

The point isn’t a tidy folder. It’s a system that stays tidy.

A one-time cleanup feels great for a week. PARA’s real value is the demotion habit that keeps things from piling up again — and that habit is precisely what’s easiest to automate. Let the tool move stale things to Archives and route the obvious files, and you’re left making only the handful of decisions that genuinely need a human.

FileMayor is free on Mac, Windows, and Linux. To try it: npm install -g filemayor, then filemayor init --para in any folder you want to bring under control. For the full PARA walkthrough, see the PARA method page.

PARA is a method created by Tiago Forte (Building a Second Brain). FileMayor is an independent tool that automates it and is not affiliated with or endorsed by him.