project-tidy

To consolidate scattered AI agent project documentation, run a scan script to generate a tidy plan, then apply it to regroup human docs into docs/ and agent tracking into agentic/. This reduces file sprawl by ensuring consistent placement across the repository.

Rewriting CLAUDE.md and creating AGENTS.md establishes strict routing rules for future AI agents. The scripts automatically generate these files to define where each document type belongs, enforcing consistent repository maintenance and preventing future documentation sprawl.

Yes, you can organize files without modifying source code because the tidy scripts explicitly protect code and system dotfolders. They guarantee no edits or moves occur to application code, .git, or other system directories during the documentation consolidation process.

To detect outdated documentation and app inconsistencies, execute the repository scan script. It identifies obsolete elements and signals mismatches between human documentation and the actual application, ensuring your project records remain accurate and aligned.

Yes, the project tidy automation works specifically with OmegaOS-style repositories. It handles scattered canon references and agentic tracking while preserving the canon itself, ensuring vision, PRD, and feature files remain untouched during consolidation.