---
name: directory-cleanup-and-inventory
description: "Full recursive scan, sidecars, categorization, folder recommendations, master report — no moves/deletes. Use when a person asks to install or apply \"Directory Cleanup & Inventory\" (FTR-25) in a project, or when working in a project that has it installed."
---

# Directory Cleanup & Inventory (FTR-25, version 1.0)

> Generated from library record FTR-25 version 1.0, publish 20261102a. Review status: unreviewed. The complete specification is in references/spec.md and is the authority; this file is the operating procedure drawn from it.

## What this does

Full recursive scan, sidecars, categorization, folder recommendations, master report — no moves/deletes

## When to use this skill

- A person asks to install, apply or update "Directory Cleanup & Inventory" (FTR-25) in a project.
- A project's agent instructions list directory-cleanup-and-inventory as installed and the task touches what it covers.
- No other feature is required first.
- Works better with, if installed: FTR-04 (skill agent-role-and-project-identity), FTR-06 (skill file-storage-and-transfer).

## Install procedure

Steps run in order. Assess comes first, every question in the Ask step is answered by the person before anything is written, and every write merges additively into the existing project files (read the file first, update an existing section in place, never overwrite).

### Assess first
- Check whether a canonical project root is already established (from File Storage & Transfer Rules / Folder Structure, if installed, or from existing `admin\AGENT_INSTRUCTIONS.md`). If so, that's PROJECT ROOT — no need to ask again.
- Check whether an output/drop folder convention is already established (`#drop\` if Folder Structure is installed). If so, that's DROP FOLDER.
- Check whether project name or context is already known (from Agent Role & Project Identity, if installed). If so, use it for PROJECT NAME OR CONTEXT — this only helps with categorization and can be left blank either way.
- Note the likely scale before starting: a full recursive scan with sidecars for every file can mean dozens or hundreds of outputs. If Cowork is available and the directory is large, this is a good candidate to hand off there rather than run entirely in-chat.

### Ask, only if needed
- If no canonical project root is established anywhere: ask directly — "What's the root folder you want scanned?"
- If no drop/output folder convention exists: ask where the master report should be saved (default: the established `#drop\` if one exists).
- Project name or context: optional. If not already known and the person doesn't offer it, proceed without it — categorization still works from content alone.

### Write

The full Write payload is in references/write-payload.md. It is applied exactly as written, with the merge rule above.

### Confirm
Confirm: Directory Cleanup & Inventory is enabled — say "run a directory cleanup," "audit this project's files," or "inventory this directory" any time to trigger the full six-phase process (scan, relationship detection, sidecars, categorization, folder recommendations, master report) against [PROJECT ROOT], with the report saved to [DROP FOLDER]. Nothing gets moved or deleted — only reported and recommended, for a human to review and approve. For large directories, this is usually better handed to Cowork than run entirely in one chat turn. Want to install another, or is that everything for now?

## Files in this skill

- references/spec.md: the complete specification, unabridged.
- references/write-payload.md: the Write step on its own.