vc-audit-plans

Audit active project plan files for staleness, completion, and routing accuracy.

2|Updated Sep 15, 2025
One-click install
npx skills add https://github.com/marsley01/Marsley-Portfolio-Web --skill vc-audit-plans-marsley01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vc-audit-plans
Source: https://github.com/marsley01/Marsley-Portfolio-Web/tree/main/.agents/skills/vc-audit-plans
Command: npx skills add https://github.com/marsley01/Marsley-Portfolio-Web --skill vc-audit-plans-marsley01

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 planning artifacts over time, making it hard to know which plans reflect real work. This Skill reconciles plan files against the actual codebase so your planning directories stay truthful. ## Core Features & Use Cases - Plan Inventory Validation: Runs a deterministic Node.js validator that counts active and completed plans, flags naming drift, duplicate basenames, and missing verification sections. - Codebase Cross-Referencing: Verifies each plan against the real code with file existence checks and targeted grep searches, then classifies plans as Completed, Partially Done, Obsolete, Stale, Active, or Reference. - Stale Artifact Detection: Finds co-located report, reference, and spec files tied to completed or obsolete plans and recommends archiving or relocation into task folders. - Use Case: After a burst of feature work where cleanup was skipped, run this Skill to archive finished task folders with git mv, flag stale plans for user decision, and produce a summary table of actions taken. ## Quick Start Ask the assistant to audit the active plans in process/general-plans/active and process/features for staleness and archive anything completed.

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 in a repository?

Run the plan inventory validator script to count active and completed plans, then cross-check each plan against the codebase with file existence checks and grep searches. Classify each plan and move completed or obsolete task folders to the completed directory with git mv.

How to classify project plans as completed or obsolete?

Verify that all phases in the plan exist in the code by globbing mentioned files and grepping key identifiers like function names and routes. Plans fully implemented are Completed; plans superseded by architectural changes are Obsolete and get an [OBSOLETE] prefix on the plan file.

When should I run a plan cleanup audit?

Run it after completing a major feature, after an architectural pivot, when active plan count exceeds ten, or as monthly maintenance. It is a manual maintenance skill, not an automatic post-task hook.

Does the plan audit delete files automatically?

No. The audit only moves clearly completed or obsolete task folders to the completed directory using git mv, and it asks before deleting anything. Stale plans are flagged for user decision rather than removed.

What are the limitations of automated plan staleness detection?

The validator detects naming, freshness, and structure drift but cannot judge whether a plan's intent still matches product direction. Classification of partially done or stale plans still requires human review of the summary table before action.