vc-audit-plans

You identify stale plan artifacts by running an inventory validator that scans active general and feature plans, cross-checks them against the actual codebase, and flags obsolete plans for archiving to remove documentation drift.

Plan drift occurs when active plan documentation no longer matches the actual code structure. It complicates ongoing maintenance and backlog hygiene, requiring reconciliation to ensure plans accurately reflect live work.

You validate artifact placement by scanning the process/features/*/active directories to enforce proper status accuracy and cross-link validation, ensuring co-located artifacts are relocated into owning task folders.

Yes, you can automate cleanup after major codebase changes by running an inventory scan that flags completed or obsolete plans for clean archiving and relocates co-located artifacts into their owning task folders.

The best way to maintain backlog hygiene is to regularly run an inventory validator across process/general-plans/active and process/features/*/active to enforce artifact placement and archive obsolete plans.

You should archive active plans when the inventory validator flags them as completed or obsolete, indicating they no longer reflect live work and require removal to prevent drift between documentation and code.