← Back to library

Keep one numbered folder per repeatable Claude task

jen729w on Hacker News keeps agent work organized with plain folders and Johnny.Decimal numbering, jumps to a folder with a small helper, starts Claude there, and resumes old sessions in place. His routine for moving a trip booking from email into calendar and notes lives in one numbered folder.

  • OutcomeMake recurring agent jobs easy to rerun by giving each its own numbered folder holding scripts, notes and past conversations, then launching the agent from there.
  • SetupMinutes
  • LevelStarter
  • Creditjen729w on Hacker News
View original
Works with
Claude Code

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 24, 2026

When should you use it?

  • You repeat the same agent tasks weekly
  • Scripts and notes for tasks get lost
  • You use a terminal agent

Not for: Tasks that need a scheduler rather than a prompt; Teams needing shared, permissioned workspaces

What do you need, and what do you get?

You need

  • A folder scheme
  • Scripts or notes per task

You get

  • A folder per task with its own docs
  • Resumable conversations per job

How does it work, step by step?

  1. Pick a numbering schemeGive every area and task a stable number and short name.
  2. One folder per jobCreate a folder for each recurring task, such as travel-to-calendar.
  3. Save what worksKeep scripts, instructions and notes in that folder.
  4. Start the agent thereChange into the folder and launch the agent so it reads the local context.
  5. Resume, do not restartPick up the previous conversation for that task instead of explaining again.

The prompt

Our own prompt, inspired by jen729w on Hacker News and written to work in Claude Code. Values in lime are placeholders.

Fill in the blanks (optional; the copied prompt uses your values)

Prompt2 variables
You are in the folder for the task: {task_name}.
Read README.md and any scripts here first. Then do this run: {request}. Update README.md with anything you learned that would help next time, and list what you changed.

Inspired by jen729w on Hacker News: Hacker News comment on organizing Claude work by folder. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • Loose folders without names drift; keep the scheme strict.
  • Credentials do not belong in the folder notes.

Our take

This is the least glamorous tip in the thread and possibly the most useful. A terminal agent reads its working directory, so a well-named folder becomes a saved workflow: instructions, helper scripts and the history of past runs. jen729w's trick costs nothing and works with any terminal agent. Give each area and task a stable number and short name, create one folder per recurring job, and keep its scripts, instructions and notes there. Starting the agent inside the folder means it reads that context automatically, and resuming the previous session for that task saves explaining everything again. His trip-booking routine lives in one such folder, which is a good model: email in, calendar and notes out. Keep the naming scheme strict, because loose folders drift quickly. Credentials never belong in folder notes; use your system's keychain or the tool's own secret storage. Tasks that need to run on a timer still need a scheduler, and teams wanting shared permissions need something more.

Where the time goes back: Each repeat run starts with the instructions and scripts already in place, so a task takes one sentence.

FAQ

Why folders and not a tool?
The folder already holds context the agent can read; nothing else is needed.
What is Johnny.Decimal?
A numbering system for organizing files into areas and categories.

Source and credit

Inspired by jen729w on Hacker News. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
Hacker News comment on organizing Claude work by folder
Creator
jen729w on Hacker News
Published on
Hacker News
Original date
Oct 4, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
Claude Code
AI dry run
Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminWorkflow✓ AI dry run

Add a merge check for every way coding agents break code

Keep a running list of the specific ways coding agents have damaged your repository, from hollow tests and invented fake responses to deleted files and silenced type errors, and turn each one into an automated gate that blocks the merge, so the same mistake cannot slip through review twice.

Credit: u/alexmarquardt on r/ClaudeCode

An afternoon+
Operations & AdminWorkflow✓ AI dry run

Ask Reddit's experience before you pick a library

Let your coding agent search Reddit for long-term user reports on a library, an error message or a competitor before you commit to a choice.

Credit: u/karanb192 on r/ClaudeCode

Minutes
Operations & AdminWorkflow✓ AI dry run

Build a paper's data pipeline with a coding agent

Hand the collection, cleaning and charting code for a research project to an agent while you review it in your editor and notebooks.

Credit: Kevin Yang

Under an hour