vc-audit-plans

Audit active project plan files for staleness, completion, and codebase alignment.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/HyuseCS/project-c --skill vc-audit-plans-hyusecs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vc-audit-plans
Source: https://github.com/HyuseCS/project-c/tree/main/.claude/skills/vc-audit-plans
Command: npx skills add https://github.com/HyuseCS/project-c --skill vc-audit-plans-hyusecs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Active plan folders accumulate stale, completed, or obsolete plan files over time, making it hard to know which plans reflect real work. This Skill reconciles plan artifacts against the actual codebase so the active plan inventory stays accurate. ## Core Features & Use Cases - Plan Inventory Validation: Runs a deterministic Node.js validator that scans process/general-plans/ and process/features/ for naming, freshness, and structure drift. - Codebase Cross-Checking: Verifies each plan's claimed files and features with glob and grep checks, then classifies plans as Completed, Partially Done, Obsolete, Stale, Active, or Reference. - Stale Artifact Cleanup: Detects co-located REPORT/REF/SPEC artifacts tied to finished plans and moves whole task folders to completed/ via git mv. - Use Case: After a burst of feature work where the update process was skipped, run this Skill to archive finished plans, flag stale ones, and produce a summary table of actions taken. ## Quick Start Ask the AI to audit the active plans in process/general-plans and process/features, classify each one against the codebase, and archive anything completed or obsolete.

Frequently Asked Questions about vc-audit-plans

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit stale project plan files?

Run the plan inventory validator script to scan active plan directories, then cross-check each plan against the codebase with file existence checks and grep searches. Classify each plan as Completed, Partially Done, Obsolete, Stale, Active, or Reference, and archive finished ones.

How to archive completed plans without losing task artifacts?

Move the entire task folder with git mv from the active directory to the sibling completed directory, keeping the folder name unchanged. Co-located REPORT, REF, and SPEC files move together with the plan since artifacts live inside the task folder.

When should I run a plan audit?

Run it after completing a major feature, after an architectural pivot, when the update process was skipped and drift accumulated, or as monthly maintenance. It is also recommended when total active plans across general and feature directories exceed ten.

Does the plan audit delete files automatically?

No, the audit never deletes anything without asking. It only moves clearly completed or obsolete plans to completed folders, and stale plans are presented to the user with a recommendation to keep, archive, or delete.

What does the plan inventory validator check?

The validator checks that plan files are date-stamped, contain PLAN in the filename, include phase completion rules and verification sections, and flags duplicate basenames and high active plan counts. Default mode reports warnings; the --strict flag turns warnings into failures.