vc-audit-plans
GitHub用于审计活跃项目计划文件,检查其陈旧性、完成状态及路由真实性。适用于清理计划、对账活跃工作或归档已完成工件的场景,帮助恢复因跳过更新流程导致的漂移。
Trigger Scenarios
Install
npx skills add withkynam/vibecode-pro-max-kit --skill vc-audit-plans -g -y
SKILL.md
Frontmatter
{
"name": "vc-audit-plans",
"layer": "contract",
"metadata": {
"author": "vibecode-pro-max-kit",
"version": "1.0.0"
},
"description": "Audit active project plan files for staleness, completion, and routing truth. Use when cleaning up plans, reconciling active work, or archiving completed artifacts.",
"trigger_keywords": "audit plans, plan inventory, stale plans, active plan count"
}
Audit Plans
Output style: Follow
process/development-protocols/communication-standards.md— answer-first, plain language, no unexplained jargon, TL;DR on long responses.
Use this skill to review active plan artifacts and reconcile them with the current codebase.
This is a maintenance and recovery skill, not an automatic post-task hook.
Optional input: a feature, folder, plan filename, or maintenance scope to prioritize.
Prefer it when:
- UPDATE PROCESS was skipped and active-plan cleanup drift accumulated
- the user wants a periodic active-plan cleanup pass
- multiple active plans need reconciliation after a burst of work
Workflow
- Read
references/audit-plans.mdfor the full audit process. - Run the inventory validator:
node .claude/skills/vc-audit-plans/scripts/validate-plan-inventory.mjs - Inventory plans in
process/general-plans/active/andprocess/features/*/active/. Plans now live inside{slug}_{date}/task subfolders — scan one level deep. Do NOT count_REPORT_,_REF_, or_SPEC_files inside task folders as plans; only_PLAN_files count. For feature-scoped audits, first runfind process/features/{feature}/ -type f | sortfor full artifact visibility. For full audits, runfind process/features/ -type f | sortto see all feature artifacts across all subdirs (active, completed, backlog, references, reports). 3.5. Scan task folder contents (co-located REPORT/REF/SPEC files) alongside each plan. Per task-folder artefact colocation, the correct home for every artefact (plan, spec, reports, references) is INSIDE its{slug}_{date}/task folder; flag any task artefact found in the deprecated siblingreports//references/dirs or any ad-hoc location as mis-located, and recommend moving it into the owning task folder. Match by feature slug, date proximity (7 days), or content reference to the plan filename. - Cross-check each plan against the actual codebase with file existence checks and targeted
rgsearches. - Classify each plan as
Completed,Partially Done,Obsolete,Stale,Active, orReference. - Move only clearly completed or obsolete plans to the appropriate
completed/folder. Usegit mv active/{slug}_{date}/ completed/{slug}_{date}/— move the WHOLE task folder; nocompleted_prefix added. - Ask before deleting anything.
- Re-run the inventory validator after moving or editing plan files.
Output
Return a concise summary table with classification, action taken, and any user decisions needed. Include stale artifact findings (reports/references tied to completed or obsolete plans) with recommended actions.
Version History
- 3bcb2f9 Current 2026-07-05 14:35


