organize-root-folderlisted

# Organize Root Folder Organize a document root into human-readable, upload-ready folders by inventorying files, extracting enough evidence, proposing safe names, and moving files only when the user has approved or clearly asked to proceed. ## Core Rules - Treat the user-provided folder as the job root. If the user says "this folder", use the current workspace root. - Work from absolute paths and stay inside the root unless the user explicitly asks otherwise. - Preserve original files and extensions. Do not overwrite files; append `-v2`, `-v3`, etc. only when a collision exists. - Ignore system/control folders such as `.git`, `.agents`, `.codex`, `.claude`, `.cursor`, and generated extraction trees unless the user asks to organize them. - Keep derived extraction artifacts separate from source documents. - Prefer cautious, evidence-backed labels over clever summaries. - Propose before first-time or uncertain rename/move operations. ## Filename Standard Use this format unless the user gives another convention: ```text YY-MM-DD Name Type Detail.ext ``` Examples: ```text 26-07-06 Patricio Perpetua Driver License Victoria.pdf 26-05-20 Patricio Perpetua NAB Facility Agreement.pdf 26-05-25 Patricio Perpetua Sachi Legal Post Settlement Letter 11 Arylide Walk.pdf 23-09-21 Budget Direct Home and Contents Insurance PDS.pdf ``` Apply these rules: - Start every filename with `YY-MM-DD`. - Use the most relevant document date, not necessarily the first date found. - If no reliable