lrh-doc-organize

Documentation refactoring is automated by applying predefined audit artifacts to systematically reorganize files into Tutorial, How-to, Reference, or Explanation quadrants. The skill enforces structural compliance through strict constraint-based validation of file movements.

Reorganizing documentation without breaking markdown links requires automated link integrity checks during file movements. The system updates internal markdown references or generates redirect stubs to prevent broken references across the repository.

Cleaning up a cluttered documentation folder is handled through phased refactoring, which implements documentation file moves in small, reviewable, and safe increments to transform a monolithic structure into a navigable hierarchy.

Documentation reorganization requires predefined audit artifacts before starting the first phase. These artifacts define the target Diataxis quadrant mapping and provide the strict constraints used to validate file movements.

Diataxis framework validation checks that documentation content correctly matches its target quadrant during refactoring. It verifies whether a file fits the Tutorial, How-to, Reference, or Explanation category before approving the structural move.

Incremental documentation refactoring can be applied to software project repositories requiring systematic cleanup. It processes documentation folder updates and README modifications in small, reviewable phases to ensure safe structural transitions.