PARA
PARA sorts information by how actionable it is right now, not by what kind of thing it is or where it came from. Four buckets, most to least actionable:
| Bucket |
Is |
Test |
| Projects |
an outcome with a goal and a deadline or timeframe, being worked on now |
can it be finished, and is something happening on it this week or month? |
| Areas |
an ongoing responsibility with a standard to maintain, no end date |
would something suffer if it were neglected? |
| Resources |
a topic of interest or reference, no responsibility attached |
useful to look up or share, but nothing breaks if ignored |
| Archives |
anything inactive from the other three |
done, dropped, handed off, or no longer interesting |
An inbox sits in front of the four. It holds capture, in time order, until a review files it. Calendars, email, chat and ticket trackers are chronological by nature and are never reorganized by PARA; PARA pages link to them.
Read references/classification.md before classifying anything non-obvious. Read references/stores.md before setting PARA up on a specific store.
Hard rules
- Plan first, act second. Never create, move, rename or archive anything until a complete written plan is shown and the owner says yes. Say this before the first scan.
- Never delete; archive. Archives keep everything findable and can be reactivated. Superseded facts are kept as history, not removed.
- Link, never duplicate. One home per item. Relate items with links or tags, never copies.
- Most actionable wins a tie. Project over Area, Area over Resource. Inside one Area, file to the most specific active Project.
- Just in time. Create a folder or page only when there is something to put in it. No empty scaffolding.
- Top level only. PARA governs the four buckets and one level of named items inside them. Keep everything below informal.
- Project names are labels. A short label, with the goal and the deadline kept beside it (inventory, frontmatter), never in the name.
Classify an item
- Goal and deadline, with work happening now? Then it is a Project, even when it lives inside an Area.
- Otherwise, an ongoing standard someone is accountable for? Then it is an Area.
- Otherwise, useful reference or interest? Then it is a Resource.
- Otherwise, inactive? Then it goes to Archives. If it is none of these, leave it in the inbox, or ask whether to delete it.
Watch for the two classic errors:
- an Area disguised as a Project ("improve sales" has no end);
- an actionable unit buried in an Area ("2026 tax filing" belongs in Projects, not under Finances).
A future project is not a project. Keep it as an idea on its Area until work starts.
When unsure, ask in small batches of 3-5 items, giving a recommended answer and one line of reason for each. Never guess silently on an item you cannot read; describe it and offer 2-3 placements.
Reorganize a store
- Discover (read-only).
- Read any existing context (a personal context doc, a project list) before asking anything.
- Ask for:
- current projects, each with a goal and a deadline;
- areas of responsibility;
- time-bound initiatives inside each area (these become Projects);
- topics of interest.
- Scan the top level, opening unclear items to judge them by content rather than by name.
- Choose the path when PARA, or something like it, already exists:
- audit and update;
- sort only the loose items;
- fresh start (everything into a dated archive first, then pull forward only what is active).
- Resolve every ambiguous item before writing the plan, so the plan has no open questions.
- Present the plan. It lists:
- every folder or page to create;
- every move with its source and destination;
- every archive;
- what is deliberately not created yet.
- Execute only after an explicit yes. A change to the plan is re-shown and needs a new yes.
- Report:
- counts per bucket;
- the judgment calls made, so they can be double-checked;
- anything that could not be placed or moved, and what is needed to resolve it.
- Write the inventory:
- Projects, each with its goal and due date;
- Areas, each with the standard it maintains;
- Resources, each with one line;
- Archives.
Reviews
| Cadence |
Do |
| Weekly |
Retitle: names that no longer match their content. Sort: finished projects to Archives, resources that became responsibilities to Areas. Update: new projects that need a home, stalled projects to cancel or archive, archived items to reactivate. Clear the inbox. |
| Monthly |
Areas and Resources that are no longer held or wanted go to Archives. Look for themes mentioned 3 or more times that deserve their own Area or Resource. |
| Yearly |
Re-architect: which Areas still describe the owner's life and work? |
A healthy project list holds 10-20 active Projects. More than 25 usually means Areas in disguise or projects that should be cancelled. Two signals to check:
- a goal with no project is a dream, not yet activated;
- a project with no goal is a hobby.
Agent knowledge bases
The same canon applies when agents keep memory. The extra rules exist because agents act on stale text with confidence:
- capture is append-only and dated;
- consolidation happens in scheduled passes, never on every write;
- live state (ticket status, thread state) is linked, never copied;
- indexes are generated;
- every page carries its lifecycle (
status, stale_after).
See references/stores.md, Agent knowledge base. When a repository defines its own contract for such a store, that contract wins on paths and fields. This skill supplies the classification and review rules.
Sources
1---2name: para3description: "Apply Tiago Forte's PARA method (Projects, Areas, Resources, Archives) as canonically defined to any store: a file system, cloud drive, notes app or Obsidian vault, or a markdown knowledge base that agents read and write. Use to classify items by actionability, decide project vs area vs resource vs archive, set up or audit a PARA structure, plan a reorganization or migration, run a weekly or monthly PARA review, or design agent memory on PARA without rot. Triggers: 'PARA', 'is this a project or an area', 'organize by actionability', 'set up PARA', 'PARA audit', 'archive finished projects', 'weekly review'. Not for capturing one note into the personal vault (vd:obsidian-vault) or the engineering journal (vd:journal)."4license: MIT5metadata:6 source: https://skillmd.com/skills/vanducng/para7 author: vanducng8 version: "0.1.0"9---1011# PARA1213PARA sorts information by how actionable it is right now, not by what kind of thing it is or where it came from. Four buckets, most to least actionable:1415| Bucket | Is | Test |16|---|---|---|17| Projects | an outcome with a goal and a deadline or timeframe, being worked on now | can it be finished, and is something happening on it this week or month? |18| Areas | an ongoing responsibility with a standard to maintain, no end date | would something suffer if it were neglected? |19| Resources | a topic of interest or reference, no responsibility attached | useful to look up or share, but nothing breaks if ignored |20| Archives | anything inactive from the other three | done, dropped, handed off, or no longer interesting |2122An inbox sits in front of the four. It holds capture, in time order, until a review files it. Calendars, email, chat and ticket trackers are chronological by nature and are never reorganized by PARA; PARA pages link to them.2324Read `references/classification.md` before classifying anything non-obvious. Read `references/stores.md` before setting PARA up on a specific store.2526## Hard rules27281. **Plan first, act second.** Never create, move, rename or archive anything until a complete written plan is shown and the owner says yes. Say this before the first scan.292. **Never delete; archive.** Archives keep everything findable and can be reactivated. Superseded facts are kept as history, not removed.303. **Link, never duplicate.** One home per item. Relate items with links or tags, never copies.314. **Most actionable wins a tie.** Project over Area, Area over Resource. Inside one Area, file to the most specific active Project.325. **Just in time.** Create a folder or page only when there is something to put in it. No empty scaffolding.336. **Top level only.** PARA governs the four buckets and one level of named items inside them. Keep everything below informal.347. **Project names are labels.** A short label, with the goal and the deadline kept beside it (inventory, frontmatter), never in the name.3536## Classify an item37381. Goal and deadline, with work happening now? Then it is a **Project**, even when it lives inside an Area.392. Otherwise, an ongoing standard someone is accountable for? Then it is an **Area**.403. Otherwise, useful reference or interest? Then it is a **Resource**.414. Otherwise, inactive? Then it goes to **Archives**. If it is none of these, leave it in the inbox, or ask whether to delete it.4243Watch for the two classic errors:44- an Area disguised as a Project ("improve sales" has no end);45- an actionable unit buried in an Area ("2026 tax filing" belongs in Projects, not under Finances).4647A future project is not a project. Keep it as an idea on its Area until work starts.4849When unsure, ask in small batches of 3-5 items, giving a recommended answer and one line of reason for each. Never guess silently on an item you cannot read; describe it and offer 2-3 placements.5051## Reorganize a store52531. **Discover (read-only).**54 - Read any existing context (a personal context doc, a project list) before asking anything.55 - Ask for:56 - current projects, each with a goal and a deadline;57 - areas of responsibility;58 - time-bound initiatives inside each area (these become Projects);59 - topics of interest.60 - Scan the top level, opening unclear items to judge them by content rather than by name.612. **Choose the path when PARA, or something like it, already exists:**62 - audit and update;63 - sort only the loose items;64 - fresh start (everything into a dated archive first, then pull forward only what is active).653. **Resolve every ambiguous item** before writing the plan, so the plan has no open questions.664. **Present the plan.** It lists:67 - every folder or page to create;68 - every move with its source and destination;69 - every archive;70 - what is deliberately not created yet.715. **Execute** only after an explicit yes. A change to the plan is re-shown and needs a new yes.726. **Report:**73 - counts per bucket;74 - the judgment calls made, so they can be double-checked;75 - anything that could not be placed or moved, and what is needed to resolve it.767. **Write the inventory:**77 - Projects, each with its goal and due date;78 - Areas, each with the standard it maintains;79 - Resources, each with one line;80 - Archives.8182## Reviews8384| Cadence | Do |85|---|---|86| Weekly | **Retitle**: names that no longer match their content. **Sort**: finished projects to Archives, resources that became responsibilities to Areas. **Update**: new projects that need a home, stalled projects to cancel or archive, archived items to reactivate. Clear the inbox. |87| Monthly | Areas and Resources that are no longer held or wanted go to Archives. Look for themes mentioned 3 or more times that deserve their own Area or Resource. |88| Yearly | Re-architect: which Areas still describe the owner's life and work? |8990A healthy project list holds 10-20 active Projects. More than 25 usually means Areas in disguise or projects that should be cancelled. Two signals to check:91- a goal with no project is a dream, not yet activated;92- a project with no goal is a hobby.9394## Agent knowledge bases9596The same canon applies when agents keep memory. The extra rules exist because agents act on stale text with confidence:97- capture is append-only and dated;98- consolidation happens in scheduled passes, never on every write;99- live state (ticket status, thread state) is linked, never copied;100- indexes are generated;101- every page carries its lifecycle (`status`, `stale_after`).102103See `references/stores.md`, Agent knowledge base. When a repository defines its own contract for such a store, that contract wins on paths and fields. This skill supplies the classification and review rules.104105## Sources106107- Tiago Forte, *The PARA Method* (2023), and [The PARA Method](https://fortelabs.com/blog/para/).108- Forte, [The Weekly Review is an Operating System](https://fortelabs.com/blog/the-weekly-review-is-an-operating-system/).109- Andrej Karpathy, [LLM Wiki](https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f), for an agent-kept wiki with ingest, query and lint.