documentation-project-scan

To inventory documentation artifacts and find gaps, scan the repository root to classify files across Documentation/, Docs/, and docs/ folders, generating an actionable backlog of missing or orphaned items.

Identify duplicate and orphaned files by scanning folder patterns to classify artifacts as canonical, superseded, orphan, or duplicated, surfacing conflicts when multiple sources compete for the canonical destination.

A documentation backlog is an actionable list of gaps and improvements generated by scanning and classifying artifacts across legacy Docs/docs and canonical Documentation/ root folders, treating the root as the primary source until consolidation.

Yes, you can detect documentation conflicts during consolidation by producing a conflict report that identifies multiple sources competing for the same canonical destination within the Documentation/ ecosystem.

The best way to scan legacy folders without deletion is to inventory and classify items with status tags, treating Documentation/ as canonical while including legacy Docs/docs in the root until full consolidation is complete.

Files appear as orphaned instead of canonical when naming and folder pattern analysis determines they do not belong to the established Documentation/ root structure, classifying them separately for backlog resolution.