vc:audit-plans

Audit active project plans and classify them for archival.

Updated May 10, 2026
One-click install
npx skills add https://github.com/cryborg1211/quant_trading_telegram_bot --skill vc-audit-plans
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vc:audit-plans
Source: https://github.com/cryborg1211/quant_trading_telegram_bot/tree/main/.agents/skills/vc-audit-plans
Command: npx skills add https://github.com/cryborg1211/quant_trading_telegram_bot --skill vc-audit-plans

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Audit and reconcile active project plans with the codebase to prevent drift, identify completed or obsolete artifacts, and enable clean archival of work.

Core Features & Use Cases

  • Inventory plans in process/general-plans/active and process/features/*/active
  • Classify plans as Completed, Partially Done, Obsolete, Stale, Active, or Reference
  • Recommend moving completed or obsolete plans to corresponding completed folders and highlight artifacts requiring user decisions

Quick Start

Read the inventory and run the validation script to establish the initial classification report.

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 active project plans for staleness and prevent drift from the codebase?

To audit project plans for staleness, you can use an inventory validator script to cross-check active plans against the codebase, classify their status, and identify drift before archiving completed work.

What is the best way to inventory and classify feature plans in a repository?

Inventorying feature plans involves scanning directories like process/features/*/active to classify plans as Completed, Partially Done, Obsolete, Stale, Active, or Reference based on their alignment with the current codebase.

How do I archive completed or obsolete plans and keep my workflow clean?

Archiving completed plans requires moving obsolete artifacts from their active folders to corresponding completed directories, which cleans the workspace and highlights any remaining items requiring user decisions.

Can I use a script to validate if my general plans are still active or stale?

Yes, you can run an inventory validator script against the process/general-plans/active directory to automatically validate whether your general plans are still active, stale, or ready for archival.

When should I reconcile project plans with the codebase to identify obsolete artifacts?

You should reconcile project plans with the codebase when drift is suspected or during regular workflow maintenance, allowing you to identify obsolete artifacts and move them to completed folders for clean archival.