Make a messy workspace navigable, nothing moved till you approve.
“I can no longer find anything in this folder. Can someone clean it up without breaking it?”
A proposed naming convention, folder structure, index, and cleanup plan, shown as a plan first so you see every move.
What this skill does
Takes a workspace you have lost the thread of, a repo, a drive, a folder, and proposes a way to make it navigable: a naming convention so files are predictable, a folder structure so things have a home, an index or README so there is a front door, and a cleanup plan for what to archive or merge. It shows you the entire plan as a proposal. Nothing moves, nothing is renamed, nothing is deleted until you approve it, move by move.
Inputs
- Works today with: a file listing, a directory dump, or a description of what is in there. It proposes a convention and a structure from that.
- More powerful connected to a repo or file store: it reads the actual tree, sizes, and dates, so the cleanup plan is grounded in what is really there.
- Sharper with a knowledge base or index: the new README links into the rest of your context, not just this folder.
- Sharper with git history: it can tell what is genuinely stale from what is just quiet.
How it works
- 1Read the current state
Inventory what is actually there: the files, the rough types, the obvious duplicates, the folders that became junk drawers. If the real tree is connected, ground this in dates and sizes. If not, work from your listing, and say so.
- 2Propose a naming convention
One convention, applied consistently, beats five clever ones. Propose a single scheme, lower-kebab-case, date-prefixed logs, type or project prefixes, and show it against your actual filenames so you can see the before and after.
- 3Propose a folder structure
A home for each kind of thing, shallow enough to navigate and deep enough to separate. Show the proposed tree next to the current one. Every file in the plan has exactly one obvious destination.
- 4Draft the index
A README that maps the workspace: what each folder holds, where to put a new file, what the conventions are. The index is what keeps the structure from decaying the week after you build it.
- 5Plan the cleanup, do not perform it
List what to archive, merge, or delete, each with a reason and its current path. This is a plan, presented for approval. Nothing is touched. You approve moves in batches, and a protected path is never in the plan at all.
Output format
WORKSPACE PLAN · /projects (proposal, nothing moved yet)
NAMING CONVENTION (proposed)
lower-kebab-case; logs get a YYYY-MM-DD prefix
before: Final_v2 NOTES.docx after: onboarding-notes.md
STRUCTURE (proposed tree)
/projects
/active (current work)
/reference (facts, specs, playbooks)
/archive (superseded, kept for history)
README.md (the map)
CLEANUP PLAN (approve per batch, nothing runs yet)
ARCHIVE Final_v2 NOTES.docx (superseded, 210 days untouched)
MERGE notes.md + notes-copy.md (near-duplicate; keep notes.md)
KEEP /billing (PROTECTED, excluded from all moves)
DO THIS FIRST
Adopt the naming convention on /active. It makes the rest self-sorting.
(this is a plan. approve moves in batches; nothing has changed.)
Tips
- Nothing is moved, renamed, or deleted without your explicit approval, batch by batch. The default action is to propose, never to execute.
- Every proposed move shows its source path and destination. No file changes location invisibly.
- Nothing is ever deleted outright when it can be archived instead. Destructive moves are the last resort and always named as such.
- Protected paths are excluded from the plan entirely. What you mark off-limits is never proposed for a move.
Turn a cold start into a warm one with one doc.
A single pack that tells a new session or teammate what the project is, where things live, what's decided, and the next move.
Capture the session context so you can resume it cold.
An end-of-session brief: progress, decisions, unfinished items with next steps, and the fragile details, then it asks whether to save.