vc-audit-plans
vc-audit-plans scans your active plan inventory to flag stale, completed, or obsolete artifacts and recommend archival or cleanup actions. It validates plan status against your codebase, detects misplaced task artifacts, and surfaces a summary table with classifications and next steps. Use it for periodic maintenance, post-burst reconciliation, or when plan cleanup has drifted.
vc-audit-plans reviews active project plan files to identify staleness, completion status, and misplaced artifacts.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-06-21
vc-audit-plans reviews active project plan files to identify staleness, completion status, and misplaced artifacts. vc-audit-plans scans your active plan inventory to flag stale, completed, or obsolete artifacts and recommend archival or cleanup actions. It validates plan status against your codebase, detects misplaced task artifacts, and surfaces a summary table with classifications and next steps. Use it for periodic maintenance, post-burst reconciliation, or when plan cleanup has drifted.
Use it when
- vc-audit-plans audits project plans for staleness by comparing plan file timestamps and content against your current codebase state.
- Yes.
Verify before relying
Read SKILL.md below before installing (18 files). Open directory: indexed for reading, not audited.
Install
withkynam/vibecode-pro-max-kit/vc-audit-plans · repository language: JavaScript
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
What does vc-audit-plans do?
vc-audit-plans scans your active plan inventory to flag stale, completed, or obsolete artifacts and recommend archival or cleanup actions. It validates plan status against your codebase, detects misplaced task artifacts, and surfaces a summary table with classifications and next steps.
How do I audit project plans for staleness?
vc-audit-plans audits project plans for staleness by comparing plan file timestamps and content against your current codebase state. It identifies plans that have drifted from reality, marks those that are completed, and flags obsolete artifacts so you can decide whether to archive or update them.
Can vc-audit-plans find stale plan files in my codebase?
Yes. vc-audit-plans finds stale plan files in your codebase by scanning your active plan inventory and cross-referencing against current development work. It surfaces plans that are no longer relevant, haven't been updated, or whose tasks have already been completed.
When should I use vc-audit-plans for cleanup?
Use vc-audit-plans for periodic maintenance after development bursts, post-project reconciliation, or whenever plan cleanup has drifted. It helps you organize your plan inventory, archive completed or obsolete plans to proper folders, and locate misplaced task artifacts for consolidation.
What output does vc-audit-plans provide?
vc-audit-plans provides a summary table classifying each plan file with its status (stale, completed, active, or misplaced), reconciliation notes, and recommended next steps. This lets you quickly decide which plans to archive, update, or consolidate.
How does vc-audit-plans reconcile plan artifacts with code?
vc-audit-plans reconciles plan artifacts with code by validating that active plans align with your current codebase state. It detects drift between documented tasks and actual implementation, identifies orphaned plan documents, and recommends consolidation of duplicates or misplaced references.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
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: ```bash node
(truncated - see the full file via the links below)
File tree — 15 files
.claude/skills/vc-audit-plans/SKILL.md
.claude/skills/vc-audit-plans/references/audit-plans.md
.claude/skills/vc-audit-plans/scripts/eval-coverage-known-gaps.json
.claude/skills/vc-audit-plans/scripts/fixtures/validate-backlog-notes/fail/malformed_NOTE.md
.claude/skills/vc-audit-plans/scripts/fixtures/validate-backlog-notes/pass/d2-fix-deferred_NOTE.md
.claude/skills/vc-audit-plans/scripts/fixtures/validate-phase-plan-completeness/fail.md
.claude/skills/vc-audit-plans/scripts/fixtures/validate-phase-plan-completeness/pass.md
.claude/skills/vc-audit-plans/scripts/fixtures/validate-phase-reports/fail/umbrella.md
.claude/skills/vc-audit-plans/scripts/fixtures/validate-phase-reports/pass/phase-01_REPORT.md
.claude/skills/vc-audit-plans/scripts/fixtures/validate-phase-reports/pass/umbrella.md
.claude/skills/vc-audit-plans/scripts/fixtures/validate-umbrella-state/fail.md
.claude/skills/vc-audit-plans/scripts/fixtures/validate-umbrella-state/pass.md
.claude/skills/vc-audit-plans/scripts/validate-backlog-notes.mjs
.claude/skills/vc-audit-plans/scripts/validate-eval-coverage.mjs
.claude/skills/vc-audit-plans/scripts/validate-phase-plan-completeness.mjs
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Audit active plan files for staleness and completion status”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
vc-generate-plan transforms feature ideas and product requirements into structured implementation plan artifacts saved to your repo. It handles both straightforward single-phase work and large multi-phase programs, organizing plans with required sections for touchpoints, contracts, blast radius, and verification gates. The skill enforces answer-first communication and ensures execution handoff clarity through explicit resume notes.
vc-context-discovery is the canonical context-loading entry point for every agent session. It discovers and surfaces all nested files under process folders, extracts frontmatter metadata, and routes context by domain using keyword matching. Use the auto-discovery script or keyword-first routing to load exactly the docs your task needs.
vc-generate-spec turns research findings and user intent into a reviewable requirements document written for stakeholders, not engineers. It captures what users want and why before any implementation approach is chosen, serving as the authoritative bridge between discovery and planning. The skill enforces structured sections—from user stories through acceptance criteria—ensuring specs remain focused on observable outcomes and user-facing behavior.
vc-setup guides you through configuring an agent development harness tailored to your project. It detects your tech stack, asks clarifying questions to understand your codebase, then scaffolds the necessary directory structure and context files—always requesting approval before making changes. Works equally well on new projects and those with existing configurations.
This skill scaffolds multi-phase programs by generating an umbrella orchestration plan, Program Goal Charter, per-phase plan stubs, and a session-goal block. It enforces a 7-step inner loop (Research → Innovate → Plan-Supplement → PVL → Execute → EVL → Update-Process) with validation gates between phases, ensuring each phase is ready before the next begins. Use it when work naturally breaks into 3+ dependent phases across multiple packages or services.
vc-audit-vc checks that your agent harness layer stays internally consistent and correctly wired across Claude, Codex, documentation, and protocol files. Run validators to catch agent definition drift, skill discovery mismatches, guide sync failures, and wiring breaks—then patch and re-run until all checks pass.
More skills vc-audit-context (MIT)